| Author |
Message
|
| francoisvdm |
 Posted: Wed May 21, 2003 4:38 am Post subject: [SOLVED]V3.4 install on AIX problem with remote DB |
 |
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Hi
I'm getting the following error immediately after I created a configuration. When I look around the queue manager was created, but no DBs on the remote system. Any ideas?
c ... Create configuration profile for 'FMC' now
s ... Save input to file
r ... Review/change input
x ... Exit (input for configuration 'FMC' will be lost)
c
- FMC33680I The profile for the configuration 'FMC' was updated successfully.
- FMC33682I The general configuration profile was updated successfully.
FMC33999E Internal error: 'FmcOSException, ServiceName=Output to stream failed!, ReturnCode=0, ReasonCode=0'.
FMC33201I Configuration Commands Menu:
l ... List
s ... Select
c ... Create
x ... Exit Configuration Commands Menu
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe
Last edited by francoisvdm on Sat May 24, 2003 8:29 am; edited 1 time in total |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed May 21, 2003 6:02 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Creating a remote DB is not as easy as you think (atleast I felt that way). Did you create the directory structure etc on the database box ??
Need more info on what you did and what you didn't, specifically on the DB box. |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Wed May 21, 2003 6:31 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Yes, I created the DB directory with all the right access etc. But, I think it is working now. There was a big core file in the root directory. I deleted that and suddenly it went ok and created the DB, but now it did not create all the MQ channels, so I'm creating that by hand. I'll soon start up the workflow to see if it works.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| vennela |
| Posted: Wed May 21, 2003 6:38 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What MQ channels are you talking about ?
It will not create any MQ channels by default.
Let the config utility do everything for you because there is always a chance of error when we manually define the mq objects. |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Wed May 21, 2003 6:50 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Yes, it creates a svrconn channel and a clntconn channel. It did create the svrconn channel, but there was a problem with the client channel. I think I have a problem with the position of the MQ client connection table, but that should be easy to fix.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| vennela |
| Posted: Wed May 21, 2003 7:13 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I gotcha
| Quote: |
MQSeries Workflow creates its own copy of the channel table and subsequently removes the default copy. You must now set a couple of environment variables on the server prior to starting runmqsc in order to point runmqsc to the newly created channel table. This will allow you to circimvent the message.
Set or export depending on the platform:
MQCHLTAB=MQWFCHL.TAB
MQCHLLIB=channeltabpath
where channeltabpath on unix is /var/fmc/chltabs and
on windows, <mqwfinstalldir>/fmc/chltabs |
This was posted by charlie a while back. |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Wed May 21, 2003 7:39 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Unless you got other queue managers on the platform that are already using the default channel table. I just pointed in the workflow configuration to the existing channel table and now everything is working.
Thanks for the help
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| sshaker |
| Posted: Thu May 22, 2003 2:12 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 185
|
i agree with vennela.. having three tier on unix and making it work is a pain.. initially.. once it is up and running ..life is little cool..
u may use the script files copied part of confguration to create any mq objects.. the directory where all the script files will be available is
/var/fmc/qmgrs/<wfqmgrname>/mqs
u may go thru inidividual file.. before u really run against runmqsc..
all the best
regards
shaker
_________________
shaker |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Thu May 22, 2003 2:23 pm Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Thanks all, I got everything running.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
|
|
