Welcome to my blog

· I have extensively worked on the following technologies/Implementation projects

· Oracle EBS R12, 11.5.10.2, 11.5.9

o Oracle Applications DBA (AD)

o Oracle Financials

o Order Management

· Oracle Retail Suite V12, V13

o Retail Merchandizing system RMS

o Invoice matching ReIM

o Retail Integration Bus RIB

o Retail price manager RPM

o Store Inventory Manager SIM

o Retail Demand Forecasting RDF

o Retail data warehousing RDW

o Oracle Internet Directory OID

· Oracle SOA Suite

o BPEL process manager

o Enterprise Service Bus

· Oracle Hyperion Suite

o Shared services OSS

o Workspace

o Planning

o Essbase

o Enterprise performance management EPM

o Financial reporting, Web analysis

· Enterprise Batch Scheduler Uc4 Appworx

· Oracle Business intelligence Suite

o Answers

o Interactive dashboards

o BI publisher


· I am responsible for several Implementations that use the following Oracle middleware products

· Oracle Weblogic Fusion Middleware web application

· Oracle Weblogic Forms and Reports Server

· Oracle Weblogic SOA Suite

o BPEL process manager

o Oracle Service Bus

o Oracle B2B server

· Oracle Business intelligence Suite

o BI publisher

o Oracle Discoverer 10g

· Enterprise Batch Scheduler Active Batch

· Oracle Internet Directory OID

· Oracle Connection Manager

· Several Custom applications deployed in Oracle 10g Application servers



My interest is to make this an arena to share my experiences.

Wednesday, September 2, 2015

OID11g DIP migrating ldap-server to a new-host



Reconfiguring AD (Domain controller)

AD – OID synchronization is setup as explained in the document  : http://docs.oracle.com/cd/E14571_01/admin.1111/e10031/odip_adm_sync.htm#OIMIG1934
For any reconfiguration relating to AD such as demoting/renaming etc, the configuration has to be updated in the following procedure :  

  • Identify the “HighestCommittedUSN” of the  domain controller in use by the enabled synchronization profile. (different replicating domain controllers )









 ldapsearch –h –p 389 –D –w “ –b “” –s base “objectclass=*” highestCommittedUSN
highestCommittedUSN=3537140
  •     determine the “HighestCommittedUSN” of the  domain controller to which it should be reconfigured to
ldapsearch –h –p 389 –D –w “ –b “” –s base “objectclass=*” highestCommittedUSN
 highestCommittedUSN=31243468
  • Disable the current synchronization profile
  •    Edit the synchronization profile to connect to the appropriate domain controller ( in this example )
  •     Reset the last applied change number
- Go to the Advanced Tab
- In the section "Additional Configuration Parameters" edit 'Skip Error To Sync Next Change' and set to true
- Check "Edit and Persist" box, then Change "Last Change Number" value to a value less than highestCommittedUSN of the new DC (in this case 31243468)

Save the change
  •   Enable the synchronization profile
  • Monitor synchronization completes without errors