DB2 - Problembeschreibung
Problem IC96277 | Status: Geschlossen |
SQL1086C WHEN CREATING DATABASE IF CURRENT WORKING DIRECTORY (CWD) IS EMPTY. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
DB2 may report an SQL1086C "An operating system error "<error>" occurred" when attempting to create databases via scripts or through a program with multiple users/processes. The db2diag.log will contain an entry like this: 2013-02-13-08.25.57.545045-300 E132099774B231 LEVEL: Error (OS) PID : 15113 TID : 140632278427392PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE EDUID : 534 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, oper system services, sqloqcurdir, probe:20 MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." DIA8411C A file "" could not be found. CALLED : OS, -, getcwd OSERR: ENOENT (2) DATA #1 : unsigned integer, 8 bytes 255 DATA #2 : String, 6 bytes ./.... The source of the problem is that the current working directory is deleted which causes the creation of the database to fail. Steps to check if the current working directory was deleted: > ps -ef | grep db2sysc db2inst1 88345 12334 0 09:54 ? 00:02:31 db2sysc 0 db2inst1 37391 94131 0 17:53 pts/2 00:00:00 grep db2sysc > ls -l /proc/88345/cwd lrwxrwxrwx 1 db2inst1 db2iadm1 0 Feb 15 17:54 /proc/14010/cwd -> /tmp/db2inst1/SAMPLE/mytables (deleted) | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Linux/Unix * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1, Fix pack 3 * **************************************************************** | |
Local-Fix: | |
Recycling the DB2 instance will replace the current working directory with a new one. db2stop force db2start | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1, Fix pack 3 | |
Workaround | |
see Local Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.09.2013 17.10.2013 17.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |