Welcome
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.
Security in HCL Informix®
The HCL® Informix® Security Guide documents methods for keeping your data secure by preventing unauthorized viewing and altering of data or database objects, including how to use the secure-auditing facility of the database server.
Auditing data security
Audit analysis
Audit-record format

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.
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.
- Security in HCL Informix®
  The HCL® Informix® Security Guide documents methods for keeping your data secure by preventing unauthorized viewing and altering of data or database objects, including how to use the secure-auditing facility of the database server.
  - Securing data
  - Auditing data security
    - Overview of auditing with the Informix® secure auditing facility
    - Audit administration
    - Audit analysis
    - The onaudit utility
      Use the onaudit utility to manage audit masks and auditing configuration.
    - The onshowaudit utility
      Use the onshowaudit utility to view the audit information from an existing audit trail. You can use this command to extract information for a particular user, database server, or both, making it possible to isolate a particular subset of data from a potentially large audit trail.
    - Audit event codes and fields
      The secure-auditing facility audits certain database server events.
    - The ADTCFG file
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.

Audit-record format

The database server generates the second part of the audit record, with fields that depend on the audit event.

Audit-record format shows the format of the database server audit records.

Table 1. Audit-record format
ONLN	date and time	hostname or hostname. domain.ext	pid	database server name	user name	sid	errno	event mnemonic	Additional Fields
ONLN	2008-07-28 15:43:00.000	turk	12930	db_audit	jazt	45	0	CRDB	dbsch
ONLN	2008-07-28 15:43:18.000	turk	12930	db_audit	jazt	45	0	ACTB	dbsch:jazt:v1:103
ONLN	2008-07-28 15:43:19.000	turk	12930	db_audit	jazt	46	0	CLDB	dbsh
ONLN	2008-07-28 15:43:21.000	turk	12939	db_audit	jazt	47	0	ALFR	local:109:-:-:4:4: db1,db2,db3, rootdbs:0
ONLN	2008-07-28 15:43:28.000	turk	12974	db_audit	jazt	48	0	ALFR	local:109:aa5x:-: 32:4: db1,db2 rootdbs:0
ONLN	2008-07-28 15:43:29.000	turk	12974	db_audit	jazt	48	0	STDS	2:-
ONLN	2008-07-28 15:43:29.000	turk	12978	db_audit	jazt	49	0	STPR	100
. . .	. . .	. . .	. . .	. . .	. . .	...	. . .	. . .	. . .

Note:

Session IDs can be suppressed using -S option of onshowaudit utility.

% onshowaudit -n 60 -S -d

ONLN: A fixed field used to identify events
date and time: Indicates when the audit event was recorded
hostname: The name of the UNIX™ host computer of the client application that executes the audit event
hostname.domain.ext: The name of the Windows™ host computer, domain, and extension of the client application that executes the audit event
pid: The process ID of the client application that causes the database server to run the audit event
database server name: The name of the database server on which the audit event is run
user name: The login name of the user who requests the event
sid: The session ID of the client application
errno: The event result that contains the error number that the event returns, indicating success (0) or failure
event mnemonic: Database server audit event that the database server ran, such as ALFR (Alter Fragment)
additional fields: Any fields that identify databases, tables, and so on. These additional fields are audit-event fields that contain information captured in tabular form by the onshowaudit utility for audit analysis.
For operating-system-managed auditing on UNIX™, the database server audit record is an additional field for the operating-system audit record. Audit event codes and fields lists the audit-event fields.