OUD - Upgrading From 22.214.171.124.0 To 126.96.36.199.0 Throws Error On ./start-ds --upgrade
(Doc ID 1635136.1)
Last updated on NOVEMBER 07, 2019
Applies to:Oracle Unified Directory - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
1) When upgrading from 184.108.40.206.0 to 220.127.116.11.0, the following error occurred following the upgrade and running start-ds --upgrade.
[12/Mar/2014:12:08:41 -0700] category=CORE severity=NOTICE msgID=458886 msg=Oracle Unified Directory 18.104.22.168.0 (build 20131115153045Z, R1311150604) starting up
[12/Mar/2014:12:08:42 -0700] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerShutdown, alert ID 458893): The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class org.opends.server.core.DirectoryServer and the reason provided for the shutdown was An error occurred while trying to start the Directory Server: An objectclass read from schema configuration file 06-compat.ldif could not be parsed: The definition for the objectclass with OID 2.16.840.1.113722.214.171.124 declared a superior objectclass with an OID of tombstone. No objectclass with this OID exists in the server schema The definition for the objectclass with OID 2.16.840.1.1137126.96.36.199 declared a superior objectclass with an OID of tombstone. No objectclass with this OID exists in the server schema
[12/Mar/2014:12:08:43 -0700] category=CORE severity=NOTICE msgID=458955 msg=The Directory Server is now stopped
2) All subsequent attempts to run ./start-ds --upgrade produced the following Null pointer error:
Exception in thread "main" java.lang.NullPointerException at java.lang.Integer.decode(Integer.java:927)
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