In general, DDL operations on the DB require an exclusive lock on the table. ALTIBASE HDB uses a network-based redundancy technique in which data is matched by transmitting the transaction log generated in the local server to the other server.
DDL-like operations are not sent to the log, so DDL operations are not replicated. Therefore, different from the disk sharing method, a different method of performing DDL operations on each node (Server) is required.
ALTIBASE HDB supports different types of DDL statements depending on the version, and the functions of DDL statements related to replication are also different.
In the case of simple DDL operation, the operation procedure in this document can be used as it is in ALTIBASE HDB 4.3.9, but it is mainly described for ALTIBASE HDB 5.3.3 or later.
If there is a possibility that a large amount of data change may occur due to the DDL statement, other safer operation procedures should be used, and please refer to the DDL Guide of ALTIBASE Replication Environment.
Operation under service outages
In an environment where all services accessing the database can be stopped for a certain period of time, it can be completed with a relatively simple procedure.
Operation under uninterrupted constraints
In an environment that requires uninterrupted service, there may be a limitation that one node must alternately work one node at a time while operating the database.
Under these conditions, compared to the environment in which service disruption described above is possible, several steps are required and caution may be required.
- Please refer to the DDL guide document of the ALTIBASE replication environment.
- Get technical support from ALTIBASE Technical Support Division (Service Portal:http://support.altibase.com/en/, TEL +82-2-2082-1114)