The changes in Version 10.1 to DB2® command line processor (CLP) and system commands can impact your existing applications and scripts after you upgrade to Version 10.1.
Command | Summary of changes with upgrade impact |
---|---|
db2cat | The output for the db2cat command
no longer includes properties for the table space where the database
object is stored. The following table space properties such as TRANSFERRATE, OVERHEAD, WRITETRANSFERRATE, WRITEOVERHEAD, PREFETCHSIZE, EXTENTSIZE and PAGESIZE are
no longer reported by the db2cat command. For more information, see db2cat command output text has changed for details. |
db2icrt, db2iupdt, db2cluster_prepare | The db2icrt and db2iupdt have
changes to existing parameters, and deprecation of parameter value
format. The format for the -m and -cf parameters
are deprecated and might be discontinued in a future release. Start
using -mnet and -cfnet parameters
to indicate network name. Modify any existing scripts and applications with -m and -cf parameters. For more information, see DB2 command and SQL statement changes summary for details. |
db2look | The db2look utility has changes
to an existing parameter. The -l parameter has
been modified to generate DDL statements for user-defined storage
groups. For more information, see Storage management has been improved for details. |
db2pd | The -catalogcache parameter
output reports details about the new table space cache. The -hadr parameter output has been completely changed. Existing fields have been renamed to match the output from the new MON_GET_HADR table function, and fields have been added to support monitoring for the new HADR multiple standby. The formatting of the output has also changed from multiple field names on one line and field values on the subsequent line to having one field per line. The serviceclasses parameter output now includes the UOW throughput, activity throughput, activity lifetime average, CPU Velocity, and CPU Utilization. The -storagepaths parameter output includes storage group configuration details. The -tablespaces parameter output now includes the storage group identifier that a table space is associated with and table space storage statistics. The -tcbstats parameter output for the column and data for IndexObjSize has been deprecated. If you perform a reorganization to reclaim extents, the IndexObjSize output does not accurately reflect the number of pages in the index object because the value still includes the pages that were released during the reorganization. You should use instead the INDEX_OBJECT_P_SIZE or INDEX_OBJECT_L_SIZE columns of the ADMIN_GET_INDEX_INFO table function to obtain accurate values. The -workclasssets parameter output is no longer in a table format. The output format lists basic work class information followed by the work class attribute information. Change applications or scripts that use the output of the db2pd command to adjust to these changes. For more information, see db2pd command has changed to support new functionality for details. |
CREATE DATABASE | Some parameter in the CREATE DATABASE command
have been deprecated. The AUTOMATIC STORAGE parameter,
the MANAGED BY SYSTEM clause in the USER
TABLESPACE parameter, and some values for COLLATE
USING parameter of the CREATE DATABASE command
have been deprecated. Collations based on the Unicode Collation Algorithm
of the Unicode Standard version 4.0.0 been deprecated. For new Unicode
databases, use the COLLATE USING clause with
a language-aware-collation or locale-sensitive-collation instead of UCA400_NO, UCA400_LSK,
or UCA400_LTH. Stop using the AUTOMATIC STORAGE parameter with the CREATE DATABASE command before it becomes discontinued. Also, remove this parameter from any scripts or applications. For more information, see Some parameters of the CREATE DATABASE command have been deprecated for details. |
EXPORT, IMPORT | Worksheet Format (WSF) for IMPORT and EXPORT utilities
has been discontinued. Use a supported file format instead of WSF files. For more information, see Worksheet Format (WSF) for IMPORT and EXPORT utilities have been discontinued for details. |
On the Windows Vista operating system, to perform administration tasks that require Local Administrator authority, you must run your scripts from a DB2 command prompt with full administrator privileges. Launch the Command Window - Administrator shortcut to get a DB2 command prompt with full administrator privileges. If extended security is enabled on the Windows Vista operating system, you also need to log on to the system with a user that is a member of the DB2ADMNS group to launch this shortcut.