By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,787 Members | 2,251 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,787 IT Pros & Developers. It's quick & easy.

DB2 Backup strange Problem

P: n/a

Hi,

I have 3 systems with db2 running on AIX. We take online backup on
weekdays and offline on saturday. For the past two weeks the offline
backup is getting terminated after exactly 2 hours 13 minutes on two
systems. I am getting a timestamp in the backup history file. The third
system takes only 30 minutes to backup. The db2diag.log file is attached
below. I increased the UTIL_HEAP_SZ parameter. Still no use. Can
somebody please tell me why this is happening.

Also for the past 1 month I am not able to stop db2 using db2stop. I
always have to use db2_kill.

2006-05-07-00.49.36.300161+330 I38570A378 LEVEL: Warning
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl,
probe:2025
MESSAGE : Starting an offline db backup.

2006-05-07-00.49.36.434173+330 E38949A509 LEVEL: Warning
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemLogPoolConditions,
probe:20
DATA #1 : <preformatted>
Configured heap limit exceeded for Backup/Restore/Util Heap
(UTIL_HEAP_SZ) on node 0. Allocating additional memory from the
overflow buffer.

2006-05-07-00.53.45.252407+330 I39459A411 LEVEL: Severe
PID : 70286 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-13 APPID: AC100897.KB0E.00E7C6191937
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-01.19.30.817373+330 I41519A411 LEVEL: Severe
PID : 13730 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-18 APPID: AC100897.LA0E.00E7C6194523
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-01.34.58.155469+330 I42755A411 LEVEL: Severe
PID : 52624 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-21 APPID: AC100897.M30E.00E7C6200050
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"
2006-05-07-01.50.25.585710+330 I43991A411 LEVEL: Severe
PID : 55204 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-24 APPID: AC100897.MB0E.00E7C6201618
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-01.55.34.694613+330 I44403A411 LEVEL: Severe
PID : 70190 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-25 APPID: AC100897.MF0E.00E7C6202127
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.00.43.814687+330 I44815A411 LEVEL: Severe
PID : 52574 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-26 APPID: AC100897.N10E.00E7C6202636
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.05.52.935864+330 I45227A411 LEVEL: Severe
PID : 52704 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-27 APPID: AC100897.N60E.00E7C6203145
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.11.02.042180+330 I45639A411 LEVEL: Severe
PID : 70754 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-28 APPID: AC100897.N80E.00E7C6203654
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.16.11.150675+330 I46051A411 LEVEL: Severe
PID : 52682 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-29 APPID: AC100897.NC0E.00E7C6204203
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.21.20.261072+330 I46463A411 LEVEL: Severe
PID : 54902 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-30 APPID: AC100897.NE0E.00E7C6204712
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.26.29.367765+330 I46875A411 LEVEL: Severe
PID : 70852 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-31 APPID: AC100897.O00E.00E7C6205221
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.31.38.473976+330 I47287A411 LEVEL: Severe
PID : 55056 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-32 APPID: AC100897.O40E.00E7C6205730
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.36.47.583247+330 I47699A411 LEVEL: Severe
PID : 13748 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-33 APPID: AC100897.O60E.00E7C6210240
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.41.56.705347+330 I48111A411 LEVEL: Severe
PID : 54912 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-34 APPID: AC100897.OB0E.00E7C6210749
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.47.05.812230+330 I48523A411 LEVEL: Severe
PID : 55140 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-35 APPID: AC100897.OD0E.00E7C6211258
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.52.14.920730+330 I48935A411 LEVEL: Severe
PID : 13584 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-39 APPID: AC100897.P10E.00E7C6211807
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.57.24.033026+330 I49347A411 LEVEL: Severe
PID : 13712 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-42 APPID: AC100897.P30E.00E7C6212316
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-03.00.40.934176+330 I49759A440 LEVEL: Severe
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubPollMsg, probe:1
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0780000275180890 : FFFF F82F .../

2006-05-07-03.00.40.945802+330 I50200A420 LEVEL: Error
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubPollMsg, probe:1
DATA #1 : Hexdump, 4 bytes
0x0780000275180890 : FFFF F82F .../

2006-05-07-03.00.52.375892+330 I50621A352 LEVEL: Severe
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:140
MESSAGE : Backup Terminated.

Dileep
--
vdileep
------------------------------------------------------------------------
vdileep's Profile: http://www.dbtalk.net/m311
View this thread: http://www.dbtalk.net/t304978

May 8 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
vdileep wrote:
Hi,

I have 3 systems with db2 running on AIX. We take online backup on
weekdays and offline on saturday. For the past two weeks the offline
backup is getting terminated after exactly 2 hours 13 minutes on two
systems. I am getting a timestamp in the backup history file. The third
system takes only 30 minutes to backup. The db2diag.log file is attached
below. I increased the UTIL_HEAP_SZ parameter. Still no use. Can
somebody please tell me why this is happening.

Also for the past 1 month I am not able to stop db2 using db2stop. I
always have to use db2_kill.

2006-05-07-00.49.36.300161+330 I38570A378 LEVEL: Warning
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl,
probe:2025
MESSAGE : Starting an offline db backup.

2006-05-07-00.49.36.434173+330 E38949A509 LEVEL: Warning
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, SQO Memory Management, sqloMemLogPoolConditions,
probe:20
DATA #1 : <preformatted>
Configured heap limit exceeded for Backup/Restore/Util Heap
(UTIL_HEAP_SZ) on node 0. Allocating additional memory from the
overflow buffer.

2006-05-07-00.53.45.252407+330 I39459A411 LEVEL: Severe
PID : 70286 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-13 APPID: AC100897.KB0E.00E7C6191937
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-01.19.30.817373+330 I41519A411 LEVEL: Severe
PID : 13730 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-18 APPID: AC100897.LA0E.00E7C6194523
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-01.34.58.155469+330 I42755A411 LEVEL: Severe
PID : 52624 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-21 APPID: AC100897.M30E.00E7C6200050
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"
2006-05-07-01.50.25.585710+330 I43991A411 LEVEL: Severe
PID : 55204 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-24 APPID: AC100897.MB0E.00E7C6201618
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-01.55.34.694613+330 I44403A411 LEVEL: Severe
PID : 70190 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-25 APPID: AC100897.MF0E.00E7C6202127
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.00.43.814687+330 I44815A411 LEVEL: Severe
PID : 52574 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-26 APPID: AC100897.N10E.00E7C6202636
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.05.52.935864+330 I45227A411 LEVEL: Severe
PID : 52704 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-27 APPID: AC100897.N60E.00E7C6203145
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.11.02.042180+330 I45639A411 LEVEL: Severe
PID : 70754 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-28 APPID: AC100897.N80E.00E7C6203654
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.16.11.150675+330 I46051A411 LEVEL: Severe
PID : 52682 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-29 APPID: AC100897.NC0E.00E7C6204203
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.21.20.261072+330 I46463A411 LEVEL: Severe
PID : 54902 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-30 APPID: AC100897.NE0E.00E7C6204712
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.26.29.367765+330 I46875A411 LEVEL: Severe
PID : 70852 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-31 APPID: AC100897.O00E.00E7C6205221
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.31.38.473976+330 I47287A411 LEVEL: Severe
PID : 55056 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-32 APPID: AC100897.O40E.00E7C6205730
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.36.47.583247+330 I47699A411 LEVEL: Severe
PID : 13748 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-33 APPID: AC100897.O60E.00E7C6210240
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.41.56.705347+330 I48111A411 LEVEL: Severe
PID : 54912 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-34 APPID: AC100897.OB0E.00E7C6210749
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.47.05.812230+330 I48523A411 LEVEL: Severe
PID : 55140 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-35 APPID: AC100897.OD0E.00E7C6211258
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.52.14.920730+330 I48935A411 LEVEL: Severe
PID : 13584 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-39 APPID: AC100897.P10E.00E7C6211807
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-02.57.24.033026+330 I49347A411 LEVEL: Severe
PID : 13712 TID : 1 PROC : db2agent
(instance) 0
INSTANCE: db2prd NODE : 000
APPHDL : 0-42 APPID: AC100897.P30E.00E7C6212316
FUNCTION: DB2 UDB, base sys utilities, sqleattach_agent, probe:60
RETCODE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC
"External Comm error"

2006-05-07-03.00.40.934176+330 I49759A440 LEVEL: Severe
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubPollMsg, probe:1
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x0780000275180890 : FFFF F82F .../

2006-05-07-03.00.40.945802+330 I50200A420 LEVEL: Error
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubPollMsg, probe:1
DATA #1 : Hexdump, 4 bytes
0x0780000275180890 : FFFF F82F .../

2006-05-07-03.00.52.375892+330 I50621A352 LEVEL: Severe
PID : 33470 TID : 1 PROC : db2agent (PRD)
0
INSTANCE: db2prd NODE : 000 DB : PRD
APPHDL : 0-12 APPID: *LOCAL.db2prd.060506191919
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:140
MESSAGE : Backup Terminated.

Dileep

How large is the backup image just before it terminates? I suspect you
are hitting the file size limit? Is the file system where you are
placing the backup images large file enabled? If not then you may be
hitting the 2GB default file size limit.

Bob
May 8 '06 #2

P: n/a

Hi

I am backing up on Tape. My DB size is more than 600 GB and I am
backing up on a 200/400 GB Tape. I am basically an AIX admin but I am
being asked to take care of db2 also now.
One more thing I forgot to tell you. We had installed Tivoli TSM on the
machines but it was not a success. So we are not using it. I wonder
whether any configuration was changed by TSM.
Also my online backup on the same database with same tape succeeds.

Thanks in advance

With Regards

Dileep
--
vdileep
------------------------------------------------------------------------
vdileep's Profile: http://www.dbtalk.net/m311
View this thread: http://www.dbtalk.net/t304978

May 10 '06 #3

P: n/a

Hi,

The problem has been resolved. There was some monitoring tool which was
being run by the customer.

Thanks for all the help

Dileep
--
vdileep
------------------------------------------------------------------------
vdileep's Profile: http://www.dbtalk.net/m311
View this thread: http://www.dbtalk.net/t304978

May 15 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.