|
Problem IC86146
|
Status: Geschlossen |
IN MULTIPLE DATABASE PARTITIONS ENVIRONMENT, SINGLE SYSTEM VIEW (SSV) BACKUP MAY RUN INTO VIOLATING NUM_LOG_SPAN PROBLEM WITH AD |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
As a rule, DB2 backup commands are excluded from the limitation
imposed by the num_log_span configuration parameter.
However, while doing the Single System View (SSV) backup in
multiple database partitions environment, violating num_log_span
problem might be raised up with ADM1541W message as belowing
db2diag.log entries:
2012-04-09-17.10.55.303124-240 E315779748E486 LEVEL: Info
PID : 7049 TID : 46916997998912PROC :
db2sysc 1
INSTANCE: Christine NODE : 001 DB : Allan
APPHDL : 1-30160 APPID: *N1.nypxt330.120411094113
AUTHID : MSDB2
EDUID : 37375 EDUNAME: db2agent (Allan) 1
FUNCTION: DB2 UDB, database utilities, sqlubMPPRequestor,
probe:543
DATA #1 : <preformatted>
Starting a multi-partition backup on 5 partitions.
...skip...
2012-04-09-23.40.39.472662-240 E355895137E710 LEVEL: Error
PID : 8048 TID : 46912925329728PROC :
db2sysc 3
INSTANCE: Christine NODE : 003 DB : Allan
EDUID : 86 EDUNAME: db2loggr (R1SCENA) 3
FUNCTION: DB2 UDB, data protection services,
sqlpScanTranTableForLowTran, probe:550
MESSAGE : ADM1541W Application "db2bp" with application handle
"1-30160" and
application id "*N1.Christine.120411094113" executing
under
authentication id "AlanDB2 " has been forced off of
the database for
violating database configuration parameter
NUM_LOG_SPAN (current
value "17"). The unit of work will be rolled back.
During SSV backups, log span immunity is set only for the
MPPRequestor agent (ie. the coordinator of all the backup
agents). However, the same immunity is not granted to the actual
backup agents spawned by the coordinator. In a non-SSV backup
there is no MPPRequestor and the backup agent itself is granted
log span immunity, thus the situation arises only in the SSV
case. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL USERS *
****************************************************************
* PROBLEM DESCRIPTION: *
* As a rule, DB2 backup commands are excluded from the *
* limitation *
* imposed by the num_log_span configuration parameter. *
* *
* However, while doing the Single System View (SSV) backup in *
* multiple database partitions environment, violating *
* num_log_span *
* problem might be raised up with ADM1541W message as belowing *
* db2diag.log entries: *
* *
* 2012-04-09-17.10.55.303124-240 E315779748E486 LEVEL: *
* Info *
* PID : 7049 TID : 46916997998912PROC : *
* db2sysc 1 *
* INSTANCE: Christine NODE : 001 DB : *
* Allan *
* APPHDL : 1-30160 APPID: *
* *N1.nypxt330.120411094113 *
* AUTHID : MSDB2 *
* EDUID : 37375 EDUNAME: db2agent (Allan) 1 *
* FUNCTION: DB2 UDB, database utilities, sqlubMPPRequestor, *
* probe:543 *
* DATA #1 : <preformatted> *
* Starting a multi-partition backup on 5 partitions. *
* *
* ...skip... *
* *
* 2012-04-09-23.40.39.472662-240 E355895137E710 LEVEL: *
* Error *
* PID : 8048 TID : 46912925329728PROC : *
* db2sysc 3 *
* INSTANCE: Christine NODE : 003 DB : *
* Allan *
* EDUID : 86 EDUNAME: db2loggr (R1SCENA) 3 *
* FUNCTION: DB2 UDB, data protection services, *
* sqlpScanTranTableForLowTran, probe:550 *
* MESSAGE : ADM1541W Application "db2bp" with application *
* handle *
* "1-30160" and *
* application id "*N1.Christine.120411094113" *
* executing *
* under *
* authentication id "AlanDB2 " has been forced off *
* of *
* the database for *
* violating database configuration parameter *
* NUM_LOG_SPAN (current *
* value "17"). The unit of work will be rolled back. *
* *
* During SSV backups, log span immunity is set only for the *
* MPPRequestor agent (ie. the coordinator of all the backup *
* agents). However, the same immunity is not granted to the *
* actual *
* backup agents spawned by the coordinator. In a non-SSV *
* backup *
* there is no MPPRequestor and the backup agent itself is *
* granted *
* log span immunity, thus the situation arises only in the SSV *
* case. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v101fp2 *
* *
* or *
* *
* As a temporary workaround: *
* Do not use SSV backup if the value of NUM_LOG_SPAN is not 0. *
**************************************************************** |
| Local-Fix: |
Do not use SSV backup if the value of NUM_LOG_SPAN is not 0. |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
The problem has been fixed in v101fp2 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 26.08.2012
14.10.2012
14.10.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
