2The NUM_LOG_SPAN specifies the maximum number of log files that a 2transaction can span. If at any time a transaction violates the 2NUM_LOG_SPAN setting, it is rolled back, and forces the application that 2caused the transaction off the database.
2However, in a multi-partition system, the db2loggr process can only force 2an application if the coordinating node for the application and the node of 2the db2loggr process that detects the error are both the same. For 2example, you have a system with 3 nodes (0,1 and 2) and have set the 2NUM_LOG_SPAN parameter to 2 on all nodes. An application connects to 2node 2 of the database, and begins a long-running transaction, which spans 2more than 2 log files. If the db2loggr process on node 1 is the first 2to detect this error, then nothing will happen. However, if the 2violation also occurs on node 2, then the db2loggr process will notice the 2error, the transaction will be rolled back and the application will be forced 2off.