Known Issues for Multiplex Environment

Descriptions of known issues and workarounds for the multiplex environment.

Multiplex issues
CR#	Description
748684	start_iq fails to restart secondary server with high availability enabled – A secondary server with the high availability option enabled fails, but start_iq fails to restart it: start_iq @params.cfg database.db Workaround – Specify the full path to restart a high availability server: start_iq @/system1/IQ16/mydb/params.cfg /system1/IQ16/mydb/database.db
611990	Emergency shutdown on secondary servers after CREATE TEXT INDEX – A secondary server goes into emergency shutdown when: It is started with the -sf external_library_full_text flag, which disables loading of external libraries, and The user issues a CREATE TEXT INDEX statement on the coordinator with a text configuration that uses external libraries. All other servers replay the DDL successfully. Workaround – Start secondary nodes in the multiplex without the -sf external_library_full_text flag.
447348	Physical file not deleted by DROP DBSPACE – Within a multiplex environment on Windows, if you execute DROP DBSPACE <`dbspace_name`> on a coordinator, the dbspace file may not be physically removed, if the file is locked by the secondary nodes. No error is reported to the client. The IQ message file (.iqmsg) of the coordinator records this error: I. 02/25 11:20:58. 0000000060 DropDBSpacePhysicalFile I. 02/25 11:20:58. 0000000060 Exception Thrown from hos_bio.cxx:1228, Err# 6, tid 398 origtid 398 I. 02/25 11:20:58. 0000000060 O/S Err#: 26, ErrID: 518 (hos_bioexception); SQLCode: -1006062, SQLState: 'sQBA62', Severity: 14 I. 02/25 11:20:58. 0000000060 [20300]: OS error 26 reported on file C:\users\mpx_tablespaces\mpx\size_dbsp_0tb. Workaround – Manually delete the file from the file system after dropping the dbspace.