cancel
Showing results for 
Search instead for 
Did you mean: 

Data integrator : C0000005 ACCESS_VIOLATION

Former Member
0 Kudos

We tried to call an Oracle Function per a Data integrator script and the following error happens :

Exception code: C0000005 ACCESS_VIOLATION

The instruction is :

DS_ODS_Perf_Offre.BI_BATCH.PK_AUDIT_SUIVI_TRT.f_Trace_fin_Df($Job_Nom,$Job_sequence ,'DF_ODS_ARTRAC','OK');

We tried to call differently (in the same script with a sql command and it works without error :

sql('DS_ODS_Perf_Offre','select PK_AUDIT_SUIVI_TRT.F_TRACE_FIN_DF({$Job_Nom},{$Job_sequence},\'DF_ODS_ARTRAC\',\'OK\') from dual');

With this solution our function is not considered as used by a Workflow (the information "usage" can't be exploited).

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

If any help to anyone in the future I got the same error. I was using a sql transform that contained the reserverd word site in a join.

I enclosed in [] so that the join was:

a.[site]=b.[site] and the error stopped occuring.

So maybe check for reserved words in a sql transform if you are using one. Note I am using sql server 2008.

Former Member
0 Kudos

what is the version of DI ?

does the trace file print stack trace from where the error is coming ?

what is the datatype for variables $Job_Nom and $Job_sequence and how are you initializing these variables ?

what is the datatype of each argument of oracle function ?

Former Member
0 Kudos

what is the version of DI ?

Data Services XI 3.0 (DI V12)

does the trace file print stack trace from where the error is coming ?

Yes

what is the datatype for variables $Job_Nom and $Job_sequence and how are you initializing these variables ?

$Job_Nom VARCHAR

$Job_sequence INT

what is the datatype of each argument of oracle function ?

$Job_Nom VARCHAR2

$Job_sequence INT

Thank's for your help

Former Member
0 Kudos

can you paste top 10 lines of the stack trace that is printed in the trace line

Former Member
0 Kudos

System Exception <ACCESS_VIOLATION> occurred. Process dump is written to <C:\Program Files\Business Objects\Data Integrator

12\log\BODI_MINI20090310112655_11220.DMP> and <C:\Program Files\Business Objects\Data Integrator

12\log\BODI_FULL20090310112655_11220.DMP>

Process dump is written to <C:\Program Files\Business Objects\Data Integrator 12\log\BODI_MINI20090310112655_11220.DMP> and

<C:\Program Files\Business Objects\Data Integrator 12\log\BODI_FULL20090310112655_11220.DMP>

Call stack:

001B:00948190, TrCallStatement::compileStatement()1568 byte(s), x:\src\compiler\dataflowstm.cpp, line 25090010 byte(s)

001B:0094D77C, DataFlowDef::compileObject()1388 byte(s), x:\src\compiler\dataflow.cpp, line 05290009 byte(s)

001B:00753643, AE_Main_Process_Options()+25491 byte(s), x:\src\xterniface\actamainexp.cpp, line 2929

001B:0075750A, AE_Main()+1482 byte(s), x:\src\xterniface\actamainexp.cpp, line 0739

001B:00402CB1

Registers:

EAX=00000000 EBX=00000000 ECX=02284258 EDX=02332C50 ESI=021FEA80

EDI=02284258 EBP=00213E0C ESP=0021398C EIP=00948190 FLG=00210246

CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

Exception code: C0000005 ACCESS_VIOLATION

Fault address: 00948190 01:00214190 C:\Program Files\Business Objects\Data Integrator 12\bin\acta.dll

Thank's for your help

Former Member
0 Kudos

what is the exact version of Data Services? check this from the Designer Help -> About Data Services

I tried to reproduce this on 12.0.0.1 and higher but didn't see the problem

is this working if you call the function in Query Mapping ?

Former Member
0 Kudos

Hi,

I'm facing the exactly the same problem. Do anyone has any idea how to get rid of it?

Version 12.1.1.0

Thanks in advance,

Kristi

Edited by: Kristi Kaljurand on Oct 30, 2009 4:54 PM

Former Member
0 Kudos

are you getting the same stack trace ?

what is the return type of the function ?

what are in/out parameter types of the function ?

Former Member
0 Kudos

Yes. Approx 40x 100MB dump files in a

day. Even if no check-in check-out operations are performed...

Error messages in errorlog.txt file remain still the same:

(12.1) 09-25-09 15:44:00 (E) (6160:8752) SYS-170101: Initialization

System Exception <ACCESS_VIOLATION> occurred. Process dump is written to<C:\Program Files\Business Objects\BusinessObjects

Data

Services\log\BODI_MINI20090925154355_6160.DMP> and <C:\Program

Files\Business Objects\BusinessObjects Data

Services\log\BODI_FULL20090925154355_6160.DMP>

Process dump is written to <C:\Program

Files\Business Objects\BusinessObjects Data

Services\log\BODI_MINI20090925154355_6160.DMP> and <C:\Program

Files\Business Objects\BusinessObjects Data

Services\log\BODI_FULL20090925154355_6160.DMP>

Call stack:

001B:00AF6904, OraDB::convertType()+0084

byte(s), x:\src\dbspec\oradb.cpp, line 3581+0007 byte(s)

001B:00B0829A, OdbcDB::convertType()+0058

byte(s), x:\src\dbspec\odbcdb.cpp, line 3886

001B:00AE3C55, SybDB::convertType()+0037

byte(s), x:\src\dbspec\sybdb.cpp, line 1968+0037 byte(s)

001B:00E02B53,

RepIntObj::get_attr_value()+0627 byte(s), x:\src\repo\rep_int_obj.cpp,

line 1120+0034 byte(s)

001B:00DC077B, RepObj::get_attr_value()+0027byte(s), x:\src\repo\rep_obj.cpp, line 0513

001B:00D9EEBB,

RepConn::export_dataflow_colmap()+0491 byte(s), x:\src\repo\rep_conn.cpp,

line 4854

001B:00D9F0E0,

RepConn::export_dataflow_colmap()+1040 byte(s), x:\src\repo\rep_conn.cpp,

line 4904+0030 byte(s)

001B:007C0A48,

AE_Main_Process_Options()+13064 byte(s),

x:\src\xterniface\actamainexp.cpp, line 1986+0011 byte(s)

001B:007C7DEA, AE_Main()+1498 byte(s),

x:\src\xterniface\actamainexp.cpp, line 0767+0030 byte(s)

001B:00402D5F

Registers:

EAX=02905EC0 EBX=00000000 ECX=00000000

EDX=00000000 ESI=028406F0

EDI=028406F0 EBP=00213428 ESP=00213220

EIP=00AF6904 FLG=00210246

CS=001B DS=0023 SS=0023 ES=0023 FS=003B

GS=0000

Exception code: C0000005 ACCESS_VIOLATION

Fault address: 00AF6904 01:00352904

C:\Program Files\Business Objects\BusinessObjects Data Services\bin\acta.dll

Former Member
0 Kudos

a similar issue was fixed in one of the 12.1 fix packs, I would suggest using the latest fix pack for 12.1, i.e 12.1.1.3 and check if the problem still exists