It's all about the answers!

Ask a question

Error while configuring RQM Live Reporting


Nikhil Vipradas (111214) | asked Jul 28 '14, 5:19 a.m.
Hello Team
I am getting error while configuring the RQM Live reporting.

Please check the error in odbc_u.log as below :

[ODBC][21174][1406538704.435421][__handles.c][450]
                Exit:[SQL_SUCCESS]
                        Environment = 0x9e9750
[ODBC][21174][1406538704.435485][SQLAllocHandle.c][364]
                Entry:
                        Handle Type = 2
                        Input Handle = 0x9e9750
[ODBC][21174][1406538704.435536][SQLAllocHandle.c][482]
                Exit:[SQL_SUCCESS]
                        Output Handle = 0x9ea080
[ODBC][21174][1406538704.435561][SQLConnect.c][3614]
                Entry:
                        Connection = 0x9ea080
                        Server Name = [RQM][length = 3 (SQL_NTS)]
                        User Name = [NULL]
                        Authentication = [NULL]
                UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE'

[ODBC][21174][1406538704.437523][SQLConnect.c][1296]Error: IM004
[ODBC][21174][1406538704.437578][SQLError.c][430]
                Entry:
                        Connection = 0x9ea080
                        SQLState = 0x7fffdc10a280
                        Native = 0x7fffdc10a078
                        Message Text = 0x7fffdc10a080
                        Buffer Length = 500
                        Text Len Ptr = 0x7fffdc10a07e
[ODBC][21174][1406538704.437622][SQLError.c][467]
                Exit:[SQL_SUCCESS]
                        SQLState = IM004
                        Native = 0x7fffdc10a078 -> 0
                        Message Text = [[unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed]
[ODBC][21174][1406538704.437651][SQLError.c][430]
                Entry:
                        Connection = 0x9ea080
                        SQLState = 0x7fffdc10a280
                        Native = 0x7fffdc10a078
                        Message Text = 0x7fffdc10a080
                        Buffer Length = 500
                        Text Len Ptr = 0x7fffdc10a07e
[ODBC][21174][1406538704.437670][SQLError.c][467]
                Exit:[SQL_NO_DATA]
[ODBC][21174][1406538704.437688][SQLError.c][510]
                Entry:
                        Environment = 0x9e9750
                        SQLState = 0x7fffdc10a280
                        Native = 0x7fffdc10a078
                        Message Text = 0x7fffdc10a080
                        Buffer Length = 500
                        Text Len Ptr = 0x7fffdc10a07e
[ODBC][21174][1406538704.437704][SQLError.c][547]
                Exit:[SQL_NO_DATA]
[ODBC][21174][1406538704.437728][SQLFreeHandle.c][279]
                Entry:
                        Handle Type = 2
                        Input Handle = 0x9ea080
[ODBC][21174][1406538704.437746][SQLFreeHandle.c][330]
                Exit:[SQL_SUCCESS]
[ODBC][21174][1406538704.437765][SQLFreeHandle.c][212]
                Entry:
                        Handle Type = 1
                        Input Handle = 0x9e9750


[root@ tmp]# odbcinst -j
unixODBC 2.2.14
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /root/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
[root@ tmp]#

[root@ tmp]# cat /etc/odbcinst.ini
# Driver from the postgresql-odbc package
# Setup from the unixODBC package
[PostgreSQL]
Description     = ODBC for PostgreSQL
Driver          = /usr/lib/psqlodbc.so
Setup           = /usr/lib/libodbcpsqlS.so
Driver64        = /usr/lib64/psqlodbc.so
Setup64         = /usr/lib64/libodbcpsqlS.so
FileUsage       = 1


# Driver from the mysql-connector-odbc package
# Setup from the unixODBC package
[MySQL]
Description     = ODBC for MySQL
Driver          = /usr/lib/libmyodbc5.so
Setup           = /usr/lib/libodbcmyS.so
Driver64        = /usr/lib64/libmyodbc5.so
Setup64         = /usr/lib64/libodbcmyS.so
FileUsage       = 1

[DB2]
Description     = DB2 new driver
Driver          = /opt/ibm/db2/V9.7/lib32/libdb2.so
Driver64       = /opt/ibm/db2/V9.7/lib32/libdb2.so
Setup           = /opt/ibm/db2/V9.7/lib32/libdb2.so
Setup64         = /opt/ibm/db2/V9.7/lib32/libdb2.so
UsageCount      = 100
CPTimeout       = 10000
CPReuse         =

[IBM Rational XML ODBC Driver]
Description=
Driver=/opt/IBM/RRDI/etl/odbc/libratlxml.so
Driver64=/usr/lib64/libodbcinst.so
Setup=/opt/IBM/RRDI/etl/odbc/libratlxmlS.so
Setup64=/usr/lib64/libodbcinst.so
LIBPATH=/opt/IBM/RRDI/etl/jdbc
MaxActiveStatements=100
QueuingTimeout=100000
DefaultPageSize=1000
DefaultRetryTimes=10
HttpConnectionTimeout=3600000
Threading=0
UsageCount=2
jdbclogpath=/tmp/jdbc.log
Debug=/tmp/odbc.log

[ODBC]
Trace=Yes
TraceFile=/tmp/odbc_u.log


[root@ tmp]# cat /etc/odbc.ini
[RQM]
Driver          = IBM Rational XML ODBC Driver
DataSource              = RQM
Description             =
User Name               = xxxxxxxx
Authentication          = xxxxxxxx
Configuration           = /opt/IBM/RRDI/etl/configs/rqm406.xdc

[RQM Live]
Driver          = IBM Rational XML ODBC Driver
DataSource              = RQM Live
Description             =
User Name               = xxxxxxxx
Authentication          = xxxxxxxx
Configuration           = /opt/IBM/RRDI/etl/configs/rqm403-live.xdc
[root@ tmp]#


[root@ tmp]# isql -v "RQM"
[IM004][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed
[ISQL]ERROR: Could not SQLConnect
[root@ tmp]#


Can you please help me on this ?

Thanks in advance.

Accepted answer


permanent link
Francesco Chiossi (5.7k11119) | answered Jul 28 '14, 5:32 a.m.
edited Jul 28 '14, 5:33 a.m.
Hello Nikhil,

I would check the following points:

1) Make sure unixodbc is 32bit:
[root@report ~]# file /usr/local/bin/isql
/usr/local/bin/isql: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
check that it says ELF 32-bit LSB executable.

2) Check that all the dependencies for /opt/IBM/RRDI/etl/odbc/libratlxml.so are satisfied

[root@report ~]# ldd /opt/IBM/RRDI/etl/odbc/libratlxml.so
        linux-gate.so.1 =>  (0xffffe000)
        libicui18n.so.38 => /opt/IBM/RRDI/etl/odbc/lib/libicui18n.so.38 (0xf7e0c000)
        libicudata.so.38 => /opt/IBM/RRDI/etl/odbc/lib/libicudata.so.38 (0xf7335000)
        libicuio.so.38 => /opt/IBM/RRDI/etl/odbc/lib/libicuio.so.38 (0xf732b000)
        libicuuc.so.38 => /opt/IBM/RRDI/etl/odbc/lib/libicuuc.so.38 (0xf7206000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xf71c7000)
        libc.so.6 => /lib/libc.so.6 (0xf706e000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf6f83000)
        libm.so.6 => /lib/libm.so.6 (0xf6f5a000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf6f4e000)
        /lib/ld-linux.so.2 (0x0077c000)

3) If everything is OK on the other point, you can consider replacing unixodbc with a more recent version (2.3.X). Sometime it helps.

Best Regards,

Francesco Chiossi
Nikhil Vipradas selected this answer as the correct answer

Comments
1
Nikhil Vipradas commented Jul 28 '14, 6:11 a.m.

Thanks a lot Francesco!! :-)
Its working after installing 32 bit unixODBC.
Cheers !!


Francesco Chiossi commented Jul 28 '14, 6:36 a.m.

Glad to hear that it's fixed.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.