4 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.

WARNING:

When you patch your deployment from Oracle Database Appliance release 19.29 to Oracle Database Appliance release 19.30, if you see the error DCS-10315 - Patch described in My Oracle Support Note KB867473 must be applied. in the prepatch report, ensure that you follow the procedure described in My Oracle Support Note KB867473, and then use the --force option with the odacli update-database or odacli update-dbhome command.

Parent topic: Known Issues with Oracle Database Appliance in This Release

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:
  • Create the database using the default oracle user created as part of provisioning the DB system.
  • As root user, run the usermod -a -G DBA role group name odaadmin command to add the user odaadmin to the DBA group. The name of the group is specified in the provisioning json for the DB system. After this, run the odacli create-database command as the odaadmin user.

Bug Number

This issue is tracked with Oracle bug 38920839.

Parent topic: Known Issues When Patching Oracle Database Appliance

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:
    SELECT file_name FROM dba_temp_files WHERE tablespace_name = IN ('TEMP', 'TEMP_ENC');
alter database tempfile <cdbfilepath> autoextend on next 100m maxsize 20g;
  2. 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;
  3. Run odacli update-database command with the -dp option.

Bug Number

This issue is tracked with Oracle bug 39728065.

Parent topic: Known Issues When Patching Oracle Database Appliance

Earlier release kernel active during patching

Before patching to a later ODA release, the active kernel may not match the latest kernel installed for the current ODA release.

Problem Description

On Oracle Database Appliance systems upgraded from an earlier Unbreakable Enterprise Kernel 6 (UEK6)-based release through the UEK6-to-UEK7 migration path, the system may continue to restart with a kernel from an earlier Oracle Database Appliance release even though the kernel RPM for the current release is installed.

This issue occurs only when all of the following conditions apply:

  • The system was originally provisioned on a UEK6-based Oracle Database Appliance release.
  • The system was later upgraded through the UEK6-to-UEK7 migration path.
  • The system is currently running Oracle Database Appliance release 19.30 or 19.31.
  • After patching, the newly installed kernel was not selected as the default boot kernel, and the system continued to run the earlier Oracle Database Appliance kernel.

Systems freshly provisioned with Oracle Database Appliance release release 19.27 or later are not affected because they do not undergo the UEK6-to-UEK7 migration.

For example, an Oracle Database Appliance release 19.31 system may still be running the Oracle Database Appliance release 19.30 kernel:
# uname -r
5.15.0-316.196.4.1.el8uek.x86_64

# rpm -qa | grep '^kernel-uek-core' | sort
kernel-uek-core-5.15.0-316.196.4.1.el8uek.x86_64
kernel-uek-core-5.15.0-319.201.4.4.el8uek.x86_64

# grubby --default-kernel
/boot/vmlinuz-5.15.0-316.196.4.1.el8uek.x86_64
In this example, the Oracle Database Appliance 19.30 kernel is active and configured as the default, while the Oracle Database Appliance release 19.31 kernel is installed but inactive. If this condition is not corrected before patching to Oracle Database Appliance release 19.32, then the patching process may preserve the active Oracle Database Appliance release 19.30 kernel and remove the inactive Oracle Database Appliance release 19.31 kernel. The system may then contain the Oracle Database Appliance release 19.32 and Oracle Database Appliance release 19.30 kernels instead of the expected Oracle Database Appliance release 19.32 and Oracle Database Appliance release 19.31 kernels. The following kernel versions are used in this example: 
Oracle Database Appliance release 19.30: kernel-uek-core-5.15.0-316.196.4.1.el8uek.x86_64
Oracle Database Appliance release 19.31: kernel-uek-core-5.15.0-319.201.4.4.el8uek.x86_64
Oracle Database Appliance release 19.32: kernel-uek-core-5.15.0-321.202.5.2.el8uek.x86_64

Command Details

Before starting the patching operation, verify the active, installed, and default kernels: 

# uname -r
# rpm -qa | grep '^kernel-uek-core' | sort
# grubby --default-kernel

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. If the system is running an earlier kernel while the latest kernel for the current Oracle Database Appliance release is installed, then configure the latest installed kernel as the default and restart the system before starting the patching operation. For example, on an Oracle Database Appliance release 19.31 system: 
    # grubby --set-default /boot/vmlinuz-5.15.0-319.201.4.4.el8uek.x86_64

# grubby --default-kernel
/boot/vmlinuz-5.15.0-319.201.4.4.el8uek.x86_64

# reboot
  2. After the system restarts, verify that the expected kernel is active: 
    # uname -r
5.15.0-319.201.4.4.el8uek.x86_64
  3. After confirming that the correct kernel is active, proceed with the Oracle Database Appliance patching operation. If the required kernel RPM has already been removed, contact Oracle Support for instructions to reinstall the appropriate kernel RPM and restore the expected boot configuration.

Bug Number

This issue is tracked with Oracle bug 39732559.

Parent topic: Known Issues When Patching Oracle Database Appliance

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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in running prepatch checks

When running prepatch report on Oracle Database Appliance, an error may be encountered.

Problem Description

When running the prechecks report for patching, the operation may fail.

Failure Message

The following error message may be displayed:

DCS-10267 - failed to run the patch precheck with Oracle FPP for Oracle home ID home_ID Internal error encountered: PRGO-1198: The source working copy is incomplete.

Command Details

# odacli create-prepatchreport

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. Verify that the Oracle home with the ID described in the prepatch report exists on both nodes.
  2. Determine which node had the prepatch failure using the odacli describe-prepatchreport -i command.
  3. Stop the DCS agent on the node where the prepatch report failed:
    systemctl stop initdcsagent
  4. Run the following command on the same node as the root use. 
    export DB_HOME=$(odacli-view describe-prepatchreport -i PREPATCH_ID | grep 'Description:' | sed -n 's/.*DbHome is \([^ ]*\).*/\1/p');
/opt/oracle/dcs/mysql/bin/mysql -hlocalhost -uroot --socket=/opt/oracle/dcs/mysql/log/mysqldb.sock -e "USE GHSUSER23; UPDATE SWHOMES SET complete=1 WHERE name='$DB_HOME'; COMMIT;"
  5. Run the command systemctl start initdcsagent.
  6. Create the prepatch report again.

Bug Number

This issue is tracked with Oracle bug 38934628.

Parent topic: Known Issues When Patching Oracle Database Appliance

Free space issue during database patching

When patching the database on Oracle Database Appliance, an error may be encountered.

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

Extend tablespace TEMP_ENC and then resume the patching operation using the command odacli update-database.
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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in DB system after server patching

After patching the server on Oracle Database Appliance, an error may be encountered on the DB system.

Failure Message

The following error message is displayed:

DCS-10172:DCS infrastructure is not ready: The infrastructure is still initializing

Command Details

Any command requiring the DCS infrastructure, such as:
# odacli update-server

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. On the DB system, stop the DCS agent service:
    # systemctl stop initdcsagent
  2. Delete the entry HWADDR=null from the /etc/sysconfig/network-scripts/ifcfg-ib* configuration files:
    # sed -i '/HWADDR=null/d' /etc/sysconfig/network-scripts/ifcfg-ib*
  3. Restart the network service:
    # systemctl restart network
  4. Start the DCS agent service:
    # systemctl start initdcsagent
  5. Wait for about 5 minutes and then verify that the DCS agent infrastructure is initialized, and both Oracle HAMI members are ONLINE.
    # /opt/oracle/dcs/hami/bin/hamictl.sh status
  6. Verify that Oracle Clusterware service is online:
    # CRS_HOME/bin/crsctl check cluster -all
**************************************************************
Node0:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
Node1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
  7. If Oracle Clusterware is not online on any DB system, then restart Oracle Clusterware on that DB system:
    # CRS_HOME/bin/crsctl stop crs -f
# CRS_HOME/bin/crsctl start crs

Bug Number

This issue is tracked with Oracle bug 38064361.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in server patching

When patching the server on Oracle Database Appliance, an error may be encountered.

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

Restart the kdump service:
# 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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in database patching

When patching a database on Oracle Database Appliance, an error may be encountered.

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

  1. Run the following SQL*Plus command:
    alter system set nls_sort='BINARY' SCOPE=SPFILE;
  2. Restart the database using srvctl command.
  3. Retry applying the datapatch with dbhome/OPatch/datapatch -verbose -db dbUniqueName.

Bug Number

This issue is tracked with Oracle bug 35060742.

Parent topic: Known Issues When Patching Oracle Database Appliance

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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in server patching

When patching Oracle Database Appliance which already has STIG V1R2 deployed, an error may be encountered.

On an Oracle Database Appliance deployment with release earlier than 19.32, if the Security Technical Implementation Guidelines (STIG) V1R2 is already deployed, then when you patch to 19.32 or earlier, and run the command odacli update-server -f version, an error may be displayed.

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.

Parent topic: Known Issues When Patching Oracle Database Appliance

AHF error in prepatch report for the update-dbhome command

When you patch server to Oracle Database Appliance release 19.32, the odacli update-dbhome command may fail.

The following error message is displayed in the pre-patch report:
Verify the Alternate Archive    Failed    AHF-4940: One or more log archive 
Destination is Configured to              destination and alternate log archive
Prevent Database Hangs                    destination settings are not as recommended

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. Run the odacli update-dbhome command with the -f option.
    /opt/oracle/dcs/bin/odacli update-dbhome --dbhomeid 7c67c5b4-f585-4ba9-865f-c719c63c0a6e -v 19.32.0.0.0 -f

This issue is tracked with Oracle bug 33144170.

Parent topic: Known Issues When Patching Oracle Database Appliance

Errors when running ORAchk or the odacli create-prepatchreport command

When you run ORAchk or the odacli create-prepatchreport command, an error is encountered.

The following error messages may be seen:
One or more log archive destination and alternate log archive destination settings are not as recommended 
Software home check failed

Hardware Models

Oracle Database Appliance hardware models bare metal deployments

Workaround

Run the odacli update-dbhome, odacli create-prepatchreport, odacli update-server commands with the -sko option. For example:
odacli update-dbhome -j -v 19.32.0.0.0 -i dbhome_id -sko

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

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in patching prechecks report

The patching prechecks report may display an error.

The following error message may be displayed:
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 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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Server status not set to Normal when patching

When patching Oracle Database Appliance, an error is encountered.

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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Patching of M.2 drives not supported

Patching of M.2 drives (local disks SSDSCKJB48 and SSDSCKJB480G7) is not supported.

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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Known Issues When Deploying Oracle Database Appliance

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

Parent topic: Known Issues with Oracle Database Appliance in This Release

Error in creating database home

When creating a database home on Oracle Database Appliance, an error may be encountered.

Problem Description

When provisioning the database home, you run the odacli create-dbhome or odacli create-prepatchreport command, an error may be encountered due to a temporary lock of the /u01/app/oraInventory/ directory.

Failure Message

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

DCS-10267 - failed to run the patch precheck with Oracle FPP for Oracle home ID dbhome_ID For input string: "dbhome_name"

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

DCS-10001:Internal error encountered: Failed to run create dbhome dbhome_name : null

Command Details

# odacli create-dbhome
# odacli create-prepatchreport

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Delete the partially created atabase home using the odacli delete-dbhome command and run the odacli create-prepatchreport or odacli create-dbhome command again.

Bug Number

This issue is tracked with Oracle bug 38143200.

Parent topic: Known Issues When 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:
    [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
  2. As root user, run the command:
    [root ~]# rm -rf dbhome_folder

Bug Number

This issue is tracked with Oracle bug 39662467.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in cloning a database

When cloning a database on Oracle Database Appliance, an error may be encountered.

Failure Message

DCS-10001 Failed to run NID utility..NID operation to change dbname and/or dbID failed

Command Details

odacli clone-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:

  1. Manually set write permissions for others on the /tmp/dcsfiles directory
    chmod u+w /tmp/dcsfiles
  2. Run the odacli clone-database command.

Bug Number

This issue is tracked with Oracle bug 39729585.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in creating DB system

When creating a DB system, an error may be encountered.

Problem Description

When you create a DB system on Oracle Database Appliance, the following error may be encountered:
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.

Parent topic: Known Issues When Deploying Oracle Database Appliance

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.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in configuring Oracle ASR

When configuring Oracle ASR, an error may be encountered when registering Oracle ASR Manager due to an issue while contacting the transport server.

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

Retry configuring Oracle ASR using the odacli configure-asr command.

Bug Number

This issue is tracked with Oracle bug 36363437.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in creating database

When creating a database on Oracle Database Appliance, an error may be encountered.

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.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in creating two DB systems

When creating two DB systems concurrently in two different Oracle ASM disk groups, an error is encountered.

When attempting to start the DB systems, the following error message is displayed:
CRS-2672: Attempting to start 'vm_name.kvm' on 'oda_server'
CRS-5017: The resource action "vm_name.kvm start" encountered the following
error:
CRS-29200: The libvirt virtualization library encountered the following
error:
Timed out during operation: cannot acquire state change lock (held by
monitor=remoteDispatchDomainCreate)
. For details refer to "(:CLSN00107:)" in
"/u01/app/grid/diag/crs/<oda_server>/crs/trace/crsd_orarootagent_root.trc".
CRS-2674: Start of 'vm_name.kvm' on 'oda_server' failed
CRS-2679: Attempting to clean 'vm_name.kvm' on 'oda_server'
CRS-2681: Clean of 'vm_name.kvm' on 'oda_server' succeeded
CRS-4000: Command Start failed, or completed with errors.

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.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in adding JBOD

When you add a second JBOD to your Oracle Database Appliance deployment on which a DB system is running, an error is encountered.

The following error message is displayed:
ORA-15333: disk is not visible on client instance

Hardware Models

All Oracle Database Appliance hardware models bare metal and dbsystem

Workaround

Shut down dbsystem before adding the second JBOD. 
systemctl restart initdcsagent

This issue is tracked with Oracle bug 32586762.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in provisioning appliance after running cleanup.pl

Errors encountered in provisioning applince after running cleanup.pl.

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.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error encountered after running cleanup.pl

Errors encountered in running odacli commands after running cleanup.pl.

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.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Errors in clone database operation

Clone database operation fails due to errors.

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.

For Oracle Database 12c and later, synchronize the source database before the clone operation, by running the command:
SQL> alter system checkpoint;

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

Parent topic: Known Issues When Deploying Oracle Database Appliance

Known Issues When Managing Oracle Database Appliance

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

Parent topic: Known Issues with Oracle Database Appliance in This Release

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.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in configuring Oracle Data Guard

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 Oracle Database 23ai database with Release Update 23.8, the operation may fail because of missing tnsnames.ora file.

Failure Message

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

DCS-10003:File '/u01/app/oracle/product/23.0.0.0/dbhome_1/network/admin/tnsnames.ora' does not exist

Command Details

odacli configure-dataguard

Hardware Models

All Oracle Database Appliance hardware models high-availability deployments

Workaround

Create the tnsnames.ora file in the location DBHOME/network/admin/tnsnames.ora of the database that has this issue, and add a TNS entry for it.

For example, add a database with database unique name testdb on the host testhost as follows:
cat /u01/app/oracle/product/23.0.0.0/dbhome_1/network/admin/tnsnames.ora 
testdb=
 (DESCRIPTION=
  (ADDRESS = (PROTOCOL = TCP)(HOST = testhost)(PORT = 1521))
  (CONNECT_DATA = 
  (SERVER = DEDICATED)
  (SERVICE_NAME = testdb.example)
  )

Bug Number

This issue is tracked with Oracle bug 38132893.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in interconnect network

DCS agent may not be able to run jobs because of an interconnect network issue.

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

Do the following:
  1. Validate that the issue is due to interconnect not working. From the first node, run the command:
    # arping -I icbond0 xx.xx.xx.xx -c 10
    The output is similar to the following:
    ARPING xx.xx.xx.xx from xx.xx.xx.xx icbond0
Sent 10 probes (10 broadcast(s))
Received 0 response(s)
  2. On both nodes, modify the /etc/sysconfig/network-scripts/ifcfg-icbond0 file to add arp_interval=100 to BONDING_OPTS. The update is as follows:
    BONDING_OPTS="mode=active-backup miimon=100 primary=p1p1 arp_interval=100"
  3. On both nodes, restart the network:
    # systemctl restart network
  4. On both nodes, restart the agent and wait for a few minutes:
    # systemctl restart initdcsagent

Bug Number

This issue is tracked with Oracle bug 37611921.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in configuring multiple standby databases on Oracle Data Guard

When configuring multiple standby databases for Oracle Data Guard on Oracle Database Appliance, an error may be encountered.

Problem Description

When you configure Oracle Data Guard for multiple standby databases, that is, two standby, the operation fails at the step Update Data Guard status (Existing standby site) but Oracle Data Guard is configured successfully with no issue. The command DGMGRL> SHOW CONFIGURATION; shows success status for all standby databases. The command odacli list-dataguardstatus on all sites shows correct Oracle Data Guard information.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: Unable to update dg config
The dcs-agent.log shows the temporary error:
"Error: ORA-16532: Oracle Data Guard broker configuration does not exist."

Hardware Models

All Oracle Database Appliance hardware models high-availability deployments

Workaround

Ignore the error. Oracle Data Guard was actually configured successfully.

Bug Number

This issue is tracked with Oracle bug 37780488.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in upgrading Oracle Data Guard

When upgrading Oracle Data Guard, an error may be encountered.

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.

The following error message is displayed:
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

For each service listed, do the following:
  1. Stop the service reported:
    srvctl stop service -d db_unique_name -service service_name
  2. Remove the service:
    srvctl remove service -d db_unique_name -service service_name

Bug Number

This issue is tracked with Oracle bug 36610040.

Parent topic: Known Issues When Managing Oracle Database Appliance

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.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in deleting a TDE-enabled database

When deleting a TDE-enabled database on Oracle Database Appliance, an error may be encountered.

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

Follow these steps:
  1. Log into as the Oracle Key Vault administrator to the Oracle Key Vault server where the Oracle Key Vault wallet is present.
  2. Navigate to the Keys & Wallets tab.
  3. Click the edit icon for the wallet that you want to delete.
  4. In the Select Endpoint/User Group section, select the Type as Users from the drop down list.
  5. Select the user that owns the Oracle Key Vault wallet.
  6. In the Select Access Level section, select Read and Modify, and then Manage Wallet.
  7. Click Save.
  8. Delete the database.

Bug Number

This issue is tracked with Oracle bug 36640379.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in configuring Oracle Data Guard

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

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.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in cleaning up a deployment

When cleaning up a Oracle Database Appliance, an error is encountered.

During cleanup, shutdown of Clusterware fails because the NFS export service uses Oracle ACFS-based clones repository.

Hardware Models

All Oracle Database Appliance hardware models with DB systems

Workaround

Follow these steps:
  1. Stop the NFS service on both nodes:
    service nfs stop
  2. Clean up the bare metal system. See the Oracle Database Appliance Deployment and User's Guide for your hardware model for the steps.

This issue is tracked with Oracle bug 33289742.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in display of file log path

File log paths are not displayed correctly on the console but all the logs that were generated for a job have actually logged the correct paths.

Hardware Models

All Oracle Database Appliance hardware models with virtualized platform

Workaround

None.

This issue is tracked with Oracle bug 33580574.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in the enable apply process after upgrading databases

When running the enable apply process after upgrading databases in an Oracle Data Guard deployment, an error is encountered.

The following error message is displayed:
Error: ORA-16664: unable to receive the result from a member

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. Restart standby database in upgrade mode: 
    srvctl stop database -d <db_unique_name> 
Run PL/SQL command: STARTUP UPGRADE;
  2. Continue the enable apply process and wait for log apply process to refresh.
  3. After some time, check the Data Guard status with the DGMGRL command:
    SHOW CONFIGURATION;

This issue is tracked with Oracle bug 32864100.

Parent topic: Known Issues When Managing Oracle Database Appliance

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.

Parent topic: Known Issues When Managing Oracle Database Appliance

Inconsistency in ORAchk summary and details report page

ORAChk report summary on the Browser User Interface may show different counts of Critical, Failed, and Warning issues than the report detail page.

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.

Parent topic: Known Issues When Managing Oracle Database Appliance

The odaeraser tool does not work if oakd is running in non-cluster mode

After cleaning up the deployment, the Secure Eraser tool does not work if oakd is running in non-cluster mode.

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.

Parent topic: Known Issues When Managing Oracle Database Appliance