When the pre-req checks run it is coming up with this error:
Users With Same UID - This test checks that multiple users do not exist with user id as "0".
List of errors: :
PRVF-4132 : Multiple users "root,root" with UID "0" exist on "tspsprodap02". - Cause: More than one user is
found to have the same user ID as specified in the message. - Action: Ensure that no two users share the
I am pretty sure that this cannot happen, but I checked /etc/passwd and there is no more then one entry with a UID of 0.
The SA who set it up is having a look before we go that route. But there certainly are not two accounts with a uid of 0 in the /etc/paswd file.
We were missing a couple of RPM's as well, now that they are on I'll have another go next week.
- any duplicated UID entries (other than '0') in both the password and shadow password file
- any issues with GID 0, and whether the Oracle user is allowed GID 0
- the state of SELinux ... I've found 'interesting' side effects when enabled so I currently only use permissive.
Well my SR with Oracle made me none the wiser about what's being done. The analyst refused to answer the question about what the installer is actually doing.
Never mind, not a big deal, just ignore this check.
2 years on from this I am seeing the same issue with server install. In my case I know that there are duplicate uid 0 users. We intentionally create named root users e.g adm_jblogs which are uid 0. In this way we can give root access to a number of engineers without having to share the root password which the auditors are so against.
(Basically if an engineer needs to be restricted from access e.g when leaving we disable his account only)
Also in this way we can see who is logged in at any one time instead of seeing anoymous "root" session.
Anyway enough of background ...... What is the actual issue with the installer seeing these duplicate uid 0 acccounts?
Is there way of disabling this check.
Worse is when you try and run any of the de-install scripts they will claim you are not root because your username is not root.