Latest versionsfixlist
11.1.0.6 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC79624 Status: Closed

DB2LOGGR REPORTS "FILE SHARING VIOLATION" IN FUNCTION SQLPGIFL()
TO INITIALIZE A TRANSACTION LOG FILE.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
1. Creation of child processes of db2sysc can be observed before 
"File sharing violation." 
 
2. The file sharing error must be reported in db2diag.log as 
follows: 
 
2011-10-28-06.44.59.880022+480 I72250072A467      LEVEL: Error 
PID     : 889178               TID  : 9768        PROC : db2sysc 
0 
INSTANCE: xxxxx             NODE : 000         DB   : xxxxx 
EDUID   : 9768                 EDUNAME: db2loggr (xxxx_ 0 
FUNCTION: DB2 UDB, data protection services, sqlpgifl, probe:130 
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing 
violation." 
          DIA8519C A file sharing violation has occurred, 
filename was "". 
 
3.  Log file cannot be used and logging was stopped because an 
new log isn't created successfully. 
 
2011-10-28-06.45.13.749354+480 I73016319A455      LEVEL: Error 
PID     : 889178               TID  : 9768        PROC : db2sysc 
0 
INSTANCE: xxx                NODE : 000         DB   : xxxx 
EDUID   : 9768                 EDUNAME: db2loggr (BCUP01) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgsck, probe:430 
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error. 
 
2011-10-28-06.45.13.749704+480 I73016775A525      LEVEL: Severe 
PID     : 889178               TID  : 9768        PROC : db2sysc 
0 
INSTANCE: xxxxx            NODE : 000         DB   : xxxxx 
EDUID   : 9768                 EDUNAME: db2loggr (BCUP01) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgasn, probe:290 
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error. 
DATA #1 : String, 41 bytes 
Logging can not continue due to an error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* 1. Creation of child processes of db2sysc can be observed    * 
* before                                                       * 
* "File sharing violation."                                    * 
*                                                              * 
* 2. The file sharing error must be reported in db2diag.log as * 
* follows:                                                     * 
*                                                              * 
* 2011-10-28-06.44.59.880022+480 I72250072A467      LEVEL:     * 
* Error                                                        * 
* PID    : 889178              TID  : 9768        PROC :       * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: xxxxx            NODE : 000        DB  : xxxxx     * 
* EDUID  : 9768                EDUNAME: db2loggr (xxxx_ 0      * 
* FUNCTION: DB2 UDB, data protection services, sqlpgifl,       * 
* probe:130                                                    * 
* RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing * 
* violation."                                                  * 
*           DIA8519C A file sharing violation has occurred,    * 
* filename was "".                                             * 
*                                                              * 
* 3.  Log file cannot be used and logging was stopped because  * 
* an                                                           * 
* new log isn't created successfully.                          * 
*                                                              * 
* 2011-10-28-06.45.13.749354+480 I73016319A455      LEVEL:     * 
* Error                                                        * 
* PID    : 889178              TID  : 9768        PROC :       * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: xxx                NODE : 000        DB  : xxxx    * 
* EDUID  : 9768                EDUNAME: db2loggr (BCUP01) 0    * 
* FUNCTION: DB2 UDB, data protection services, sqlpgsck,       * 
* probe:430                                                    * 
* RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File   * 
* cannot be used"                                              * 
*           DIA8414C Logging can not continue due to an error. * 
*                                                              * 
* 2011-10-28-06.45.13.749704+480 I73016775A525      LEVEL:     * 
* Severe                                                       * 
* PID    : 889178              TID  : 9768        PROC :       * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: xxxxx            NODE : 000        DB  : xxxxx     * 
* EDUID  : 9768                EDUNAME: db2loggr (BCUP01) 0    * 
* FUNCTION: DB2 UDB, data protection services, sqlpgasn,       * 
* probe:290                                                    * 
* MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File   * 
* cannot be used"                                              * 
*           DIA8414C Logging can not continue due to an error. * 
* DATA #1 : String, 41 bytes                                   * 
* Logging can not continue due to an error.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.5FP9 and  higher versions.                      * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The problem will be addressed in V9.5FP9 and higher versions
Workaround
N/A
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC79923 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2011
22.03.2012
22.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.