|
Problem IT05643
|
Status: Geschlossen |
WHEN THERE IS NO DATABASE FIXPACK UPDATE TO PRIMARY CF, EXPECTS SECONDARY TO COME UP IN PEER STATE WHICH NEVER HAPPENS. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
When the there is no database or no active database in the
purescale cluster. And the customer is trying to do "Rolling
fixpack update" online on the primary CF, it expecte the
secondary CF to come to "PEER" state. It looks like secondary
never comes to "PEER" state, if there is no active database.
The installfixpack return the error give below. But when there
is no db2 to start back, this is not over head for the customer
to complete the fixpack update. I this restruction needs to be
corrected.
# ./installFixPack -p /opt/ibm/db2/fp4 -I db2inst1 -l
/tmp/fp4.log -t /tmp/fp4.trc
DBI20135E The online fix pack update has halted because the
secondary CF is not in PEER state.
DBI1264E This program failed. Errors encountered during
execution were
written to the installation log file. Program name:
installFixPack. Log file name: /tmp/fp4.log.
Explanation:
This message is returned when some processes and operations have
failed.
Detailed information about the error was written to the log
file.
User response:
Contact IBM support to get assistance in resolving this issue.
Keep the
log file intact as this file is an important reference for IBM
support.
Related information:
Contacting IBM Software Support
# # su - db2inst1
$ db2instance -list
ID TYPE STATE HOME_HOST
CURRENT_HOST ALERT PARTITION_NUMBER
LOGICAL_PORT NETNAME
-- ---- ----- ---------
------------ ----- ----------------
------------ -------
0 MEMBER STARTED lpar169
lpar169 NO 0 0
lpar169-ib0
1 MEMBER STARTED lpar171
lpar171 NO 0 0
lpar171-ib0
128 CF PRIMARY lpar168
lpar168 NO - 0
lpar168-ib0
129 CF CATCHUP lpar170
lpar170 NO - 0
lpar170-ib0
HOSTNAME STATE INSTANCE_STOPPED
ALERT
-------- ----- ----------------
-----
lpar171 ACTIVE NO
NO
lpar170 ACTIVE NO
NO
lpar168 ACTIVE NO
NO
lpar169 ACTIVE NO
NO
$ exit
# |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.5 fixpack 7 *
**************************************************************** |
| Local-Fix: |
|
| Lösung |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 18.11.2014
18.02.2016
18.02.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.7
|
 |
