Under the section "Altering a Table Space", the following new sections are to be added:
You can add a container to an SMS table space on a partition (or node) that currently has no containers.
The contents of the table space are rebalanced across all containers. Access to the table space is not restricted during the rebalancing. If you need to add more than one container, you should add them all at the same time.
To add a container to an SMS table space using the command line, enter the following:
ALTER TABLESPACE <name>
ADD ('<path>')
ON NODE (<partition_number>)
The partition specified by number, and every partition (or node) in the range of partitions, must exist in the nodegroup on which the table space is defined. A partition_number may only appear explicitly or within a range in exactly one on-nodes-clause for the statement.
The following example shows how to add a new container to partition number 3 of the nodegroup used by table space "plans" on a UNIX based operating system:
ALTER TABLESPACE plans
ADD ('/dev/rhdisk0')
ON NODE (3)
The SWITCH ONLINE clause of the ALTER TABLESPACE statement can be used to move table spaces in an OFFLINE state to an ONLINE state if the containers associated with that table space have become accessible. The table space is moved to an ONLINE state while the rest of the database is still up and being used.
An alternative to the use of this clause is to disconnect all applications from the database and then to have the applications connect to the database again. This moves the table space from an OFFLINE state to an ONLINE state.
To switch the table space to an ONLINE state using the command line, enter:
ALTER TABLESPACE <name>
SWITCH ONLINE
Under the section "Tivoli Storage Manager", subsection "Managing Backups and Log Archives on TSM", the third paragraph just before "Examples of Using db2adutl:" and the last sentence in that paragraph is missing information on the right-hand side of the page. The missing information is:
You can also qualify the command with OLDER [THAN] <timestamp> or <n> DAYS. This will delete backups older than the given date (timestamp) or older than the days specified. You can also select a range of logs to be listed instead of seeing all of the logs. A specific backup for deletion can be selected by using the TAKEN AT <timestamp> parameter.
Under the section "Archive and Retrieve Considerations", the following paragraph is no longer true and should be removed from the list:
A user exit may be interrupted if a remote client loses its connection to the DB2 server. That is, while handling the archiving of logs through a user exit, one of the other SNA-connected clients dies or powers off resulting in a signal (SIGUSR1) being sent to the server. The server passes the signal to the user exit causing an interrupt. The user exit program can be modified to check for an interrupt and then continue.
The Error Handling section has a Notes list that should replace the contents of Note 3 with the following information:
Following the five minute suspension in processing requests, the next request is processed. If no error occurs with the processing of this request, then processing of new user exit program requests continues and DB2 will reissue the archive request for the log files that either failed to archive previously, or were suspended. If a return code of greater than 8 is generated during the retry, requests are suspended for an additional five minutes. The five minute suspensions continue until the problem is corrected or the database is stopped and restarted.
Once all applications disconnect from the database and the database is reopened, DB2 will issue the archive request for any log file that might not have been successfully archived in the previous use of the database.
If the user exit program fails to archive log files, your disk can be filled with log files and performance may be degraded because of extra work to format these log files. Once the disk becomes full, the database manager will not accept further application requests for database changes.
If the user exit program was called to retrieve log files, roll-forward recovery is suspended but not stopped unless a stop was specified in the ROLLFORWARD DATABASE utility. If a stop was not specified, you can correct the problem and resume recovery.
The following section has been updated:
Detailed installation information is found in DB2 Enterprise - Extended Edition for Windows Quick Beginnings.
After completing the installation of DB2 as documented in DB2 Enterprise - Extended Edition for Windows Quick Beginnings, set the following DB2 registry variables and carry out the following tasks on each database partition server in the instance:
Use the db2set command to modify the value for the registry variable. Use the db2_all command to run the db2set command on all database partition servers in the instance. You must be logged on with a user account that is a member of the Administrators group to run the db2_all command.
In the following example, the ; character is placed inside the double quotation marks to allow the request to run concurrently on all the database partition servers in the instance:
db2_all ";db2set DB2_VI_ENABLE=ON"
For more information about the db2_all command, see "Issuing Commands to Multiple Database Partition Servers" in the Administration Guide: Implementation.
For example:
db2_all ";db2set DB2_VI_DEVICE=nic0"
| Note: | With Synfinity Interconnect, this variable should be set DB2_VI_DEVICE=VINIC. The device name (VINIC) must be in upper case. |
For example:
db2_all ";db2set DB2_VI_VIPL=vipl.dll"
| Note: | The value used in the example is the default for the registry variable. For more information on the registry variables, see Administration Guide: Performance. |