Data Preserving Reprovisioning: Multi-User Access
Understand FAQs on multi-user access in the Data Preserving Reprovisioning process.
Is it possible to convert a non-multi user access environment to a multi-user access deployment during Data Preserving Reprovisioning?
No. During Data Preserving Reprovisioning process, the Oracle Database Appliance deployment is restored to exactly the same state and configuration as was the case prior to the detach process. Hence, a non-multi user access environment continues to function in a similar manner even after the Data Preserving Reprovisioning process is complete. Similarly, a multi user access-enabled environment is restored with the same configuration.
There is an error about User ID (UID) or Group ID (GID) conflict while performing restore node for Oracle Grid Infrastructure. How do I resolve this issue?
In a multi user access-enabled environment, all users must be restored with the same UID/GID as the ones prior to detach. Hence, post reimage of the system, if there are any conflicts, the restoration of Oracle Grid Infrastructure may fail. Manually resolve this conflict and then run the command again.
Do I need to remember old passwords for users to run ODACLI commands after the Data Preserving Re-provisioning process?
For system users such as odaadmin, oracle and
grid, you are prompted to enter a new password of your choice. These are
preactivated accounts, and you can log into the appliance with the new password, either
through ODACLI commands or through the BUI. For custom users, Oracle Database Appliance
accounts are created as locked-out accounts. You can connect to the appliance using SSH with
your previous password. When you run the first ODACLI command, you are prompted to unlock
your account. After you unlock your account and reset to the new password in the process,
you can log into the BUI or run ODACLI commands using the new password.