Many "I already changed the parameter, why is the result still the old one?" situations in a gbase database aren't about the parameter failing to take effect — they're about not understanding the boundary: is it session‑level or system‑level? When exactly does it activate? Does the session need to reconnect or the cluster need to restart?

Three Parameter Classes by Activation Boundary

Class

Meaning

When It Takes Effect