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 » My WMB 6109 possibly calling V6.0 lib and running V6 profile

Post new topic  Reply to topic
 My WMB 6109 possibly calling V6.0 lib and running V6 profile « View previous topic :: View next topic » 
Author Message
raam
PostPosted: Tue Jul 19, 2011 3:42 am    Post subject: My WMB 6109 possibly calling V6.0 lib and running V6 profile Reply with quote

Apprentice

Joined: 14 May 2011
Posts: 29

Hi,

I had opened a PMR with IBM regarding a core dump event that was being generated a few days ago in the Prod environment. And so I sent over some information (and files) that were requested including some abend files.

I notified them that for some reason, the installation path shows as /opt/IBM/mqsi/6.0/* instead of 6.1. I also mentioned that the installed version is in fact WMB 6.1.0.9 (I only had upgraded WMB from the existing 6.1.0.2 to 6.1.0.9 recently). And I received the below response from IBM. It looks like broker is still running under the V6 profile according to them.

The abend file indicates the customer's WMB version is 6109, however the libraries are being called from V6.0.

Since the migration from WMB 6.0 to 6.1 was done by a different person that quit prior to my joining this project, I am unable to answer the below questions. I recently upgraded WMB to 6109 (from the WMB V6102 which was existing from prior to my joining here). Can I kindly get some guidance as to how to do the necessary checks and resolve this issue?

Below are IBM's questions that I need to still respond to (with my answers within brackets):

Was V6 installed on the same machine? (yes)
Did customer encounter any problems during migration? (don't know because the person that migrated WMB left the project prior to my joining.)
Is customer running in mixed env? (no)
Did they export V6.1 mqsiprofile before starting the migrated V6.1 broker? (don't know because the person that migrated WMB left the project prior to my joining.)
From the abend it appears the broker is still running under V6 profile.


FYI, in our work environment (Test and Prod), we have 1 QMgr and 1 Broker setup in each of the two AIX servers.
Both, the Config Manager CMGR00 and the Message Broker are using the
same MQ Queue Manager in each server.

AIX- V5.3
WMB- V6.1.0.9
WMQ- V6.0.2.5


Thanks a lot. Regards.
_________________
Thanks a lot.

You're only given a little spark of madness. You mustn't lose it…..
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jul 19, 2011 12:50 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20703
Location: LI,NY

Check the default setup of the user profile you are using.
You may have to make sure you are sourcing the mqsiprofile from the correct directory.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
raam
PostPosted: Tue Jul 19, 2011 11:20 pm    Post subject: Reply with quote

Apprentice

Joined: 14 May 2011
Posts: 29

Hi,

Below is the .profile that was already set up. And I am not running multiple versions of Broker in Production. WMB 6109 is the only installation, but it is installed under /opt/IBM/mqsi/6.0/*.

Please suggest how I must take this further. Thanks a lot.

mqbrk@gsb-p-app-01:/home/mqbrk >more .profile

PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/java5/bin:.

alias ll="ls -lrt"
export PATH

if [ -s "$MAIL" ] # This is at Shell startup. In normal
then echo "$MAILMSG" # operation, the Shell checks
fi # periodically.
HOST=$(hostname)
PS1='$USER@$HOST:$PWD >'
set -o vi
if [ -f /opt/IBM/db2/sqllib/db2profile ]; then
. /opt/IBM/db2/sqllib/db2profile
fi
ODBCINI=/var/mqsi/odbc/odbc64.ini
export ODBCINI
if [ -f /opt/IBM/mqsi/6.0/bin/mqsiprofile ]; then
. /opt/IBM/mqsi/6.0/bin/mqsiprofile
fi
MQSI_LIBPATH64=/opt/IBM/db2/sqllib/lib64:$MQSI_LIBPATH64
export MQSI_LIBPATH64
LIBPATH=/opt/IBM/db2/sqllib/lib32:$LIBPATH
export LIBPATH
MQSI_LIBPATH32=/opt/IBM/db2/sqllib/lib32:$MQSI_LIBPATH32
export MQSI_LIBPATH32

export MQSI_FILEPATH=/opt/IBM/mqsi/6.0

#export PATH=$PATH:$MQSI_FILEPATH/jre15/bin

export CLASSPATH=$CLASSPATH:$MQSI_FILEPATH/sample/ConfigManagerProxy/ConfigManagerProxySamples.jar

----

mqbrk@:/opt/IBM/mqsi/6.0/bin >mqsiservice -v
BIPv610 en US
ucnv Console CCSID 819 dft ucnv CCSID 819
ICUW ISO-8859-1 ICUA ISO-8859-1

BIP8996I: Version: 6109
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S610-FP09 DH610-FP09
BIP8999I: Build Type: Production

BIP8071I: Successful command completion.


Also if it is of any help, pasted below is the mqsiprofile file contents from /opt/IBM/mqsi/6.0/bin.


mqbrk@:/opt/IBM/mqsi/6.0/bin >more mqsiprofile
#!/usr/bin/ksh

# Licensed Materials - Property of IBM;
# 5724-A82
# (c) Copyright IBM Corp. 2005;
# All Rights Reserved;
# US Government Users Restricted Rights - use,
# duplication or disclosure restricted by GSA
# ADP Schedule Contract with IBM Corp.;

MQSI_FILEPATH=/opt/IBM/mqsi/6.0
export MQSI_FILEPATH

MQSI_WORKPATH=/var/mqsi
export MQSI_WORKPATH

MQSI_JREPATH=${MQSI_FILEPATH}/jre15
export MQSI_JREPATH

MQSI_VERSION=6.1.0.9
MQSI_VERSION_V=6
MQSI_VERSION_R=1
MQSI_VERSION_M=0
MQSI_VERSION_F=9
export MQSI_VERSION MQSI_VERSION_V MQSI_VERSION_R MQSI_VERSION_M MQSI_VERSION_F

MQSI_FAD=4
export MQSI_FAD

MQSI_REGISTRY=${MQSI_WORKPATH}
PATH=${MQSI_FILEPATH}/bin:${PATH}

MQSI_LILPATH64=${MQSI_FILEPATH}/lil:${MQSI_FILEPATH}/jplugin${MQSI_LILPATH64:+":"${MQSI_LILPATH64}}
MQSI_LILPATH32=${MQSI_FILEPATH}/lil32:${MQSI_FILEPATH}/jplugin${MQSI_LILPATH32:+":"${MQSI_LILPATH32}}
MQSI_SECURITY_PROVIDER_PATH64=${MQSI_FILEPATH}/SecurityProviders${MQSI_SECURITY_PROVIDER_PATH64:+":"${MQSI_SECURITY_PROVIDER_PATH64}}
MQSI_SECURITY_PROVIDER_PATH32=${MQSI_FILEPATH}/SecurityProviders32${MQSI_SECURITY_PROVIDER_PATH32:+":"${MQSI_SECURITY_PROVIDER_PATH32}}

MQSI_EXMLTCONFIGPATH=${MQSI_FILEPATH}/exmltConfig

LIBPATH=${MQSI_FILEPATH}/xml4c/lib64:/usr/mqm/lib64:${MQSI_FILEPATH}/ODBC64/V5.3/lib:${MQSI_FILEPATH}/xlxpc/lib64:${MQSI_FILEPATH}/lib:${MQSI_FILEPATH}/bin:$
{LIBPATH}
MQSI_LIBPATH32=${MQSI_FILEPATH}/xml4c/lib:/usr/mqm/lib:${MQSI_FILEPATH}/ODBC32/V5.3/lib:${MQSI_FILEPATH}/xlxpc/lib${MQSI_LIBPATH32:+":"${MQSI_LIBPATH32}}

NLSPATH=${MQSI_FILEPATH}/messages/%L/%N:${MQSI_FILEPATH}/messages/En_US/%N:${NLSPATH}
MQSI_JARPATH=${MQSI_FILEPATH}/classes:${MQSI_FILEPATH}/messages${MQSI_JARPATH:+":"${MQSI_JARPATH}}
MQSI_CATALINA_HOME=${MQSI_FILEPATH}/catalina

DISTHUB_PATH=${MQSI_FILEPATH}

MQSI_DEVELOPMENT=${MQSI_REGISTRY}/registry

CLASSPATH=${MQSI_FILEPATH}/classes/derby.jar:${MQSI_FILEPATH}/classes/ConfigManagerProxy.jar:${MQSI_FILEPATH}/classes/configutil.jar:/usr/mqm/java/lib/com.ib
m.mq.jar:/usr/mqm/java/lib/connector.jar:${MQSI_FILEPATH}/messages:${MQSI_WORKPATH}/common/wsrr:${CLASSPATH}
LIBPATH=/usr/mqm/java/lib64:${LIBPATH}
MQSI_LIBPATH32=/usr/mqm/java/lib:${MQSI_LIBPATH32}
export MQSI_REGISTRY PATH MQSI_LILPATH64 MQSI_LILPATH32 MQSI_EXMLTCONFIGPATH LIBPATH MQSI_LIBPATH32 NLSPATH MQSI_JARPATH MQSI_CATALINA_HOME DISTHUB_PATH MQSI
_DEVELOPMENT CLASSPATH MQSI_SECURITY_PROVIDER_PATH64 MQSI_SECURITY_PROVIDER_PATH32

# unset some V6.0 environment variables (must be done before calling user profiles)
MQSI_LIBPATH64=
MQSI_LILPATH=
export MQSI_LIBPATH64 MQSI_LILPATH

for SCRIPT in ${MQSI_WORKPATH}/common/profiles/*.sh; do
if [ -r "${SCRIPT}" ]; then
. ${SCRIPT}
fi
done

PATH=${MQSI_JREPATH}/ppc64/bin:${PATH}
LIBPATH=${MQSI_JREPATH}/ppc64/bin:${MQSI_JREPATH}/ppc64/bin/classic:${LIBPATH}
MQSI_LIBPATH32=${MQSI_JREPATH}/bin:${MQSI_JREPATH}/bin/classic:${MQSI_LIBPATH32}
export PATH LIBPATH MQSI_LIBPATH32

echo
echo MQSI $MQSI_VERSION
echo $MQSI_FILEPATH
echo
_________________
Thanks a lot.

You're only given a little spark of madness. You mustn't lose it…..
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Jul 20, 2011 10:51 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20703
Location: LI,NY

Which user is running the DataFlow processes and the bip processes? Is it mqbrk?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
raam
PostPosted: Sat Jul 23, 2011 12:57 am    Post subject: Reply with quote

Apprentice

Joined: 14 May 2011
Posts: 29

Hi,

Yes. It is 'mqbrk'.

And I received the below response from IBM in this regard:

We pursue environment issues by looking at the env output rather than
the .profiles or exports because we're primarily interested in only the
environment variables that are present in the environment in which the
broker is started. In the future, please send the env output, as it's
possible we may miss something when attempting to figure out what the
profile scripts have set.
From the .profile you sent, we clearly see you're trying to run what is
supposed to be a v6.1 broker in a v6 environment. This will certainly
not work. The v6.0 environment variables must be removed, however they
were entered, and the v6.1 environment variables must be used instead.
Please remove all references to v6.0 paths, libraries, files, etc from
your profile scripts or, alternatively, create a profile specifically
for 6.1 and attempt to run the broker from the environment resulting
from running the 6.1 profile.
Please use the following instructions to configure the environment for
v6.1:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.et
ools.mft.doc/an26230_.htm
Please also ensure that you have configured the environment to connect
to the broker database by following the links in the document above.


However, I need to know what I must do appropriate so that the existing path could be changed to /opt/IBM/mqsi/6.1 from the existing /opt/IBM/mqsi/6.0.

And also, would commenting out the V6.0 variables within the mqsiprofile and the .profile of user 'mqbrk' help resolve any part of this issue?

Thank you.
_________________
Thanks a lot.

You're only given a little spark of madness. You mustn't lose it…..
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Jul 23, 2011 3:14 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20703
Location: LI,NY

Do a fresh install of 6.1 on some box.
Look at the mqsiprofile on that box and compare to the mqsiprofile you are running...

Check on your box if you have
Quote:
if [ -f /opt/IBM/mqsi/6.1/bin/mqsiprofile ]; then
. /opt/IBM/mqsi/6.1/bin/mqsiprofile
fi


If the file exists on your system, change the service user profile to source the 6.1 file as shown above...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » My WMB 6109 possibly calling V6.0 lib and running V6 profile
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.