IBM Support

SQLE_RC_RESUME_FAILED Error level message may be logged by "set write resume"

Question & Answer


Question

We use a shell script and run it by unix cron.  There is no associated
terminal log left so we are not sure what message was returned by them.  
But found an Error level message as SQLE_RC_RESUME_FAILED at db2diag.log.
It seems to be related to "write resume" but not sure why we receive
SQLE_RC_RESUME_FAILED message.  Could you educate us?

Answer

Here is an example test script.
-----
#!/bin/sh
db2diag -A
db2 -v terminate
db2stop force
db2start
db2 -v create db db1
db2 -v connect to db1
db2 -v set write suspend for db
db2 -v terminate
db2 -v connect to db1
db2 -v set write resume for db
db2 -v set write resume for db
db2 -v terminate
-----
If we run the above script and have a chance to look at the terminal, below
message should be returned by the second "set write resume".
---
SQL1551N  The SET WRITE RESUME command or the RESTART DATABASE command with
the WRITE RESUME parameter failed because of the condition that is indicated
by the reason code. Reason code = "2".
---
And here is the first "set write resume" associated db2diag.log message.
---
2019-04-17-23.05.01.742455-240 I83216A498           LEVEL: Info
PID     : 10158118             TID : 2058           PROC : db2sysc
INSTANCE: db2inst1             NODE : 000           DB   : DB1
APPHDL  : 0-62                 APPID: *LOCAL.db2inst1.190418030550
AUTHID  : DB2INST1             HOSTNAME: db2inst1
EDUID   : 2058                 EDUNAME: db2agent (DB1)
FUNCTION: DB2 UDB, base sys utilities, sqleSetWriteResume, probe:5603
DATA #1 : <preformatted>
Set Write Resume issued from member 0
2019-04-17-23.05.01.746729-240 E83715A551           LEVEL: Warning
PID     : 10158118             TID : 2058           PROC : db2sysc
INSTANCE: db2inst1             NODE : 000           DB   : DB1
APPHDL  : 0-62                 APPID: *LOCAL.db2inst1.190418030550
AUTHID  : DB2INST1             HOSTNAME: db2inst1
EDUID   : 2058                 EDUNAME: db2agent (DB1)
FUNCTION: DB2 UDB, base sys utilities, sqleSetWriteResume, probe:5986
MESSAGE : ADM6076W  The database is no longer in the WRITE SUSPEND state.
          Database name: "DB1     ".
---
Here is the second one's associated db2diag.log messages.
---
2019-04-17-23.05.01.834049-240 I84267A498           LEVEL: Info
PID     : 10158118             TID : 2058           PROC : db2sysc
INSTANCE: db2inst1             NODE : 000           DB   : DB1
APPHDL  : 0-62                 APPID: *LOCAL.db2inst1.190418030550
AUTHID  : DB2INST1             HOSTNAME: db2inst1
EDUID   : 2058                 EDUNAME: db2agent (DB1)
FUNCTION: DB2 UDB, base sys utilities, sqleSetWriteResume, probe:5603
DATA #1 : <preformatted>
Set Write Resume issued from member 0
2019-04-17-23.05.01.834535-240 E84766A542           LEVEL: Info
PID     : 10158118             TID : 2058           PROC : db2sysc
INSTANCE: db2inst1             NODE : 000           DB   : DB1
APPHDL  : 0-62                 APPID: *LOCAL.db2inst1.190418030550
AUTHID  : DB2INST1             HOSTNAME: db2inst1
EDUID   : 2058                 EDUNAME: db2agent (DB1)
FUNCTION: DB2 UDB, base sys utilities, sqleSetWriteResume, probe:5622
MESSAGE : ADM6077I  The database is not in the WRITE SUSPEND state.  Database
          name: "DB1     ".
2019-04-17-23.05.01.835218-240 I85309A591           LEVEL: Error
PID     : 10158118             TID : 2058           PROC : db2sysc
INSTANCE: db2inst1             NODE : 000           DB   : DB1
APPHDL  : 0-62                 APPID: *LOCAL.db2inst1.190418030550
AUTHID  : DB2INST1             HOSTNAME: db2inst1
EDUID   : 2058                 EDUNAME: db2agent (DB1)
FUNCTION: DB2 UDB, relation data serv, sqlrrRdsSetupPost, probe:6482
CALLED  : DB2 UDB, relation data serv, sqlrr_rds_common_post
RETCODE : ZRC=0x8005047C=-2147154820=SQLE_RC_RESUME_FAILED
          "Set Write Resume failed"
---
The reason why we receive SQLE_RC_RESUME_FAILED is that there two
"set write resume" commands were run in the above script.  As above second
one's messages explain, the database is "not in the WRITE SUSPEND state"
So Db2 wrote an Error message SQLE_RC_RESUME_FAILED at the end.
To prevent the Error message, review your shell script file to see if
there any chance to run "set write resume" two times or not.
The last message might be expected to have more explanation, such as
'if you use a shell script to run "set write resume", review the script
to see if there any chance to run it two or more times.  If run it
two times continuously, this error message should be logged.'.

Related Information

SET WRITE command

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
18 April 2019

UID

ibm10881710

Page Feedback