Bug #89261 Program terminated unexpectedly in mysql_ping ()
Submitted: 16 Jan 2018 6:51 Modified: 16 Jan 2018 7:30
Reporter: Ravi Kumar Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:5.3.9 OS:Linux (Red Hat Enterprise Linux Server release 6.5 (Santiago))
Assigned to: CPU Architecture:Any

[16 Jan 2018 6:51] Ravi Kumar
Description:
MySQL ODBC 5.3.9( 64 bit) connector is being used with Infomratica to extract data from MySQL 5.1 server. Program getting terminated unexpectedly for while closing connection.
Here is the coredump trace.

(gdb) "Current Thread :" >> core.16257.trace(gdb) #0  0x0000003cc660f5db in raise () from /lib64/libpthread.so.0
#1  0x00007fa0fa0e56ba in skgesigOSCrash () from /oracle/product/11.2.0/client_1/lib/libclntsh.so.10.1
#2  0x00007fa0fa396f6d in kpeDbgSignalHandler () from /oracle/product/11.2.0/client_1/lib/libclntsh.so.10.1
#3  0x00007fa0fa0e58ca in skgesig_sigactionHandler () from /RDAP/oracle/product/11.2.0/client_1/lib/libclntsh.so.10.1
#4  <signal handler called>
#5  0x0000003cc5e32925 in raise () from /lib64/libc.so.6
#6  0x0000003cc5e34105 in abort () from /lib64/libc.so.6
#7  0x00007fa128119729 in PmAbortProcess() () from /RDAP/Informatica/server/bin/libpmuti.so
#8  0x00000000005d208f in fatalSignalHandler(int, siginfo*, void*) ()
#9  <signal handler called>
#10 0x00007fa10c3a73b1 in cli_advanced_command () from /usr/lib64/libmyodbc5.so
#11 0x00007fa10c394786 in mysql_ping () from /usr/lib64/libmyodbc5.so
#12 0x00007fa10c38e82c in check_if_server_is_alive () from /usr/lib64/libmyodbc5.so
#13 0x00007fa10c389584 in ?? () from /usr/lib64/libmyodbc5.so
#14 0x00007fa10c3896aa in ?? () from /usr/lib64/libmyodbc5.so
#15 0x0000003cc6e27d42 in SQLTransact () from /usr/lib64/libodbc.so
#16 0x00007fa10cbbb245 in TODBCDb::Commit() () from /RDAP/Informatica/server/bin/libpmodbc.so
#17 0x00007fa10cbbb2a6 in TODBCDb::Disconnect() () from /Informatica/server/bin/libpmodbc.so
#18 0x00007fa124b61970 in TDatabase::Disconnect() () from /Informatica/server/bin/libpmodl.so
#19 0x00000000007bd356 in frame_blkReader::run() ()
#20 0x00000000007be68a in SReaderRunnable::handleRequest(SManagerRequest const&) ()
#21 0x00000000006209e9 in SWorker::run() ()
#22 0x00000000005f9b27 in SDTMRunnable::MainEntryPoint() ()
#23 0x00007fa129fbce8a in runit(void*) () from /Informatica/server/bin/libpmcef.so
#24 0x0000003cc66079d1 in start_thread () from /lib64/libpthread.so.0
#25 0x0000003cc5ee8b7d in clone () from /lib64/libc.s

How to repeat:
Rerun the program
[16 Jan 2018 6:59] Ravi Kumar
Hi,

I have changed timeout parameters to higher values and it got succeeded.

Program taken 50 minutes to complete. wait_timeout set to 7000 and it failed.

when i change wait_timeout to 15000 it got succeeded. i am still wondered why it failed with 7000 seconds when actual program execution was 3000 seconds.

Thanks,
RaviKumar
[16 Jan 2018 7:30] Chiranjeevi Battula
Hello Ravi Kumar,

Thank you for the bug report.
I'm glad that you found a solution for your problem and let us know if you are still having the issue with complete repeatable steps.

Thanks,
Chiranjeevi.