Open Bugs for Linux for Arm (aarch64) for Oracle Database 19c

This section contains information about issues related to Linux for Arm (aarch64) for Oracle Database 19c:

• Bug 34398211
  
• Bug 34501504
  
• Bug 34485708
  
• Bug 35386579
  

Bug 34398211

Adding a node from grid fails due to SSH configuration issue and returns the following error:

[INS-06003] Failed to setup passwordless SSH connectivity with the following
node(s): node1, node2

Workaround:

Passwordless SSH configuration is a mandatory installation requirement. SSH is used during installation to configure cluster member nodes, and SSH is used after installation by configuration assistants, Oracle Enterprise Manager, Opatch, and other features.

If the system has OpenSSH 7.8 or later configured, then the Automatic Passwordless SSH configuration using OUI fails.

Manually setup SSH to the node that you want to add before performing the addnode operation.

Bug 34501504

If the shell TZ environment variable is not in sync with the clusterware timezone, then the data might not be displayed as part of oclumon dumpnodeview.

Workaround:

Set the TZ environment variable based on the clusterware timezone.

Bug 34485708

Deleting a node from grid fails due to SSH configuration issue and returns the following error:

[PILOT-00452] Unable to establish SSH connection to node1 to execute command
"Grid_home/deinstall/deinstall" 
CAUSE: An attempt to connect to specified node to execute specified command using SSH failed. 
ACTION: Make sure that the specified node is reachable and the SSH daemon on the specified
node is alive.

Workaround:

Update OpenSSH format to RSA format by running the following command on all nodes:

ssh-keygen -p -f private_key_location -m pem
Example: ssh-keygen -p -f ~/.ssh/id_rsa -m pem

Bug 35386579

While you migrate a PDB from source release 19.19 RU (Linux x86-64 and Microsoft Windows x64) to target release Linux for Arm (aarch64), you may encounter the following issue at aarch64 while trying to restore the foreign PDB from the backup set:

- database (19.0.0.0.0 1.8) does not match that of the oracle executable (19.0.0.0.230117 1.8)

Workaround:

Run the following SQLs to resolve the issue:

SQL> alter session set "_ORACLE_SCRIPT"=true;
Session altered.

SQL> DECLARE n varchar2(100);

BEGIN
n := dbms_java_test.funcall('-rujs', ' ');
initjvmaux.validate_javavm;
END;
/

  2    3    4    5    6    7    8    9

PL/SQL procedure successfully completed.

SQL> select dbms_java.get_jdk_version from dual; 

GET_JDK_VERSION

------------
1.8.0_371