HPE NonStop SQL/MX Error – 20295 The MODIFY request has completed successfully, but ORSERV failed. Please run FUP RELOAD to reclaim free space.

In this blog post, let’s learn about the error message “20295 The MODIFY request has completed successfully, but ORSERV failed. Please run FUP RELOAD to reclaim free space.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20295 The MODIFY request has completed successfully, but ORSERV failed. Please run FUP RELOAD to reclaim free space.

Reason for the Error

The MODIFY utility has completed, but it failed to start ORSERV (the FUP RELOAD operation) successfully. The failures are reported in separate error messages. If the failures were caused by the MODIFY process being killed inadvertently, the warning message is issued by the RECOVER utility during the recovery.

Solution

Run FUP RELOAD manually to reclaim free space on the specified partitions if the D or F flag is present for the partitions. Use the FUP INFO or SHOWLABEL utility to see if the D or F flag is set

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022