Quantcast
Channel: SCN : All Content - Data Services and Data Quality
Viewing all articles
Browse latest Browse all 4013

IQ16 SP08 Bulk Load in Binary Format gets C0000005 ACCESS_VIOLATION error

$
0
0

ETL jobs that are loading data to IQ16SP08 in binary format get following error. When we try bulk load in ASCII format, they work successfully. Moreover, when we load data to IQ16SP03 and lower version, ETL jobs run successfully in binary format again. I think something in IQ16SP08 changed and bulk load in binary format don't work anymore.

 

(14.2) 06-23-14 14:37:44 (R) (1316:3732) SYS-170101: |Session jb_test_x|Data flow df_dim_calendar_work

                                                     System Exception <ACCESS_VIOLATION> occurred. Process dump option is off. Process is not dumped.

                                                     Call stack:

                                                     0x00000000806B1715, SybaseIQBulkLoader::execute_file_bulkload()+1301 byte(s),

                                                     d:\im_ds_4.2_sp_rel\src\dataservices\dataintegrator\codeline\code\src\loader\sybase_iq_bulkldr.cpp, line 0507+0007 byte(s)

                                                     0x00000000806B0CA7, SybaseIQBulkLoader::execute()+0135 byte(s),

                                                     d:\im_ds_4.2_sp_rel\src\dataservices\dataintegrator\codeline\code\src\loader\sybase_iq_bulkldr.cpp, line 0303

                                                     0x00000000801B4E70, XTran_desc::execute()+0448 byte(s),

                                                     d:\im_ds_4.2_sp_rel\src\dataservices\dataintegrator\codeline\code\src\core\xtran.cpp, line 0799

                                                     0x0000000081022589, Rww_thread::main()+0249 byte(s),

                                                     d:\im_ds_4.2_sp_rel\src\dataservices\dataintegrator\codeline\code\src\rww\rww.cpp, line 0451

                                                     0x00000000009B438E, RWThreadFunctionImp::run()+0126 byte(s)

                                                     0x000000000099C184, RWRunnableImp::exec()+0372 byte(s)

                                                     0x00000000009B4643, RWThreadImp::exec()+0051 byte(s)

                                                     0x00000000009B5F59, RWThreadImp::_setTimeSliceQuantum()+0169 byte(s)

                                                     0x00000000710A37D7, endthreadex()+0071 byte(s)

                                                     0x00000000710A3894, endthreadex()+0260 byte(s)

                                                     0x000000008A3115CD, BaseThreadInitThunk()+0013 byte(s)

                                                     0x000000008C7A43D1, RtlUserThreadStart()+0029 byte(s)

                                                     Registers:

                                                     RAX=0000000000000000  RBX=0000000007B579B0  RCX=0000000009E84020  RDX=0000000000000001  RSI=0000000000000000

                                                     RDI=0000000009EC8010  RBP=0000000000000000  RSP=000000000BD7F180  RIP=00000000806B1715  FLG=0000000000010202

                                                     R8=0000000007B3E160   R9=0000000009BE8730  R10=0000000000000000  R11=0000000007B579B0  R12=0000000000000000

                                                     R13=0000000009C3A570  R14=0000000000000000  R15=0000000000000000

                                                     Exception code: C0000005 ACCESS_VIOLATION

                                                     Fault address:  00000001806B1715 01:00000000006B0715 E:\SAP BusinessObjects\Data Services\bin\acta.dll

                                                     ==========================================================

                                                     Collect the following and send to Customer Support:

                                                     1. Log files(error_*, monitor_*, trace_*) associated with this failed job.

                                                     2. Exported ATL file of this failed job.

                                                     3. DDL statements of tables referenced in this failed job.

                                                     4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when

                                                     the job failed.

                                                     5. Core dump, if any, generated from this failed job.


Viewing all articles
Browse latest Browse all 4013

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>