Welcome
Administering
In addition to administering the database server, you can tune performance, replicate data, and archive data.
Enterprise Replication
The describes the concepts of data replication using HCL Informix® Enterprise Replication, including how to design your replication system, as well as administer and manage data replication throughout your enterprise.
Setting up and managing Enterprise Replication
After you design your replication system, you define it and start replication.
Managing Replication Servers and Replicates
Managing Replication Servers
Deleting a Replication Server
You can remove from a database server and then remove the database server from an domain.

HCL Informix® V15.0.0 documentation
Welcome to the documentation for HCL Informix® 15.0.0 and related client tools and products.
Product overview
HCL Informix® is a fast and scalable database server that manages traditional relational, object-relational, and dimensional databases. Its small footprint and self-managing capabilities are suited to embedded data-management solutions.
Installing
These topics describe how to install HCL Informix® database servers, client products, and modules.
Administering
In addition to administering the database server, you can tune performance, replicate data, and archive data.
- System administration
  These topics contain concepts, procedures, and reference information for database and database server administrators to use for managing and tuning HCL Informix® database servers.
- Backup and Restore Guide
  The HCL® Informix® Backup and Restore Guide describes how to use the HCL Informix and ontape utilities to back up and restore database server data. These utilities enable you to recover your databases after data is lost or becomes corrupted due to hardware or software failure or accident.
- Enterprise Replication
  The describes the concepts of data replication using HCL Informix® Enterprise Replication, including how to design your replication system, as well as administer and manage data replication throughout your enterprise.
  - About Enterprise Replication
    HCL Informix® Enterprise Replication generates and manages multiple copies of data at one or more sites, which allows an enterprise to share corporate data throughout its organization.
  - Planning and designing for Enterprise Replication
    Before you set up your replication system, plan how to include Enterprise Replication into your database server environment, design your database schema by following Enterprise Replication requirements, and then design your replication system between database servers.
  - Setting up and managing Enterprise Replication
    After you design your replication system, you define it and start replication.
    - Preparing the Replication Environment
      The following topics explain the steps that are required for setting up .
    - Using High-Availability Clusters with Enterprise Replication
    - Defining Replication Servers, Replicates, Participants, and Replicate Sets
      These topics describe the steps defining and starting .
    - Grid setup and management
      A grid is a set of replication servers that are configured to simplify administration. When you run SQL data definition statements from within a grid context on a grid server, the statements propagate to all servers in the grid. You can run SQL data manipulation statements and routines through grid routines. You can choose to set up replication automatically when you create a table through a grid. You can propagate external files to other servers in the grid.
    - Shard cluster setup
      Sharding is a way to horizontally partition a single table across multiple database servers in a shard cluster. Enterprise Replication moves the data from the source server to the appropriate target server as specified by the sharding method. You query a sharded table as if the entire table is on the local server. You do not need to know where the data is. Queries that are performed on one shard server retrieve the relevant data from other servers in a shard cluster. Sharding reduces the index size on each shard server and distributes performance across hardware. You can add shard servers to the shard cluster as your data grows.
    - Managing Replication Servers and Replicates
      - Managing Replication Servers
        Modify server attributes
        You modify replication server attributes by running the cdr modify server command.
        Dynamically Modifying Configuration Parameters for a Replication Server
        You can alter the settings for Enterprise Replication configuration parameters and environment variables on a replication server while replication is active.
        Viewing Replication Server Attributes
        Connect to another replication server
        By default, when you view information about a server, connects to the global catalog of the database server specified by the INFORMIXSERVER environment variable. You can connect to the global catalog of another database server by using the --connect option.
        Temporarily stopping replication on a server
        You can temporarily stop replication on a server to perform maintenance tasks in several different ways.
        Restarting Replication on a Server
        You can restart replication after was temporarily stopped.
        Suspending Replication for a Server
        Resuming a Suspended Replication Server
        Deleting a Replication Server
        You can remove from a database server and then remove the database server from an domain.
      - Managing Replicates
      - Managing Replicate Sets
      - Managing Templates
      - Managing Replication Server Network Connections
      - Resynchronizing Data among Replication Servers
        If replication has failed for some reason and data is not synchronized, there are different ways to correct data mismatches between replicated tables.
      - Alter, rename, or truncate operations during replication
        When Enterprise Replication is active and data replication is in progress, you can perform many types of alter, rename, or truncate operations on replicated tables and databases.
      - Recapture replicated transactions
        If you want a transaction to continue to be replicated after it reaches the target replication servers, you can use the ifx_set_erstate() procedure.
    - Monitor and troubleshooting Enterprise Replication
      You can monitor and diagnose problems with the Enterprise Replication system by using several different methods, depending on your needs.
  - Push data feature
  - Loopback replication
  - Appendixes
Migrating and upgrading
You can upgrade to the 15.0.0 release of HCL Informix® or migrate from other database servers to Informix. Upgrading is an in-place migration method that uses your existing hardware and operating system software. Some changes to the Informix database server can affect upgrading from a previous release.
Client APIs and tools
You can use the HCL Informix® implementation of client APIs to develop applications for Informix database servers.
Embedding Informix®
When you embed HCL Informix®, you can use enterprise-class high-availability and high performance with embeddability features such as easy programmability, a small disk and memory footprint, and silent deployment.
Extending Informix®
Beyond standard relational database objects, HCL Informix® can be extended to handle specialized data types, access methods, routines, and other objects. Informix includes many built-in extensions that are fully integrated in the database server. Informix also provides modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for Informix.
Data warehousing
In addition to designing and implementing Informix® dimensional databases, you can use tools to create data warehouse applications and optimize your data warehouse queries.
Designing databases
The first step in creating a relational database is to construct a data model, which is a precise, complete definition of the data you want to store. After you prepare your data model, you must implement it as a database and tables. To implement your data model, you first select a data type for each column and then you create a database and tables and populate the tables with data. You can also implement fragmentation strategies and control access to your data.
JSON compatibility
You can use the popular JSON-oriented query language created by MongoDB to interact with data stored in HCL Informix®.
Security
You can secure your Informix® database server and the data that is stored in your Informix databases. You can encrypt data, secure connections, control user privileges and access, and audit data security.
SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
Troubleshooting HCL Informix®
Several troubleshooting techniques, tools, and resources are available for resolving problems that you encounter in your HCL Informix® database server environment.

Deleting a Replication Server

You can remove from a database server and then remove the database server from an domain.

About this task

Run the cdr delete server command two times to remove from a database server, and then remove the database server from an domain. The first time, run the command on the server you want to remove from. The second time, connect to a different server in the domain and run the command, specifying the server you ran the first command on.

To remove from an inactive database server, use the cdr delete server command with the --force option.

To restart on a disabled database server, define the server again with the cdr define server command and then synchronize data. Row history is deleted when a server has removed, so the history is not recoverable if is restarted.

Important: If you are creating a replicate to replace the one you deleted, use the cdr check queue --qname=ctrlq command to make sure that the delete operation propagated to all the servers.

Examples

To remove from local database server reynolds, and then remove database server reynolds from the domain it shares with database server stimpson, run the following commands:

cdr delete server reynolds
cdr delete server --connect=stimpson reynolds

The first command removes from the local database server, reynolds. The second command connects to database server stimpson, which is another server in the domain, and then removes database server reynolds from the shared domain.