Home
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.
Administrator's Guide
The Informix® Administrator's Guide provides the information required to administer HCL Informix.
Disk, memory, and process management
Moving data with external tables
You can use external tables to load and unload database data.
Manage errors from external table load and unload operations
You can manage errors that occur during external table load and unload operations.
Reject files
Rows that have conversion errors during a load are written to a reject file on the server that performs the conversion.

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.
  - List of utilities
    HCL Informix® includes utilities and applications that you can use to perform administrative tasks and capture information about configuration and performance.
  - Administrator's Guide
    The Informix® Administrator's Guide provides the information required to administer HCL Informix.
    - The database server
    - Disk, memory, and process management
      - Virtual processors and threads
        These topics describe virtual processors, explain how threads run within the virtual processors, and explain how the database server uses virtual processors and threads to improve performance.
      - Manage virtual processors
        These topics describe how to set the configuration parameters that affect database server virtual processors, and how to start and stop virtual processors.
      - Shared memory
        These topics describe the content of database server shared memory, the factors that determine the sizes of shared-memory areas, and how data moves into and out of shared memory.
      - Manage shared memory
      - Data storage
        The database server uses physical units of storage to allocate disk space. It stores data in logical units. Unlike the logical units of storage whose size fluctuates, each of the physical units has a fixed or assigned size that is determined by the disk architecture.
      - Manage disk space
        You can use several utilities and tools to manage disk spaces and the data that the database server controls.
      - Moving data with external tables
        You can use external tables to load and unload database data.
        External tables
        An external table is a data file that is not managed by the Informix® database server. The definition of the external table includes data-formatting type, external data description fields, and global parameters.
        Defining external tables
        To define an external table, you use SQL statements to describe the data file, define the table, and then specify the data to load or unload.
        Map columns to other columns
        Load data from and unload to a named pipe
        You can use a named pipe, also called a first-in-first-out (FIFO) data file, to load from and unload to a nonstandard device, such as a tape drive.
        Monitor the load or unload operations
        You can monitor the status of an external table load or unload operation.
        External tables in high-availability cluster environments
        You use external tables on secondary servers in much the same way they are used on the primary server.
        System catalog entries for external tables
        You can query system catalog tables to determine the status of external tables.
        Performance considerations when using external tables
        Use external tables when you want to manipulate data in an ASCII file using SQL commands, or when loading data from an external data file to a RAW database table.
        Manage errors from external table load and unload operations
        You can manage errors that occur during external table load and unload operations.
        Reject files
        Rows that have conversion errors during a load are written to a reject file on the server that performs the conversion.
        External table error messages
        Most of the error messages related to external tables are in the -26151 to -26199 range.
        Recoverability of table types for external tables
        The database server checks the recoverability level of the table when loading of data.
      - Storage space encryption
        You can encrypt storage spaces (dbspaces, blobspaces and smart blobspaces) with Informix Dynamic Server. The data in encrypted storage spaces is unintelligible without the encryption key. Encrypting storage spaces is an effective way to protect sensitive information that is stored on disk.
    - Logging and log administration
    - Fault tolerance
    - High availability and scalability
      A successful production environment requires database systems that are always available, with minimal if any planned outages, and that can be scaled quickly and easily as business requirements change.
    - Distributed data
    - Overview of automatic monitoring and corrective actions
      You can use the SQL administration API, the Scheduler, and drill-down queries to manage automatic maintenance, monitoring, and administrative tasks.
  - Administrator's Reference
    The Informix® Administrator's Reference includes comprehensive descriptions of HCL Informix configuration parameters, the system-monitoring interface (SMI) tables in the sysmaster database, the syntax of database server utilities such as onmode and onstat, logical-log records, disk structures, event alarms, and unnumbered error messages.
  - DB-Access User's Guide
    The Informix® DB-Access User's Guide describes how to use the DB-Access utility to access, modify, and retrieve information from Informix database servers.
  - High-Performance Loader User's Guide
    The describes how to use the HCL Informix® to load and unload large quantities of data efficiently to or from Informix databases.
  - Performance Guide
    The Informix® Performance Guide describes how to configure and operate your HCL Informix database server to improve overall system throughput and to improve the performance of SQL queries.
  - SNMP Subagent Guide
    The describes the Simple Network Management Protocol (SNMP) and the software that you need to use SNMP to monitor and manage HCL Informix® database servers and databases.
  - InformixHQ Guide
    InformixHQ is a modern web console for visualizing, monitoring, and managing your Informix server instances. It is purpose built for ease-of-use, scaling out, and optimizing DevOps needs. It provides critical performance management capabilities, monitoring how key performance metrics are changing over time and tracking how efficiently Informix is running your workload even when you’ve stepped away from your screen. Its monitoring system feeds directly into a customizable alerting system so you can be immediately alerted via email, Twilio, or PagerDuty whenever an issue occurs on one of your Informix database server instances. InformixHQ is designed to be scalable to efficiently manage and monitor as many Informix database server instances as you need. Moreover, it's a tool that can be shared by the DBAs, the app developers, the ops engineers, and management and accessed from any desktop, laptop, or mobile device. InformixHQ is the centralized hub for graphical monitoring, alerting, and administration of your Informix database servers.
- Backup and Restore Guide
  The Informix® Backup and Restore Guide describes how to use the Informix ON-Bar 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 HCL® Informix® Enterprise Replication Guide describes the concepts of data replication using Informix Enterprise Replication, including how to design your replication system, as well as administer and manage data replication throughout your enterprise.

Reject files

Rows that have conversion errors during a load are written to a reject file on the server that performs the conversion.

The REJECTFILE keyword in the CREATE EXTERNAL TABLE statement determines the name given to the reject file.

Instead of using a reject file, you can use the MAXERRORS keyword in the CREATE EXTERNAL TABLE statement to specify the number of errors that are allowed before the database server stops loading data. (If you do not set the MAXERRORS keyword, the database server processes all data regardless of the number of errors.)

The database server removes the reject files, if any, at the beginning of a load. The reject files are recreated and written only if errors occur during the load.

Reject file entries are single lines with the following comma-separated fields:

file name, record, reason-code, field-name: bad-line

file name: Name of the input file
record: Record number in the input file where the error was detected
reason-code: Description of the error
field-name: The external field name where the first error in the line occurred or <none> if the rejection is not specific to a particular column
bad-line: For delimited or fixed-ASCII files only, the bad line itself

The load operation writes file name, record, field-name, and reason-code in ASCII.

The bad-line information varies with the type of input file:

For delimited files or fixed text files, the entire bad line is copied directly into the reject file. However, if the delimited format table has TEXT or BYTE columns, the reject file does not include any bad data. The load operation generates only a header for each rejected row.
For Informix® internal data files, the bad line is not placed in the reject file because you cannot edit the binary representation in a file. However, the file name, record, reason-code, and field-name are still reported in the reject file so that you can isolate the problem.

The following types of errors can cause a row to be rejected.

CONSTRAINT constraint name: This constraint was violated.
CONVERT_ERR: Any field encounters a conversion error.
MISSING_DELIMITER: No delimiter was found.
MISSING_RECORDEND: No record end was found.
NOT NULL: A null was found in field-name.
ROW_TOO_LONG: The input record is longer than 2 GB.