Jump to main content
HCL Logo Product Documentation
Customer Support Community
Customer Support HCLSoftware U Community Forums Customer Idea Portal
HCL Informix V15.0.0
  1. Home icon
  2. Welcome
  3. Administering

    In addition to administering the database server, you can tune performance, replicate data, and archive data.

  4. 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.

  5. Setting up and managing Enterprise Replication

    After you design your replication system, you define it and start replication.

  6. 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.

  7. Preventing Memory Queues from Overflowing

    In a well-tuned system, the send queue and receive queue do not regularly overflow from memory to disk. However, if the queues in memory fill, the transaction buffers are written (spooled) to disk. Spooled transactions consist of transaction records, replicate information, and row data. Spooled transaction records and replicate information are stored in the transaction tables and the replicate information tables in a single dbspace. Spooled row data is stored in one or more sbspaces.

  8. Recovering when Storage Spaces Fill
Product logo

  • 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

        • 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.

          • Solve Replication Processing Problems

            Diagnose, monitor, and solve possible problems that can occur while is running.

          • Failed Transaction (ATS and RIS) Files

            Aborted Transaction Spooling (ATS) and Row Information Spooling (RIS) files can be generated when replicated transactions fail.

          • Preventing Memory Queues from Overflowing

            In a well-tuned system, the send queue and receive queue do not regularly overflow from memory to disk. However, if the queues in memory fill, the transaction buffers are written (spooled) to disk. Spooled transactions consist of transaction records, replicate information, and row data. Spooled transaction records and replicate information are stored in the transaction tables and the replicate information tables in a single dbspace. Spooled row data is stored in one or more sbspaces.

            • Handle potential log wrapping

              The potential for log wrap occurs when log processing lags behind the current log and the replay position is in danger of being overrun.

            • Monitoring Disk Usage for Send and Receive Queue Spool

              Periodically monitor disk usage for the dbspace.

            • Increasing the Sizes or Numbers of Storage Spaces
            • Recovering when Storage Spaces Fill
          • Common configuration problems

            If you experience problems setting up , check the configuration of your environment and database.

          • Troubleshooting Tips for Alter Operations

            Alter operations on replicated tables might result in errors.

          • Enterprise Replication Event Alarms

            Certain errors and other actions generate event alarms. You can use event alarms specific to to automate many administrative tasks.

      • 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.

 Feedback

Recovering when Storage Spaces Fill

When the dbspace runs out of disk space, raises an alarm and writes a message to the log. When the sbspace runs out of disk space, hangs. In either case, you must resolve the problem that is causing to spool (Preventing Memory Queues from Overflowing) or you must allocate additional disk space (Increasing the Sizes or Numbers of Storage Spaces) before you can continue replication.

Related information
  • Handle potential log wrapping
  • Monitoring Disk Usage for Send and Receive Queue Spool
  • Increasing the Sizes or Numbers of Storage Spaces
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences