Problem Description

After DB system upgrade, the existing vdisks are not attached. Only the vdisk metadata associated with the DB system is preserved. The virtual device name may be different from the name before you run the odacli upgrade-dbsystem command.

Command Details

# odacli upgrade-dbsystem

Hardware Models

All Oracle Database Appliance hardware models X9-2, X8-2, and X7-2

Workaround

Detach the vdisk manually with the --force option from the VM to reconcile the metadata. Then, attach the vdisk to the respective VM. Then, manually mount the file system on the device in the DB system.

Bug Number

This issue is tracked with Oracle bug 36885595.

Problem Description

When patching a multi-user access or multi-user access passwordless-enabled DB system from Oracle Database Appliance release 19.21, 19.22, 19.23, or 19.24 to release 19.26, an error is encountered. The error occurs when you run the odacli update-server -l command on the second node.

Failure Message

The following error message is displayed:

InternalError

Command Details

# odacli update-server -l

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 37626937.

Problem Description

The odacli update-dcscomponents command may fail to run after the Apply Metadata Change step, and running the command again may cause an error.

Failure Message

The following error message is displayed:

DCS-10008: Failed to update DCScomponents: 19.26.0.2.0
DCS-10001: Internal error encountered: Failed to execute action with exception:
DCS-10001: Internal error encountered: Failed to apply metadata change using script '/opt/oracle/dcs/log/jobfiles/02fb42de-8a98-463f-9621-5b1f7f2be912/apply_metadata_change.sh'.
Please check the detailed log at: /opt/oracle/dcs/log/jobfiles/02fb42de-8a98-463f-9621-5b1f7f2be912/apply_metadata_change.log.
Metadata schema rollback is done.

Command Details

# odacli update-dcscomponents

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bugs 37612491 and 37612515.

Problem Description

When patching the database or dbhome on Oracle Database Appliance, the datapatch sanity check or the datapatch application may fail because of insufficient free space for TEMP tablespace.

Failure Message

The following error message may be displayed in the sqlpatch_debug.log:

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP_ENC

Or, in the sanity_checks.log:

Check: Tablespace Status - ERROR

Command Details

# odacli update-dbhome 
# odacli update-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

alter database tempfile 4 resize 400M;
alter session set container=CHSTPDB;
alter database tempfile 5 resize 400M;

Bug Number

This issue is tracked with Oracle bug 37616088.

Problem Description

When patching Oracle Database Appliance, there may be an error in creating the patching prechecks report.

Failure Message

The following error message is displayed:

PRKH-1001 : HASContext Internal Error
PRKH-3003 : An attempt to communicate with the CSS daemon failed

Command Details

# odacli create-prepatchreport -db
# odacli create-prepatchreport -d

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Ignore this error and run the odacli update-dbhome or the odacli update-database command with the -f option to continue with the the patching operation.

Bug Number

This issue is tracked with Oracle bug 37616138.

Problem Description

When patching the server on Oracle Database Appliance, the kdump may fail to start during node restart, and an error message may be displayed.

Failure Message

There may be an error locating the modules.dep for the newly installed kernel, and the following error message is displayed:

# systemctl status kdump -l
 kdump.service - Crash recovery kernel arming
   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2024-10-15 11:51:15 IST; 8min ago
  Process: 6280 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE)
 Main PID: 6280 (code=exited, status=1/FAILURE)

Oct 15 11:51:12 systemd[1]: Starting Crash recovery kernel arming...
Oct 15 11:51:12 kdumpctl[6471]: kdump: No kdump initial ramdisk found.
Oct 15 11:51:12 kdumpctl[6471]: kdump: Rebuilding /boot/initramfs-5.4.17-2136.335.4.el8uek.x86_64kdump.img
Oct 15 11:51:13 kdumpctl[6566]: kdump: Warning: There might not be enough space to save a vmcore.
Oct 15 11:51:13 kdumpctl[6566]: kdump:          The size of /dev/mapper/VolGroupSys-LogVolRoot should be greater than 393610208 kilo bytes.
Oct 15 11:51:15 dracut[8055]: Executing: /usr/bin/dracut --add kdumpbase --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict --hostonly-nics  -o "plymouth dash resume ifcfg earlykdump" --compress=xz --mount "/dev/mapper/VolGroupSys-LogVolRoot /sysroot ext4 rw,relatime,nofail,x-systemd.before=initrd-fs.target" --no-hostonly-default-device --add-device /dev/md0 -f /boot/initramfs-5.4.17-2136.335.4.el8uek.x86_64kdump.img 5.4.17-2136.335.4.el8uek.x86_64
Oct 15 11:51:15 kdumpctl[7997]: dracut: /lib/modules/5.4.17-2136.335.4.el8uek.x86_64//modules.dep is missing. Did you run depmod?
Oct 15 11:51:15 dracut[8055]: /lib/modules/5.4.17-2136.335.4.el8uek.x86_64//modules.dep is missing. Did you run depmod?
Oct 15 11:51:15 kdumpctl[6471]: kdump: mkdumprd: failed to make kdump initrd
Oct 15 11:51:15 kdumpctl[6471]: kdump: Starting kdump: [FAILED]
Oct 15 11:51:15 systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 11:51:15 systemd[1]: kdump.service: Failed with result 'exit-code'.
Oct 15 11:51:15 systemd[1]: Failed to start Crash recovery kernel arming.

Command Details

# odacli update-server

Hardware Models

All Oracle Database Appliance hardware models

Workaround

# systemctl restart kdump

# systemctl status kdump -l
kdump.service - Crash recovery kernel arming
   Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sat 2024-10-19 09:34:23 IST; 8s ago
  Process: 2028 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)
 Main PID: 2028 (code=exited, status=0/SUCCESS)

Oct 19 09:34:21 dracut[2762]:  rd.lvm.lv=VolGroupSys/LogVolRoot
Oct 19 09:34:21 dracut[2762]:  rd.md.uuid=1e7140f4:2f5386a9:3093dd8d:ee3b9b29
Oct 19 09:34:22 dracut[2762]: *** Install squash loader ***
Oct 19 09:34:22 dracut[2762]: *** Squashing the files inside the initramfs ***
Oct 19 09:34:23 dracut[2762]: *** Squashing the files inside the initramfs done ***
Oct 19 09:34:23 dracut[2762]: *** Creating image file '/boot/initramfs-5.4.17-2136.335.4.el8uek.x86_64kdump.img' ***
Oct 19 09:34:23 dracut[2762]: *** Creating initramfs image file '/boot/initramfs-5.4.17-2136.335.4.el8uek.x86_64kdump.img' done ***
Oct 19 09:34:23 kdumpctl[2104]: kdump: kexec: loaded kdump kernel
Oct 19 09:34:23 kdumpctl[2104]: kdump: Starting kdump: [OK]
Oct 19 09:34:23 systemd[1]: Started Crash recovery kernel arming.

Bug Number

This issue is tracked with Oracle bug 36998253.

Problem Description

When updating the database on Oracle Database Appliance after a previously run odacli update-dbhome command failed with the error DCS-10274, then an error message may be displayed.

Failure Message

The following error message is displayed:

DCS-10274:Prepatchreport is not present for database: database_ID, source database home: source_dbhome_ID, destination database home: destination_dbhome_ID, components: [orachk, db], on node: node_name

Command Details

# odacli update-database

Hardware Models

All Oracle Database Appliance hardware models with DB systems on Oracle Database Appliance release 19.25 or later

Workaround

supported version="destination version of target-to-patch database" clone="xxx"  min_gi_version="23.0" max_gi_version="23.99" size="1.5" agent_version="23.xxxx"  ignore_patches="xxx" platform="VM"/

After the update-database job succeeds, restore the DB entry in the file.

Bug Number

This issue is tracked with Oracle bug 37566140.

Problem Description

When updating an Oracle RAC One database on Oracle Database Appliance, an error message may be displayed.

The failure occurs if the database name contains uppercase letters.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: PRGH-1106 : null.
DCS-10001:Internal error encountered: PRGH-1106 : could not connect to database.
ORA-12162: TNS:net service name is incorrectly specified

Command Details

# odacli update-database

Hardware Models

All high-availability Oracle Database Appliance hardware models

Workaround

1. Apply datapatch by running the following two commands:

   odacli create-prepatchreport -dp -dbid target_to_patch_database_ID

   odacli update-database -dp -i target_to_patch_database_ID

2. Remove the checkpoint for Rapid Home Provisioning for the incomplete patch on both nodes:

   [root@ ~]# /opt/oracle/dcs/mysql/bin/mysql -hlocalhost -uroot --socket=/opt/oracle/dcs/mysql/log/mysqldb.sock
         mysql> use GHSUSER23;
         mysql> select ID,cast(NAME as char(100000) character set utf8),SRCWC,SRCHOME,DSTWC,DSTHOME,CLUSTERNAME from MOVE;
         Remove ALL entries in the table that match {source and destination dbhomes}
         mysql> commit;

3. Update the checkpoint for DCS for the incomplete patch on both nodes:

   [root@ ~]# /opt/oracle/dcs/mysql/bin/mysql -hlocalhost -uroot --socket=/opt/oracle/dcs/mysql/log/mysqldb.sock
         mysql> use dcsagentdb;
         mysql> select * from UnfinishedDbPatch;
         locate the SINGLE entry that matches {databaseId, sourceDbHomeId, and destinationDbHomeId}, and update the entry as below,
         mysql> update UnfinishedPatch set rhpFailure=false where id=’<entry_id>’;
         mysql> commit;

4. Run the odacli update-database -i database_ID -to destination_dbhome_ID command to resume the job from the failure point.
5. If you encounter bug 37566140, that is, error code DCS-10274 when running step 4, apply the workaround for bug 37566140.

Bug Number

This issue is tracked with Oracle bug 37594043.

Problem Description

When patching the server on Oracle Database Appliance, and the DCS agent loads, the scheduler service may fail to start and an error message may be displayed.

Failure Message

The dcs-agent.log file displays the following error message:

-----------------------
2024-07-29 14:24:30,351 WARN [backgroundjob-zookeeper-pool-7-thread-2] [] o.j.s.JobZooKeeper: JobRunr encountered a problematic exception. Please create a bug report (if possible, provide the code to reproduce this and the stacktrace) - Processing will continue.
java.lang.NullPointerException: null
        at org.jobrunr.server.zookeeper.tasks.ZooKeeperTask.pollIntervalInSecondsTimeBoxIsAboutToPass(ZooKeeperTask.java:93)
        at org.jobrunr.server.zookeeper.tasks.ZooKeeperTask.getJobsToProcess(ZooKeeperTask.java:84)
        at org.jobrunr.server.zookeeper.tasks.ZooKeeperTask.processJobList(ZooKeeperTask.java:57)
        at org.jobrunr.server.zookeeper.tasks.ProcessOrphanedJobsTask.runTask(ProcessOrphanedJobsTask.java:29)
        at org.jobrunr.server.zookeeper.tasks.ZooKeeperTask.run(ZooKeeperTask.java:47)
        at org.jobrunr.server.JobZooKeeper.lambda$runMasterTasksIfCurrentServerIsMaster$0(JobZooKeeper.java:76)
        at java.util.Arrays$ArrayList.forEach(Arrays.java:3880)
        at org.jobrunr.server.JobZooKeeper.runMasterTasksIfCurrentServerIsMaster(JobZooKeeper.java:76)
        at org.jobrunr.server.JobZooKeeper.run(JobZooKeeper.java:56)
-----------------------

Command Details

# odacli update-server

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 36896020.

Problem Description

When you create Oracle ASM databases, the RECO directory may not have been created on systems provisioned with the OAK stack. This directory is created when the first RECO record is written. After successfully upgrading these systems using Data Preserving Reprovisioning to Oracle Database Appliance release 19.15 or later, if you attempt to upgrade the database, an error message may be displayed.

Failure Message

When the odacli upgrade-database command is run, the following error message is displayed:

# odacli upgrade-database -i 16288932-61c6-4a9b-beb0-4eb19d95b2bd -to b969dd9b-f9cb-4e49-8e0d-575a0940d288
DCS-10001:Internal error encountered: dbStorage metadata not in place:
DCS-12013:Metadata validation error encountered: dbStorage metadata missing
Location info for database database_unique_name..

Command Details

# odacli upgrade-database

Hardware Models

All Oracle Database Appliance X6-2HA and X5-2 hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 34923078.

Problem Description

When applying the datapatch during patching of database on Oracle Database Appliance, an error message may be displayed.

Failure Message

When the odacli update-database command is run, the following error message is displayed:

Failed to execute sqlpatch for database …

Command Details

# odacli update-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 35060742.

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.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

The STIG V1R2 rule OL7-00-040420 tries to change the permission of the file /etc/ssh/ssh_host_rsa_key from '640' to '600' which causes the error. During patching, run the command chmod 600 /etc/ssh/ssh_host_rsa_key command on both nodes.

This issue is tracked with Oracle bug 33168598.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

This issue is tracked with Oracle bug 33144170.

Hardware Models

Oracle Database Appliance hardware models bare metal deployments

Workaround

odacli update-dbhome -j -v 19.26.0.0.0 -i dbhome_id -sko

This issue is tracked with Oracle bugs 30931017, 31631618, and 31921112.

Failure in the pre-patch report caused by “AHF-5190: operating system boot device order is not configured as recommended”

Hardware Models

Oracle Database Appliance X-7 hardware models

Workaround

Run the odacli update-server or odacli update-dbhome command with the -f option.

This issue is tracked with Oracle bug 33631256.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

This is a timing issue with setting up the SSH equivalence.

Run the odacli update-dcscomponents command again and the operation completes successfully.

This issue is tracked with Oracle bug 32553519.

When patching the appliance, the odacli update-server command fails with the following error:

DCS-10001:Internal error encountered: Server upgrade state is not NORMAL node_name 

Hardware Models

All Oracle Database Appliance hardware models

Workaround

1. Run the command:

   Grid_home/bin/cluvfy stage -post crsinst -collect cluster -gi_upgrade -n all

2. Ignore the following two warnings:

   Verifying OCR Integrity ...WARNING
   PRVG-6017 : OCR backup is located in the same disk group "+DATA" as OCR.
   
   Verifying Single Client Access Name (SCAN) ...WARNING
   RVG-11368 : A SCAN is recommended to resolve to "3" or more IP

3. Run the command again till the output displays only the two warnings above. The status of Oracle Custerware status should be Normal again.

4. You can verify the status with the command:

   Grid_home/bin/crsctl query crs activeversion -f

This issue is tracked with Oracle bug 30099090.

These drives are displayed when you run the odacli describe-component command. Patching of neither of the two known versions 0112 and 0121 of the M.2 disk is supported.

Hardware Models

Oracle Database Appliance bare metal deployments

Workaround

None

This issue is tracked with Oracle bug 30249232.

Problem Description

When you create a DB system with Oracle AFD on Oracle Database Appliance release 19.22, with Oracle Grid Infrastructure or Oracle Database release 19.21 or earlier, then an error may be encountered at the "Install DB System" step.

Failure Message

The following error message is displayed in the database alert.log:

WARNING: group 2 (RECO) has missing disks
ORA-15040: diskgroup is incomplete
WARNING: group 2 is being dismounted

Command Details

# odacli create-dbsystem

Hardware Models

All Oracle Database Appliance hardware models running Oracle Grid Infrastructure 19.21

Workaround

This issue is fixed in Oracle Grid Infrastructure 19.22 Release Update (RU). Create the DB system using Oracle Grid Infrastructure and Oracle Database release 19.22.

You can create DB system without enabling Oracle AFD by specifying enableAFD=false in the DB system JSON file during DB system creation.

Do not patch or upgrade the existing Oracle AFD-enabled DB system with Oracle Grid Infrastructure or Oracle Database release 19.21 till the fix for bug 36114443 is available in the Oracle Grid Infrastructure and Oracle Database clone files.

Bug Number

This issue is tracked with Oracle bug 36300713.

Problem Description

When you rekey a TDE-enabled database configured using Oracle Key Vault keystore, the rekey operation may fail after changing the TDE password of the database, and an error message is displayed.

Failure Message

DCS-10164:Failed to configure TDE: Failed to set TDE Master Encryption key: PL/SQL procedure successfully completed.   PL/SQL procedure successfully completed.  begin * ERROR at line 1: ORA-46627: keystore password mismatch ORA-06512: at line 3

Command Details

# odacli modify-database -n dbname -rkt

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 37431957.

Problem Description

When the bare metal system is configured with FLEX redundancy, the database creation uses file group templates, and you create an Oracle Database 23ai database of version 23.6 or earlier on an Oracle Database Appliance release 19.25 or earlier deployment, and the DB_SYSTEM_NAME and DB_ORACLE_USER_NAME together are greater than 22 characters, an error is encountered.

Failure Message

The following error message may be displayed:

ORA-01261: Parameter db_create_file_dest destination string cannot be translated

Hardware Models

All Oracle Database Appliance hardware models

Workaround

In FLEX disk group environment, if the DB system version is Oracle Database Appliance 19.25 or earlier, with Oracle Database 23ai version 23.6 or earlier, then ensure that the DB_SYSTEM_NAME and DB_ORACLE_USER_NAME together are greater than 22 characters.

Bug Number

This issue is tracked with Oracle bug 37305833.

Problem Description

When you submit jobs to change the password for a TDE-enabled Oracle RAC One database configured using Oracle Key Vault keystore simultaneously for the same database, and an error message is displayed.

Failure Message

DCS-10001:Internal error encountered: Failed to relocate database.

Command Details

# odacli modify-database -n dbname -ctp

Hardware Models

All Oracle Database Appliance hardware models

Workaround

None.

Bug Number

This issue is tracked with Oracle bug 37567042.

Problem Description

For Oracle Database 23ai databases, when you run the odacli switchover-dataguard command from the primary site and provide the primary database unique name with the -u option, then an error may be encountered.

Failure Message

The following error message may be displayed:

DCS-10001:Internal error encountered: Unable to create auto login wallet for remote db.

Command Details

# odacli switchover-dataguard

Hardware Models

All Oracle Database Appliance hardware models running Oracle Database 23ai, versions 23.6 and 23.7 DB systems

Workaround

Run odacli switchover-dataguard from the primary site and provide the standby database unique name on the remote site for the Oracle Data Guard switchover operation.

Bug Number

This issue is tracked with Oracle bug 37622670.

Problem Description

When you enable high-availability on a TDE-enabled database that uses Oracle Key Vault to store TDE keys, an error message may be displayed.

Failure Message

DCS-12721:OKV command "okv admin endpoint create" failed to run: Failed to create endpoint endpoint_name

Command Details

# odacli modify-database -n dbname -ha

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Instead of enabling high-availability after creating the database, enable high-availability during database creation itself.

Bug Number

This issue is tracked with Oracle bug 37182129.

Problem Description

DCS-10001:THE CONNECTION IS CLOSED

This error may occur when the bare metal system is provisioned with NTP configured, or there is a time difference between bare metal system and the standard NTP server, or the DB system is created after NTP is configured.

Failure Message

[DB System n1 creation] -  DCS-10001:Internal error encountered: Job 'Provision DB System 'n1'' (f91fd1db-78ec-452d-bcdb-975947849370) failed.

Command Details

odacli create-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Provision the bare metal system without configuring NTP.

If there is a time difference between the bare metal system and the standard NTP server, then add several minutes to the current date.

Enable chrony.

1. Before enabling chrony, add or update the chrony configuration as follows:

   --------
   # cat /etc/chrony.conf
   server 10.246.6.36 iburst
   driftfile /var/lib/chrony/drift
   makestep 1.0 -1
   rtcsync
   logdir /var/log/chrony
   ---------

2. Run the systemctl command to enable and start chronyd service:

   date;
   systemctl enable chronyd
   systemctl start chronyd
   systemctl status chronyd
   sleep 10;
   date;

3. Create DB system with NTP configured.

Bug Number

This issue is tracked with Oracle bug 37166091.

Problem Description

If you run the odacli modify-asmport command on an appliance configured with Oracle Data Guard that uses MAX PROTECTION mode, then this could cause a disruption in primary site due to the standby Oracle Clusterware being restarted as part of the Oracle ASM port change.

Failure Message

The following error message may be displayed in the alert logs for the database on the primary host:

ORA-16072: a minimum of one standby database destination is required

terminating the instance due to ORA error 16072

Task Level Failure Message

The job may fail at the Stop CRS on DB System(s) step. The complete details of the error are displayed in the Message section of the command output.

Command Details

# odacli modify-asmport

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Start the database instance on the primary host.

Bug Number

This issue is tracked with Oracle bug 36931905.

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

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.

Failure Message

The following error message is displayed:

DCS-10045:Validation error encountered: Registration failed : Please check the agent logs for details.

Command Details

# odacli configure-asr

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 36363437.

Problem Description

If DBVM is undefined using virsh undefine dbvm_name, then the odacli start-dbsystem command may fail to run.

Failure Message

DCS-10001:Internal error encountered: error: failed to get domain 'dbvm_name'

Hardware Models

All Oracle Database Appliance hardware models running Oracle Database Appliance release 19.21

Workaround

Run virsh define /u05/app/sharedrepo/dbsystem/.ACFS/snaps/vm_dbvm_name/dbvm_name.xml to define the VM. Then start the DB system.

Bug Number

This issue is tracked with Oracle bug 36051738.

Problem Description

When creating a database on Oracle Database Appliance, the operation may fail after the createDatabaseByRHP task. However, the odacli list-databases command displays the status as CONFIGURED for the failed database in the job results.

Failure Message

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

DCS-10001:Internal error encountered: Failed to clear all listeners from database

Command Details

# odacli create-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Check the job description of the odacli create-database command using the odacli describe-job command. Fix the issue for the task failure in the odacli create-database command. Delete the database with the command odacli delete-database -n db_name and retry the odacli create-database command.

Bug Number

This issue is tracked with Oracle bug 34709091.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Do not create two DB systems concurrently. Instead, complete the creation of one DB system and then create the other.

This issue is tracked with Oracle bug 33275630.

Hardware Models

All Oracle Database Appliance hardware models bare metal and dbsystem

Workaround

systemctl restart initdcsagent 

This issue is tracked with Oracle bug 32586762.

After running cleanup.pl, provisioning the appliance fails because of missing Oracle Grid Infrastructure image (IMGGI191100). The following error message is displayed:

DCS-10042:User oda-cliadmin cannot be authorized.

Hardware Models

All Oracle Database Appliance hardware models for bare metal deployments

Workaround

After running cleanup.pl, and before provisioning the appliance, update the repository as follows:

# odacli update-repository -f /**gi** 

This issue is tracked with Oracle bug 32707387.

After running cleanup.pl, when you try to use odacli commands, the following error is encountered:

DCS-10042:User oda-cliadmin cannot be authorized.

Hardware Models

All Oracle Database Appliance hardware models for bare metal deployments

Workaround

Run the following commands to set up the credentials for the user oda-cliadmin on the agent wallet:

# rm -rf /opt/oracle/dcs/conf/.authconfig  
# /opt/oracle/dcs/bin/setupAgentAuth.sh 

This issue is tracked with Oracle bug 29038717.

If the source database is single-instance or Oracle RAC One Node, or running on the remote node, the clone database operation fails, because the paths are not created correctly in the control file.

Clone database operation may also fail with errors if the source database creation time stamp is too close to the clone operation (at least within 60 minutes).

Hardware Models

All Oracle Database Appliance high-availability hardware models for bare metal deployments

Workaround

Create the clone database from the source database instance that is running on the same node from which the clone database creation is triggered.

SQL> alter system checkpoint;

This issue is tracked with Oracle bugs 29002563, 29002004, 29001906, 29001855, 29001631, 28995153, 28986643, 30309971, and 30228362.

Problem Description

When you run the odacli ping-agent command, an error may be encountered.

Failure message

DCS-10033:Service DCS agent is down.

Command Details

# odacli ping-agent

Hardware Models

All Oracle Database Appliance hardware models with high-availability

Workaround

Bug Number

This issue is tracked with Oracle bug 37611921.

Problem Description

If you configured Oracle Data Guard on a multi-user access enabled Oracle Database Appliance release 19.19 system, as odaadmin user, then this Oracle Data Guard configuration may not display when you run the odacli list-dataguardstatus command. If you upgrade this system to Oracle Database Appliance release 19.23 using Data Preserving Reprovisioning, then the Validate Database Service presence step in the the create-preupgradereport precheck may fail for the Oracle Data Guard database.

One or more pre-checks failed for [DB]

Command Details

# odacli create-preupgradereport 

# odacli describe-preupgradereport 

Task Level Failure message

"The following services [TDG1yn_ro, TDG1yn_rw, Y6Z_ro, Y6Z_rw] created on database 
'TDG1yn' can result in a failure in 'detach-node'

Hardware Models

All Oracle Database Appliance hardware models X9-2, X8-2, and X7-2

Workaround

Bug Number

This issue is tracked with Oracle bug 36610040.

Problem Description

When you relocate a TDE-enabled database that uses Oracle Key Vault to store TDE keys with the option --target-node,-tn, and re-key with the option --rekey-tde,-rkt, at the same time, an error may be encountered when setting the TDE master encryption key.

Failure Message

DCS-10164:Failed to configure TDE: Failed to set TDE Master Encryption key

Command Details

# odacli modify-database -n dbname -rkt -tn target_node_name

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Perform the relocation and re-key operations separately, one after another.

Bug Number

This issue is tracked with Oracle bug 37155404.

Problem Description

When you delete a TDE-enabled database that uses Oracle Key Vault release 21.8 to store TDE keys, then an error message may be displayed during the OKV delete task.

Failure Message

DCS-10001:Internal error encountered: Failed to delete Wallet <wallet_name> : okv.log.0 (Permission denied)
{
"result" : "Failure",
"message" : "Insufficient privileges on wallet"
}.

Command Details

# odacli delete-database -n db_name

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Bug Number

This issue is tracked with Oracle bug 36640379.

Problem Description

When you delete a database home, the database home is not deleted completely. The subfolders and files exist in the corresponding database home location and the database home entry exists in the /u01/app/oraInventory/ContentsXML/inventory.xml file.

Failure Message

When the odacli update-database command is run, the following error message is displayed:

Failed to execute sqlpatch for database …

Command Details

# odacli delete-dbhome

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Before you run the odacli delete-dbhome command, confirm that the wOraDBversion_homeidx exists in the /opt/oracle/rhp/RHPCheckpoints/ location on the same node where you run the command.

Bug Number

This issue is tracked with Oracle bug 36864228.

Problem Description

When you configure Oracle Data Guard on the second node of the standby system on an Oracle Database Appliance high-availability deployment, the operation may fail at step Configure Standby database (Standby site) in the task Reset Db sizing and hidden parameters for ODA best practice.

Command Details

odacli configure-dataguard

Hardware Models

All Oracle Database Appliance hardware models high-availability deployments

Workaround

Run odacli configure-dataguard on the first node of the standby system in the high-availability deployment

Bug Number

This issue is tracked with Oracle bug 33401667.

Hardware Models

All Oracle Database Appliance hardware models with DB systems

Workaround

This issue is tracked with Oracle bug 33289742.

Hardware Models

All Oracle Database Appliance hardware models with virtualized platform

Workaround

None.

This issue is tracked with Oracle bug 33580574.

Error: ORA-16664: unable to receive the result from a member

Hardware Models

All Oracle Database Appliance hardware models

Workaround

This issue is tracked with Oracle bug 32864100.

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.

Hardware Models

Oracle Database Appliance hardware models bare metal deployments

Workaround

Ignore counts of Critical, Failed, and Warning issues in the ORAchk report summary on the Browser User Interface. Check the report detail page.

This issue is tracked with Oracle bug 30676674.

Hardware Models

All Oracle Database Appliance Hardware bare metal systems

Workaround

After cleanup of the deployment, oakd is started in the non-cluster mode, and it cannot be stopped using "odaadmcli stop oak" command. In such a case, if the Secure Erase tool is run, then the odaeraser command fails.

Use the command odaadmcli shutdown oak to stop oakd.

This issue is tracked with Oracle bug 28547433.