Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Desired behaviour or bug? RECLAIM DATAVOLUME / -fl #40

Open
spiezmaestro opened this issue Jun 15, 2023 · 0 comments
Open

Desired behaviour or bug? RECLAIM DATAVOLUME / -fl #40

spiezmaestro opened this issue Jun 15, 2023 · 0 comments

Comments

@spiezmaestro
Copy link

spiezmaestro commented Jun 15, 2023

Hi,

The parameter -fl is described as:

-fl fragmentation limit [%], maximum fragmentation of data volume files, of any service, before defragmentation of that
service is started: ALTER SYSTEM RECLAIM DATAVOLUME ':' 120 DEFRAGMENT, default: -1 (not used)
Note: If you use System Replication see Q19 in SAP Note 1999880.

This means, that when parameter -fl is set to e.g. 110, the check is made if a reclaim needs to be done (defrag > 110%) and when so, a reclaim datavolume 120 defragment is executed.

Should this not be a reclaim datavolume 110? What purpose could the check for a specific value have, when always a reclaim datavolume 120 is executed anyway?

Therefore the question, desired behaviour (in which case we will need to change the hardcoded 120 with our desired value) or a bug?

Thanks a lot!

Cheers.

@spiezmaestro spiezmaestro changed the title Desired behaviour oder bug? RECLAIM DATAVOLUME / -fl Desired behaviour or bug? RECLAIM DATAVOLUME / -fl Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant