Version 10.0 includes new features that enhance the functionality of the database server and make it easier to use.
| New Features | Reference |
|---|---|
|
A new Security chapter that contains information on new security-related features. In addition, information on Communication Support Modules (CSMs) was moved from Chapter 3 to Chapter 5, the new Security chapter. Chapters 5 through 23 that existed in previous versions of the guide have been renumbered to 6 through 24. |
|
| 3A new configuration parameter used to give
3specified users permission to create databases and thus prevent other users
3from creating databases
3 If this parameter is not set, any user can create 3a database. |
Setting Permission to Create Databases |
| 3New AES ciphers to use when encrypting network 3data | Configuring Network Data Encryption |
|
Functionality for most server utilities on UNIX or Linux to check for a secure environment before contacting the database server (or, starting the database server when using the oninit utility) |
|
|
A new default role that you can assign to individual users or to the PUBLIC group for a particular database. The default role is automatically applied when a user establishes a connection with the database. |
|
|
3New configuration parameters that you 3can use on UNIX, Linux, and Windows platforms to reduce the incomplete connection 3timeout period and restrict the number of incomplete requests for connections, 3thus reducing the risk of a hostile, denial-of-service (DOS) flood attack |
|
|
Options for implementing column-level encryption, as well as password and data-transmission encryption |
|
|
A configuration parameter that a database server security administrator can use to restrict the users who can register an external routine |
|
|
A new event-alarm parameter to use if you want the event-alarm program to operate for all events that are logged in the MSGPATH, not just noteworthy events |
|
|
Rename-dbspace functionality |
|
|
Single-user mode, a new database server mode to use when performing maintenance tasks involving the execution of SQL and DDL statements |
Database Server Operating Modes and Changing Database Server Operating Modes |
|
The DRAUTO configuration parameter to use to automate switching High-Availability Data Replication database servers if the primary server fails |
Actions When an HDR Failure Is Detected, Actions to Take If the Primary Database Server Fails, Changing the Database Server Mode, Critical Media Failure on the Primary Database Server, and The Secondary Database Server Is Changed to a Standard Database Server Automatically |
|
External back up and restore functionality to use when setting up HDR |
|
|
Two configuration parameters that enable the database server to perform physical logging on fuzzy checkpoints during the roll-forward phase of recovery, thus reducing the time required for recovery |
Alternative Fast Restart Recovery Options for Fuzzy Operations |
|
The DS_NONPDQ_QUERY_MEM configuration parameter to use to increase the amount of sort memory that is available for a query that is not a Parallel Database Query (PDQ) |
Size of the Virtual Portion of Shared Memory and the IBM Informix Dynamic Server Performance Guide |
|
Functionality for either manually or automatically replicating a High-Availability Data Replication (HDR) index to the secondary server when an index on the secondary server becomes corrupt |
|
|
Functionality for creating multiple partitions of a table or index within a single dbspace for fragmented tables that use expression-based or round-robin distribution schemes |
|
|
New configuration parameters and onspaces options for specifying the first and next extent sizes for the tblspace tblspace in the dbspace |
Specifying the First and Next Extent Sizes for the tblspace tblspace |
|
Functionality for specifying the page size for a standard or temporary dbspace when you create the dbspace and the BUFFERPOOL configuration parameter to use for defining a buffer pool Information that was specified with the BUFFERS, LRUS, LRU_MAX_DIRTY, and LRU_MIN_DIRTY configuration parameters prior to Version 10.0 should now be specified using the BUFFERPOOL configuration parameter. |
|
|
Functionality for changing the name of a database server instance |
Using the Instance Manager to Rename a Database Server Instance (Windows) |
|
3Transaction support for XA-compliant, 3external data sources |
Using Dynamic Server Transaction Support for XA-Compliant, External Data Sources |
|
3A configuration parameter that allows 3you to remove the restriction that only DBA users can execute certain onstat commands |
Enabling non-DBAs to View SQL Statements a Session Is Executing |
|
4IPv6 support, including automatic discovery 4of whether or not a platform supports IPv6 |
|
|
4Functionality for specifying a comma-separated 4list of valid directory prefix locations from which the database server can 4load external modules |