Этот баннер — требование Роскомнадзора для исполнения 152 ФЗ.
«На сайте осуществляется обработка файлов cookie, необходимых для работы сайта, а также для анализа использования сайта и улучшения предоставляемых сервисов с использованием метрической программы Яндекс.Метрика. Продолжая использовать сайт, вы даёте согласие с использованием данных технологий».
Политика конфиденциальности
|
|
|
проблема коннекта к DB2 со стророны Message Broker
|
|||
|---|---|---|---|
|
#18+
Что дано: WebSphere Message broker IBM DB2 HP-UX На одном сервере стоит брокер и база DB2. Создана база, нормально к ней подключаюсь. При попытке создать брокер сообщений выдается сообщение mqsicreatebroker BROKER -i user1 -a userpass -q BROKER -n DBBROKER -u db2user -p passuser AMQ8110: WebSphere MQ queue manager already exists. WebSphere MQ queue manager running. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. The setmqaut command completed successfully. BIP2321E: Database error: ODBC return code '-1'. The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error. Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration. BIP2322E: Database error: SQL State ''HY010''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] The driver is incapable of supporting the current environment attributes.''. The error has the following diagnostic information: SQL State ''HY010'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] The driver is incapable of supporting the current environment attributes.'' This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error. BIP8040E: Unable to connect to the database. The database cannot be accessed with the userid and password that were specified when the broker was created. Check that the database is running, that an ODBC connection has been created and that the userid and password pair specified for ODBC connect on the mqsicreate command are capable of being used to connect to the database using an ODBC connection. Also ensure that the database has a adequate number of database connections available for use. Вот содержимое ODBC64.ini [ODBC Data Sources] DBBROKER=IBM DB2 ODBC Driver [DBBROKER] Driver=/opt/IBM/db2/V8.1/lib64/libdb2.so Description=DBBROKER DB2 ODBC Database Database=DBBROKER [ODBC] Trace=1 TraceFile=/var/mqsi/odbc/odbctrace.out TraceDll=/opt/WebSphere/IBM/mqsi/6.0/DD64/lib/odbctrac.so InstallDir=/opt/WebSphere/IBM/mqsi/6.0/DD64 UseCursorLib=0 IANAAppCodePage=4 В odbctrace.out интересно следущее: 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 EXIT SQLConnect with return code -1 (SQL_ERROR) 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 HDBC 0x00163050 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 UCHAR * 0x00041590 [ -3] "DBBROKER" 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 SWORD -3 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 UCHAR * 0x00041560 [ -3] "db2user" 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 SWORD -3 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 UCHAR * 0xbf74a020 [ -3] "******" 2008-06-24 17:20:07.942817 ppid=12679:pid=13620:1 SWORD -3 ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 25.06.2008, 12:15 |
|
||
|
проблема коннекта к DB2 со стророны Message Broker
|
|||
|---|---|---|---|
|
#18+
Может проще сконфигурировать DB2 ODBC от IBM а не от DataDirect? ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 25.06.2008, 12:22 |
|
||
|
проблема коннекта к DB2 со стророны Message Broker
|
|||
|---|---|---|---|
|
#18+
2 xz321 Ну насколько я понимаю IBM Message Broker использут odbc64.ini bp rfnfkjuf cdjtuj /var/mqsi/odbc Если подскажешь как сконфигурировать DB2 ODBC от IBM то непременно попробую)) ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 25.06.2008, 12:31 |
|
||
|
проблема коннекта к DB2 со стророны Message Broker
|
|||
|---|---|---|---|
|
#18+
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.apdv.cli.doc/doc/t0006349.html?resultof=%22%2e%6f%64%62%63%2e%69%6e%69%22%20%22%6f%64%62%63%2e%69%6e%69%22%20 ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 25.06.2008, 12:37 |
|
||
|
проблема коннекта к DB2 со стророны Message Broker
|
|||
|---|---|---|---|
|
#18+
Всем спасибо, ограничился тем что перенаправил к другой библиотеке)) вместо Driver=/opt/IBM/db2/V8.1/lib64/libdb2.so поставил Driver=/opt/WebSphere/IBM/mqsi/6.0/lib/libdb2Wrapper.so )) ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 25.06.2008, 12:58 |
|
||
|
|
start [/forum/topic.php?fid=43&msg=35393119&tid=1603819]: |
0ms |
get settings: |
7ms |
get forum list: |
10ms |
check forum access: |
2ms |
check topic access: |
2ms |
track hit: |
31ms |
get topic data: |
6ms |
get forum data: |
1ms |
get page messages: |
27ms |
get tp. blocked users: |
1ms |
| others: | 246ms |
| total: | 333ms |
| 0 / 0 |
