1. Manuals
  2. Brands
  3. Computer Equipment
  4. Server
  5. IBM
  6. Computer Equipment
  7. Server

IBM 000-8697 Long Transactions

1 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 702
Download on canonical page 702 pages, 4.15 Mb
System Architecture 2-159
Long Transactions
To free a logical log, the log must be backed up to tape and all records with
the logical log must be part of closed transactions. If any record in the log is
part of an open transaction, the log file cannot be freed.
The backup strategy for OnLine requires that the statement that creates a
blobspace and the statements that insert blobs into that blobspace must
appear in separate logical log files.
Therefore,after you create a blobspace, you must switch to a new logical log
beforeyou can insert a blob into that blobspace. Execute tbmode -l to switch
to a new logical log.
Theblobspace logging procedure affects the way that blobspaces are treated
duringan archive. During an archive, the tbtape process blocks allocation of
blobspace blobpages in a chunk until it has read the chunk and archived all
used blobpages therein. As soon as the chunk is archived, blobpage
allocation in that chunk resumes.
One implication of this procedure is that during an online archive, blobs
cannot be inserted into a blobspace until the blobspace chunk has been
archived.Since chunks are read and archived by tbtape in order of the chunk
identification numbers, you can minimize this inconvenience by creating
blobspaces early, ensuring them a low chunk ID number.
Tounderstand why the archive must block allocation, refer to page 4-30 for a
full description of what happens during an archive.
Long Transactions
A long-transaction condition occurs when the logical log fills past the mark
specifiedby the first long-transaction high-water mark,LTXHWM. The source of
the long-transaction condition is an open transaction that is preventing the
operator from freeing logical log files to create additional free space in the
log. (No log file can be freed if any records in the file are associated with an
open transaction.) The open transaction might not be generating many
logical log records itself; the problem might be the duration of the trans-
action.If the open transaction spans several logical log files, records written
byother processes can fill the logical log while the open transaction prevents
individual logical log files from becoming free.
MENU

Models

Contents