|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQWF Config Problems |
« View previous topic :: View next topic » |
Author |
Message
|
lzn9b8bpm |
Posted: Tue Mar 01, 2005 8:28 pm Post subject: MQWF Config Problems |
|
|
 Newbie
Joined: 23 May 2003 Posts: 6 Location: Dallas, Texas
|
Problem, can not get product configured. Here is what the fmczchk util spit out after the configuration ran.
FMC34010I: Configuration checker version 3.5.0.117 started.
FMC34120I: Command-line options specified: -i -d
FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.5.0 checks.
FMC34101I: The Operating System is AIX 5.2.
FMC34103I: Local time is 2005-03-01 16:04:56.
FMC34104I: Universal time coordinated (UTC) is 2005-03-01 22:04:56.
FMC34-DBG: TZ is set to CST6CDT
FMC34157I: Patch xlC.rte-6.0.0.0 is installed, minimum required version is 5.0.0.0.
FMC34314I: The local IP address is 170.49.26.13.
FMC34131I: The WebSphere MQ Workflow installation directory is /usr/lpp/fmc/bin.
FMC34154I: WebSphere MQ Workflow Version 3.5.0.3 is installed.
FMC34143I: The default configuration is 'FMC' (from the general configuration profile).
FMC34121I: The current configuration is 'FMC'.
FMC34145I: The following configurations are available: FMC.
FMC34135I: The installation profile is /usr/lpp/fmc/fmcrc.
FMC34135I: The general configuration profile is /var/fmc/fmcrc.
FMC34135I: The configuration profile is /var/fmc/cfgs/FMC/fmcrc.
FMC34136I: The user profile for root is /.fmcrc.
FMC34-DBG: Installation profile values:
FMC34-DBG: InstallationDirectory: '/usr/lpp/fmc'
FMC34-DBG: ConfigurationRootDirectory: '/var/fmc'
FMC34-DBG: InstalledComponents: 'SMIHPGJCUAD'
FMC34-DBG: MQWorkflowAdministrator: 'wasadm'
FMC34-DBG: MQWorkflowGroup: 'fmcgrp'
FMC34-DBG: VRM: '030500'
FMC34-DBG: ServiceLevel: '3'
FMC34-DBG: Language: 'enu'
FMC34-DBG: RTDatabaseType: 'DB2'
FMC34-DBG: MQConnectionType: 'MQServer'
FMC34-DBG: General configuration profile values:
FMC34-DBG: DefaultConfigurationID: 'FMC'
FMC34-DBG: Current configuration profile values:
FMC34-DBG: ConfigurationAdministrator: 'wasadm'
FMC34-DBG: ConfigurationGroup: 'fmcgrp'
FMC34-DBG: ConfiguredComponents: 'SIU'
FMC34-DBG: SystemGroup: 'FMCGRP'
FMC34-DBG: System: 'FMCSYS'
FMC34-DBG: MQPrefix: 'FMC'
FMC34-DBG: MQQueueManager: 'QICSD01'
FMC34-DBG: RTDatabase: 'FMCDB'
FMC34-DBG: RTDatabaseAlias: 'FMCDB'
FMC34-DBG: RTDatabaseInstanceIsRemote: '1'
FMC34-DBG: RTDB2Instance: 'db2wbsp2'
FMC34-DBG: RTDB2LocalInstance: 'db2clnt'
FMC34-DBG: RTDatabaseAdministratorUserID: 'wasadm'
FMC34-DBG: RTDatabaseUserID: 'wasadm'
FMC34-DBG: RTDatabaseMQWorkflowUser: 'ADMIN'
FMC34-DBG: CreateRuntimeDatabase: '0'
FMC34-DBG: LoadFDL: '1'
FMC34-DBG: MQPrincipal: 'wasadm'
FMC34-DBG: MQCommunicationProtocol: 't'
FMC34-DBG: MQCommunicationAddress: 'ftwaxwbid001'
FMC34-DBG: MQPort: '5010'
FMC34-DBG: FMLServerChannelTable: '/var/fmc/chltabs/MQWFCHL.TAB'
FMC34-DBG: MQBackupQueues: 'c'
FMC34-DBG: MQTransactionCoordinator: 'wasadm'
FMC34-DBG: MQTransactionCoordinatorStartsQM: '0'
FMC34-DBG: MQClusterName: 'FMCGRP'
FMC34-DBG: MQClusterMode: 'f'
FMC34-DBG: RTExecutionServerOperationMode: 'Standalone'
FMC34-DBG: RTErrorLogFile: '/var/fmc/cfgs/FMC/log/fmcerr.log'
FMC34-DBG: RTSystemLogFile: '/var/fmc/cfgs/FMC/log/fmcsys.log'
FMC34-DBG: FMLClientChannelTable: '/var/fmc/chltabs/MQWFCHL.TAB'
FMC34-DBG: FMLConnectName: 'FMC.FMCGRP.FMCSYS,QICSD01'
FMC34-DBG: FMLSegmentation: '0'
FMC34-DBG: RTDatabasePassword: '********'
FMC34-DBG: User profile values:
FMC34-DBG: (none)
FMC34113I: Language specification is 'enu' (from the installation profile).
FMC34115I: The message catalog is /usr/lpp/fmc/msg/fmckmenu.cat.
FMC34-DBG: LC_MESSAGES='', NLSPATH='/usr/lpp/fmc/msg/%N'
FMC34132I: The XPG4 locale is en_US en_US en_US en_US en_US en_US.
FMC34134I: The locale file used is /usr/lib/nls/loc/en_US.
FMC34-DBG: LC_ALL='', LANG='en_US', LOCPATH='/usr/lib/nls/loc'
FMC34146I: The current code page is ISO8859-1.
FMC34013I: ===> Admin Server found, checks started.
FMC34-DBG: Found /usr/lpp/fmc/bin/fmcamain
FMC34-DBG: Successfully loaded library libdb2.a
FMC34-DBG: Read '/db2/db2clnt/sqllib/db2profile'
FMC34-DBG: Read '/db2/db2clnt/sqllib/userprofile'
FMC34-DBG: Read '/db2/db2clnt/sqllib/profile.env'
FMC34516E: Variable DB2_RR_TO_RS is not set (should be set to 'YES').
FMC34500I: ==> Database Manager configuration for db2clnt.
FMC34509E: Query heap size is 0, must be at least 1500.
FMC34501I: ==> Database configuration for FMCDB.
FMC34508I: Log file size is 1000.
FMC34508I: Log primary is 5.
FMC34508I: Log second is 4.
FMC34508I: Database heap is 1200.
FMC34508I: Default application heap is 4096.
FMC34509E: Number of page cleaners is 1, must be at least 2.
FMC34508I: Log buffer size is 500.
FMC34508I: Lock list is 1000.
FMC34502I: ==> Database connection to FMCDB.
FMC34503E: sqleatin: SQL1427N An instance attachment does not exist.
FMC34515I: Connect to FMCDB was successful (user ID 'ROOT').
FMC34-DBG: User ID specified for connect was '<null>'
FMC34510I: The DBMS name is DB2/6000 (version 08.01.0005).
FMC34511I: The database driver is libdb2.a (Version 08.01.0005).
FMC34512I: The database name for alias 'FMCDB' is 'WBID5000'.
FMC34013I: ===> Server message device found, checks started.
FMC34-DBG: Found /usr/lpp/fmc/lib/libfmccdfms.a
FMC34-DBG: Services file is '/etc/services'
FMC34303I: TCP port MQSeries14 found at number 1414.
FMC34306I: The local listener for port 1414 is active.
FMC34303I: TCP port fmclQICSD015010 found at number 5010.
FMC34306I: The local listener for port 5010 is active.
FMC34407W: User mqm does not have connect authority.
FMC34404I: The MQSeries Server 5.3.0.7 is installed.
FMC34-DBG: Using /var/mqm/mqs.ini to locate qm.ini files
FMC34nnnI: System for QICSD01 is FMC.FMCGRP.FMCSYS
FMC34538E: Instance for QICSD01 is <null>, but DB2INSTANCE is set to db2clnt.
FMC34nnnE: DB name for QICSD01 in /var/mqm/qmgrs/QICSD01/qm.ini is <null>, should be FMCDB
FMC34nnnE: QM switch file not set for QICSD01 in /var/mqm/qmgrs/QICSD01/qm.ini
FMC34nnnI: Settings for QICSD01 from /var/mqm/qmgrs/QICSD01/qm.ini
FMC34nnnI: XAResourceManager.XAOpenString = <null>
FMC34nnnI: Channels.MaxChannels = 1000
FMC34nnnI: Channels.MaxActiveChannels = 1000
FMC34nnnI: Default queue manager is QICSD01
FMC34013I: ===> Execution Server found, checks started.
FMC34-DBG: Found /usr/lpp/fmc/bin/fmcemain
FMC34013I: ===> Client message layer (server API) found, checks started.
FMC34-DBG: Found /usr/lpp/fmc/lib/mqserver/libfmccfmlc.a
FMC34-DBG: FMLConnectName taken from configuration profile
FMC34nnnI: FMLConnectName is 'FMC.FMCGRP.FMCSYS,QICSD01'
FMC34-DBG: FMLClientChannelTable taken from configuration profile
FMC34nnnE: Channel definition file '/var/fmc/chltabs/MQWFCHL.TAB' does not exist
FMC34-DBG: FMLSegmentation taken from configuration profile
FMC34nnnI: This client can connect to an OS/390 server
FMC34013I: ===> Client message layer (client API) found, checks started.
FMC34-DBG: Found /usr/lpp/fmc/lib/mqclient/libfmccfmlc.a
FMC34-DBG: FMLConnectName taken from configuration profile
FMC34-DBG: /usr/lpp/fmc/lib/mqclient/libfmccfmlc.a is not active, skipping checks
FMC34-DBG: ===> WebSphere MQ Workflow C/C++ API not checked (none of 'A' configured)
FMC34-DBG: Checking /usr/lpp/fmc/bin/java3500...
FMC34-DBG: Checking /usr/lpp/fmc/bin/java3503...
FMC34-DBG: ===> Java Agent not checked (none of 'C' configured)
FMC34-DBG: Checking /usr/lpp/fmc/bin/java3500...
FMC34-DBG: Checking /usr/lpp/fmc/bin/java3503...
FMC34-DBG: ===> Java API not checked (none of 'J' configured)
FMC34100I: Messages have been written to /db2/db2clnt/fmczchk.log.
FMC34998I: See fmczchk.htm for more information on the messages.
FMC34999I: Configuration checker ended: 8 error(s), 1 warning(s), rc = 0.
Three Tier set-up, the db instance and db were created by the DBA, installed mqwf 3.5 step 3, db2 8.2, MQseries 5.3x, _________________ Senior WBI IT Specialist
IBM Websphere Business Integration Services
Dallas, Texas |
|
Back to top |
|
 |
jmac |
Posted: Wed Mar 02, 2005 6:26 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
There are others on this forum with more experience in setting up 3Tier MQWF configurations, but I would have a close look at the errors/warnings that relate to database access:
Code: |
FMC34407W: User mqm does not have connect authority.
FMC34503E: sqleatin: SQL1427N An instance attachment does not exist. |
There is a fairly comprehensive step by step installation process in the Install guide, when I have installed 3Tier (on Windows) I have simply followed those steps and been successful. It is my opinion that you will be best off starting over with your MQWF configugration. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
Ratan |
Posted: Wed Mar 02, 2005 9:31 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
Quote: |
the db instance and db were created by the DBA, installed mqwf 3.5 step 3, db2 8.2, MQseries 5.3x |
Was the remote DB Instance catalogued on the WF Server? _________________ -Ratan |
|
Back to top |
|
 |
karthik |
Posted: Wed Mar 02, 2005 12:17 pm Post subject: |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
Did the DBA created the database , or the database created using fmczutil?
Is 'wasadm' in mqm group?
Thanks
Karthik |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|