My Oracle Support Banner

OUD 12c: Stopping Directory Instance Takes A Long Time After Upgrade To 12c (Doc ID 2349731.1)

Last updated on SEPTEMBER 12, 2019

Applies to:

Oracle Unified Directory - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

After OUD upgrade from 11g to 12c, stopping an instance takes about 60s.
After about 10s there is the message "The Directory Server is now stopped" but instance and stop command take another ~50s to actually stop.

Please find below an example from the tests

 

$ORACLE_INSTANCE/OUD/bin : date ; time ./stop-ds ; date
Tue Sep 19 13:38:26 CEST 2017
Stopping Server...

[19/Sep/2017:13:38:36 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=ercl,cn=Workflow elements,cn=config is now taken offline
[19/Sep/2017:13:38:36 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=userRoot,cn=Workflow elements,cn=config is now taken offline
[19/Sep/2017:13:38:36 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=virtualAcis,cn=Workflow Elements,cn=config is now taken offline
[19/Sep/2017:13:38:36 +0200] category=CORE severity=NOTICE msgID=458955 msg=The Directory Server is now stopped

real 1m1.006s
user 0m2.873s
sys 0m0.621s
Tue Sep 19 13:39:28 CEST 2017

oud 31024 30909 2 13:48 pts/0 00:00:01 /usr/java/jdk1.8.0_144/jre/bin/java -client org.opends.server.tools.WaitForFileDelete --targetFile $ORACLE_INSTANCE/OUD/logs/server.pid --logFile $ORACLE_INSTANCE/OUD/logs/errors


A 60+ seconds is considered not acceptable for a stopping time of an instance.

 

Changes

The issue is encountered only when the replication is enabled

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.