Posted: Thu May 11, 2006 7:11 am Post subject: help urgent
Apprentice
Joined: 22 Jun 2004 Posts: 34
i am getting this error
Probe Description :- AMQ7605: The XA resource manager OracleKate has returned an unexpected return code -3, when called for xa_recover.
in the .FDC file
The issue has been resolved but need to investigate why did it occur.
This is the qm.ini file,where the Resource manager stanza is added
==========================================
#*******************************************************************#
#* Module Name: qm.ini *#
#* Type : WebSphere MQ queue manager configuration file *#
# Function : Define the configuration of a single queue manager *#
#* *#
#*******************************************************************#
#* Notes : *#
#* 1) This file defines the configuration of the queue manager *#
#* *#
#*******************************************************************#
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
#* *#
#* *#
Log:
LogPrimaryFiles=32
LogSecondaryFiles=31
LogFilePages=4095
LogType=CIRCULAR
LogBufferPages=0
LogPath=/var/mqm/log/XHLW_KATE001/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib/amqzfu
ComponentDataSize=0
#*******************************************************************#
# DO NOT EDIT THIS WITHOUT ASKING FIRST: TPC 26-MAR-03
# ADDED XA RESOURCE MANAGER TO ENABLE THE DEPLOYMENT OF KROKER
# CHANGED XAOpenString TO 'Threads=false' AS TO OVERCOME XA PROBLEM
# WHEN HAVING 2 INSTANCES OF KROKER RUNNING CONCURENTLY - JAY JAYATISSA
# 28-MAR-03
# CHANGED THE username/password IN THE XAOpenString - JAY JAYATISSA 09-APR-04
#*******************************************************************#
XAResourceManager:
Name=OracleKateT
SwitchFile=/var/mqm/oraswit
XAOpenString=Oracle_XA+DB=UKVAL188+Acc=P/KATE_SERVICE_USER/ADAYATTHERACES33+SesTm=60+Threads=false+DbgFl=0x7+SqlNet=UKVAL188
ThreadOfControl=PROCESS
==============================================
Now there was some upgrade in progress on the DB UKVAL188, and once this upgrade was done and the DB UKVAL188 was fully apperaed the error that we were facing on PRODUCTION DB UKPRD188 was resolved.
so i need to know in first place how the upgrade on the DB UKVAL188 affected the resource manager for PROD DB UKPRD188.
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