| Author |
Message
|
| punky |
 Posted: Wed Jun 27, 2012 9:39 pm Post subject: Steps to restart the broker during maintenance activity. |
 |
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi all,
Require your help to understand the sequence of steps to be followed to restart the broker during maintenance activity on production server.
Please correct me if I am wrong:
1. Stop the message flows.
2. Stop the database server.
3. Stop the Broker.
4. Start the Broker.
5. Start the database server
6. Start the message flow.
Regards,
Punky |
|
| Back to top |
|
 |
| marko.pitkanen |
| Posted: Wed Jun 27, 2012 10:29 pm Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi punky,
What is your broker version?
Why do you want to let broker be running without database server?
What about WMQ on which broker is running?
--
Marko |
|
| Back to top |
|
|
| punky |
| Posted: Wed Jun 27, 2012 11:37 pm Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
| Quote: |
What is your broker version?
|
The broker version is 7.0
I just wanted to know because the steps followed by the team is:
Stop message flow.
Start message flow.
Stop database server.
Stop Broker.
Start database server.
Start Broker.
but there were few outbound IDOCS which showed the status as 41 and still did not reach the destination.
I am investigating the issue.
There was no record in the database table as the database was down.
Regards,
Punky |
|
| Back to top |
|
|
| aravind703 |
| Posted: Thu Jun 28, 2012 6:03 am Post subject: @ punlu |
|
|
Apprentice
Joined: 24 Sep 2011
Posts: 29
|
I am assuming
mqsireload Broker_name -e Execution_Group_Name should do the broker restart for you.
If you are having different applications running on different Execution Groups, why to stop the broker for one application. Unless there
is a real need to stop broker, it is not recomended to stop broker .
To check if a broker is connected to database use mqsicvp Broker_name -n Data_Source_Name
Last edited by aravind703 on Thu Jun 28, 2012 11:57 am; edited 2 times in total |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jun 28, 2012 9:46 am Post subject: Re: @ punlu |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| aravind703 wrote: |
I am assuming
mqsireload Broker_name -e Execution_Group_Name should do the broker restart for you.
If you are having different applications running on different Execution Groups, why to stop the broker for one application. Unless there
is a real need to stop broker, it is not recomended to stop broker .
To check if a broker is connected to database use mqsicvp Broker_name -n Data_Source_Name |
Really?
| Quote: |
Use the mqsireload command to request the broker to stop and restart execution groups.
|
Granted that not specifying the Execution Group will stop and restart the broker BUT that is not what the OP was asking about.
As for the 'mqsicvp' command,
| Quote: |
The mqsicvp command:
Checks that the broker environment is set up correctly; for example, that the installed level of Java is supported.
|
It does not check to see if the broker IS CURRENTLY connected to a DB but can be used to validate that the broker CAN be connected to a DB. There is a subtle difference.
Please don't shout like that. It is impolite.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| aravind703 |
| Posted: Thu Jun 28, 2012 11:50 am Post subject: @ smdavies99 |
|
|
Apprentice
Joined: 24 Sep 2011
Posts: 29
|
| smdavies99 wrote: |
| aravind703 wrote: |
I am assuming
mqsireload Broker_name -e Execution_Group_Name should do the broker restart for you.
If you are having different applications running on different Execution Groups, why to stop the broker for one application. Unless there
is a real need to stop broker, it is not recomended to stop broker .
To check if a broker is connected to database use mqsicvp Broker_name -n Data_Source_Name |
Really?
| Quote: |
Use the mqsireload command to request the broker to stop and restart execution groups.
|
Granted that not specifying the Execution Group will stop and restart the broker BUT that is not what the OP was asking about.
|
I clearly told its my assumption abt mqsireload.
| Quote: |
As for the 'mqsicvp' command,
| Quote: |
The mqsicvp command:
Checks that the broker environment is set up correctly; for example, that the installed level of Java is supported.
|
It does not check to see if the broker IS CURRENTLY connected to a DB but can be used to validate that the broker CAN be connected to a DB. There is a subtle difference.
Please don't shout like that. It is impolite.
|
/opt/IBM/mqsi/7.0> mqsicvp MB7BROKER -n AROMA_DB
BIP8272E: Datasource 'AROMA_DB' has not been associated with broker 'MB7BROKER'.
This invocation of the mqsicvp command requires that the datasource name has been associated with the broker, using the mqsisetdbparms command.
Check that this datasource has been associated with the broker.
/opt/IBM/mqsi/7.0> mqsicvp MB7BROKER -n SAMPLE_DB
BIP8270I: Connected to Datasource 'SAMPLE_DB' as user 'msgbrkr'. The datasource platform is 'SQL Server', version '15.00.0000'.
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jun 28, 2012 1:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
But this is not what the OP asked...
The OP asked about a sequence for a MAINTENANCE interval...
Ok so here it is:
- If in cluster suspend broker qmgr
- stop broker
- stop all qmgrs (not needed if maintenance only to broker)
- stop DB (not needed if DB on a different server or maintenance only to broker or qmgr
- apply maintenance
- check if reboot necessary
- if reboot necessary shut down any other app on the box (like DB, MQ)
- if reboot => reboot box
- if reboot check everything is up and running
- if reboot and in cluster resume broker qmgr
- and following case no reboot
- check DB up and running else start DB
- check qmgrs up and running else start them
- start broker
- sleep 1 min
- resume broker qmgr if in cluster
If your flows are in "maintained" mode, stopping them will only force you to start them once the broker is up... Extra work if you can arrange it in such a way that the broker stops processing work...(MQ cluster)
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Jun 28, 2012 6:45 pm Post subject: Re: @ smdavies99 |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| aravind703 wrote: |
/opt/IBM/mqsi/7.0> mqsicvp MB7BROKER -n AROMA_DB
BIP8272E: Datasource 'AROMA_DB' has not been associated with broker 'MB7BROKER'.
This invocation of the mqsicvp command requires that the datasource name has been associated with the broker, using the mqsisetdbparms command.
Check that this datasource has been associated with the broker.
/opt/IBM/mqsi/7.0> mqsicvp MB7BROKER -n SAMPLE_DB
BIP8270I: Connected to Datasource 'SAMPLE_DB' as user 'msgbrkr'. The datasource platform is 'SQL Server', version '15.00.0000'.
|
This is clearly not the purpose of the mqsicvp command. As smdavies99 clearly pointed out, it is to check if the environment is setup correctly.
| Quote: |
Purpose
The mqsicvp command:
Checks that the component environment is set up correctly; for example, that the installed level of Java is supported.
Verifies that the WebSphere® MQ queues are defined and accessible.
If the component is a broker, checks that the expected database tables are present.
The mqsicvp command completes all these checks, and fails if one or more checks fail. It reports all errors in the system log, or to the command line, or both.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fan07235_.htm
|
|
|
| Back to top |
|
|
| punky |
| Posted: Thu Jun 28, 2012 8:29 pm Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Thanks Fjb_saper,
I got what I really wanted. 
Thanks all for all your suggestions.
I learn a lot through this forum.
Regards,
Punky |
|
| Back to top |
|
|
|
|
