5 Issues Affecting Microsoft Windows for Oracle Database 21c
These topics contain last-minute features and changes for Microsoft Windows for Oracle Database 21c.
- Product Support for Microsoft Windows
The following product or feature is supported for Oracle Database 21c. - Installation, Configuration, and Upgrade Issues for Microsoft Windows
These topics describe information about issues that affect Oracle Database installation, configuration, and upgrade.
Product Support for Microsoft Windows
The following product or feature is supported for Oracle Database 21c.
Multithreaded Oracle Database Model
The multithreaded Oracle Database model is supported.
Installation, Configuration, and Upgrade Issues for Microsoft Windows
These topics describe information about issues that affect Oracle Database installation, configuration, and upgrade.
Bug 31618110
tfactl
help with invalid parameters display the results but did not
return any invalid argument error.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 31623788
Oracle Autonomous Health Framework (AHF) and Trace File Analyzer (TFA)
tfactl
print configuration does not update the configuration
value in all nodes.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 31624542
tfactl
access add -group is not supported, but the document
contains details to add the user group.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 31654946
tfactl diagcollect -collectdir -help
command starts collecting
reports instead of displaying the help.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 31660201
tfactl
does not uninstall Trace File Analyzer (TFA) in all the
nodes, it uninstalls only in the local node.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 31666299
tfactl analyze
command does not give results and returns errors in
the log.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 32987272
Oracle Trace File Analyzer (TFA) was not installed, but
validateenv
shows "TFA Successfully installed".
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 33030281
When you upgrade Grid Infrastructure Management Repository (GIMR) home from a lower home version to Oracle Database 21c, it fails with the following error message:
INS-20801.
If the user list in ACL of the mgmtdb resource is empty.
Workaround
Modify the ACL attribute of the mgmtdb
resource using the
crsctl
command. Add the owner of the
mgmtdb
resource to the user list in the ACL of
mgmtdb
. When the user list is updated in ACL of the
mgmtdb
resource, upgrade GIMR.
crsctl getperm res ora.mgmtdb
Name: ora.mgmtdb
owner:nt authority\system:rwx,pgrp::r-,other::r--,group:ORA_INSTALL:r-x,user:nt authority\system:rwx
If the user list is empty in the ACL retrieved for the
mgmtdb
resource, then add the owner of the mgmtdb
resource to the user list in ACL.
Run this command to modify or add the user list in the ACL command:
crsctl setperm resource ora.mgmtdb -u "user:nt authority\system:rwx" -unsupported
Bug 33169497
tfactl
analyze command does not work and returns an error.
Workaround
Download the latest Oracle Autonomous Health Framework (AHF) from My Oracle Support note 2550798.1 and upgrade Oracle Autonomous Health Framework (AHF).
Bug 33212356
[INS-32700] The gold image creation failed.
Workaround
Set the TEMP environment variable to c:\
or c:\Temp
before performing the -createGoldImage
operation.
Bug 33279556
On a pure IPv6 Windows environment, the IPv6 addresses fail to resolve during the SCAN verification check due to a known issue.
Workaround
Apply a one off patch explicitly on such an IPv6 environment to ensure that the Java code attempting to resolve the IPv6 addresses uses the correct network property when you start the Java Virtual Machine (JVM) by running the prerequisite checks.
Bug 33382160
The edition column in the table registry$database
incorrectly displays as Oracle Database Enterprise Edition for an Oracle Database 21c
Express Edition (XE). This is not a functional issue but rather a display problem
only.
SQL> select edition from registry$database;
EDITION
------------------------------
EE
The edition is displayed as EE instead of XE. However, the edition column in
the table registry$
correctly displays as XE.
SQL> select edition from registry$;
EDITION
------------------------------
XE
Workaround
Manually update the edition column value in
registry$database
.
SQL> update registry$database set edition='XE';
1 row updated.
SQL> commit;
Commit complete.
SQL> select edition from registry$database;
EDITION
------------------------------
XE
Bug 33394156
Transparent Data Encryption (TDE) is not supported if you install through a Windows virtual account.
Workaround
This issue is fixed in Oracle Database 19c, release update (RU) 19.19 or later. You can request for a one-off patch.
Bug 33605836
Database token authentication fails in Windows for Oracle Client Libraries with the following error:
ORA-01017: Invalid username/password; Logon denied
.
Workaround
- Specify the parameters
TOKEN_AUTH, TOKEN_LOCATION, SSL_SERVER_DN_MATCH, PASSWORD_AUTH, OCI_IAM_URL, OCI_TENANCY, OCI_COMPARTMENT, OCI_DATABASE
in asqlnet.ora
file instead of atnsnames.ora
file. - Set the TZ environment variable to
the Greenwich Mean Time (GMT) as follows:
set TZ=GMT
- Specify the
TOKEN_LOCATION
for the IAM Proof Of Possession (POP) token in asqlnet.ora
file. Do not rely on the default token location.
Related Topics