Uid Used for Omsuser Isn’t Unique Across All Pods in BRM CNE
(Doc ID 2924445.1)
Last updated on FEBRUARY 01, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.5.0 and laterInformation in this document applies to any platform.
Goal
The user ID (uid) used for 'omsuser' is not the same across all pods in BRM CNE.
A few pods have uid "1000" for omsuser, while a few others have it as "1001".
Pods for which uid=1001(omsuser) - cm, dmo, dm_aq, dm_ifw_sync, pje
Pods for which uid=1000(omsuser) - batch_controller, realtime-pipe, rel-daemon
Pods for which uid=1000(oracle) - billingcare, pdc-bre-deployment, pdc-rre-deployment, pdc-domain-adminserver
Pods for which uid=1000(omsuser) - batch_controller, realtime-pipe, rel-daemon
Pods for which uid=1000(oracle) - billingcare, pdc-bre-deployment, pdc-rre-deployment, pdc-domain-adminserver
This inconsistency results in a need to manually give permissions to the files being run within specific pods to access them.
Is there a specific reason for using different uid for the same user on different pods? Having the same uid in all pods will avoid permissions-related issues.
Solution
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
| Goal |
| Solution |
| References |