| Author |
Message
|
| gkp |
 Posted: Tue Dec 04, 2001 1:01 pm Post subject: |
 |
|
Newbie
Joined: 03 Dec 2001
Posts: 5
|
I've been facing problems with deployment of MQSIV202 assignments and topology repeatedly. This problem has been talked about in the forum a couple of times... but I've not been able to sort out the problems I'm facing with any of the solutions suggested.
We'd initially done the MQSI installation on Solaris without NEON support and the deployments were successful.
But ever since we installed the NEON support, I've been getting the following errors on the control center
1. BIP2087I - Unable to process internal configuration message
2. BIP2066E - Exec grp did not respond in a timely manner
3. BIP1536E - Conf manager unable to register for internal subscriptions with broker.
The system log on the Solaris machine repeatedly shows these errors
1. BIP2081E - unable to load implementation files...imbdfdb2v5.lil and imbdfdb2v6.lil(We're using Sybase as the DB)
2. BIP2060E - execution group terminated
3. BIP2080E - Exec grp failed to return an internal confuguration Start message response within a 60 sec time period.
Am I facing this problem because the NEON pack was installed after the MQSI is installation?
|
|
| Back to top |
|
 |
| Nick Lethbridge |
| Posted: Wed Dec 05, 2001 1:57 pm Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
We had a similar problem when deploying to a MQSI v2.0.2 broker on Sun Solaris (with NEON support installed).
We had created the broker with UNIX userid = mqsi, but created the ConfigMgr with a NT userid <> mqsi.
When we re-created the ConfigMgr with userid = mqsi (a member of the usual 'mqsi' groups), we were able to deploy without a problem.
n.b. The BIP2081E messages about the DB2 lil files is a 'feature' that presumably will be resolved in a CSD - we get the same messages when using an Oracle 8.1.7 database.
|
|
| Back to top |
|
|
| kirani |
| Posted: Wed Dec 05, 2001 6:17 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
gkp,
Did you update .odbc.ini file after Installing and setting up NEON DB? In this file you have to specify user-id, password and database name for NEON database.
Please refer to Appendix B of Administration guide for more details.
Hope this helps. |
|
| Back to top |
|
|
| gkp |
| Posted: Thu Dec 06, 2001 11:05 am Post subject: |
|
|
Newbie
Joined: 03 Dec 2001
Posts: 5
|
Nick,
We are using the same user-id and password for the configuration manager and the broker domain.
The passwords were initially different but we tried using the same password but to no avail.
Kirani,
We first tried deploying message flows with Neon nodes in them. They didn't work. For the past couple of days we've been deploying brokers with just the default execution group and no message flows. We're still facing the same problem.
As suggested by you, we looked into Appendix B to check if we have to make modifications to .odbc.ini for Neon database. The contents of the appendix talk only about the addition of the database details in neonreg.dat as far as Neon db is concerned.
If you have any more information on .odbc.ini or a sample of .odbc.ini that includes NEON, please forward the same.
I thank both of you for your prompt replies. |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Dec 06, 2001 2:37 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
gkp,
I am very sure your broker is failing at startup and its not allowing you to deploy even empty execution group. This indicates that there is some problem with NEON setup.
If NEONRules and NEONFormatter Support is installed, you need to ensure that the file neonreg.dat, which is identified in the NN_CONFIG_FILE_PATH environment variable, contains the correct information to locate the NEONFormatter and NEONRules database. A sample neonreg.dat file is supplied in the directory:
examples
Also, there could be a problem with environment variables.
Page 68 in "Sun Solaris Installation Guide" tals about environment variables related to MQSI and NEON. Please check your environment variables for NEON.
Page 12 in "MQSI Administration Guide" talks about Database setup and configuration. There is also an explanation for .odbc.ini file.
Good luck!
Regards,
Kiran
|
|
| Back to top |
|
|
| gkp |
| Posted: Mon Dec 10, 2001 4:08 pm Post subject: |
|
|
Newbie
Joined: 03 Dec 2001
Posts: 5
|
To cross-verify that the Neon installation is creating all the problems, we removed all the .lil files related to NEON and deployed the broker with the execution groups.
Without the Neon files, the deploy operation is successful and the message flows in the execution groups are working fine.
The source of the problem is NEON installation on the Sun Sparc machine.
Can someone throw some light on this combination
MQSIV202 + Neon + Sybase12 + SunSolaris. Has anyone used this combination?
We've done some testing with a MQSIV202 + Neon + DB2 + WinNT combination which works just fine.
|
|
| Back to top |
|
|
| Nick Lethbridge |
| Posted: Tue Dec 11, 2001 1:03 pm Post subject: |
|
|
Voyager
Joined: 13 Aug 2001
Posts: 88
Location: Santander, UK
|
Another possible cause is the locale settings.
When we encountered a similar problem with MQSI V2.0.2 on Sun Solaris (unable to deploy broker and message flows), IBM advised that the locale settings should be changed from:
LANG=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=
to the following:
LANG=
LC_CTYPE=en_US
LC_NUMERIC=en_US
LC_TIME=en_US
LC_COLLATE=en_US
LC_MONETARY=en_US
LC_MESSAGES="C"
LC_ALL=
Regards,
Nick. |
|
| Back to top |
|
|
| gkp |
| Posted: Tue Dec 11, 2001 3:18 pm Post subject: |
|
|
Newbie
Joined: 03 Dec 2001
Posts: 5
|
Nick,
Changing the locale settings has been mentioned in one of the topics related to broker deployment and that was one of the first things that we did.
We've got our env settings etc. cross-checked and they seem to be OK.
After a lot of testing, we believe the source of the problem to be the MQSIV202 + Neon + Sybase12 + SunSolaris combo. If someone could help us with it.
Nick, thanks for devoting your time to this topic.
|
|
| Back to top |
|
|
|
|
