CDR error on stop/start Answered: green (solid confidence) — Madison Pruet (IBM) explains the RQM spool errors simply mean transactions were being spooled when 'cdr stop' interrupted them; the original poster explicitly confirms he now has no worry about it.

Advisory only.

Posted in 2012

Topics: High Availability & Replication, Logging & Checkpoints

FRANK — Tue, 03 Jan 2012 15:38:15 — source: IIUG Forums & Mailing Lists

Folks, IDS11.50 FC8, RedHat Linux When I did "cdr stop /start", I saw the following error messages in online log, any idea? what attention we should pay? action needed? Thanks, Frank 15:33:59 CDR NIF Shutdown: connections all shutdown. 15:33:59 CDR The NIF sub-component has shut down. 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12d/0x(nil)) status=-1 SQLERR=0 thread 9574132 queue control_send 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12d/0x(nil)) status=-1 SQLERR=0 thread 9574132 queue control_send 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12d/0x0) failed on CNTRL 15:34:00 CDR GC: operation control message construction failed (error -1). 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12e/0x(nil)) status=-1 SQLERR=0 thread 9574133 queue control_send 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12e/0x(nil)) status=-1 SQLERR=0 thread 9574133 queue control_send 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12e/0x0) failed on CNTRL 15:34:00 CDR GC: operation control message construction failed (error -1). 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12f/0x(nil)) status=-1 SQLERR=0 thread 9574135 queue control_send 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12f/0x(nil)) status=-1 SQLERR=0 thread 9574135 queue control_send 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12f/0x0) failed on CNTRL 15:34:00 CDR GC: operation control message construction failed (error -1). 15:34:02 DDR Log Snooping - Shutdown 15:34:03 CDR shutdown complete 15:36:24 CDR GC: catalog recovery begin 15:36:24 CDR GC: operation control message construction failed (error -1). 15:36:25 CDR GC: operation control message construction failed (error -1). 15:36:26 CDR GC: operation control message construction failed (error -1). 15:36:27 Logical Log 19705 Complete, timestamp: 0x61879cf8. 15:36:27 Logical Log 19705 - Backup Started 15:36:27 CDR GC: catalog recovery complete 15:36:27 CDR queuer initialization complete 15:36:27 CDR NIF listening on asf://g_nsofops 15:36:27 DDR Log Snooping - Snooping started in log 19705 15:36:27 CDR: Re-connected to server, id 22, name <g_ncdcops> 15:36:27 CDR: Re-connected to server, id 23, name <g_ngdcops> 15:36:32 Logical Log 19705 - Backup Completed --0016e6dee825a010c404b5a17cdd

↪ replying to FRANK

Madison Pruet — Tue, 03 Jan 2012 16:32:57 — source: IIUG Forums & Mailing Lists

It means that we were spooling transactions at the time that cdr stop was issued and that the spooling was interrupted. From: "FRANK" <yunyaoqu@gmail.com> To: ids@iiug.org Date: 01/03/2012 09:39 AM Subject: CDR error on stop/start [25791] Sent by: ids-bounces@iiug.org Folks, IDS11.50 FC8, RedHat Linux When I did "cdr stop /start", I saw the following error messages in online log, any idea? what attention we should pay? action needed? Thanks, Frank 15:33:59 CDR NIF Shutdown: connections all shutdown. 15:33:59 CDR The NIF sub-component has shut down. 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12d/0x(nil)) status=-1 SQLERR=0 thread 9574132 queue control_send 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12d/0x(nil)) status=-1 SQLERR=0 thread 9574132 queue control_send 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12d/0x0) failed on CNTRL 15:34:00 CDR GC: operation control message construction failed (error -1). 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12e/0x(nil)) status=-1 SQLERR=0 thread 9574133 queue control_send 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12e/0x(nil)) status=-1 SQLERR=0 thread 9574133 queue control_send 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12e/0x0) failed on CNTRL 15:34:00 CDR GC: operation control message construction failed (error -1). 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12f/0x(nil)) status=-1 SQLERR=0 thread 9574135 queue control_send 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12f/0x(nil)) status=-1 SQLERR=0 thread 9574135 queue control_send 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12f/0x0) failed on CNTRL 15:34:00 CDR GC: operation control message construction failed (error -1). 15:34:02 DDR Log Snooping - Shutdown 15:34:03 CDR shutdown complete 15:36:24 CDR GC: catalog recovery begin 15:36:24 CDR GC: operation control message construction failed (error -1). 15:36:25 CDR GC: operation control message construction failed (error -1). 15:36:26 CDR GC: operation control message construction failed (error -1). 15:36:27 Logical Log 19705 Complete, timestamp: 0x61879cf8. 15:36:27 Logical Log 19705 - Backup Started 15:36:27 CDR GC: catalog recovery complete 15:36:27 CDR queuer initialization complete 15:36:27 CDR NIF listening on asf://g_nsofops 15:36:27 DDR Log Snooping - Snooping started in log 19705 15:36:27 CDR: Re-connected to server, id 22, name <g_ncdcops> 15:36:27 CDR: Re-connected to server, id 23, name <g_ngdcops> 15:36:32 Logical Log 19705 - Backup Completed --0016e6dee825a010c404b5a17cdd ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Madison Pruet

FRANK — Tue, 03 Jan 2012 16:55:44 — source: IIUG Forums & Mailing Lists

OK. Madison, then I have no worry about it. Thanks! Frank On Tue, Jan 3, 2012 at 11:32 AM, Madison Pruet <mpruet@us.ibm.com> wrote: > It means that we were spooling transactions at the time that cdr stop was > issued and that the spooling was interrupted. > > From: "FRANK" <yunyaoqu@gmail.com> > > To: ids@iiug.org > > Date: 01/03/2012 09:39 AM > > Subject: CDR error on stop/start [25791] > > Sent by: ids-bounces@iiug.org > > Folks, > > IDS11.50 FC8, RedHat Linux > > When I did "cdr stop /start", I saw the following error messages in > online log, any idea? what attention we should pay? action needed? > > Thanks, > Frank > > 15:33:59 CDR NIF Shutdown: connections all shutdown. > 15:33:59 CDR The NIF sub-component has shut down. > 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12d/0x(nil)) > > status=-1 SQLERR=0 thread 9574132 queue control_send > 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12d/0x(nil)) > > status=-1 SQLERR=0 thread 9574132 queue control_send > 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12d/0x0) failed on CNTRL > 15:34:00 CDR GC: operation control message construction failed (error -1). > 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12e/0x(nil)) > > status=-1 SQLERR=0 thread 9574133 queue control_send > 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12e/0x(nil)) > > status=-1 SQLERR=0 thread 9574133 queue control_send > 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12e/0x0) failed on CNTRL > 15:34:00 CDR GC: operation control message construction failed (error -1). > 15:34:00 CDR RQM: rqmSpoolHeader() failed for KEY (21/0/0x0x12f/0x(nil)) > > status=-1 SQLERR=0 thread 9574135 queue control_send > 15:34:00 CDR RQM: rqmSpoolTxn() failed for KEY (21/0/0x0x12f/0x(nil)) > > status=-1 SQLERR=0 thread 9574135 queue control_send > 15:34:00 CDR Queuer: rqmQueueTxn (21/0/0x12f/0x0) failed on CNTRL > 15:34:00 CDR GC: operation control message construction failed (error -1). > 15:34:02 DDR Log Snooping - Shutdown > 15:34:03 CDR shutdown complete > > 15:36:24 CDR GC: catalog recovery begin > 15:36:24 CDR GC: operation control message construction failed (error -1). > 15:36:25 CDR GC: operation control message construction failed (error -1). > 15:36:26 CDR GC: operation control message construction failed (error -1). > 15:36:27 Logical Log 19705 Complete, timestamp: 0x61879cf8. > > 15:36:27 Logical Log 19705 - Backup Started > 15:36:27 CDR GC: catalog recovery complete > 15:36:27 CDR queuer initialization complete > 15:36:27 CDR NIF listening on asf://g_nsofops > 15:36:27 DDR Log Snooping - Snooping started in log 19705 > 15:36:27 CDR: Re-connected to server, id 22, name <g_ncdcops> > 15:36:27 CDR: Re-connected to server, id 23, name <g_ngdcops> > 15:36:32 Logical Log 19705 - Backup Completed > > --0016e6dee825a010c404b5a17cdd > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --f46d043be264b0999f04b5a2914e

CDR error on stop/start Answered: green (solid confidence) — Madison Pruet (IBM) explains the RQM spool errors simply mean transactions were being spooled when 'cdr stop' interrupted them; the original poster explicitly confirms he now has no worry about it.

Advisory only.

Glossary

Your privacy choices

CDR error on stop/start ✓ Answered: green (solid confidence) — Madison Pruet (IBM) explains the RQM spool errors simply mean transactions were being spooled when 'cdr stop' interrupted them; the original poster explicitly confirms he now has no worry about it.Advisory only.

Glossary

CDR error on stop/start Answered: green (solid confidence) — Madison Pruet (IBM) explains the RQM spool errors simply mean transactions were being spooled when 'cdr stop' interrupted them; the original poster explicitly confirms he now has no worry about it.

Advisory only.