You may receive SQL5160N when updating the database
configuration parameter, mirrologpath, on the pureScale
environment.
Here are the example steps:
$ db2 get db cfg for sample |grep MIRROR
==> worked. Mirror log path is returned.
$ db2 update db cfg for sample using MIRRORLOGPATH NULL
==> worked. Complete is returned.
$ db2 activate db sample
==> completed.
$ db2 deactivate db sample
==> completed.
*** Then tried to set the parameter again, SQL5160N is reported.
$ db2 update db cfg for sample using MIRRORLOGPATH /log2
==> SQL5160N
*** Even tried to re-connect, SQL5160N still gets reported.
$ db2 terminate
$ db2 deactivate db sample
$ db2 activate db sample
$ db2 connect to sample
$ db2 update db cfg for sample using MIRRORLOGPATH /log2
==> SQL5160N
You may find similar messages at db2diag.log as below:
...
2011-02-08-21.57.31.793103+540 E114471A651 LEVEL:
Warning
PID : 11862174 TID : 71733 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-4188 APPID: *N0.db2inst1.110208125719
AUTHID : DB2INST1
EDUID : 71733 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, config/install, sqlfudb_backend, probe:695
DATA #1 : <preformatted>
The database configuration parameter update was not
broadcast to all nodes because the update contains
an HA supported parameter and is being done in a cluster
environment. Update the parameter to a unique
value on each node.
2011-02-08-21.57.31.813055+540 I115123A494 LEVEL: Error
PID : 11862174 TID : 71733 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-4188 APPID: *N0.db2inst1.110208125719
AUTHID : DB2INST1
EDUID : 71733 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, config/install, sqlfUpdateDbCfg, probe:90
MESSAGE : ZRC=0xFFFFEBD8=-5160
DATA #1 : String, 38 bytes
Error updating global DB config, rc =
... |
