Dbspace updates on multiplex
differ slightly from those on simplex databases.
In general, when updating shared dbspaces on a multiplex:
- Only the coordinator can manipulate shared IQ dbspaces.
- Before you can drop a shared dbspace file, you must alter the
file to read-only mode. All servers must be at the version corresponding to the
ALTER READONLY statement, and must have
returned all reserved blocks on the file.
- CREATE DBSPACE, ALTER DBSPACE, and DROP
DBSPACE commands for main and catalog dbspaces are allowed only on
the coordinator.
Due to TLV propagation and version maintenance, there may be a delay of a few
minutes before you can drop an empty dbfile or dbspace. You see a Command not
replayed error. To perform the DROP
DBSPACE or ALTER DBSPACE DROP FILE
commands, the OkToDrop column reported by the sp_iqdbspace and sp_iqfile procedures
must indicate Y.
Start the coordinator in single-node mode (-iqmpx_sn
-1) before dropping files from IQ_SHARED_TEMP. The first file made
read-write in IQ_SHARED_TEMP must be the last file dropped. You may also drop files in
IQ_SHARED_TEMP in simplex.
Note: Do not start the coordinator in single-node mode with -iqro, or
adding or dropping a file returns the error SQL Anywhere Error -757:
Modifications not permitted for read-only database.