OSM SDK Directory Not Updated After Applying Patch
(Doc ID 1274204.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Communications Order and Service Management - Version 7.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 31-May-2013***
If you upgrade OSM, for instance, from version 7.0.0 b234 to version 7.0.1 b589 and use the same OSM Installation Directory, then the SDK and Database directory will not be updated with a new version of SDK and Database utilities.
The SDK must generally be upgraded with each upgrade of OSM. Please see the install Guide or the Patch Readme which is applicable to your upgrade.
You will see an error similar to the following in your NOHUP file:
The automation module[osm_xxx-yyy_1_0_0.ear] was built with OSM SDK
version[18.104.22.1684], however the OSM core application deployed in this server is version[22.214.171.1246].
Please rebuild and redeploy the automation module with the OSM SDK that matches the OSM core application.
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