Known Issues with Oracle Database Appliance in This Release

The following are known issues deploying, updating, and managing Oracle Database Appliance in this release.

Known Issues When Patching Oracle Database Appliance

Understand the known issues when patching Oracle Database Appliance to this release.

Error in patching a database home or database

When patching a database home or database, an error is encountered.

Problem Description

Database home or database, the patch may fail at datapatch prerequisite stage with error code PRGO-1069.

Failure Message

Error: prereq checks failed! UJS is running, wait for a few minutes and re-run datapatch Prereq check failed, exiting without installing any patches. Please refer to Knowledge Article KA1374 and/or the invocation log /u01/app/odaorabase/oracle/cfgtoollogs/sqlpatch/sqlpatch_79765_2026_10_09_00_54_06/sqlpatch_invocation.log for information on how to resolve the above errors.

Command Details

# odacli update-dbhome
# odacli update-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Resume the patching operation on the failed-to-patch database using the odacli update-database command.

Bug Number

This issue is tracked with Oracle bug 40139617.

Error in upgrading a database

When upgrading a database, an error is encountered.

Problem Description

CVU warnings terminated the prepatch operation for database upgrade.

Failure Message

OperationAPIException: PRGT-509 : Pre-upgrade verification through Configuration Verification Utility reported one or more errors.
PRVF-5610 : The file "/etc/resolv.conf" on the following nodes have more than one 'search' entry: scaoda11ha02c3n1,scaoda11ha02c3n2.

PRVH-0687 : AutoUpgrade check "HIDDEN_PARAMS" completed with a warning.
The database contains the following initialization parameters whose name begins with an underscore:  _db_writer_coalesce_area_size _disable_interface_checking _enable_NUMA_support
PRVH-0687 : AutoUpgrade check "POST_DISABLE_BCT_UPG" completed with a warning.
Block Change Tracking was previously enabled in the lower version Oracle home.
Error Message Not Available
PRVH-0687 : AutoUpgrade check "PRE_FIXED_OBJECTS" completed with a warning.
None of the fixed object tables have had stats collected.
PRVH-0687 : AutoUpgrade check "JAVAVM_JIT_MEMORY" completed with a warning.
The JAVAVM JIT requires 3.75M bytes minimum POSIX shared memory for upgrade or 48M bytes minimum if JAVA is to be used in an application or trigger.
PRVH-0687 : AutoUpgrade check "POST_RECOMPILE" completed with a warning.
There are 0 invalid objects in Oracle-maintained schemas and 0 invalid objects in application schemas after upgrade.
PRVH-0687 : AutoUpgrade check "UNIAUD_RECORDS_IN_FILE" completed with a warning.
There are Unified Audit records present in the OS spillover audit files.
PRVH-0687 : AutoUpgrade check "POST_DICTIONARY" completed with a warning.
Oracle recommends gathering dictionary statistics after upgrade.
PRVH-0687 : AutoUpgrade check "PARAMETER_MIN_VAL" completed with a warning.

PRVH-0687 : AutoUpgrade check "TIMESTAMP_MISMATCH" completed with a warning.
There are objects whose timestamp are mismatched with its parent objects.
PRVH-0687 : AutoUpgrade check "PARAM_VALUES_IN_MEM_ONLY" completed with a warning.
Found at least one parameter with a value in memory that is not in the database's initialization parameter file.
PRVH-0687 : AutoUpgrade check "POST_FIXED_OBJECTS" completed with a warning.
Oracle recommends gathering fixed object statistics after upgrade. This recommendation is given for all preupgrade runs.
PRVH-0686 : AutoUpgrade check "PARAMETER_OBSOLETE" failed.

Command Details

# odacli create-prepatchreport --upgrade-db

Hardware Models

All Oracle Database Appliance hardware models with 26ai DB system

Workaround

Ignore the CVU precheck warnings(PRVH-0686/PRVH-0687/resolv.conf) and proceed further with DB upgrade using the odacli upgrade-database -f command.

Bug Number

This issue is tracked with Oracle bug 39956350.

Error in creating database on DB system on multi-user access enabled system

When creating a database on a multi-user access enabled DB system, an error is encountered.

Problem Description

Creation of database as the odaadmin user on a multi-user access enabled DB system with enableRoleSeparation set to false during provisioning of the DB system may fail.

Failure Message

When you run the odacli create-database command, the following error message may be displayed:

DCS-10001: FAILED TO CREATE THE DATABASE: THERE ARE NO ASM DISK GROUPS DETECTED

Command Details

# odacli create-database

Hardware Models

All Oracle Database Appliance hardware models with multi-user access enabled systems

Workaround

Do one of the following:

Bug Number

This issue is tracked with Oracle bug 38920839.

Error in applying data patch

When applying the data patch on Oracle Database Appliance, an error may be encountered.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: Apply datapatch failed

Task Level Failure Message

DcsException{errorHttpCode=InternalError, msg=Internal error encountered: Apply datapatch failed., msgId=10001, causedBy=null}

Command Details

# odacli update-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps: 1. Run the following command on CDB and non-CDB:

<pre class="copy"><code>SELECT file_name FROM dba_temp_files WHERE tablespace_name = IN (&#39;TEMP&#39;, &#39;TEMP_ENC&#39;); alter database tempfile &lt;cdbfilepath&gt; autoextend on next 100m maxsize 20g;</code></pre>

  1. For CDB, run the following commands for each PDB:

    ALTER SESSION SET CONTAINER = pdbname
SELECT file_name FROM dba_temp_files WHERE tablespace_name IN ('TEMP', 'TEMP_ENC');
ALTER DATABASE TEMPFILE pdbfilepath AUTOEXTEND ON NEXT 100M MAXSIZE 20G;

  2. Run odacli update-database command with the -dp option.

Bug Number

This issue is tracked with Oracle bug 39728065.

Alert about Oracle ASMFD when patching DB system

When patching a DB system, an alert message about Oracle ASMFD is displayed.

Problem Description

The precheck Validate DB System AFD state may report DB systems that do not have Oracle ASMFD configured.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Create the prepatch report on DB systems after patching the bare metal system. The precheck for Oracle ASMFD is not run if Oracle ASMFD is not enabled on the DB systems.

Bug Number

This issue is tracked with Oracle bug 38866175.

Component version not updated after patching

After patching the Oracle Database Appliance server, the odacli describe-component command does not display the correct Intel Model 0x1528 Ethernet Controller version, if the current version is 8000047B or 8000047C.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Manually update the Ethernet controllers to 00005DD or 800005DE using the fwupdate command.

This issue is tracked with Oracle bug 34402352.

Known Issues When Deploying Oracle Database Appliance

Understand the known issues when provisioning or deploying Oracle Database Appliance.

Database home not completely deleted

After the job to delete Oracle Database Standard Edition database is completed on a two node DB system, the database home folder along with its payloads are not deleted on the remote node.

Command Details

odacli delete-dbhome

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Remove the JSON and folders of the database home that is not deleted on the remote folder, that is different from the node where you ran the odacli delete-dbhome command. 1. As dbhome owner, run the command:

<pre class="copy"><code>[dbhome_owner ~]$ sh dbhome_location/oui/bin/detachHome.sh        Starting Oracle Universal Installer...         Checking swap space: must be greater than 500 MB.  Actual 22931 MB  Passed        The inventory pointer is located at /etc/oraInst.loc</code></pre>

  1. As root user, run the command:

    [root ~]# rm -rf dbhome_folder

Bug Number

This issue is tracked with Oracle bug 39662467.

Error in database creation on multi-user access enabled system

When creating a database on multi-user access enabled system on Oracle Database Appliance, an error may be encountered.

Problem Description

When you create a database on a multi-user access enabled system, an error message may be displayed.

Failure Message

When the user name of database owner contains both lowercase and uppercase letters, the error message may be as follows:

[jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - [FATAL] Error in Process: /u01/app/KvEl6/product/19.0.0.0/dbhome_2/bin/orapwd
    [jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - Enter password for SYS:
    [jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - OPW-00010: Could not create the password file.
    [jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - ORA-00600: internal error code, arguments: [kfzpCreate02], [0], [], [], [], [], [], [], [], [], [], []
    [jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - ORA-15260: permission denied on ASM disk group
    [jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - ORA-06512: at "SYS.X$DBMS_DISKGROUP", line 679
    [jobid-74f31148-ebe0-4507-9296-b9ad4ca7e03b] - ORA-06512: at line 2

When the user name of database owner begins with number digit, the error message may be as follows:

PRCZ-4001 : failed to execute command "/u01/app/6RXNI/product/19.0.0.0/dbhome_15//bin/dbca" using the privileged execution plugin "odaexec" on nodes "scaoda901c7n1" within 5,000 seconds
PRCZ-2103 : Failed to execute command "/u01/app/6RXNI/product/19.0.0.0/dbhome_15//bin/dbca" on node "scaoda901c7n1" as user "6RXNI". Detailed error:
[FATAL] [DBT-05801] There are no ASM disk groups detected.
  CAUSE: ASM may not be configured, or ASM disk groups are not created yet.
  ACTION: Create ASM disk groups, or change the storage location to File System.
[FATAL] [DBT-05801] There are no ASM disk groups detected.
  CAUSE: ASM may not be configured, or ASM disk groups are not created yet.
  ACTION: Create ASM disk groups, or change the storage location to File System.

Command Details

# odacli create-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Do not start custom user name with number digit or have mixed-case letters in the custom user name.

Bug Number

This issue is tracked with Oracle bug 36878796.

Known Issues When Managing Oracle Database Appliance

Understand the known issues when managing or administering Oracle Database Appliance.

Error in switch over operation on Oracle Data Guard

When switching over Oracle Data Guard on Oracle Database Appliance, an error may be encountered.

Problem Description

When switching over Oracle Data Guard on Oracle Database Appliance, an error may be encountered.

Failure Message

When the odacli switchover-dataguard command is run, the following error message is displayed:

DCS-10001:Internal error encountered: Unable to switchover Dg.

Command Details

odacli switchover-dataguard

Hardware Models

All Oracle Database Appliance hardware models high-availability deployments

Workaround

Check Oracle Data Guard status using dgmgrl command. Wait for sometime before running odacli describe-dataguardstatus before checking Oracle Data Guard status.

Bug Number

This issue is tracked with Oracle bug 39722078.

Error in configuring Oracle Data Guard in a multiple standby environment

When configuring Oracle Data Guard on Oracle Database Appliance, an error may be encountered.

Problem Description

When you configure Oracle Data Guard on an Oracle Database Appliance for multiple standby databases, where dbType is ACFS, an error may be encountered.

Failure Message

When the odacli configure-dataguard command is run, the following error message is displayed:

DCS-10001:Internal error encountered: Unable to add standby db.

Command Details

odacli configure-dataguard

Hardware Models

All Oracle Database Appliance hardware models high-availability deployments

Workaround

None.

Bug Number

This issue is tracked with Oracle bug 38974337.

Error in creation of Oracle Key Vault TDE-enabled database

When creating an Oracle Key Vault TDE-enabled database on Oracle Database Appliance, an error may be encountered.

Problem Description

Creation of Oracle Key Vault TDE database on an Oracle Key Vault server whose version is earlier than the version of the existing Oracle Key Vault PKCS library /opt/oracle/extapi/64/hsm/oracle/1.0.0/liborapkcs.so on the system may fail.

Failure Message

DCS-10164:Failed to configure TDE: Failed to set TDE Master Encryption key: ERROR at line 1:
ORA-28353: failed to open wallet

Command Details

# odacli create-database -n db_name -t -kt OKV -ocp absolute_path_to_okvclient.jar

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Remove the later version of Oracle Key Vault PKCS library /opt/oracle/extapi/64/hsm/oracle/1.0.0/liborapkcs.so and retry the operation.

Bug Number

This issue is tracked with Oracle bug 38175259.

Error in updating Role after Oracle Data Guard operations

When performing operations with Oracle Data Guard on Oracle Database Appliance, an error is encountered in updating the Role.

The dbRole component described in the output of the odacli describe-database command is not updated after Oracle Data Guard switchover, failover, and reinstate operations on Oracle Database Appliance.

Hardware Models

All Oracle Database Appliance hardware models with Oracle Data Guard configuration

Workaround

Run odacli update-registry -n db --force/-f to update the database metadata. After the job completes, run the odacli describe-database command and verify that dbRole is updated.

This issue is tracked with Oracle bug 31378202.