Errors and warnings generated by the sec2er command

The sec2er command checks several conditions before converting a primary and secondary server pair to an ER system. The following conditions are checked by the sec2er command; ER conversion will take place only if the following conditions are met:

• The group definition must use the i= option.
• The CDRID option must be the same on both the primary and secondary servers (The CDRID is the unique identifier for the database server in the Options field of the sqlhosts file).
• The sqlhosts files on the primary server must match the sqlhosts file on the secondary server. The sec2er command checks only the lines in the sqlhosts files that must to match to support ER.
• The database must not contain a typed table without a primary key.
• User-defined types (UDT) must have ER support.
• Tables must not be protected with label-based access control (LBAC).
• A secondary server must be defined.
• An sbspace for a stable queue must exist.
• You must be running Informix® version 11.00 or later.

The following warnings might occur. Warnings do not always indicate a problem but should be addressed. A warning is generated if any of the following are true:

• The CDR_SERIAL configuration parameter is not set.
• The values for the CDR_SERIAL configuration parameter are the same on both the primary and secondary servers. Identical values can cause conflicts.
• The database has sequence generators. Because sequence generators are not replicated, if you replicate tables using sequence objects for update, insert, or delete operations, the same sequence values might be generated on different servers at the same time, leading to conflicts.
• The database is not logged.
• A table is not logged.
• The DBSPACE is more than 70-percent full.

If the cdr start sec2er command fails or is interrupted, you might see a message that is similar to this message:

ERROR:  Command cannot be run on pre-11.70 instance if ER is already running