|
Problem IT25990
|
Status: Closed |
STARTING HADR AS STANDBY ON A PURESCALE DATABASE COULD SOMETIME RETURN SQL1776N RC7
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Start hadr requires instance file lock in exclusive mode.
However, if there is another connection from another member that
holds the instance file lock in shared mode, the start hadr
command would fail with SQL1776N rc7.
The following diagnostic message can be found in db2diag.log:
2018-08-09-16.22.59.315402-240 I391461E622 LEVEL:
Error
PID : 25626 TID : 140080781977344 KTID : 4535
PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
TESTDB
APPHDL : 0-56 APPID: *N0.yhao.180809202116
AUTHID : DB2INST1 HOSTNAME: DB2INST1
EDUID : 28 EDUNAME: db2agent (TESTDB) 0
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::FirstConnect, probe:9689
MESSAGE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing
violation."
DIA8519C A file sharing violation has occurred,
filename was "". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT25967
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.08.2018
27.11.2018
27.11.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
