DB2 - Problembeschreibung
Problem IC72063 | Status: Geschlossen |
TWO OR MORE CONCURRENT INVOCATIONS OF SYSPROC.DB2LOAD FAIL WITH SQL3508. COLLIDE ON TEMP FILE db2p0t0.msg | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
If the sysproc.db2load system stored procedure is invoked concurrently by two or more applications, even if these applications are connected to different databases or dbm instances on the same machine, they will attempt to use the same temporary file. So one of them will fail with a "SQL3508N Error in accessing a file or path". A db2diag.log message showing the failure to access temp file "db2p0t0.msg" can be seen in the db2diag.log: 2010-06-10-14.19.38.817428+480 E27875747E552 LEVEL: Warning (OS) PID : 15361 TID : 140606899443440PROC : db2agent (SAMPLE) 0 INSTANCE: db2inst5 NODE : 000 DB : SAMPLE FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" DIA8701C Access denied for resource "", operating system return code was "". CALLED : OS, -, open OSERR: EACCES (13) DATA #1 : File name, 16 bytes /tmp/db2p0t0.msg | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users doing concurrent load job via sysproc.db2load * **************************************************************** * PROBLEM DESCRIPTION: * * During a concurrent load job via sysproc.db2load, one job * * will create the file /tmp/db2p0t0.msg. The other load job * * will fail with "SQL3508N Error in accessing a file or path" * **************************************************************** * RECOMMENDATION: * * Upgrade to V95 FP 8 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.10.2010 07.07.2011 07.07.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP8 | |
Problem behoben lt. FixList in der Version | |
9.5.0.8 |