Informatica provides the PowerExchange for Google bigquery to perform read/write operations. ODBC connection to the GBQ only for few usecases such PDO. I am assuming you are configuring ODBC for pushdown optimization.
The error message "FATAL ERROR : Caught a fatal signal or exception" is printed in the session log when a session is terminated. This is a very generic error message. In order to identify the cause of the error, we need traces collected on the core file generated for the session crash. Steps for retrieving the trace from core file:
Also, please check if the GBQ DSN is configured correctly as given in the below user guide:
If the connection is configured according to the manual that you indicate and verified the correct connection through DSN. Moreover, from PowerCenter Designer we can import tables and views without any problem.
For the Core log issue, we do not have the "pmstack" instruction, and the "Core" file is not modified since the middle of last year.
Any more information that we can provide you to verify if there is a connection error?
We have defined the connection as UTF-32 since the BQ fields are large.
Greetings and Thanks.
Please keep the codepage of the GBQ connection to default value "MS Windows Latin 1 (ANSI)", save the changes and see if session run goes through fine. If the BQ fields are large, you can change the ianaappcodepage value in the odbc.ini file.
Core file will not get generated if core file size value is set to 0. This can be verified with ulimit -a for the user with with informatica services are installed.
If core is still not getting generated, then i guess you can enable Simba ODBC trace and check if there are connectivity errors. THis can be done by updating the simba.googlebigqueryodbc.ini file which will be in the GBQ ODBC installation path.
When logging is enabled, the driver produces two log files at the location you specify in the Log Path (LogPath) property, where [DriverName] is the name of the driver:
1. [DriverName].log file that logs driver activity that is not specific to a connection.
2. [DriverName]_connection_[Number].log for each connection made to the database, where [Number] is a number that identifies each log file. This file logs driver activity that is specific to the connection.
If issue persists with the above change, please re-run the session again and share the below logs for debugging as core file is not getting generated:
1) Session log for recent failure run.
2) Integration service log for the relevant run time.
The error is essentially a crash . I would recommend to open a ticket with GCS .
Yes, I have changed it to Latin but it still gives the same error.
It's weird because the ODBC test is OK, and we can import Source/Target via PWX or ODBC without problems.
The configuration is correct according to the INFA documentation.
Any more ideas?
Regards and Thanks.
1 of 1 people found this helpful
as this is a crash, a core file may be created and needs to be read to understand what is happening internally.
It is better to open a ticket with GCS for this.