-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ODBC driver issue while working with Informatica Cloud #22
Comments
What version of psqlodbc are you using |
OS: Linux RedHat server Connection test successful using iSQL utility & Informatica UI. Able to browse objects. Let me know what additional information you need, I can provide. TY. |
Additional Stack trace form tomcat log. UTC INFO [com.informatica.saas.dtm.executor.impl.ProcessStreamReader] dtm-executor-0-01CRID0E0000000001PT-wf_mtt_01CRID0Z000000000007-4 - [01CRID0Z000000000007 01CRID0E0000000001PT] FATAL ERROR : Caught a fatal signal or exception. FATAL ERROR : Aborting the DTM process due to fatal signal or exception. ***********FATAL ERROR : Signal Received: SIGSEGV (11) Stack trace produced by process [pmdtm(:wf_mtt_01CRID0Z000000000007.s_mtt_01CRID0Z000000000007)] with pid [1929074]. |
This looks like this is happening right in the connect What version of pgsql odbc ? |
Hi Dave, Here's the version details. postgresql-odbc.x86_64 |
That's pretty old. Any chance you can try with the latest version ? |
Thank you for checking. Sure, please help me with documentation link, so that I can check the supported version and use? |
I tried version 16.0.0 still same error. |
OK, as I said this looks like a connection error. Can you share the details of the connection ? |
Using this driver, connection in informatica is successful and also I can browse the objects in the database. But when I run the mapping Informatica DTM (Data Transformation Manager) fails with fatal error. Regarding, I have to check with Network security team and get back. May I know what exact details you need? |
How you created the ODBC datasource what is in the odbc.ini file |
Here it is. odbc.ini[ODBC_pgconnection] odbcinst.ini[PostgreSQL] |
Why is there no servername or database name ? |
It's in the file, I have just removed it here for security reasons. |
Is it possible to have a call to review the details? If yes, what's the best time. |
This is not possible. |
Tested the connection from Linux server using isql utility, able to connect and browse objects. |
so it would seem something the informatica driver is doing. |
Yeah that’s what I thought initially but Informatica support told it’s ODBC driver libraries which are causing this issue. |
Ha! Of course they did. If you can connect and browse with isql, it seems that the driver is working. Did you mention that to them? |
Yes, Informatica support knows about it. |
Can I get the stack trace from the version 16 of the driver please |
Sure, I will upload it tomorrow once I login. TY |
Dave, Here's the latest stack trace. 2024-05-28 19:50:51,951 UTC INFO [com.informatica.saas.dtm.executor.impl.ProcessStreamReader] dtm-executor-0-01CRID0E000000000209-wf_mtt_01CRID0Z000000000005-38 - [01CRID0Z000000000005 01CRID0E000000000209]*********** FATAL ERROR : Aborting the DTM process due to fatal signal or exception. FATAL ERROR : Signal Received: SIGSEGV (11) |
Dave, did you get chance to look into the latest stack trace. Please let me know if you notice any discrepancy. TY |
Sorry, no. I'll try to find some time today. |
FYI, this looks very similar https://knowledge.informatica.com/s/article/000218542?language=en_US |
Yes, it is similar but no where can I find the version of driver which is working for PostgreSQL. Even Informatica support is not helping much. |
This appears to be their problem. Since this requires an informatica
connector I don’t have any way to debug it
Dave Cramer
…On Thu, May 30, 2024 at 6:37 AM Maniyur1Git ***@***.***> wrote:
Yes, it is similar but no where can I find the version of driver which is
working for PostgreSQL. Even Informatica support is not helping much.
—
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADDH5RLGTBCNHWAR6KTVTLZE4TS7AVCNFSM6AAAAABH2LSCIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGU3TOOBWGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Thank you Dave, let me know if there is a way to connect so that I can walkthrough the issue for debugging, TY. |
Dave, Informatica recommded to use driver version - 14.x or 15.x. But job failed with same error, sharing the stack trace for your reference. 2024-05-31 20:16:46,656 UTC INFO [com.informatica.saas.dtm.executor.impl.ProcessStreamReader] dtm-executor-1-01CRID0E00000000025T-wf_mtt_01CRID0Z000000000005-39 - [01CRID0Z000000000005 01CRID0E00000000025T] ***********FATAL ERROR : Caught a fatal signal or exception. FATAL ERROR : Aborting the DTM process due to fatal signal or exception. FATAL ERROR : Signal Received: SIGSEGV (11) Stack trace produced by process [pmdtm(:wf_mtt_01CRID0Z000000000005.s_mtt_01CRID0Z000000000005)] with pid [2394934]. |
seems like exactly the same issue. This isn't particularly helpful |
Something that may be helpful is to capture the problem with ODBC tracing enabled. This will log every api call and return. It slows everything down quite a bit and the log grows quickly. I imagine only the tail end of the log would be useful to see what calls lead up to the crash. Note that I'm not sure if it will include personal information so you will probably want to review it before sending it. |
Informatica Engine is failing with fatal error, attached traces for your reference.
1 Thread 0x7fa5092c0700 (LWP 1016655) 0x00007fa50dfe9acf in raise ()
from /lib64/libc.so.6
2 Thread 0x7fa51bc23740 (LWP 1016646) 0x00007fa51b81045c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
3 Thread 0x7fa50c7ac700 (LWP 1016648) 0x00007fa51b8107aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
4 Thread 0x7fa50a2c2700 (LWP 1016652) 0x00007fa50e0bef41 in poll ()
from /lib64/libc.so.6
5 Thread 0x7fa509ac1700 (LWP 1016653) 0x00007fa51b81045c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
6 Thread 0x7fa50aac3700 (LWP 1016651) 0x00007fa51b8107aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb) #0 0x00007fa50dfe9acf in raise () from /lib64/libc.so.6
#1 0x00007fa50dfbcea5 in abort () from /lib64/libc.so.6
#2 0x00007fa5196e47a9 in PmAbortProcess() () from ./libpmuti.so
#3 0x00000000005e88cf in fatalSignalHandler(int, siginfo*, void*) ()
#4
#5 0x00007fa50e06232e in _strcmp_avx2 () from /lib64/libc.so.6
#6 0x00007fa519bd5019 in lh_insert () from ./libpmcrypto.so.1.0.0
#7 0x00007fa519b32639 in OBJ_NAME_add () from ./libpmcrypto.so.1.0.0
#8 0x00007fa4d7eb518c in ossl_init_ssl_base_ossl () from /lib64/libssl.so.1.1
#9 0x00007fa51b811e67 in __pthread_once_slow () from /lib64/libpthread.so.0
#10 0x00007fa4d7b84f5d in CRYPTO_THREAD_run_once ()
from /lib64/libcrypto.so.1.1
#11 0x00007fa4d7eb53eb in OPENSSL_init_ssl () from /lib64/libssl.so.1.1
#12 0x00007fa4d813777c in pgtls_init () from /lib64/libpq.so.5
#13 0x00007fa4d8122660 in PQconnectPoll () from /lib64/libpq.so.5
#14 0x00007fa4d8123805 in connectDBComplete () from /lib64/libpq.so.5
#15 0x00007fa4d8126748 in PQconnectdbParams () from /lib64/libpq.so.5
#16 0x00007fa4d837a3ce in LIBPQ_connect () from /usr/lib64/psqlodbc.so
#17 0x00007fa4d837f380 in CC_connect () from /usr/lib64/psqlodbc.so
#18 0x00007fa4d837fcab in PGAPI_Connect () from /usr/lib64/psqlodbc.so
#19 0x00007fa4d83b88f2 in SQLConnect () from /usr/lib64/psqlodbc.so
#20 0x00007fa5081d473e in SQLConnect ()
from /opt/infaagent/apps/Data_Integration_Server/../../drivers/misc/base/bin/libodbc.so.2
#21 0x00007fa5084485ba in TODBCDb::Connect(PmUString const&, PmUString const&, PmUString const&, short) () from ./libpmodbc2.so
#22 0x00007fa515fa3867 in TDatabase::ConnectImpl(PmUString const&, PmUString const&, PmUString const&, short) () from ./libpmodl.so
#23 0x00007fa515fa403a in TDatabase::Connect(PmUString const&, PmUString const&, PmUString const&, short, int) () from ./libpmodl.so
#24 0x00007fa50867da98 in relReader::connect(int) () from ./libpmrelrdr.so
#25 0x00007fa508682893 in relReader::Connect() () from ./libpmrelrdr.so
#26 0x00000000007bffd2 in frame_blkReader::init() ()
#27 0x00000000007c032d in SReaderRunnable::handleRequest(SManagerRequest const&) ()
#28 0x0000000000633c62 in SWorker::run() ()
#29 0x000000000060f3b1 in SDTMRunnable::MainEntryPoint() ()
#30 0x00007fa51b5fcfea in runit(void*) () from ./libpmcef.so
#31 0x00007fa51b80a1ca in start_thread () from /lib64/libpthread.so.0
#32 0x00007fa50dfd4e73 in clone () from /lib64/libc.so.6
The text was updated successfully, but these errors were encountered: