ExaCS|ExaCC: DB patching fails from UI :Error [Invalid Patch Txn Status received from smwrapper Failed: -apply_async]
(Doc ID 2771432.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/AInformation in this document applies to any platform.
Symptoms
DB patch application initiated from UI fails
24-abr-2021 14H31' UTC Phase initialize completed
24-abr-2021 14H31' UTC APPLY_PATCH job [5066753] initiated by [<name>@<domain>l] started...
24-abr-2021 14H31' UTC Patching of Database Cloud Service is in progress with patch [2021-04-24 10:31]
24-abr-2021 14H31' UTC Failed to perform patching of Database Cloud Service with patch [32131241]. Error [Invalid Patch Txn Status received from smwrapper Failed: -apply_async]. Please look at Database Cloud Service patch logs for more details.
24-abr-2021 14H31' UTC Failed
24-abr-2021 14H31' UTC Activity Ended
24-abr-2021 14H31' UTC APPLY_PATCH job [5066753] initiated by [<name>@<domain>l] started...
24-abr-2021 14H31' UTC Patching of Database Cloud Service is in progress with patch [2021-04-24 10:31]
24-abr-2021 14H31' UTC Failed to perform patching of Database Cloud Service with patch [32131241]. Error [Invalid Patch Txn Status received from smwrapper Failed: -apply_async]. Please look at Database Cloud Service patch logs for more details.
24-abr-2021 14H31' UTC Failed
24-abr-2021 14H31' UTC Activity Ended
There are no exadbcpatch log file generated under /var/opt/oracle/log/exadbcpatch for the failed operation
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |