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 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.
Appendixes
Messages in the database server log
Unnumbered messages are printed in the database server message log (online.log). The error messages include corrective actions.
Messages: N-O-P
oninit: VPCLASS classname name is too long. Maximum length is maxlength.

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.
  - 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.
    - Configuring and monitoring Informix®
    - Administrative Utilities
    - SQL Administration API
    - Appendixes
      - Database server files
        Database server files are created in default directories, or in a directory that the relevant configuration parameter specifies. A database administrator might need to edit or examine the content of files that are used by the database server.
      - Troubleshooting errors
        Occasionally, a series of events causes the database server to return unexpected error codes.
      - Event Alarms
        The database server provides a mechanism for automatically triggering administrative actions based on an event that occurs in the database server environment. This mechanism is the event-alarm feature.
      - Messages in the database server log
        Unnumbered messages are printed in the database server message log (online.log). The error messages include corrective actions.
        How the Messages Are Ordered in This Chapter
        Messages: A-B
        Messages: C
        Messages: D-E-F
        Messages: G-H-I
        Messages: J-K-L-M
        Messages: N-O-P
        Newly specified value of value for the pagesize in the configuration file does not match older value of value. Using the older value.
        Not enough main memory.
        Not enough logical-log files, Increase LOGFILES.
        The number of configured inline poll threads exceeds the number of CPU virtual processors.
        onconfig parameter parameter modified from old_value to new_value.
        oninit: Cannot have SINGLE_CPU_VP non-zero and number of CPU VPs greater than 1.
        oninit: Cannot have SINGLE_CPU_VP non-zero and user-defined VP classes.
        oninit: Fatal error in initializing ASF with 'ASF_INIT_DATA' flags asfcode = '25507'.
        Cannot alter a table which has associated violations table.
        oninit: Too many VPCLASS parameters specified.
        oninit: VPCLASS classname bad affinity specification.
        oninit: VPCLASS classname duplicate class name.
        oninit: VPCLASS classname illegal option.
        oninit: VPCLASS classname maximum number of VPs is out of the range 0-10000.
        oninit: VPCLASS classname name is too long. Maximum length is maxlength.
        oninit: VPCLASS classname number of VPs is greater than the maximum specified.
        oninit: VPCLASS classname number of VPs is out of the range 0-10000.
        onmode: VPCLASS classname name is too long. Maximum length is maxlength.
        Online Mode.
        onspaces: unable to reset dataskip.
        Open transaction detected when changing log versions.
        Out of message shared memory.
        Out of resident shared memory.
        Out of virtual shared memory.
        PANIC: Attempting to bring system down.
        Participant site database_server heuristically rolled back.
        Physical recovery complete: number pages examined, number pages restored.
        Physical recovery started at page (chunk:offset).
        Portions of partition partnum of table tablename in database dbname were not logged. This partition cannot be rolled forward.
        Possible mixed transaction result.
        Prepared participant site server_name did not respond.
        Prepared participant site server_name not responding.
        Messages: Q-R-S
        Messages: T-U-V
        Messages: W-X-Y-Z
        Messages: Symbols
        Conversion and reversion error messages
        If conversion or reversion is not successful, error messages are stored in the online.log file to help you identify what failed and what actions to take to fix the problem.
        Conversion and Reversion Messages for Enterprise Replication
        During conversion and reversion, specific messages are logged for Enterprise Replication by the concdr, revcdr, and revtestcdr scripts.
        Dynamic Log Messages
        Sbspace Metadata Messages
        Truncate Table Messages
      - Limits in Informix®
        This topic lists the system-level and table-level parameter limits, the system defaults, and the access capabilities of Informix®.
  - 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.

oninit: VPCLASS `classname` name is too long. Maximum length is `maxlength`.

Cause

The length of the name field in VPCLASS classname is too long.

Action

Choose a shorter class name, correct the ONCONFIG file, and restart the database server.

oninit: VPCLASS classname name is too long. Maximum length is maxlength.

Cause

Action

oninit: VPCLASS `classname` name is too long. Maximum length is `maxlength`.