Avoid overwriting a chunk
The chunks associated with each HCL OneDB™ instance are not known to other HCL OneDB instances. It is possible to inadvertently create a chunk on a file or device that is allocated as a chunk to another HCL OneDB instance, which results in data corruption.
If you attempt
to initialize an instance, where the ROOTPATH configuration parameter
specifies a file or device that is the root chunk of another instance,
the command fails with the following message in the online.log:
DISK INITIALIZATION ABORTED: potential instance overwrite detected.
To disable this initialization check, set the FULL_DISK_INIT configuration parameter to 1 in your configuration file and try to initialize the instance again. However, this initialization check is restricted to the root chunk. Adding dbspaces or chunks succeeds even when the file or device is allocated to another instance.