| Author |
Message
|
| saddankula |
 Posted: Fri Sep 20, 2013 3:07 am Post subject: backup queue manager for an existing queue manager |
 |
|
Acolyte
Joined: 27 Jun 2013
Posts: 51
|
Hello ,
I am trying to create a backup queue manager for an existing queue manager,when using linear logging in MQ 7.5V. For this
i take copies of all the existing queue manager’s data and log file directories, and i overwrite the backup queue manager's data and log file directories, including all subdirectories, with the copies taken from the existing queue manager.
after i run this following commands for starting backup queue manger. but the backup queue manger is will not be start. can any one reslove this error.
C:\Program Files (x86)\IBM\MQSI\8.0.0.1>strmqm -r BACKUP_EXIST
WebSphere MQ queue manager 'BACKUP_EXIST' is being started for replay.
The queue manager is associated with installation 'Installation1'.
The oldest log file required to start queue manager BACKUP_EXIST is S0000000.LOG
.
The oldest log file required to perform media recovery of queue manager BACKUP_E
XIST is S0000000.LOG.
WebSphere MQ queue manager 'BACKUP_EXIST' replay completed.
C:\Program Files (x86)\IBM\MQSI\8.0.0.1>strmqm -a BACKUP_EXIST
WebSphere MQ queue manager 'BACKUP_EXIST' is being activated.
The queue manager is associated with installation 'Installation1'.
WebSphere MQ queue manager 'BACKUP_EXIST' activated.
C:\Program Files (x86)\IBM\MQSI\8.0.0.1>strmqm BACKUP_EXIST
WebSphere MQ queue manager 'BACKUP_EXIST' starting.
The queue manager is associated with installation 'Installation1'.
11 log records accessed on queue manager 'BACKUP_EXIST' during the log replay ph
ase.
Log replay for queue manager 'BACKUP_EXIST' complete.
Transaction manager state recovered for queue manager 'BACKUP_EXIST'.
An error occurred while restoring the cluster cache, see the error logs for deta
ils
WebSphere MQ queue manager 'BACKUP_EXIST' started using V7.5.0.0. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Sep 20, 2013 4:37 am Post subject: Re: backup queue manager for an existing queue manager |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| saddankula wrote: |
Hello ,
I am trying to create a backup queue manager for an existing queue manager,when using linear logging in MQ 7.5V. For this
i take copies of all the existing queue manager’s data and log file directories, and i overwrite the backup queue manager's data and log file directories, including all subdirectories, with the copies taken from the existing queue manager.
after i run this following commands for starting backup queue manger. but the backup queue manger is will not be start. can any one reslove this error.
C:\Program Files (x86)\IBM\MQSI\8.0.0.1>strmqm -r BACKUP_EXIST
WebSphere MQ queue manager 'BACKUP_EXIST' is being started for replay.
The queue manager is associated with installation 'Installation1'.
The oldest log file required to start queue manager BACKUP_EXIST is S0000000.LOG
.
The oldest log file required to perform media recovery of queue manager BACKUP_E
XIST is S0000000.LOG.
WebSphere MQ queue manager 'BACKUP_EXIST' replay completed.
C:\Program Files (x86)\IBM\MQSI\8.0.0.1>strmqm -a BACKUP_EXIST
WebSphere MQ queue manager 'BACKUP_EXIST' is being activated.
The queue manager is associated with installation 'Installation1'.
WebSphere MQ queue manager 'BACKUP_EXIST' activated.
C:\Program Files (x86)\IBM\MQSI\8.0.0.1>strmqm BACKUP_EXIST
WebSphere MQ queue manager 'BACKUP_EXIST' starting.
The queue manager is associated with installation 'Installation1'.
11 log records accessed on queue manager 'BACKUP_EXIST' during the log replay ph
ase.
Log replay for queue manager 'BACKUP_EXIST' complete.
Transaction manager state recovered for queue manager 'BACKUP_EXIST'.
An error occurred while restoring the cluster cache, see the error logs for details WebSphere MQ queue manager 'BACKUP_EXIST' started using V7.5.0.0. |
Did you do what the errors suggested?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| saddankula |
| Posted: Fri Sep 20, 2013 5:00 am Post subject: |
|
|
Acolyte
Joined: 27 Jun 2013
Posts: 51
|
error log details:
9/20/2013 16:11:30 - Process(10024.21) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(MIRACLE-PC) Installation(Installation1)
VRMF(7.5.0.0)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
BACKUP_EXIST.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 10024.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 906 --------------------------------------------------------
9/20/2013 16:11:30 - Process(10024.22) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(MIRACLE-PC) Installation(Installation1)
VRMF(7.5.0.0)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
BACKUP_EXIST.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 10024.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 906 --------------------------------------------------------
9/20/2013 16:11:30 - Process(10024.23) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
Host(MIRACLE-PC) Installation(Installation1)
VRMF(7.5.0.0)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
BACKUP_EXIST.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 10024.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the MQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
----- amqxfdcp.c : 906 -------------------------------------------------------- |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 20, 2013 5:20 am Post subject: Re: backup queue manager for an existing queue manager |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| saddankula wrote: |
| i take copies of all the existing queue manager’s data and log file directories |
Did you stop it first?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| saddankula |
| Posted: Fri Sep 20, 2013 5:46 am Post subject: |
|
|
Acolyte
Joined: 27 Jun 2013
Posts: 51
|
| ya, i stopped . after stopping i take copies of all the existing queue manager’s data and log file directories |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 20, 2013 6:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What do the FDC files indicate as the problem?
(The output from the "error reporting process" indicated in the logs)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| saddankula |
| Posted: Fri Sep 20, 2013 6:40 am Post subject: |
|
|
Acolyte
Joined: 27 Jun 2013
Posts: 51
|
logs in .fdc file
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri September 20 2013 16:10:24 India Standard Time |
| UTC Time :- 1379673624.957000 |
| UTC Time Offset :- 330 ((UNKNOWN)) |
| Host Name :- MIRACLE-PC |
| Operating System :- Windows 7 Professional x64 Edition, Build 7600 |
| PIDS :- 5724H7220 |
| LVLS :- 7.5.0.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- C:\Program Files (x86)\IBM\WebSphere MQ |
| Installation Name :- Installation1 (1) |
| Probe Id :- ZX049014 |
| Application Name :- MQM |
| Component :- zxcCreateRepositoryCache |
| SCCS Info :- F:\build\p000_P\src\cmd\zmain\amqzxmb0.c, |
| Line Number :- 3506 |
| Build Date :- Jun 4 2012 |
| Build Level :- p000-L120604 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files (x86)\IBM\WebSphere MQ\bin\amqzxm |
| a0.exe |
| Addressing mode :- 32-bit |
| Process :- 00008188 |
| Thread :- 00000001 |
| QueueManager :- BACKUP_EXIST |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Last HQC :- 2.5.5-2458400 |
| Last HSHMEMB :- 2.13.13-279960 |
| Major Errorcode :- MQRC_UNKNOWN_REMOTE_Q_MGR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
EDIT by exerk: Stack trace removed. Please don't post stuff that's pretty much only of use to IBM Support, thank you. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Sep 23, 2013 10:31 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
You should look up the "ProbeID" on the www.ibm.com/mqseries software page to try to figure out what issues are associated with the ProbeID. The search is at the top on the right.
In this case, it came up blank. You will need to open a PMR (unless somebody has see this before). |
|
| Back to top |
|
|
| rcp_mq |
| Posted: Tue Sep 24, 2013 7:09 am Post subject: |
|
|
Centurion
Joined: 13 Dec 2011
Posts: 133
|
QueueManager :- BACKUP_EXIST |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Last HQC :- 2.5.5-2458400 |
| Last HSHMEMB :- 2.13.13-279960 |
| Major Errorcode :- MQRC_UNKNOWN_REMOTE_Q_MGR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
Investigate that. |
|
| Back to top |
|
|
|
|
