HPE NonStop SQL/MX Error – 20297 The MODIFY request has completed successfully, but was directed not to start ORSERV. Please run FUP RELOAD to reclaim free space.

In this blog post, let’s learn about the error message “20297 The MODIFY request has completed successfully, but was directed not to start ORSERV. 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

20297 The MODIFY request has completed successfully, but was directed not to start ORSERV. Please run FUP RELOAD to reclaim free space.

Reason for the Error

The MODIFY utility was directed not to start ORSERV because the NO RECLAIM option was specified, but partitions involved in the operation require reloading.

Solution

Run FUP RELOAD manually to reclaim any free space on any partitions of the object if the D (INCOMPLETE SQLDDL OPERATION) or F (UNRECLAIMED FREE SPACE) flag is present for the partition. 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