Mass Loading and Deleting Records in a Cluster
In Adabas Cluster, you can adds records to, or delete records from a file in a database on the primary node of a cluster environment with the mass update utility ADAMUP.
Loading records on a secondary node will be rejected with the following error message:
ADABCK-E-CLUSTER, In a cluster this operation is only allowed on the primary node
The input files (MUPISN, MUPDVT, MUPDTA) are automatically replicated to all secondary nodes. The ADAMUP output shows in the nucleus log on the secondary nodes.
If a secondary node loses connection to the cluster before the load is replicated, the ADABAS file remains invalid.
If you are to use ADAMUP on a single node, perform an ADABCK dump beforehand.
When a file is successfully loaded on or deleted from the cluster, copies of the input files are stored in the database directory on the secondary nodes. You can specify a different directory with the environment variable ADA_CLUSTER_FILE_DIR. The copies on the secondary nodes is deleted after a successful load or delete.
Ensure that sufficient space is available in the database of the secondary nodes or the custom directory with the nucleus parameter OPTIONS=AUTO_EXPAND.
The following example shows how to load data in a cluster:
1. Display cluster status.
# Display cluster status:
bash-4.4$
adaopr db=100 di=clu
%ADAOPR-I-STARTED, 22-JAN-2025 11:18:53, Version 7.x.0.0 (Linux 64Bit)
Database 100, startup at 22-JAN-2025 11:11:37
ADANUC Version 7.4.0.0, PID 834425
ADANUC Version 7.4.0.0
Database 100 Cluster on 22-JAN-2025 11:18:53
Cluster UUID 445b4b6f-d8a9-11ef-806f-ce3e52ae5641
view was last updated at sequence number 4
cluster node is at sequence number 8
3 Node(s) Primary component of the cluster
Name ADATCP Status Seqno
---- ------ ------ -----
redada6c-25101 adatcp://redada6c.eur.ad.sag:26101 SYNCED 8
redada6c-25100 adatcp://redada6c.eur.ad.sag:26100 SYNCED 8
redada6c-25102 adatcp://redada6c.eur.ad.sag:26102 SYNCED 8
Primary node: redada6c-25100
Current node: redada6c-25100 Cluster_Log_Level: DEBUG
%ADAOPR-I-TERMINATED, 22-JAN-2025 11:18:53, elapsed time: 00:00:002
2. Load data on the primary node. (The file was empty)
export MUPDTA=ULDDTA;export MUPDVT=ULDDVT;adamup db=100 update=11,add
%ADAMUP-I-STARTED, 22-JAN-2025 11:13:30, Version 7.x.0.0 (Linux 64Bit)
%ADAMUP-I-DBON, database 100 accessed online
%ADAMUP-I-DSUPD, data storage being modified
%ADAMUP-I-DSDONE, data storage completed
%ADAMUP-I-SRTWPSZE, work pool size 4000000 bytes
%ADAMUP-I-SORTDESC, sorting descriptor S3
%ADAMUP-I-LOADDESC, loading descriptor S3
%ADAMUP-I-SORTDESC, sorting descriptor S2
%ADAMUP-I-LOADDESC, loading descriptor S2
...
%ADAMUP-I-SORTDESC, sorting descriptor PH
%ADAMUP-I-LOADDESC, loading descriptor PH
%ADAMUP-I-DVTPASSES, DVT records processed 12 times
%ADAMUP-I-ADDREC, file 11, 1107 records added
%ADAMUP-I-IOCNT, 27 IOs on dataset MUPDTA
%ADAMUP-I-IOCNT, 372 IOs on dataset MUPDVT
%ADAMUP-I-IOCNT, 3 IOs on dataset DATA
%ADAMUP-I-IOCNT, 47 IOs on dataset ASSO
%ADAMUP-I-TERMINATED, 22-JAN-2025 11:13:31, elapsed time: 00:00:01