1. Release Notes
  2. Known Issues with Oracle Database Appliance in This Release

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.

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

Error in updating the operating system when patching the server

When patching the server, the operating system may not be updated.

The following error message is displayed:
DCS-10001:Internal error encountered: Failed to patch OS.
Run the following command:
rpm -q kernel-uek

If the output of this command displays multiple RPM names, then perform the workaround.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Remove the following RPMs:
# yum remove kernel-uek-4.14.35-1902.11.3.1.el7uek.x86_64
# yum remove kernel-uek-4.14.35-1902.301.1.el7uek.x86_64

This issue is tracked with Oracle bug 34154435.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in server patching

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

Failure Message

When the odacli update-server command is run, the following error message may be displayed: 

DCS-10057:Failed to run command systemctl restart kdump

Command Details

# odacli update-server

Hardware Models

All Oracle Database Appliance hardware models

Workaround

  1. Update the kernel version to V4.14.35-2047.524.2 or later as follows:
    1. Check the current version of the kernel.
      # uname -r
    2. If the current kernel version is earlier than V4.14.35-2047.524.2, then update the kernel on both nodes.
      rpm -ivh
    3. Locate the kernel RPM on the local system at /opt/oracle/oak/pkgrepos/os/19.20/osrpms. For example:
      rpm -ivh 
/opt/oracle/oak/pkgrepos/os/19.20/osrpms/kernel-uek-4.14.35-2047.524.5.el7uek.x86_64.rpm
    4. Restart the nodes.
  2. Modify the grub.conf file and run grub2-mkconfig as follows:
    1. Edit the /etc/default/grub.conf file and modify the crashkernel value:
      "crashkernel=1G-64G:512M,64G-:1024M"
    2. Run grub2-mkconfig:
      grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
    3. Restart the nodes.
  3. Run the odacli update-server command:
    /opt/oracle/dcs/bin/odacli update-server -v 19.20

Bug Number

This issue is tracked with Oracle bug 35446758.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in running prechecks for server patching

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

Problem Description

When patching the database home on an Oracle Database Appliance that has Oracle Data Guard configured, an error message may be displayed.

Failure Message

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

DCS-10001:Internal error encountered: One or more pre-checks failed. Run describe-prepatchreport for more details.

Command Details

# odacli create-prepatchreport

Hardware Models

All Oracle Database Appliance hardware models

Workaround

If your database home has databases configured with Oracle Data Guard and the protection mode is set to MAX PROTECTION or MAX AVAILABILITY, then patch the databases separately.

For the databases, run the prechecks and update the database as follows:
odacli create-prepatchreport -dbid databaseId -to destination_dbhomeid -db
odacli update-database -i databaseId -to  destination_dbhomeid

When any password-related error occurs on the standby system, copy the password file from the primary to the standby database.

Bug Number

This issue is tracked with Oracle bug 35516049.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in database home patching

When patching the database home, an error may be encountered.

Problem Description

When patching the database home on an Oracle Database Appliance that has Oracle Data Guard configured, an error message may be displayed.

Failure Message

If your database home has databases configured with Oracle Data Guard and the protection mode is set to MAX PROTECTION or MAX AVAILABILITY, then the following error message may be displayed when you patch the database home:

PRCD-1199: The stop request on instance {0} of standby database {1} was rejected to prevent termination of the primary database

Command Details

# odacli update-database -i databaseId -to  destination_dbhomeid

Hardware Models

All Oracle Database Appliance hardware models

Workaround

If your database home has databases configured with Oracle Data Guard and the protection mode is set to MAX PROTECTION or MAX AVAILABILITY, then set the protection mode to MAX PERFORMANCE.
  1. Before patching the DB home, for each associated database with Oracle Data Guard configured with protection mode MAX PROTECTION or MAX AVAILABILITY, run the following DGMGRL command:
    DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXPERFORMANCE;
  2. Patch the DB home.
  3. After the DB home patching is completed, set the Oracle Data Guard protection mode as needed. Set to MAX AVAILABILITY:
    DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
    Or, set to MAX PROTECTION:
    DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXPROTECTION;

Bug Number

This issue is tracked with Oracle bug 35332834.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in generating core dump and LKCE report during patching

When patching the database home, an error may be encountered.

Problem Description

The core dump and LKCE reports may not be generated for patched enviroment. In the console log, the entries for mdraid cannot be found and dracut-initqueue timeout entries are found.

Failure Message

The following error message may be displayed:

Warning: dracut-initqueue timeout - starting timeout scripts

Command Details

# odacli update-server

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Regenerate the kdump initramfs after the node restarts after patching.
# touch /etc/kdump.conf 
# systemctl restart kdump

Bug Number

This issue is tracked with Oracle bug 35661634.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in running prechecks for patching

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

Problem Description

When patching Oracle Database Appliance, an error message may be displayed.

If the number of open PDBs in a container database is not in between 0.1 times the value of target_pdb parameter + 1 and 10 times the value of target_pdbs parameter - 1, and if the prepatchreport is generated before updating the CDB or updating DB home containing the CDB, then an error is encountered.

Failure Message

When the odacli update-server command is run, the following error message is displayed in the prechecks report: 

AHF-6563: Database parameter target_pdbs is not set within best practice thresholds

Command Details

# odacli create-prepatchreport

Hardware Models

All Oracle Database Appliance high-availability hardware models

Workaround

Follow these steps:
  1. Connect to the SQL*Plus prompt:
    1. Switch to the DB user. For example, if the DB user is oracle, then run the following command:
      su - oracle
    2. Run .oraenv and set ORACLE_SID.
      . oraenv
          ORACLE_SID = [lowcdb2] ? lowcdb1
          The Oracle base remains unchanged with the value /u01/app/odaorabase/odaadmin
    3. Connect to SQL*Plus. be executing 'sqlplus / as sysdba' command.
      sqlplus / as sysdba
 
          SQL*Plus: Release 19.0.0.0.0 - Production on Mon XXX XX XX:XX:XX XXXX
          Version 19.19.0.0.0
 
          Copyright (c) 1982, 2022, Oracle.  All rights reserved.
 
          Connected to:
          Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
          Version 19.19.0.0.0
 
          SQL>
  2. Identify the number of open PDBs in the CDB:
    SQL> select count(*) from v$pdbs where name not like 'PDB$SEED' and open_mode like 'READ WRITE';

       COUNT(*)
     ----------
              1
  3. Set the target_pdbs parameter to a value which is 10 times the number of open PDBs - 1. For example, if number of open PDBs is 1, then the value of target_pdbs must be set to 9 (1x10 - 1). Note that for Oracle RAC databases, the 'ttarget_pdbs parameter must be set on both nodes.
    SQL> alter system set target_pdbs=<10 x number_of_open_pdbs-1> scope=spfile sid='*';
  4. Exit from the SQL prompt:
    SQL> exit
     Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
     Version 19.19.0.0.0
  5. Stop the database by running the srvctl stop database -db db_unique_name command.
  6. Start the database by running the srvctl start database -db db_unique_name command.

Bug Number

This issue is tracked with Oracle bug 35587396.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in running jobs

When upgrading a database, an error may be encountered.

Problem Description

When running jobs, the DCS agent may not be registered correctly during bootstrap and the job may fail with error DCS-10058.

Failure Message

The following error message is displayed:

DCS-10058:DCS Agent is not running on all nodes.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

  1. Restart the DCS agent service with the following command on both nodes in sequential order, starting from the first node:
    # systemctl restart initdcsagent
  2. Retry the command that failed earlier.

Bug Number

This issue is tracked with Oracle bug 35056432.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in upgrading a database

When upgrading a database, an error may be encountered.

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 Provisioning 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

  1. Verify that the odacli list-dbstorages command displays null for the redo location for the database that reported the error. For example, the following output displays a null or empty value for the database unique name F.
    # odacli list-dbstorages

ID                                     Type   DBUnique Name  Status     
Destination Location  Total      Used       Available      
---------------------------------------- ------ --------------------
...
...
...
198678d9-c7c7-4e74-9bd6-004485b07c14     ASM    F            CONFIGURED   
DATA    +DATA/F  4.89 TB    1.67 GB    4.89 TB                                                                   
REDO    +REDO/F  183.09 GB  3.05 GB    180.04 GB                                                                                
RECO             8.51 TB              
...
...
...

    In the above output, the RECO record has a null value.

  2. Manually create the RECO directory for this database. If the database unique name is dbuniq, then run the asmcmd command as the grid user.
    asmcmd
  3. Run the mkdir command.
    asmcmd> mkdir +RECO/dbuniq
  4. Verify that the odacli list-dbstorages command output does not display a null or empty value for the database.
  5. Rerun the odacli upgrade-database command.

Bug Number

This issue is tracked with Oracle bug 34923078.

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

Error in server patching

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

Problem Description

When converting Oracle Clusterware resource type on KVM virtual machines, an error message may be displayed.

Failure Message

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

DCS-10001:Internal Error encountered: (...), caused by:
CRS-2510: Resource 'ora.data.acfs_resource.acfs' used in dependency 'hard'
does not exist or is not registered.
CRS-2514: Dependency attribute specification 'hard' is invalid in resource
'vm_resource.kvm'
CRS-4000: Command Add failed, or completed with errors.

Command Details

# odacli update-server

Hardware Models

All Oracle Database Appliance hardware models

Workaround

  1. List and identify DB systems with FAILED status:
    # odacli list-dbsystems
  2. Delete the DB systems with FAILED status:
    # odacli delete-dbsystem -n dbsystem_name -f
  3. Retry the command that failed earlier.

Bug Number

This issue is tracked with Oracle bug 35060579.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in server patching during DB system patching

When patching the server during DB system patching to Oracle Database Appliance release 19.15, an error may be encountered.

The following error message is displayed:
ORA-12559: Message 12559 not found;  product=RDBMS; facility=ORA

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Retry server patching on the DB system.

This issue is tracked with Oracle bug 34153158.

Parent topic: Known Issues When Patching Oracle Database Appliance

Component version not updated after patching

After patching the server to Oracle Database Appliance release 19.16, 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

Detaching of databases with additionally configured services not supported by odaugradeutil

When running odaugradeutil in the Data Preserving Reprovisioning process, if there are additionally configured services, then databases cannot be detached.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Additional services must be deleted to complete the detach operation by running the command srvctl remove service. If these services are required, then before removing the service, the metadata must be captured manually and then the services must be recreated on the system running Oracle Database Appliance release 19.15 using the srvctl command from the appropriate database home.

This issue is tracked with Oracle bug 33593287.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in restore node process in Data Preserving Reprovisioning

In the Data Preserving Reprovisioning process, during node restore, an error may be encountered.

If incorrect VIP names or VIP IP addresses are configured, then the detach completes successfully but the command odacli restore-node -g displays a validation error. This is because the earlier releases did not validate VIP names or VIP IP addresses before provisioning.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:

Manually edit the file /opt/oracle/oak/restore/metadata/provisionInstance.json with the correct VIP names or VIP IP addresses. Retry the command odacli restore-node -g. For fixing VIP names or VIP IP addresses, nslookup can be used to query hostnames and IP addresses.

This issue is tracked with Oracle bug 34140344.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in restore node process in Data Preserving Reprovisioning

In the Data Preserving Reprovisioning process, during node restore, an error may be encountered.

The following error message may be displayed:
DCS-10045: groupNames are not unique.

This error occurs if the source Oracle Database Appliance is an OAK version. This is because on the DCS stack, the same operating system group is not allowed to be assigned two or more roles.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:

Manually edit the file /opt/oracle/oak/restore/metadata/provisionInstance.json with unique group names for each role. Retry the command odacli restore-node -g.

This issue is tracked with Oracle bug 34042493.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error messages in log entries in Data Preserving Reprovisioning

In the Data Preserving Reprovisioning process, during node restore, the log entries may display error messages though the overall status of the job is displayed as SUCCESS.

For Oracle Database Appliance running the DCS stack starting with Oracle Database Appliance release 12.2.1.4.0, the command odacli restore-node -d performs a set of ignorable tasks. Failure of these tasks does not affect the status of the overall job. The output of the command odacli describe-job may report such failures. These tasks are:
Restore of user created networks
Restore of object stores
Restore of NFS backup locations
Restore of backupconfigs
Relinking of backupconfigs to databases
Restore of backup reports

In the sample output above, even if these tasks fail, the overall status of the job is marked as SUCCESS.

Hardware Models

All Oracle Database Appliance hardware models being upgraded using the Data Preserving Reprovisioning process

Workaround

Investigate the failure using the dcs-agent.log, fix the errors, and then retry the command odacli restore-node -d.

This issue is tracked with Oracle bug 34512193.

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.20, if the Security Technical Implementation Guidelines (STIG) V1R2 is already deployed, then when you patch to 19.20 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.20, 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.20.0.0.0 -f

This issue is tracked with Oracle bug 33144170.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error in patching prechecks report

The patchung 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 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.

Parent topic: Known Issues When Patching Oracle Database Appliance

Error message displayed even when patching Oracle Database Appliance is successful

Although patching of Oracle Database Appliance was successful, an error message may be displayed.

The following error is seen when running the odacli update-dcscomponents command: 
# time odacli update-dcscomponents -v 19.20.0.0.0 
^[[ADCS-10008:Failed to update DCScomponents: 19.20.0.0.0
Internal error while patching the DCS components : 
DCS-10231:Cannot proceed. Pre-checks for update-dcscomponents failed. Refer  
to /opt/oracle/dcs/log/-dcscomponentsPreCheckReport.log on node 1 for  
details.

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.

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 a DB system

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

Problem Description

When creating a DB system, the following errors may be encountered:
  • The odacli create-dbsystem job may be stuck in the running status for a long time.
  • Other DB system or application VM lifecycle operations such as create, start, or stop VM jobs may be stuck in the running status for a long time.
  • Any virsh command such as virsh list command process may not respond.
  • The command ps -ef | grep libvirtd displays that there are two libvirtd processes. For example:
    # ps -ef |grep libvirtd
root      5369     1  0 05:27 ?        00:00:03 /usr/sbin/libvirtd
root     27496  5369  0 05:29 ?        00:00:00 /usr/sbin/libvirtd  <<<

    The second libvirtd process (pid 27496) is stuck and causes the job hang.

Command Details

# odacli create-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Delete the second libvirtd, that is, the one spawned by the first libvirtd, for example, pid: 27496 in the above example.

Bug Number

This issue is tracked with Oracle bug 34715675.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in creating vnetwork on a DB System

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

Problem Description

When creating a vnetwork with name length of 14 or 15 without providing a bridge name, an error message may be displayed.

Failure Message

The following error message may be displayed in dcs-agent.log: 

Device xxxxx does not seem to be present, delaying initialization.

Command Details

# odacli create-vnetwork

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Use a vnetwork name with 13 or less characters or provide a bridge name with less than 15 characters

Bug Number

This issue is tracked with Oracle bug 35668001.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in detaching vnetwork on a DB System

When detaching a vnetwork on a DB system, an error may be encountered.

Failure Message

The following error message may be displayed:

DCS-10001:Internal error encountered: Could not delete network 'dbs_vlan': null.

The dbvm agent logs may contain the following entries:

PRCR-1028 : Failed to remove resource ora.SCAN_LISTENER2_SCAN1_NET2.lsnr
PRCR-1072 : Failed to unregister resource ora.SCAN_LISTENER2_SCAN1_NET2.lsnr
CRS-2586: Deletion of a running resource 'ora.SCAN_LISTENER2_SCAN1_NET2.lsnr' requires the force option
2023-07-21 03:28:28,092 ERROR [Remove listeners for network {dbs_vlan}] [] c.o.d.a.r.s.n.NetworkLifecycleUtils: 
PRCR-1028 : Failed to remove resource ora.SCAN_LISTENER2_SCAN1_NET2.lsnr

Command Details

# odacli modify-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Run the odacli modify-dbsystem command again.

Bug Number

This issue is tracked with Oracle bug 35628863.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in running odacli modify-dbsystem on a DB System

When running the odacli modify-dbsystem command on a DB system, an error may be encountered.

Failure Message

The following error message may be displayed:

DCS-10001:Internal error encountered: Invalid nodeId, the format is as 'node_#'.

Command Details

# odacli modify-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Do not run the odacli modify-dbsystem command in a failed state.

Bug Number

This issue is tracked with Oracle bug 35630118.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in attaching vnetwork on a DB System

When attaching a vnetwork that was previously attached on a DB system, an error may be encountered.

Failure Message

The following error message may be displayed:

DCS-10045:Validation error encountered: The scan name specified is not consistent with the corresponding network {dbs_vlan} on node 1.

Command Details

# odacli modify-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

None. Contact Oracle Support.

Bug Number

This issue is tracked with Oracle bug 35630911.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error in DB System creation

When creating a DB system with mixed-case letters in the oracle user name, an error may be encountered.

Failure Message

The following error message may be displayed in the DBCA trace file:

ORA-15260: permission denied on ASM disk group

Command Details

# odacli create-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Do not specify mixed-case letters in the oracle user name when you create a DB system.

Bug Number

This issue is tracked with Oracle bug 35647573.

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 creating DB system

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

When running the odacli create-dbsystem command, the following error message may be displayed:
DCS-10001:Internal error encountered: ASM network is not online in all nodes

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. Manually bring the offline resources online:
    crsctl start res -all
  2. Run the odacli create-dbsystem command.

This issue is tracked with Oracle bug 33784937.

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 when upgrading database from 11.2.0.4 to 12.1 or 12.2

When upgrading databases from 11.2.0.4 to 12.1 or 12.2, an error is encountered.

Database upgrade can cause the following warning in the UpgradeResults.html file, when upgrading database from 11.2.0.4 to 12.1 or 12.2: 
Database is using a newer time zone file version than the Oracle home

Hardware Models

All Oracle Database Appliance bare metal deployments

Workaround

  1. Refer to the Database Upgrade Guide for manual steps for fixing the time zone.
  2. After manually completing the database upgrade, run the following command to update DCS metadata:
    /opt/oracle/dcs/bin/odacli update-registry update-registry -n db -f

This issue is tracked with Oracle bug 31125985.

Parent topic: Known Issues When Deploying Oracle Database Appliance

Error when upgrading 12.1 single-instance database

When upgrading 12.1 single-instance database, a job failure error is encountered.

Hardware Models

All Oracle Database Appliance hardware models bare metal deployments

Workaround

Use the following workaround:
  1. Before upgrading the 12.1 single-instance database, run the following PL/SQL command to change the local_listener to an empty string: 
    ALTER SYSTEM SET LOCAL_LISTENER='';
  2. After upgrading the 12.1 single-instance database successfully, run the following PL/SQL command to change the local_listener to the desired value: 
    ALTER SYSTEM SET LOCAL_LISTENER='-oracle-none-';

This issue is tracked with Oracle bugs 31202775 and 31214657.

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

Clone database operation fails

For Oracle Database release 12.1 databases, the database clone creation may fail because the default compatible version from Oracle binaries was set to 12.0.0.0.0

Hardware Models

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

Workaround

Set the compatible value to that of the source database. Follow these steps:
  1. Change the parameter value.
    SQL> ALTER SYSTEM SET COMPATIBLE = '12.1.0.2.0' SCOPE=SPFILE;
  2. Shut down the database.
    SQL> SHUTDOWN IMMEDIATE
  3. Start the database.
    SQL> Startup
  4. Verify the parameter for the new value.
    SQL> SELECT name, value, description FROM v$parameter WHERE name ='compatible';

This issue is tracked with Oracle bug 30309914.

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 recovery of database

When recovering an Oracle Database Enterprise Edition High Availability database from node 0, with target node as 1, an error may be encountered.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: null

Command Details

# odacli recover-database

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Retry the operation from the target node number of the database.

Bug Number

This issue is tracked with Oracle bug 34785410.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in scaling up database

When scaling up an Oracle Database Enterprise Edition database with High Availability enabled or disabled, if the job is run on the node where the database is not running, an error may be encountered.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: Timeout waiting for event 'Check database dbname is running' after 300000 ms.

Command Details

# odacli create-dbsystem

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Run the job on the node where the database is running.

Bug Number

This issue is tracked with Oracle bug 35695194.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in switchover operation on Oracle Data Guard

When running the odacli switchover-dataguard command, an error may be encountered.

Problem Description

The odacli switchover-dataguard job sometimes fails at step "Postcheck switchover DataGuard" but switchover operation is in fact successful.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: Index: 0, Size: 0

Command Details

# odacli switchover-dataguard

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Ignore the error. Verify from DGMGRL to see if Oracle Data Guard switchover operation was successful.
 DGMGRL> show configuration;

Run odacli list-dataguardstatus to update Oracle Data Guard status metadata.

Bug Number

This issue is tracked with Oracle bug 35675411.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in Oracle Data Guard operations on Oracle Database Appliance

When running switchover, failover, or reinstate operations on Oracle Data Guard, an error may be encountered.

Problem Description

On Oracle Database Appliance high-availability deployments, for databases with dbType SI and RACOne, the switchover-dataguard, failover-dataguard, and reinstate-dataguard job may fail at step "Check if DataGuard config is updated" after a waiting time.

Failure Message

The following error message is displayed:

DCS-10001:Internal error encountered: Unable enqueue Id and update DgConfig.

Command Details

# odacli switchover-dataguard
# odacli failover-dataguard
# odacli reinstate-dataguard

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Ignore the error. Verify from DGMGRL to see if Oracle Data Guard switchover, failover, or reinstate operation was successful.
 DGMGRL> show configuration;

Run odacli list-dataguardstatus to update Oracle Data Guard status metadata.

Bug Number

This issue is tracked with Oracle bug 35676752.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in configuring Oracle Data Guard

When running the command odacli configure-dataguard on Oracle Database Appliance, an error may be encountered at the upload password file to standby database step.

When running the command odacli configure-dataguard on Oracle Database Appliance, the following error message may be displayed at CONFIGUREDG - DCS-10001: UNABLE TO CONFIGURE BROKER DGMGRL> SHOW CONFIGURATION;:
ORA-16783: cannot resolve gap for database tgtpodpgtb

Hardware Models

Oracle Database Appliance hardware models with DB system and database version earlier than Oracle Database Appliance release 19.15

Workaround

Manually copy the password file from primary to standby system and retry the command odacli configure-dataguard with the --skip-password-copy option.
  1. On the primary system, locate the password file:
    srvctl config database -d dbUniqueName | grep -i password
    If the output is the Oracle ASM directory, then copy the password from the Oracle ASM directory to the local directory.
    su - grid
asmcmd
ASMCMD> pwcopy +DATA/tiger2/PASSWORD/orapwtiger /tmp/orapwtiger

    If the output is empty, then check the directory at /dbHome/dbs/orapwdbName. For example, the orapwd file can be at /u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger

  2. Copy the password file to the standby system. Back up the original password file.
    /u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger
/u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger.ori
scp  
root@primaryHost:/u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger
/u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger
  3. Change the standby orapwd file permission.
    chown -R oracle /u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger
chgrp oinstall /u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger
  4. Check the password file location on the standby system and copy to the Oracle ASM directory, if necessary.
    srvctl config database -d tiger2 | grep -i password
Password file: +DATA/tiger2/PASSWORD/orapwtiger
    In this example, copy the password from the local directory to the Oracle ASM directory.
    su - grid
asmcmd
ASMCMD> pwcopy /u01/app/oracle/product/19.0.0.0/dbhome_1/dbs/orapwtiger
+DATA/tiger2/PASSWORD/orapwtiger

This issue is tracked with Oracle bug 34484209.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in backup of database

When backing up a database on Oracle Database Appliance, an error is encountered.

After successful failover, running the command odacli create-backup on new primary database fails with the following message:
DCS-10001:Internal error encountered: Unable to get the
rman command status commandid:xxx
output:STATUS
-------------------------
[COMPLETED WITH WARNINGS] error:.

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Follow these steps:
  1. On the new primary database, connect to RMAN as oracle and edit the archivelog deletion policy.
    rman target /
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE';
  2. On the new primary database, as the root user, take a backup:
    odacli create-backup -in db_name -bt backup_type

This issue is tracked with Oracle bug 33181168.

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 configuring Oracle Data Guard

After upgrading the standby database from release 12.1 to 19.14, the following error message may be displayed at step Enable redo transport and apply. 

Warning: ORA-16629: database reports a different protection level from the protection mode standbydb - Physical standby database (disabled)

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Enable the standby database again by running the following DGMGRL command:
DGMGRL> Enable database tgtptdcnvo
Enabled.

This issue is tracked with Oracle bug 33749492.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in reinstate operation on Oracle Data Guard

When running the command odacli reinstate-dataguard on Oracle Data Guard an error is encountered.

Following are the errors reported in dcs-agent.log:
DCS-10001:Internal error encountered: Unable to reinstate Dg." and can 
further find this error "ORA-12514: TNS:listener does not currently know of  
service requested

Hardware Models

All Oracle Database Appliance hardware models

Workaround

Ensure that the database you are reinstating is started in MOUNT mode.

To start the database in MOUNT mode, run this command: 
srvctl start database -d db-unique-name -o mount

After the command completes successfully, run the command odacli reinstate-dataguard job. If the database is already in MOUNT mode, this can be an temporary error. Check the Data Guard status again a few minutes later with odacli describe-dataguardstatus or odacli list-dataguardstatus, or check with DGMGRL> SHOW CONFIGURATION; to see if the reinstatement is successful.

This issue is tracked with Oracle bug 32367676.

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 creating Oracle Data Guard status

When configuring Oracle Active Data Guard on Oracle Database Appliance, an error is encountered.

When configuring Oracle Data Guard, the odacli configure-dataguard command fails at step NewDgconfig with the following error on the standby system:
ORA-16665: TIME OUT WAITING FOR THE RESULT FROM A MEMBER

Verify the status of the job with the odacli list-jobs command.

Hardware Models

All Oracle Database Appliance hardware models with Oracle Data Guard configuration

Workaround

Follow these steps:

  1. On the standby system, run the following: 
    export DEMODE=true; 
odacli create-dataguardstatus -i dbid -n dataguardstatus_id_on_primary -r configdg.json 
export DEMODE=false; 
configdg.json example
Example configdg.json file for a single-node system:
{
  "name": "test1_test7",
  "protectionMode": "MAX_PERFORMANCE",
   "replicationGroups": [
    {
      "sourceEndPoints": [
        {
          "endpointType": "PRIMARY",
          "hostName": test_domain1",
          "listenerPort": 1521,
          "databaseUniqueName": "test1",
          "serviceName": "test", 
          "sysPassword": "***", 
          "ipAddress": "test_IPaddress"
        },
         ],
      "targetEndPoints": [
        {
          "endpointType": "STANDBY",
          "hostName": "test_domain2",
          "listenerPort": 1521,
          "databaseUniqueName": "test7",
          "serviceName": "test", 
          "sysPassword": "***", 
          "ipAddress": "test_IPaddress3"
        },
      ],
      "transportType": "ASYNC"
    }
  ]
}

This issue is tracked with Oracle bug 32719173.

Parent topic: Known Issues When Managing Oracle Database Appliance

Error in Reinstating Oracle Data Guard

When reinstating Oracle Data Guard on Oracle Database Appliance, an error is encountered.

The odacli reinstate-dataguard command fails with the following error:
Unable to reinstate Dg. Reinstate job was executed within 24hrs after failover job.

The dcs-agent.log file has the following error entry:

DGMGRL> Reinstating database "xxxx", 
 please wait... 
Oracle Clusterware is restarting database "xxxx" ... 
Connected to "xxxx" 
Continuing to reinstate database "xxxx" ... 
Error: ORA-16653: failed to reinstate database

Hardware Models

All Oracle Database Appliance hardware models with Oracle Data Guard configuration

Workaround

Follow these steps:

  1. On the primary machine, get the standby_became_primary_scn:
    SQL> select standby_became_primary_scn from v$database; 
STANDBY_BECAME_PRIMARY_SCN 
-------------------------- 
          3522449
  2. On the old primary database, flashback to this SCN with RMAN with the backup encryption password:
    RMAN> set decryption identified by 'rman_backup_password' ; 
executing command: SET decryption 
RMAN> FLASHBACK DATABASE TO SCN 3522449 ; 
... 
Finished flashback at 24-SEP-20 
RMAN> exit
  3. On the new primary machine, run the odacli reinstate-dataguard command.

This issue is tracked with Oracle bug 31884506.

Parent topic: Known Issues When Managing Oracle Database Appliance

Failure in Reinstating Oracle Data Guard

When reinstating Oracle Data Guard on Oracle Database Appliance, an error is encountered.

The odacli reinstate-dataguard command fails with the following error:
Message:   
DCS-10001:Internal error encountered: Unable to reinstate Dg.

The dcs-agent.log file has the following error entry:

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Hardware Models

All Oracle Database Appliance hardware models with Oracle Data Guard configuration

Workaround

Follow these steps:

  1. Make sure the database you are reinstating is started in MOUNT mode. To start the database in MOUNT mode, run this command:
    srvctl start database -d db-unique-name -o mount
  2. After the above command runs successfully, run the odacli reinstate-dataguard command.

This issue is tracked with Oracle bug 32047967.

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