Version 5
|
|
Version 5
|
A new option has been added for handling decimal data. MODIFIED BY IMPLIEDDECIMALPOINT allows LOAD and IMPORT to insert an implied decimal point based on the column definition. Another new option, MODIFIED BY BINARYNUMERIC, allows all numeric data to be imported in binary or packed decimal format. See the Command Reference for details.
A selected subset of table spaces can now be rolled forward to a specified point in time. You can also restore a subset of the table spaces from a table space backup. See the Administration Guide and Command Reference for details.
You can now selectively choose the table spaces to be restored from the full database backup image. See the Administration Guide and the Command Reference for details.
Various APIs and commands for querying table spaces and table space containers have been enhanced.
The LIST TABLESPACES command is enhanced to display the additional information when SHOW DETAIL is specified.
See the Command Reference and the API Reference for details.
The FORCE command has been modified so that on a DB2 Universal Database
Extended Enterprise Edition system, any application can be forced from any
database partition using the agent ID (an identifier that uniquely identifies
an application). See the Command Reference for details.
 |
Version 5.2
|
The DB2 audit function generates, and allows you to maintain an audit trail for a series of predefined database events. The records generated from this facility are kept in an audit log file. These records can be used to detect and deter penetration of the DB2 system. With analysis, the records can reveal usage patterns that identify system misuse. For details on the audit function and the db2audit command see the Administration Guide.
The sqleseti - Set Client Information API allows an application to set client information associated with a specific connection. A successful API call means that the client information has accepted and will be propagated on subsequent connections. See the API Reference for details.
The sqleqryi - Query Client Information API allows you to query current client information. If a specific connection is requested, then the latest values for that connection are returned. If all connections are specified, then the values associated with all connections specified by the last sqleseti API are returned. See the API Reference for details.
Administration information is now available in the history file. The administrative events recorded will contain ROLLFORWARD, ALTER TABLESPACE, REORG, RUNSTATS, and DROP TABLE information. See the API Reference for details on obtaining this information with the sqluhops - Open Recovery History File Scan API. For information on extracting information with the LIST HISTORY command see the Command Reference.
New parameters have been added to provide support for transferring objects between table hierarchies (see "Typed Tables and Views"). Data residing in typed tables can be exported and imported as an entire table hierarchy, a subhierarchy, or a single typed table or subtable. See the Administration Guide for more details on table hierarchies.
See the Command Reference for information on the changes to the IMPORT and EXPORT commands. See the API Reference for information on the changes to sqluexpr - EXPORT and sqluimpr - IMPORT APIs.
New parameters have been added to the LOAD and RESTORE commands extending support to the new DATALINK data type. See the Command Reference for details.
The RECONCILE command validates the references to files for the DATALINK data in a table. See the Command Reference for details.
Statistics support has been extended to hierarchical data (see "Typed Tables and Views"). Statistics are still collected using the RUNSTATS command and updated through regular UPDATE commands on the system catalog tables. See the RUNSTATS command in the Command Reference and the sqlustat - Runstats API in the API Reference for details.
The db2flsn - Find Log Sequence Number command allows users to determine which log file contains the log record identified by a given log sequence number (LSN). Locating an LSN is of particular interest to users of IBM DataPropagator Relational (DPROPR) and the sqlurlog - Asynchronous Read Log API. See the Command Reference for details.