Issue with concurrent users on Ignite 1.6.0 ODBC

classic Classic list List threaded Threaded
21 messages Options
12
Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Team,

We are running the script with 16 users concurrently on Ignite ODBC node.

Some of the user processors are interrupted and stopped in between.And also this issue happens even with 2 user concurrent test.

The same scenario works with Ignite 1.5.0.

Please suggest, do we need to modify any configuration for concurrent test on ODBC.

Thanks,
Agneeswaran
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Agneeswaran,

Can you please clarify what kind of test are you running and what kind of
an issue are you facing? What does the test do exactly and what kind of
behavior do you observe? Are the any exceptions?

Best Regards,
Igor

On Tue, Jul 12, 2016 at 4:26 AM, Agneeswaran <[hidden email]> wrote:
Hi Team,

We are running the script with 16 users concurrently on Ignite ODBC node.

Some of the user processors are interrupted and stopped in between.And also
this issue happens even with 2 user concurrent test.

The same scenario works with Ignite 1.5.0.

Please suggest, do we need to modify any configuration for concurrent test
on ODBC.

Thanks,
Agneeswaran



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

We are running the same query or different query on parallel for concurrent test using Ignite ODBC node to check the data retrieval time but we are end up with the Segmentation fault as the processors gets interrupted/stopped.

We are unable to execute the same or different query on parallel for more than 2 times.

The scripts do internally as below, for example following is for 7 user processors,
The sleep time between the processes is 1 second.

[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[1] 36099
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[2] 36105
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[3] 36113
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[4] 36118
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[5] 36123
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[5] 36123
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[6] 36129
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[7] 36136

The process stopped for few users,
./gotest: line 6: 35296 Segmentation fault      (core dumped) ./Bc_AggProc $1 $2 $3 $4 "$5" $6

Sometime scripts never gets stopped till we do ctl+c or kill the process.

The same scripts runs with 16 and 48 users without any issues on ignite 1.5.0.

Please provide your suggestion.

Thanks,
Agneeswaran
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

Do you use ODBC for these tests?

Best Regards,
Igor

On Tue, Jul 12, 2016 at 1:45 PM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

We are running the same query or different query on parallel for concurrent
test using Ignite ODBC node to check the data retrieval time but we are end
up with the Segmentation fault as the processors gets interrupted/stopped.

We are unable to execute the same or different query on parallel for more
than 2 times.

The scripts do internally as below, for example following is for 7 user
processors,
The sleep time between the processes is 1 second.

[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[1] 36099
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[2] 36105
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[3] 36113
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[4] 36118
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[5] 36123
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[5] 36123
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[6] 36129
[ignite@dayrhegapd022 Linux]$ ./gotest 712 4378038 5000007 0 COFFEE 1 &
[7] 36136

The process stopped for few users,
./gotest: line 6: 35296 Segmentation fault      (core dumped) ./Bc_AggProc
$1 $2 $3 $4 "$5" $6

Sometime scripts never gets stopped till we do ctl+c or kill the process.

The same scripts runs with 16 and 48 users without any issues on ignite
1.5.0.

Please provide your suggestion.

Thanks,
Agneeswaran




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6228.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

Yes, we have used the ODBC to test this scenario.

Please.

Thanks,
Agneeswaran
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

You said you were running the same test on 1.5.0. But 1.5.0 does not include ODBC driver.
Were you using one of the nightly builds?

Also, it would be very useful if you could provide either your test or segfault core dump.

Best Regards,
Igor

On Tue, Jul 12, 2016 at 2:21 PM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

Yes, we have used the ODBC to test this scenario.

Please.

Thanks,
Agneeswaran



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6230.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

Yes, this test is executed with ignite 1.5.0 release version without ODBC.

I could see there is no code dump files generated in our executable path.

Could you please suggest the configuration which you need for test.

We are using our client project for testing this scenario.

Thanks in advance,

With regards,
Agneeswaran
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

I'm a little confused here, as you are telling you used the same test for the
1.5.0 and for the 1.6, but for the 1.5.0 you didn't use ODBC and for the
1.6 you do. How could this be possible? Have you modified your test to use
ODBC on 1.6?

Do you use the same ODBC connection concurrently or do you open new
connection for every thread?

Regarding core dumps, if you are using bash, try this command prior to
starting your program:
ulimit -c unlimited
With this your program should start generate core dumps on crash.



Best Regards,
Igor

On Tue, Jul 12, 2016 at 4:35 PM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

Yes, this test is executed with ignite 1.5.0 release version without ODBC.

I could see there is no code dump files generated in our executable path.

Could you please suggest the configuration which you need for test.

We are using our client project for testing this scenario.

Thanks in advance,

With regards,
Agneeswaran




--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6232.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

Thanks for the information.

Sorry for the confusion caused, We are running this test case as the first time with ODBC in 1.6.0.
We never tried this test scenario with ODBC earlier.

Yes, We are creating a new connection for every thread.

Please find the attached core dump.

Please suggest us.

Thanks,
Agneeswaran

Core_dump.zip</<nabble_a href="Core_dump1.zip">Core_dump1.zipnabble_a>
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

Can you also send me your ignite libraries from the /usr/local/lib/libignite* ?
That would be helpful for analyzing core dump as I seem to have different gcc version.

Best Regards,
Igor

On Tue, Jul 12, 2016 at 5:50 PM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

Thanks for the information.

Sorry for the confusion caused, We are running this test case as the first
time with ODBC in 1.6.0.
We never tried this test scenario with ODBC earlier.

Yes, We are creating a new connection for every thread.

Please find the attached core dump.

Please suggest us.

Thanks,
Agneeswaran

Core_dump.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/n6234/Core_dump.zip>
</&lt;nabble_a href=&quot;Core_dump1.zip&quot;>Core_dump1.zip nabble_a>



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6234.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

Please find the attached lib files,

Thanks,
Agneeswaran

lib1.zip

lib2.zip

lib3.zip

lib4.zip

lib5.zip

Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

What I can see is that SEGFAULT caused by the misuse of the SQLGetDiagRec -
our current implementation of the function assumes that TextLengthPtr could not
be NULL. Fix that and you are going to get some meaningful error message that
we could analyze further. From the core dump it looks like a "Failed to run map
query remotely." error message, but it's better to be sure.
Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Thanks Igor,

Will debug our code and will share our analysis.

Thanks,
Agneeswaran
Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

In reply to this post by Igor Sapego
Hi Igor,

We have debugged our code, as the core dump refers to SQLGetDiagRec() function.

We are using this particular function to do the error validation,Yes previously TextLengthPtr was assigned to NULL pointer.

while (SQLGetDiagRec(hType,
                hHandle,
                ++iRec,
                (SQLCHAR*)wszState,
                &iError,
                wszMessage,
                (SQLSMALLINT)(sizeof(wszMessage) / sizeof(CHAR)),
                /*(SQLSMALLINT *)NULL*/ &len) == SQL_SUCCESS)
        {
       ...
          }

With/Without the above code the concurrent test is failing.And we are getting the following error message for failed process.

[HY000] Failed to run map query remotely. (0)

[ignite@dayrhegapd022 Linux]$ ./launch_job_list.ksh testjuy11.txt 16
main: mypid 24465
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] [Failed to run map query remotely. (HY0000] )Failed to run map query remotely. (0)
-984
-984
[HY000] Failed to run map query remotely. (0)
rawdata failed
-984

There is no core dump file is generated after we changed from NULL pointer in SQLGetDiagRec().

Please let us know, how to debug further on this.

Thanks,
Agneeswaran
Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

Could you please suggest us, how to look forward with this.

Thanks,
Agneeswaran

Pasting earlier post.

Hi Igor,

We have debugged our code, as the core dump refers to SQLGetDiagRec() function.

We are using this particular function to do the error validation,Yes previously TextLengthPtr was assigned to NULL pointer.

while (SQLGetDiagRec(hType,
                hHandle,
                ++iRec,
                (SQLCHAR*)wszState,
                &iError,
                wszMessage,
                (SQLSMALLINT)(sizeof(wszMessage) / sizeof(CHAR)),
                /*(SQLSMALLINT *)NULL*/ &len) == SQL_SUCCESS)
        {
       ...
          }

With/Without the above code the concurrent test is failing.And we are getting the following error message for failed process.

[HY000] Failed to run map query remotely. (0)

[ignite@dayrhegapd022 Linux]$ ./launch_job_list.ksh testjuy11.txt 16
main: mypid 24465
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] [Failed to run map query remotely. (HY0000] )Failed to run map query remotely. (0)
-984
-984
[HY000] Failed to run map query remotely. (0)
rawdata failed
-984

There is no core dump file is generated after we changed from NULL pointer in SQLGetDiagRec().

Please let us know, how to debug further on this.

Thanks,
Agneeswaran
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Agneeswaran,

Sorry, I seem to miss your previous mail.
I'm going to take a look and tell you about the results.

Best Regards,
Igor

On Tue, Jul 19, 2016 at 9:51 AM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

Could you please suggest us, how to look forward with this.

Thanks,
Agneeswaran

Pasting earlier post.

Hi Igor,

We have debugged our code, as the core dump refers to SQLGetDiagRec()
function.

We are using this particular function to do the error validation,Yes
previously TextLengthPtr was assigned to NULL pointer.

while (SQLGetDiagRec(hType,
                hHandle,
                ++iRec,
                (SQLCHAR*)wszState,
                &iError,
                wszMessage,
                (SQLSMALLINT)(sizeof(wszMessage) / sizeof(CHAR)),
                /*(SQLSMALLINT *)NULL*/ &len) == SQL_SUCCESS)
        {
       ...
          }

With/Without the above code the concurrent test is failing.And we are
getting the following error message for failed process.

[HY000] Failed to run map query remotely. (0)

[ignite@dayrhegapd022 Linux]$ ./launch_job_list.ksh testjuy11.txt 16
main: mypid 24465
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] [Failed to run map query remotely. (HY0000] )Failed to run map query
remotely. (0)
-984
-984
[HY000] Failed to run map query remotely. (0)
rawdata failed
-984

There is no core dump file is generated after we changed from NULL pointer
in SQLGetDiagRec().

Please let us know, how to debug further on this.

Thanks,
Agneeswaran



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6369.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

Can you see any errors in the nodes log?

Best Regards,
Igor

On Tue, Jul 19, 2016 at 1:10 PM, Igor Sapego <[hidden email]> wrote:
Hi Agneeswaran,

Sorry, I seem to miss your previous mail.
I'm going to take a look and tell you about the results.

Best Regards,
Igor

On Tue, Jul 19, 2016 at 9:51 AM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

Could you please suggest us, how to look forward with this.

Thanks,
Agneeswaran

Pasting earlier post.

Hi Igor,

We have debugged our code, as the core dump refers to SQLGetDiagRec()
function.

We are using this particular function to do the error validation,Yes
previously TextLengthPtr was assigned to NULL pointer.

while (SQLGetDiagRec(hType,
                hHandle,
                ++iRec,
                (SQLCHAR*)wszState,
                &iError,
                wszMessage,
                (SQLSMALLINT)(sizeof(wszMessage) / sizeof(CHAR)),
                /*(SQLSMALLINT *)NULL*/ &len) == SQL_SUCCESS)
        {
       ...
          }

With/Without the above code the concurrent test is failing.And we are
getting the following error message for failed process.

[HY000] Failed to run map query remotely. (0)

[ignite@dayrhegapd022 Linux]$ ./launch_job_list.ksh testjuy11.txt 16
main: mypid 24465
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
Executing: 712,4378038,5000007,0,COFFEE,1
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] Failed to run map query remotely. (0)
-984
[HY000] [Failed to run map query remotely. (HY0000] )Failed to run map query
remotely. (0)
-984
-984
[HY000] Failed to run map query remotely. (0)
rawdata failed
-984

There is no core dump file is generated after we changed from NULL pointer
in SQLGetDiagRec().

Please let us know, how to debug further on this.

Thanks,
Agneeswaran



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6369.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Hi Igor,

Sorry, I am not sure where to check this Node log file.

Could you please help me on this.

Thanks,
Agneeswaran
Igor Sapego Igor Sapego
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Agneeswaran,

When you start your node there should be a path to the log:
[18:27:41]   ^-- Logging to file '...'

By default, logs are stored in $IGNITE_HOME/work/log/

Best Regards,
Igor

On Tue, Jul 19, 2016 at 1:20 PM, Agneeswaran <[hidden email]> wrote:
Hi Igor,

Sorry, I am not sure where to check this Node log file.

Could you please help me on this.

Thanks,
Agneeswaran



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6382.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Agneeswaran Agneeswaran
Reply | Threaded
Open this post in threaded view
|

Re: Issue with concurrent users on Ignite 1.6.0 ODBC

Thanks Igor,

Please find the attached Node log file.

ignite-157c6cf1.zip


We could see SQL Exception caused while executing SQL statements,

From the Node log,
at java.lang.Thread.run(Thread.java:745)
Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.ArrayIndexOutOfBoundsException"; SQL statement:
SELECT DISTINCT
SID_MAH_ID __C0,
SID_ITM_ID __C1,
SID_PRM_ID __C2,
SID_CHA_CODE __C3,
SID_SERVICE __C4,
SID_ITM_DIST __C5
FROM MARKET_POD_ACV_CACHE.MARKETPODACV MKT
 INNER JOIN SHOP_ITEM_BITMAP_CACHE.SHOPITEMBITMAP BITMAP
WHERE (BITMAP.SID_PER_ID = 712) AND ((BITMAP.SID_MAH_ID = MKT.CHLD_MRKT_KEY) AND ((BITMAP.CATEGORY = 'COFFEE') AND ((MKT.MRKT_KEY = 4378038) AND (MKT.PRD_ID = 712)))) [50000-175]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:332)

With regards,
Agneeswaran
12