Under normal circumstances, you will not need to add or remove catalog dbspaces, as catalog dbspace files automatically grow as needed. However, if your catalog dbspace file is on constrained storage, you may need to add a new catalog dbspace to accommodate catalog data.
Shut down all servers in the multiplex.
Start the coordinator in single node mode using -iqmpx_sn 1. For example:
start_iq @params.cfg mpxtest.db -iqmpx_sn 1 -n mpxnode_c
Create the dbspace.
CREATE DBSPACE DspCat2 AS 'sadb2.db' CATALOG STORE
Restart the coordinator normally, without the -iqmpx_sn1 switch. For example:
start_iq @params.cfg mpxtest.db -n mpxnode_c
Synchronize all secondary servers in the multiplex. For details, see “Synchronizing secondary servers”.
Follow this procedure to drop a dbspace from the catalog store.
Shut down all the servers in the multiplex.
Start the coordinator with the -gm and -iqmpx_sn switches.
start_iq @params.cfg mpxtest.db -gm 1 -iqmpx_sn 1 -n mpxnode_c
Drop the catalog dbspace in Interactive SQL.
DROP DBSPACE DspCat2
Restart the coordinator normally, without the -iqmpx_sn 1 switch.
Synchronize all secondary servers in the multiplex. See “Synchronizing secondary servers”.
Adding a catalog dbspace