LUW

Because earlier versions of the DB2 LUW did not have global variable support, MTK had to support it using an alternative method.

This is all well and good for a single database maintenance action in the LUW.

For this reason, applications with few database update operations in a single LUW are good candidates for this transaction strategy.

If the client makes multiple calls to the API for a single LUW, then the transactional unit of work must start and end at the client.

For DB2 LUW, what you can backup depends on the logging mode of the database.

However, this also means that you can have only one call from the client layer for any given logical unit of work (LUW).

DB2 LUW load does not enforce relational integrity (RI) for the data affected.

You can issue LIST DB DIRECTORY and LIST NODE DIRECTORY commands in DB2 LUW to enquire about cataloged databases and nodes respectively.

DB2 LUW also stores table data on files, directories and raw devices depending upon the type of table space.

For such large-scale data movement in LUW, you can use BACKUP and RESTORE commands with redirected restore methods or db2move tool.

The impact, however, is that you no longer have atomic updates to the database in the same LUW.

Using the wizard, Tom names the new PDM, and he determines that it should be compatible with his DB2 LUW V9. 7 database instance.

You can register an alternate DB2 LUW server at the primary server using the UPDATE ALTERNATE SERVER FOR DATABASE command.

Global variables in DB2 LUW are qualified with two part names: the schema name and variable name.

DB2 LUW provides you with an easy way to manage various memory structures through self-tuning memory management (STMM).

The waiter LUW instance 0CC544053119 was requesting a mode of locks on the same resource.

The waiter LUW instance 0E26A4053107 was requesting a mode of lock S on the same resource.

In DB2 LUW, you can perform monitoring through an Event Monitor and Snapshot Monitor.

The configuration used to characterize the benefits of using EMC EFDs in a DB2 9. 7 LUW OLTP environment is summarized in Table 2.

Operations: Transactions that represent single logical units of work (LUWs).

However, DB2 UDB for LUW has not (yet) implemented this part of the SQL standard.

While each database in DB2 LUW holds its exclusive catalog tables, it is every DB2 subsystem that holds catalog tables.

Listing 12 demonstrates online database backup and recovery methods in DB2 LUW.

In DB2 LUW, a default system temporary table space called TEMPSPACE1 will be available for such DB2 DBM requirements as sorts or joins.

A simple, yet powerful API is available in DB2 UDB V8. 2 for LUW to allow tracing of SQL Procedures.

The support for global variables was introduced in DB2 9. 5 LUW through the use of the CREATE VARIABLE syntax.

In DB2 LUW, the REORG INDEX utility can perform both functions.

While in DB2 LUW, you can also use various administrative views under schema SYSIBMADM while monitoring DB2 instance or database.

Listing 14 shows an example of creating and administering an Event Monitor in DB2 LUW.

This technique works fine if you have a single database maintenance activity within the logical unit of work (LUW).

Unlike in DB2 LUW, you can not place more than one index on an index space.

In DB2 for LUW, you can place individual partitions of such table on one or more table spaces.

The ARRAY data type was introduced in DB2 9. 5 LUW.

These are similar to private agent memory in DB2 LUW.

In DB2 LUW, you have the following two methods to define DB2 storage.

Run DB2 LUW administration commands and utilities from the SQL Editor