Last updated on JULY 17, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
You have a LPAR running ERP9.0 Environment (Say LPAR1 and LPAR2 both are logic/batch server too). One of the servers is your security server(LPAR2).
When you Deploy packages for any Environment, you select each LPAR one by one and then Deploy (keep checking that no reports are running on those Enterprise server). Even if reports are running on LPAR2 you never faced issue deploying on LPAR1.
Now suddenly while deploying update package on LPAR1 you saw reports running on LPAR2 are getting into MUTEX state. And R98825D report came up with "Error:34 : LPAR2 - Failed to lock/unlock server". While when there are no reports running on LPAR2 you have no problem deploying package on LPAR1.
Why the Package Deployment failed on LPAR1 as it Failed to get locks on server LPAR2 ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms