KB44284: "Failed to execute: %1" error appears when upgrading Metadata in Oracle on a Linux machine from MicroStrategy 9.3.0 or older to 9.4.x-10.x

SYMPTOM: 
"Failed to execute: %1" error appears when upgrading Metadata in Oracle on a Linux machine from 9.3.0 or older to 9.4.x-10.x, as shown below:

Failed to execute: '%1'
Unknown failed. Unable to connect.
Error type: System call error. Error communicating with connection process. Find target process dead while sending a message.

Following entries may be found in the DSSErrors.log file:

[HOST:xxx][PID:xxx][THR:xxxxxxxxxx][MultiProcess][Error] Failed to write to pipe.
System Error (EPIPE): --- Broken pipe
[HOST:xxx][PID:xxx][THR:xxxxxxxxxx][MultiProcess][Error] Find target process dead while sending a message.
[HOST:xxx][PID:xxx][THR:xxxxxxxxxx][Database Classes][Error] Unknown failed. Unable to connect.
Error type: System call error. Error communicating with connection process. Find target process dead while sending a message.

 
CAUSE:
A possible reason of the issue is that a non-unicode database is used as the metadata.
From Strategy 9.3.1, the Oracle database used as Metadata is supported for Unicode databases ONLY (refer to 9.4.0 Release Note: https://resource.microstrategy.com/support/releasenote/9.4.0/ReleaseNotes/ReadAll_8.htm).
ACTION: 
Use a unicode database as the metadata.