Installation, Configuration, and Upgrade Issues for Microsoft Windows
These topics describe information about issues that affect Oracle Database installation, configuration, and upgrade.
Bug 20918120
Installing Oracle Real Application Clusters Database home with a Group Managed Services Account (gMSA) as the Oracle home user, fails with the following error if the gMSA name consists of more than 15 characters (including the domain name):
[INS-32101] Specified Oracle Home user does not exist
Workaround:
Use a gMSA name (including the domain name) that consists of less than 15 characters.
Bug 21325903
The deinstallation operation fails to remove Oracle home and displays file in use errors because the services and processes running from Oracle home are not removed completely before Oracle home removal.
Workaround:
Manually remove the Oracle home.
Bug 29426320
ORA-28575 Unable to open RPC connection to external procedure agentWorkaround#1
Restart the Oracle listener service and the OracleClrAgent service using a non-virtual user account.
Workaround#2
Reinstall Oracle Database 19c and select a non-virtual user account.
Workaround#3
If you require a virtual user account, then set
sqlnet.authentication_services to NONE in
SQLNET.ORA.
Bug 38057837
When installing a 32-bit Oracle Database Client in the same Oracle base directory as
an existing 64-bit Oracle Database Client, the installer revokes permissions for
non-Administrator users on the 64-bit client home. Consequently, non-Administrator users
may receive Access is denied errors when attempting to run executables,
applications, or graphical user interface (GUI) tools associated with the 64-bit client
installation.
Workaround:
To avoid permission conflicts, install 32-bit and 64-bit Oracle Database Clients in separate Oracle base directories.