suche 36x36
Neueste VersionenFixList
11.1.0.7 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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT25967 Status: Geschlossen

STARTING HADR AS STANDBY ON A PURESCALE DATABASE COULD SOMETIME RETURN
SQL1776N RC7

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
****************************************************************
* USERS AFFECTED:                                              *
* purescale                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to release inclusive of this fix. Refer to SYSROUTE  *
* APAR.                                                        *
****************************************************************
Local-Fix:
To prevent connections from other members affecting the 'start
hadr' command, we recommend the following steps:

1. db2stop and db2start on the standby instance

2. For each member on the standby instance, issue "db2trc on
-debug DB2.SQLCC.sqlcctcpconnmgr_child.115 -suspend".

This will stop all incoming TCP connections.

3. Start hadr as standby.

4. For each member, issue "db2trc off" to resume the incoming db
connections.
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : 
Nachfolger : IT25990 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.08.2018
26.10.2018
12.11.2018
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version