The syntax diagram and parameter description incorrectly refer to the parameter "-f filename"; this should be changed to "-i filename".
In the Examples section, the third example shows the use of options "-c" and "-n". However, these options are not supported, and are not included in the syntax diagram. The example should be disregarded.
The Usage Notes section has been changed to:
For dynamic SQL statements, the frequency with which statements are executed can be
obtained from the monitor as follows:
1. Issue db2 reset monitor for database <database-alias>.
Wait for an appropriate interval of time.
2. Issue db2 get snapshot for dynamic sql on <database-alias> write to file.
3. Issue db2 "insert into advise_workload (select 'myworkload',
0,stmt_text, cast(generate_unique() as char(254)),
num_executions, 1, num_executions, 0, 0 from
table(SYSFUN.SQLCACHE_SNAPSHOT()) as correlation_name)".
The default frequency for each SQL statement in a workload is 1,
and the default importance is also 1. The generate_unique() function
assigns a unique identifier to the statement, which can
be updated by the user to be a more meaningful description of that SQL statement.
Change the first sentence of the Usage Notes section to:
Although SQL statements can be up to 65 535 characters in length, no text line in the input file can exceed 3 898 characters, and long statements must be divided among several lines.
The following information is to be added to the Command Reference:
db2jstrt - DB2 JDBC Applet Server
Starts the JDBC applet server on the specified TCP/IP port number.
The JDBC applet server is a server daemon that enables SQLJ and JDBC applets
to connect to the DB2 server.
To terminate the JDBC applet server, kill the JDBC applet server process.
The JDBC applet server process is identified as "db2jd" on UNIX operating systems,
and "db2jd.exe" on OS/2 and Windows 32-bit operating systems.
Syntax:
+-----6789------+
| |
>>---db2jstrt------+---------------+--------><
| |
+-<port number>-+
where <port number> represents a TCP/IP port number that is not registered
for another service.
The following entry is to be added to the index: "db2jd -- see db2jstrt".
Change the first paragraph of the description of this tool to:
Generates DDL statements to reproduce the objects of a production database on a test database. The utility can also generate the required DML statements to replicate the statistics on those objects in the test database.
The description of the "-e" option states that triggers are not supported. That is no longer true. If the database contains triggers, db2look will generated the DDL statements to recreate these triggers if the "-e" option is specified.
The "-a" option specifies all creators. If this option is specified, the utility will consider all the user tables in the database, The "-a" option does not require that the "-t" option also be specified.
The following options are missing from the documentation:
Following is the correct syntax for db2look:
>>-db2look---d--DBname----+--------------+------------->
'--u--Creator--'
>-----+-------------------------+---------------------->
'-+----+---+----+--+----+-'
'--s-' '--g-' '--a-'
>-----+--------------------------------------------------------------------------------------+>
'-+----+---o--Fname--+-----------------+--+-----------------+--+----+--+----+--+----+--'
'--p-' '--e--+----------+' '--m--+----------+' '--c-' '--r-' '--h-'
'--t--Tname' '--t--Tname'
>-----+---------------------------------------------------+----------------------------------><
'-+----+---+----+--+------------+---+-------------+-'
'--l-' '--x-' '--i--userID-' '--w--password'
When issued on a Version 5.2 client against a Version 6.1 database, this command does not support table or column names that are greater than 18 characters in length.
This command has a new option, /r, with two valid values, "conservative" and "any":
>>--db2rbind--database--/l logfile--.-----.--.------------------------.---->
'-all-' '-/u userid--/p password-'
.--/r conservative--.
>--+-------------------+--------------------------------------------------><
'--/r any-----------'
Specifying "/r conservative" causes the RESOLVE CONSERVATIVE option to be used during rebind. Only functions and types in the SQL path that were defined before the last explicit bind time stamp (for each package) are considered for function and type resolution. Conservative binding semantics are used. This is the default. Specifying "/r any" causes the RESOLVE ANY option to be used during rebind. Any of the functions and types in the SQL path are considered for function and type resolution. Conservative binding semantics are not used.
Change the second to the last paragraph of the Usage Notes section to:
SQL statements can be up to 65 535 characters in length. Statements must be terminated by a semicolon.
When commands are entered from the MS-DOS prompt in command line mode, the Windows 95 DOS command processor preprocesses them in such a way that everything entered between pairs of percent signs (%) is interpreted as a variable name. For example:
db2 "SELECT NAME, CREATOR FROM SYSIBM.SYSPLAN WHERE NAME LIKE 'SQLL%' OR NAME LIKE 'SQLC%'"
gets passed to db2.exe as:
"SELECT NAME,CREATOR FROM SYSIBM.SYSPLAN WHERE NAME LIKE 'SQLL'" (%' OR NAME LIKE 'SQLC% is treated by DOS as a variable whose value is NULL)
To avoid this behavior, use a double percent sign (%%) to indicate that a percent sign (and not a variable) is to be passed to the program:
db2 "SELECT NAME, CREATOR FROM SYSIBM.SYSPLAN WHERE NAME LIKE 'SQLL%%' OR NAME LIKE 'SQLC%%'"
This gets passed to db2.exe as:
"SELECT NAME, CREATOR FROM SYSIBM.SYSPLAN WHERE NAME LIKE 'SQLL%' OR NAME LIKE 'SQLC%'"
When registering one or more DB2 Data Links Managers for a database using this command, ensure that the DB2 Data Links Manager is not registered twice; otherwise, error SQL20056N with reason code "99" may be returned during DataLink processing. The db2diag.log file for the DB2 Data Links Manager server that is registered twice will have the following entry when such a failure occurs:
dfm_xnstate_cache_insert : Duplicate txn entry. dfmBeginTxn : Unable to insert ACTIVE transaction in cache, rc = 41. DLFM501E : Transaction management service failed.
Following are some bind considerations in a client/server environment:
In a client/server environment, when a BIND command is issued on a pre-Version 6.1 client connected to a Version 6.1 server, an erroneous SQL0020W may be returned to the client. This situation will be encountered if the command uses either or both of the parameters DYNAMICRULES or OWNER. Although the error message is displayed, the parameters are still effective, and will be used. Any other parameters displayed in the SQL0020W message are correctly noted as errors, and will be ignored as indicated by the message. These other parameters include, but are not restricted to, the following: ACTION, CCSIDG, CCSIDM, CCSIDS, CHARSUB, CNULREQD, DEC, DECDEL, GENERIC, RELEASE, REPLVER, RETAIN, STRDEL, TEXT, VALIDATE, VERSION.
The format of the data returned from this command has changed for Version 6, and the sample outputs for Table Snapshot & Database Lock Snapshot are incorrect. Longer table names do not permit the collected data to be displayed in a tabular format. Table and lock data is now returned in individual lines. For example:
Table Schema Table Name Table Type Rows Written Rows Read Overflows
-------------------- -------------------- -------------------- ------------ ---------- ----------
USER1 STAFF User 0 35 0
...
becomes
Table Schema = USER1
Table Name = STAFF
Table Type = User
Rows Written = 0
Rows Read = 35
Overflows = 0
If this modifier is specified, and the transaction log is not sufficiently large, the import operation will fail. The transaction log must be large enough to accommodate either the number of rows specified by COMMITCOUNT, or the number of rows in the data file if COMMITCOUNT is not specified. It is therefore recommended that the COMMITCOUNT option be specified to avoid transaction log overflow.
This modifier is incompatible with INSERT_UPDATE mode, hierarchical tables, and the USEDEFAULTS modifier.
If an error occurs during migration, it may be necessary to issue a "db2 terminate" command before attempting the suggested user response. For example, if a log full error occurs during migration (SQL1704: Database migration failed. Reason code "3".), it will be necessary to issue "db2 terminate" before increasing the values of the database configuration parameters LOGPRIMARY and LOGFILSIZ. The CLP must refresh its database directory cache if the migration failure occurs after the database has already been relocated (which is likely to be the case when a "log full" error returns).
Change the description of "LOGFILE PRIOR TO log-file-name" to the following:
Specifies a string for a log file name, for example S0000100.LOG. All log files prior to (but not including) the specified log file will be deleted. The LOGRETAIN database configuration parameter must be set to "RECOVERY" or "CAPTURE".
This command has a new option, RESOLVE, with two valid values, "ANY" and "CONSERVATIVE":
.--RESOLVE--ANY-----------.
>>-REBIND-+---------+--package-name--+-------------------------+--><
'-PACKAGE-' '--RESOLVE--CONSERVATIVE--'
RESOLVE
Specifies whether rebinding of the package is to be performed
with or without conservative binding semantics. This affects whether new functions
and data types are considered during function resolution and type resolution
on static DML statements in the package. This DB2 option is not supported by DRDA.
Valid values are:
ANY
Any of the functions and types in the SQL path are considered for function
and type resolution. Conservative binding semantics are not used.
This is the default.
CONSERVATIVE
Only functions and types in the SQL path that were defined before
the last explicit bind time stamp are considered for function and type resolution.
Conservative binding semantics are used.
Reconcile produces a message file (reconcil.msg) in the instance path on UNIX based systems, and in the install path on Windows NT and 0S/2. This file will contain warning and error messages that are generated during validation of the exception table.
In the Usage Notes section, there is a list of possible violations that can appear in the exception table, or an exception report. Following are two new error codes that should be added to this list:
00008 File restored but modified file has been copied to
<filename>.MOD
00009 File is already linked to another table.
For typed tables, the specified table name must be the name of the hierarchy's root table.
The following sentence is to be added to the first paragraph of the Usage Notes section:
The reorganize utility will implicitly close all the cursors.
For typed tables, the specified table name must be the name of the hierarchy's root table.
On Windows operating systems and on OS/2, specify only the drive letter when using the "TO target-directory" parameter. If a longer path is specified, an error is returned.
The description of "TABLE table-name" includes the statement:
For row types, table-name must be the name of the hierarchy's root table.
This statement should be changed to:
For typed tables, the specified table name must be the name of the hierarchy's root table.
For an updated version of Table 8, "SQL Statements (DB2 Universal Database)", see the Application Development Guide, or the CLI Guide and Reference.