BusinessObjects Board

Rapid mart Job taking long time to complete

ar Friends,

One of the job called cost center Rapid marts is running since 24 hours and still it is running.It is taking long time compared to the regular job loads.

When I check the error details I found the following.Please assist what would be necassary action to be taken to address this issue.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768461> while processing column number <54> in file

<//pthmssap01p01…local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

                                                   for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768462> while processing column number <5> in file

<//pthmssap01p01…local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768463> while processing column number <54> in file

<//pthmssap01p01…local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768464> while processing column number <5> in file

                                                   <//pthmssap01p01...local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

                                                   A row delimiter was seen for row number <1768465> while processing column number <54> in file

<//pthmssap01p01…local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768466> while processing column number <5> in file

<//pthmssap01p01…local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

                                                   for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768467> while processing column number <54> in file

                                                   <//pthmssap01p01...local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

for bad data, or redefine the input schema for the file by editing the file format in the UI.

(12.2) 12-11-13 10:13:35 (W) (10008:10312) FIL-080105: |Data flow DF_CostTransactionFact_SAP|Embedded Dataflow EDF_CostTransactionFact_SAP|Reader EID_2_R3_CostTransactionFact

A row delimiter was seen for row number <1768468> while processing column number <5> in file

<//pthmssap01p01…local/trans/COTransFact.dat>. The row delimiter should be seen after <58> columns. Please check the file

for bad data, or redefine the input schema for the file by editing the file format in the UI.

Please do the needful

Thanks & Regards,


Md_Fasi (BOB member since 2011-11-19)

This is indicative of hard return characters in your data. You will be able to see this in the dat file; I use the unix sed command to extract the particular line from the file since they are so big. Look at the transport definition to find out the column and trace it back to the source. In SAP return characters are displayed as “#” characters on screen.

This is not the cause of the slow performance though. There are a couple things with that job that are slow; look at the performance monitor to find out which data flow is the problem.


craiggsmith (BOB member since 2009-06-01)

Thanks craig for your valuable suggestions.

I need to clarify few thing please help.

  1. we are having windows server system.Need to know how to open the .DAT file (I presume .Dat file will be BODS system) and if found any error how to rectify ? can I directly delete there itself.

  2. A row delimiter was seen for row number <1768462> while processing column number <5> in file

Here in this case I can see row number 1768462 in error.But when I check in DS by selecting the table I can find only 3000 records(both in Source & Target table).
Then why it is showing<1768462> in records

  1. And I find this error also
    <D:\Program Files\Business Objects\BusinessObjects Data
    Services\log\PCache/pth-sapsql03_bormdsp_bormdsp /6505284235201Sort24_3352_1>. OS Error:

When I checked OS level I found 3 GB is already available in that D path

Pleas help

Thank in advance

Regards


Md_Fasi (BOB member since 2011-11-19)

I’m really sorry that I never replied; I must have gotten busy with other things and forgot. A little late but for the record:

The .dat files are just text files. You can fix the file, but then you’ll have to make a copy of the data flow that reads directly from the file instead of the ABAP transport. You can easily do this by clicking right-clicking on the input schema in the next transform and clicking “Create File Format”.

There is a limit to what is shown in DS. The files are often quite large and overwhelm many editors. I use a Windows unix emulator to extract the files using a sed command. Then I view them in vi or another editor that shows hidden characters. Or you can turn on an overflow file and run the job again and see what lines are sent to the file.

I have often seen files over 3GB. That’s why you don’t want to try to open them in a regular text editor!


craiggsmith (BOB member since 2009-06-01)

In general you do not want cache files that large. It means that data is handled on the BODS server that does not fit in to memory (normally around 4GB or so). A redesing of the DF to push the data to the database will perform much better.


Johannes Vink :netherlands: (BOB member since 2012-03-20)

This is something different – it is not a cache file but rather an SAP export file. This is how data is extracted from SAP in 4.0, there is no way to change it.


craiggsmith (BOB member since 2009-06-01)

Sorry, I was referring to point 3, not point 1.

For the .dat file you are definitely right.


Johannes Vink :netherlands: (BOB member since 2012-03-20)

Oh, OK, sounds good.


craiggsmith (BOB member since 2009-06-01)