Error in DB2 log file while monitoring standby instance: "Direct writes are not supported on HADR Standby database." (4261167)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Error in DB2 log file while monitoring standby instance: "Direct writes are not supported on HADR Standby database."
Description

While monitoring the standby DB of a HADR DB2 setup the following error appears in the DB2 log file:
FUNCTION: DB2 UDB, buffer pool services, sqlbDirectWrite, probe:123
MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY
"The operation that attempted to modify the contents of the database failed"
DATA #1 :
Direct writes are not supported on HADR Standby database.
In the DB2 agent log file.
ERROR [AGENTNAME-lowPriorityPool-1121-[DB2_History_Locks_Wait][]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DB2HistoryLocksWaitPartitionProcessor processor of DB2_History_Locks_Wait collection.
java.lang.RuntimeException: Failed to execute collection [DB2_History_Locks_Wait], reason=[Foglight][DB2 JDBC Driver][DB2]Error occured with SQLCode -1773 with the following parameters: 5, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, SQL-Parameters = [0],[0],
Cause

DB2 bug - look at here.
Resolution

According to the DB2 bug report set the following parameter on the standby DB:
"DB2_STANDBY_ISO=UR"
Or upgrade to the latest DB2 fixpack of 10.5.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title