ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Migration

Post new topic  Reply to topic
 Migration « View previous topic :: View next topic » 
Author Message
abiram8
PostPosted: Wed May 01, 2002 12:07 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi,

We are doing the migration from WINDOWS -NT to AIX for our publish- Subscribe programme

As a result now my QueueManager (QM_A) resides in the AIX succesfully created & the Broker in the AIX is QM_A_Broker.

The Communication between the Broker of Windows Broker & Aix Broker is also done succesfully created no issue on that

As a result the broker (QM_A_Broker) is visible in the Assignment pane but If Iam doing the Complete Deployment on this broker (QM_A_Broker) it gives me error

BIP1510E: Unable to deploy configuration data.

An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker QM_EBBS_BROKER. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed.

Wait for the outstanding deploy to complete before retrying the operation. The Log view may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all MQSeries queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then retry the deploy operation specifying the 'Forced' option which overrides any outstanding deploy. Note that 'Forced' causes all configuration throughout the entire domain to be re-deployed so you may not have authority to perform this. The 'Forced' option may only be selected when deploying 'Complete configuration (all types)' from the File menu.


Even I tried the Forced Deployment of the whole Configration Manager , when I view the Log view Pane I get the message succesfully deploying of all WinDows NT Brokers(QM_W_Broker) not the AIX Broker (QM_A_Broker) & my QM_A_Broker is not visible in Operation pane

How to Succesfully Deplloy my AIX broker in the Windows NT Control Center so that I can view in the Operation Pane

Note : My Broker & QueueManager is in the AIX machine & as per instruction Control Center in The Windows NT

Thanks
R.Abiram
Back to top
View user's profile Send private message Send e-mail
abiram8
PostPosted: Thu May 02, 2002 4:37 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi,
Can any one help me as to rectify the above problem its very Urergent
Back to top
View user's profile Send private message Send e-mail
vmcgloin
PostPosted: Thu May 02, 2002 5:08 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Is is possible that the communication between the ConfigMgr and the AIX broker
is not set up correctly? Or is the configmgr using the same queue manager as the NT broker?

Forced deploy is the safest thing to do to overcome your first error. Have you determined why the deploy to QM_EBBS_BROKER was outstanding too?

Regards,
Vicky

[ This Message was edited by: vmcgloin on 2002-05-02 06:10 ]
Back to top
View user's profile Send private message
abiram8
PostPosted: Thu May 02, 2002 5:35 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi,
You are right as the Windows NT Event VIewver gave me following information

( QM_NT.default ) Interbroker connection ended with neighbor (Queue Manager QM_AIX).

An active connection has been ended with the neighboring broker (Queue Manager QM_Ebbs). Publications will not flow between the brokers until the connection is reestablished.

This message is for information only, to confirm that the connection has been ended.


I dont understand but both the channel NT & AIX channel are up (running)

Iam able to ping to Aix server from NT server & vise versa

then why it is giving such error

And as you asked Iam using diffrent Qmmanager for AIX & diffrnt Queuemanager for Windows NT server

Hi the Config Queuemanager is in NT it is using QM_NT the broker is in the AIX using QM_AIX queuemanager



_________________


[ This Message was edited by: abiram8 on 2002-05-02 06:40 ]

[ This Message was edited by: abiram8 on 2002-05-02 06:42 ]
Back to top
View user's profile Send private message Send e-mail
vmcgloin
PostPosted: Thu May 02, 2002 5:53 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Sorry, I cannot help. Maybe someone else can?

I think you are doing the right thing. You just need to keep checking that the right channels are running & try to deploy again.

Vicky
Back to top
View user's profile Send private message
abiram8
PostPosted: Thu May 02, 2002 9:34 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi when I saw the Syslog.user logs file I could list out the folowing error can you give me solution how to solve below error




BIP7064S Failed to create Java VM &1.
Explanation: The broker creates a Java Virtual
Machine to support internal operations, but in this case
has been unable to do so. There may have been a
problem with the way the product was installed, or
something has subsequently affected the installation.
User Response: This is an internal error and you
should contact your IBM support center.



BIP2204I Execution group using process ’&1’
thread ’&2’ stopped.
Explanation: The execution group using process ’&1’
and thread ’&2’ has stopped. This may be because it
has been instructed to do so or because it has
encountered a problem.
User Response: No user action required. The
execution group will be restarted automatically if need
be.


BIP2203E An execution group has encountered a
problem whilst starting.
Explanation: An execution group has encountered a
problem whilst starting and is unable to continue.
User Response: Check the following error messages to
try to identify the cause of the problem. If it is unclear
what the cause is, and the problem occurs continually
after restarting the message broker contact your IBM
support center.


BIP2060E Not Found Execution Group Failed

Looking for quick reply

Abiram
Back to top
View user's profile Send private message Send e-mail
kirani
PostPosted: Thu May 02, 2002 12:31 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Abiram,

In previous postings I came across following broker names,
1. QM_A_Broker (on AIX)
2. QM_W_Broker (on NT)
3. QM_EBBS_BROKER (which os?)

Looks like you have a reference to 3 brokers in your configuration manager. When you created broker QM_A_Broker, have you followed proper instructions to create a broker reference in config mgr? Do you see all 3 brokers in the Topology view? Do you have a collective defined? If so, do you have a pair of channels defined between all brokers in collective?

What is the name of the queue manager for your configuration managers?



_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
abiram8
PostPosted: Fri May 03, 2002 12:42 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi the name of the Broker in NT is QM_W_Broker (on NT) & QM_A_Broker (on AIX)

Forget about the other broker by mistake I wrote that which is in AS400(QM_EBBS_BROKER )(AS400 Broker)

now QM_A_Broker is a AIX Broker. QM_W_Broker (on NT Config Mgr)
I can see both broker in Topology & Assignment Pane Channel are up & runnig fine no issue

Can you suggest me some thing diffrent


Back to top
View user's profile Send private message Send e-mail
kirani
PostPosted: Fri May 03, 2002 7:50 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Can you verify whether your broker was created properly on AIX machine or not?
How much RAM do you have on your AIX box? Do you see any errors in syslog for broker queue manager or broker itself?
Check the log file for queue manager and see if any FDC files are created.
Back to top
View user's profile Send private message Visit poster's website
abiram8
PostPosted: Sat May 04, 2002 4:03 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi,

I have increased the AIX server Hard Disk capacity & the RAM capacity is 4 GB

Now there is some improvment ie in Operation pane I got only the AIX Broker without Execution Group I got the several Error as listed below


BIP2201I Execution Group started: process ’&14’;
thread ’&15’; additional information
’&1’, ’&2’, ’&3’, ’&4’, ’&5’, ’&6’, ’&7’,
’&8’, ’&9’, ’&10’, ’&11’, ’&12’, ’&13’.
Explanation: The execution Group has started using
process ’&14’ and thread ’&15’ and will now start
processing messages.


object ’&4’. Valid values are ’&3’. This can be caused by
a mismatch in levels between the Control Center, the
Configuration Manager and the Broker, or as a result of
a user or third party written plug-in node where the
implementation library installed at the broker does not
match the node definition held at the Configuration
manager and Control Center.
User Response: Ensure that the levels of code
installed at the Control Center, Configuration Manager
and Broker are all consistent. If they are, identify the
supplier of the target object and report the problem to
them. If this is IBM, contact your IBM support center.




BIP7064S Failed to create Java VM &1.
Explanation: The broker creates a Java Virtual
Machine to support internal operations, but in this case
has been unable to do so. There may have been a
problem with the way the product was installed, or
something has subsequently affected the installation.
User Response: This is an internal error and you
should contact your IBM support center.




BIP2204I Execution group using process ’&1’
thread ’&2’ stopped.
Explanation: The execution group using process ’&1’
and thread ’&2’ has stopped. This may be because it
has been instructed to do so or because it has
encountered a problem.
User Response: No user action required. The
execution group will be restarted automatically if need
be.


& Also I have made changes to this Enviroment Variables

LC_CTYPE=en_US
export LC_CTYPE
LC_NUMERIC=en_US
export LC_NUMERIC
LC_TIME=en_US
export LC_TIME
LC_COLLATE=en_US
export LC_COLLATE
LC_MONETARY=en_US
export LC_MONETARY
LC_MESSAGES=C
export LC_MESSAGES
LANG=
export LANG

I dont know why the Execution Group of AIX broker dont come into the Operation Pane can you help me out



Back to top
View user's profile Send private message Send e-mail
abiram8
PostPosted: Mon May 06, 2002 12:11 am    Post subject: Reply with quote

Master

Joined: 27 Mar 2002
Posts: 207
Location: India

Hi,

The same problem Iam facing pl if some one can help me out
Back to top
View user's profile Send private message Send e-mail
CodeCraft
PostPosted: Mon May 06, 2002 1:26 am    Post subject: Reply with quote

Disciple

Joined: 05 Sep 2001
Posts: 195

This sounds like there may be a fundamental problem with the AIX installation or pre-requisites. Proper diagnosis may be time consuming, and, since this has been going for five days, formal IBM support should be sought. It will probably require detailed examination of the installation and the steps used to create it, and may require service tracing on the AIX platform.

There are a variety of reasons why the broker and execution group will not be seen in operations. An obvious one, is that they are not functioning correctly, another one is that the pub-sub functionality between AIX and NT is not functioning for some reason, eg: If memory serves me right, the ID under which the ConfigMgr is running and deploys performed, should a member of the "mqbrkrs" group on the AIX system for the p/s to work between the broker and configuration manager.

I would not begin worrying about the operations tab problem until you have successfully managed to start the broker and execution group on AIX, ie: Resolve the JVM problem.

The code level is not mentioned here. If this is 2.1, ensure it's at CSD 02 level on NT and AIX. My inclination here, if you have full control over the AIX system, would be to uninstall the product and reinstall having first checked all pre-requisites, etc. Using SMITTY, uninstall and re-install can be performed quite quickly. However, as a second user now complains of the problem, proper input from IBM technical support should be sought.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Migration
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.