| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Solaris Installation Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| KittieKat |
 Posted: Thu Jan 24, 2002 2:56 pm Post subject: |
 |
|
Apprentice
Joined: 17 Dec 2001
Posts: 31
|
Hi,
I recently intalled MQSI 2.0.2 on a Solaris server machine, but every time I try to create a broker using the "mqsicreatebroker" command, the same error message would show up:
ld.so.1: mqsicreatebroker: fatal: relocation error: file /opt/mqsi/lib/libbipicu
.so: symbol __1cDstdJbad_allocG__vtbl_: referenced symbol not found
I have checked that the file it's referring does exist. Can someone tell me what this error means? I also tried to uninstall MQSI (I thought maybe I didn't install it correctly), but the "pkgrm mqsi" command doesn't exist. I'm not sure what I am doing wrong here, the only thing I can think of is that I didn't change kernel configurations (because that would require restarting the server). Thank you for your help.
- Alison
|
|
| Back to top |
|
 |
| kolban |
| Posted: Thu Jan 24, 2002 10:05 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Here is an IBM report matching this problem
| Quote: |
PROBLEM SUMMARY:
Mqseries Integrator v2 - unable to create a broker. Error
message " relocation error file/opt/mqsi/lib/libbipicu.so
symbol_1cdstdjbad_allokg_vtbl_referenced symbol not found".
I think something is more fundamentally amiss with MQSI on this
system. No MQSI program can begin executing, since the linker is
having trouble linking in any MQSI shared lib:
isq-sa-01:% export MQSI_UTILITY_TRACE=bug
isq-sa-01:% mqsicreatebroker BRKUS02
ld.so.1: mqsicreatebroker: fatal: relocation error: file
/opt/mqsi/lib/libbipicu.so: symbol __1cDstdJbad_allocG__vtbl_:
referenced symbol not found
SOLUTION:
The unscrambled version of the missing symbol is
std::bad_alloc::__vtbl.
And libbipicu.so does require this. Looking at the Solaris libraries
to find where this comes from we found it in libCrun.so.1. Looking
back at the required Solaris patches that coincide with libCrun.so.1
(see the readme.txt file) we found patch 106327-08. I then checked
the list of patches in the notes sent to mqserv@uk.ibm.com and I
could not find this one. This will need to be installed. Go to the
http://access1.sun.com site and search for 106327. Download and
install it and this should clear up the problem. Also ask customer to
re-read the readme.txt file just in case something else is missing.
The Solaris patch resolved the problem along with some DB2 config
changes. Cust considers the problem closed.
|
[ This Message was edited by: kolban on 2002-01-24 22:09 ] |
|
| Back to top |
|
|
| KittieKat |
| Posted: Mon Jan 28, 2002 8:48 am Post subject: |
|
|
Apprentice
Joined: 17 Dec 2001
Posts: 31
|
Hi,
Thank you for that helpful article! After installing the missing patches, the previous error messages stopped showing up when I try to create a broker, instead I got these database error messages:
BIP2321E Database error: ODBC return code '&1'
BIP2322E Datebase error: SQL state '&1'; Native Error Code '&2'; Error Text '&3'
The database we are using is DB2 7.2. Could this be the result of not changing the kernel configs? I'm not sure what's causing the problem, and also I wasn't able to delete the broker afterwards. Thank you for your help.
-Alison |
|
| Back to top |
|
|
| KittieKat |
| Posted: Mon Jan 28, 2002 11:25 am Post subject: |
|
|
Apprentice
Joined: 17 Dec 2001
Posts: 31
|
Hi,
This is the actual error messages I am getting from creating the broker:
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he ODBC return code was '-1'. See the following messages for information obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State 'IM004'; Native Error Code '0'; Error Text '
[MERANT][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'.
The error has the following diagnostic information: SQL State 'I
M004' SQL Native Error Code '0' SQL Error Text '[MERANT][ODBC lib
] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed'.
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
Please help, thank you!
-Alison |
|
| 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
|
|
|
|
