Issue when number of records in a DSO exceeds DTP package size

Hi all,
I'm having a strange problem with the package size of my DTPs.
I move data from a DSO to another one while performing some transformations in an Export routine. The DTP has a package size of 6 million records.
When the number of records in the first DSO exceeds the package size, some of the records seem not to be processed properly by the transformation and this forces me to choose a very large number for the package size so that the ABAP code in the transformation is processed for all the records of the source DSO.
I can't understand why this is happening because package size is only supposed to determine the number of records to be processed in a single step and nothing else.
Am I right?
Thanks

My tip would also be the summary item

Similar Messages

BP: Only continue when number of records is greater zero

Hi everybody!
In my business process I have a decision step which should end the process if a synchronous send step does not yield a result.
I thought this could be achieved using an XPATH syntax like so:
count(/p1:data/p1:records/p1:PKEY)
Using a container operation I assign the result of this count to a variable. However, this XPATH expression yields 0 - regardless of the number of records received. What am I doing wrong?
Regards, Joerg

Hi,
it has to work but the xpath needs to be used <b>correctly:</b>
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Sync Issues When a Separate Recorder is Used?

Unfortunately, I do not know the author of this material, and first saw it in another post to the Adobe forum. If the author sees this, please step up to take credit for a well-written explanation of why Audio is OOS with footage, when one has used a separate recorder, that is not hard-wired into the camera and deriving the sync signals from it. I must emphasize that I did not write this piece, and am only posting it to help others, when they use a separate recorder, not tied to the camera, say a Zoom, or similar.
I have also not used the mentioned/linked program, so cannot comment on that. However, I would make one change, if possible, and that would be to use PCM/WAV and not the recommended Linear WAV, as some Adobe programs can have issues with Linear WAV. Other than that little suggestion, I really like this piece, and for many other NLE's, the Linear WAV will probably not be an issue - just with some Adobe programs.
The Problem -
Miniature audio recorders, be they minidisc or solid state, offer a very attractive, cost effective, alternative to the traditional use of radio microphones, for the capture of remote audio sources in video recordings
These machines record the audio in a variety of different formats - MP3, WMA, WAV, ATRAC -- and in a variety of qualities - but they all suffer from the same problem. It can be difficult to synchronise the remotely recorded audio, with the camera recorded audio.
Although the time honoured tradition of an audio 'clapper board' works well enough to align the beginning of the two soundtracks, there is a tendency for the two tracks to appear to 'drift' out of sync over time - and the longer the recording, the worse the problem. In fact they do not actually 'drift', but the gradual loss of sync is a function of the camera and audio recorder sample clocks being slightly different frequencies.
The simple reason for this loss of 'sync' therefore is that the audio is being recorded at different speeds. Although the recorder will specify the sampling frequency, the accuracy is then dependent on the internal crystal oscillator of the recorder - which is, of course, a different oscillator from the one controlling the camera timing. Although these crystals may typically be accurate to within 0.005% or better, even this degree of accuracy can cause the two recorded audio tracks to be out of sync by up to 300mS after 30 minutes. Even after 5 minutes, the 2 tracks can be some 60mS different in length, in a worst case scenario.
60mS difference will cause a distinctly audible 'echo' between the two audio tracks. (Even 20mS is detectable as a separate echo).
This difference is of course totally unacceptable, and corrections need to be applied. It is important to remember that even if your audio recorder crystal is absolutely accurate, and it is the camera clock that is slightly wrong, it is still the remote audio track that will have to be corrected. The 'wrong' camera audio track is the one in sync with the video, and has to be the 'master' track.
The Solution
It is important to realise that although the sample oscillators may vary with regard to each other, they tend to be remarkably accurate over time, referenced to themselves.
This means that if you know by how much the frequency your audio recorder sample 'clock' differs from the camera 'clock', then a single correction factor will bring both tracks back into sync.
A simple procedure is outlined below, using free programs, to enable you to calculate the correction factor required for your particular recorder.
Programs required (all free):
1) AoA audio Extractor --- (not necessary if you can extract the audio track from a video recording in your NLE)
2) Audacity , a free audio editor
3) Switch , a free audio file type converter
Step 1: Set up your camera and audio recorder next to each other, and start both running
Step 2: Make a good audio 'clapperboard' point by tapping a pencil firmly onto a hard surface, as close to both camera and recorder mics as possible. This will cause a fast 'edge' to become the reference point, which will be useful later.
Step3: Let both devices run for at least 10 minutes. 20 minutes are better, but not essential.
At the end of the period, (timing not critical), make a second similar 'clapperboard' reference point. Allow a few more seconds recording, and then stop both devices.
Step 4: Download the video from the camera, and the audio from the recorder to yourcomputer.
Step 5: Open the video file in 'AoA audio Extractor', and extract the audio from the video. Convert this audio file (if necessary) to a 48KHz 16 bit LPCM (wav) file, using the 'Switch' program linked to above. This file will be your reference audio file.
Step 6: Open the WAV file saved in the previous step in 'Audacity' - a free audio editor.
It is now necessary to save only the part of the file between the two 'clapperboard' references, which hopefully stand out clearly (if you hit the pencil hard enough in steps 2 and 3!).
This must be done accurately, to within 100th of a second, or better.
Click and drag the file to highlight the beginning section, including the first 'clapperboard' waveform. Use the 'fit selection to window' tool (immediately to the right of the 'zoom' tools) to magnify. Delete as much as possible before the 'clapper' reference. Repeat the operation until you can clearly identify the first distinct waveform of the 'clapper' reference waveform. Click, hold and place the cursor directly over the first full (clipped) waveform, where it crosses the centre line. Delete every thing to the left of that point, by clicking and dragging to highlight, and then deleting with the scissors tool.
Step 7: Repeat the above procedure for the end part of the waveform, again using thestart of the second 'clapper' waveform as your reference cutting point. In this case, cut everything to the right of your selected reference point (not the left, as in the first case.)
Step 8: It is necessary to record the exact length of this new cropped waveform. This information is listed at the bottom of the window, but in a rather inappropriate format. Locate the toolbar at the top of the window, click 'Edit'-'select all' and then 'Effects'-'change tempo' . Note the length of the file in seconds in the right hand box (the left hand box is greyed out).
Record this figure. It is the reference file length
Step 9: It is necessary to convert the file recorded on the audio recorder into an identical format to the camera audio track, namely 48 KHz 16 bit PCM. If the track is not already in this format, open it in Switch, a free file transfer program, and select the output encoding as 48 KHz 16 bit, mono or stereo to fit your audio file. This program will then convert whatever format your input file is (MP3, WMA, 44.1 KHz PCM, etc) into the required 48 KHz, 16 bit format required.
Step 10: Repeat the procedures in steps 6 and 7 for this new file. Edit the 'clapper' points with as much accuracy as before, but notice that the 'clapper' waveform will appear different from the first, although hopefully with as clearly defined first ' zero crossing' point.
Step 11: Repeat the procedure in step 8, and you will notice that the overall file length is different.
Overwrite the original file length into the right hand box, and take careful note of the resulting figure in the percent change box. Make sure you record whether it is a plus or minus value - it could be either! This is the most important figure, because it represents the percentage variation between the two units.
Once you have obtained this value, simply apply it to all files recorded with the same recorder and this camera. Providing you can align the start of the file with a single 'clapperboard' mark, there is no need to repeat the rest. Simply change the length of the external audio file by the correct percentage value, to allow the two audio tracks to remain synchronised.
It may seem a long winded process, but it only needs to be done once, and could then save quite a lot of time, against the option of trying to align tracks manually in your NLE, in small sections.
You may of course wish to use an alternative audio editor, and the details of this procedure may then be slightly different, but the principle remains the same.

Unfortunately, I do not know the author of this material, and first saw it in another post to the Adobe forum. If the author sees this, please step up to take credit for a well-written explanation of why Audio is OOS with footage, when one has used a separate recorder, that is not hard-wired into the camera and deriving the sync signals from it. I must emphasize that I did not write this piece, and am only posting it to help others, when they use a separate recorder, not tied to the camera, say a Zoom, or similar.
I have also not used the mentioned/linked program, so cannot comment on that. However, I would make one change, if possible, and that would be to use PCM/WAV and not the recommended Linear WAV, as some Adobe programs can have issues with Linear WAV. Other than that little suggestion, I really like this piece, and for many other NLE's, the Linear WAV will probably not be an issue - just with some Adobe programs.
The Problem -
Miniature audio recorders, be they minidisc or solid state, offer a very attractive, cost effective, alternative to the traditional use of radio microphones, for the capture of remote audio sources in video recordings
These machines record the audio in a variety of different formats - MP3, WMA, WAV, ATRAC -- and in a variety of qualities - but they all suffer from the same problem. It can be difficult to synchronise the remotely recorded audio, with the camera recorded audio.
Although the time honoured tradition of an audio 'clapper board' works well enough to align the beginning of the two soundtracks, there is a tendency for the two tracks to appear to 'drift' out of sync over time - and the longer the recording, the worse the problem. In fact they do not actually 'drift', but the gradual loss of sync is a function of the camera and audio recorder sample clocks being slightly different frequencies.
The simple reason for this loss of 'sync' therefore is that the audio is being recorded at different speeds. Although the recorder will specify the sampling frequency, the accuracy is then dependent on the internal crystal oscillator of the recorder - which is, of course, a different oscillator from the one controlling the camera timing. Although these crystals may typically be accurate to within 0.005% or better, even this degree of accuracy can cause the two recorded audio tracks to be out of sync by up to 300mS after 30 minutes. Even after 5 minutes, the 2 tracks can be some 60mS different in length, in a worst case scenario.
60mS difference will cause a distinctly audible 'echo' between the two audio tracks. (Even 20mS is detectable as a separate echo).
This difference is of course totally unacceptable, and corrections need to be applied. It is important to remember that even if your audio recorder crystal is absolutely accurate, and it is the camera clock that is slightly wrong, it is still the remote audio track that will have to be corrected. The 'wrong' camera audio track is the one in sync with the video, and has to be the 'master' track.
The Solution
It is important to realise that although the sample oscillators may vary with regard to each other, they tend to be remarkably accurate over time, referenced to themselves.
This means that if you know by how much the frequency your audio recorder sample 'clock' differs from the camera 'clock', then a single correction factor will bring both tracks back into sync.
A simple procedure is outlined below, using free programs, to enable you to calculate the correction factor required for your particular recorder.
Programs required (all free):
1) AoA audio Extractor --- (not necessary if you can extract the audio track from a video recording in your NLE)
2) Audacity , a free audio editor
3) Switch , a free audio file type converter
Step 1: Set up your camera and audio recorder next to each other, and start both running
Step 2: Make a good audio 'clapperboard' point by tapping a pencil firmly onto a hard surface, as close to both camera and recorder mics as possible. This will cause a fast 'edge' to become the reference point, which will be useful later.
Step3: Let both devices run for at least 10 minutes. 20 minutes are better, but not essential.
At the end of the period, (timing not critical), make a second similar 'clapperboard' reference point. Allow a few more seconds recording, and then stop both devices.
Step 4: Download the video from the camera, and the audio from the recorder to yourcomputer.
Step 5: Open the video file in 'AoA audio Extractor', and extract the audio from the video. Convert this audio file (if necessary) to a 48KHz 16 bit LPCM (wav) file, using the 'Switch' program linked to above. This file will be your reference audio file.
Step 6: Open the WAV file saved in the previous step in 'Audacity' - a free audio editor.
It is now necessary to save only the part of the file between the two 'clapperboard' references, which hopefully stand out clearly (if you hit the pencil hard enough in steps 2 and 3!).
This must be done accurately, to within 100th of a second, or better.
Click and drag the file to highlight the beginning section, including the first 'clapperboard' waveform. Use the 'fit selection to window' tool (immediately to the right of the 'zoom' tools) to magnify. Delete as much as possible before the 'clapper' reference. Repeat the operation until you can clearly identify the first distinct waveform of the 'clapper' reference waveform. Click, hold and place the cursor directly over the first full (clipped) waveform, where it crosses the centre line. Delete every thing to the left of that point, by clicking and dragging to highlight, and then deleting with the scissors tool.
Step 7: Repeat the above procedure for the end part of the waveform, again using thestart of the second 'clapper' waveform as your reference cutting point. In this case, cut everything to the right of your selected reference point (not the left, as in the first case.)
Step 8: It is necessary to record the exact length of this new cropped waveform. This information is listed at the bottom of the window, but in a rather inappropriate format. Locate the toolbar at the top of the window, click 'Edit'-'select all' and then 'Effects'-'change tempo' . Note the length of the file in seconds in the right hand box (the left hand box is greyed out).
Record this figure. It is the reference file length
Step 9: It is necessary to convert the file recorded on the audio recorder into an identical format to the camera audio track, namely 48 KHz 16 bit PCM. If the track is not already in this format, open it in Switch, a free file transfer program, and select the output encoding as 48 KHz 16 bit, mono or stereo to fit your audio file. This program will then convert whatever format your input file is (MP3, WMA, 44.1 KHz PCM, etc) into the required 48 KHz, 16 bit format required.
Step 10: Repeat the procedures in steps 6 and 7 for this new file. Edit the 'clapper' points with as much accuracy as before, but notice that the 'clapper' waveform will appear different from the first, although hopefully with as clearly defined first ' zero crossing' point.
Step 11: Repeat the procedure in step 8, and you will notice that the overall file length is different.
Overwrite the original file length into the right hand box, and take careful note of the resulting figure in the percent change box. Make sure you record whether it is a plus or minus value - it could be either! This is the most important figure, because it represents the percentage variation between the two units.
Once you have obtained this value, simply apply it to all files recorded with the same recorder and this camera. Providing you can align the start of the file with a single 'clapperboard' mark, there is no need to repeat the rest. Simply change the length of the external audio file by the correct percentage value, to allow the two audio tracks to remain synchronised.
It may seem a long winded process, but it only needs to be done once, and could then save quite a lot of time, against the option of trying to align tracks manually in your NLE, in small sections.
You may of course wish to use an alternative audio editor, and the details of this procedure may then be slightly different, but the principle remains the same.

Issue showing number of records overdue. How to seperate out into their own count.

I have a report which shows number of action items created, number open, closed and overdue by 30,60,90 and 120 days.
The problem is if I have a record that is overdue by say 120 days, it will not only show as counted in the 120 days overdue field but the 90, 60 and 30 days overdue fields as well. I want it to be counted just once in the 120 days overdue field. So
basically I am trying to write an expression which would do the following: If it is a Near miss record and it over 30 days past due but less than 60 then count 1 other wise do not count. If it is a ndar miss and is over 60 days past due but less
than 90 then count 1 otherwise do not count.
Below is the expression for the overdue field I currently use and a snapshot of the report so to better understand what I am doing.
=iif((Fields!Incident_Type.Value="Near Miss"), Sum(Fields!Overdue_By_120_Days.Value),0)

Hi blumm1,
If I understand correctly, the issue you are occurred is that a record which is over 90 days would be counted in the 90, 60 and 30 days overdue fields, but you want it just be counted in 90 days overdue field. In this scenario, we can try to refer to the
expression below:
Overdue By 30 Days:
=iif((Fields!Incident_Type.Value="Near Miss"), Sum(Fields!Overdue_By_30_Days.Value)- Sum(Fields!Overdue_By_60_Days.Value),0)
Overdue By 60 Days:
=iif((Fields!Incident_Type.Value="Near Miss"), Sum(Fields!Overdue_By_60_Days.Value)- Sum(Fields!Overdue_By_90_Days.Value),0)
Overdue By 90 Days:
=iif((Fields!Incident_Type.Value="Near Miss"), Sum(Fields!Overdue_By_90_Days.Value)- Sum(Fields!Overdue_By_120_Days.Value),0)
If there are any misunderstanding, please elaborate the issue for further investigation.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Gender issue when creating Child Record in ESS

Dear experts,
I'm currently have a problem when creating new child for family infotype (0021). Everytime I create a new child record, the gender will always be 'Male' eventhough when I input the data, I choose the 'Female' radiobutton, but when I choose Next and display the 'Review' page, the gender will always be Male.
It make sense if it is creating a spouse record, since the spouse must be an opposite gender, but supposedly I can change the gender freely when I create the child record.
Is there something I missed out in the customization process? Or is there anything else that could solve this problem?
I found a topic that almost similar to our problem in Gender Unknown after selecting female/male in Family data But in that topic the gender will always set to 'Unknown', in our problem it will always set to 'Male'
Thank you for all the answers

Hi madav ,
create inforecord me11
vender name
mat
purchase org
plant
maintain that and enter,
go to text maintain, then click on condition hear maintain as per as the requirement,
go back
click on purchase organization data then save
u will not get error .
hope it will help u .
thanks
BIswa

Top Link Causes out of memory issue when millions of records need to update

Hello everyone,
I am using TopLink 9.0.4 in a batch process. The batch process reads from the temp table(temp table has millions of records one month worth of data which need be updated). The database being used is sqlserver 2005. Below is the snippet of code. It works for 6-7 hours and crashes after that due of out of memory:
ExpressionBuilder expressionBuilder = new ExpressionBuilder();
Statement stmt = con.createStatement();
ResultSet rs = st.executeQuery("Select * from database tablename where field= 'done'");
while(rs!=null && rs.next()){
*//where vo is the value object obtained from the rs row by row*
if (updateInfo(vo, user,expressionBuilder )){
               logger.info("updated : "+ rs.getString("col_name"));
               projCount++;
rs.close();
st.close();
private boolean updateInfo(ProjectVO vo, YNUser tcUser,expressionBuilder ) {
          boolean updated;
          updated = false;
          try {
               updated = true;
          } catch (Exception e) {
               logger.warn("update: caused exception, "
                         + e.getMessage());
          return updated;
Edited by: user8981696 on Jan 14, 2010 1:00 PM

Thanks for your reply.
Please find below the answers to you suggestions/concerns:
You seem to be using raw JDBC to select all of the records in a single result set, not sure if this may be causing a memory issue. You could try paging through the results instead.
Ans: I have modified the code to get me 1000 records each time and I am getting the ResultSet by using PrepartedStatement instead of regular Statement object.
What type of caching are you using?
Ans: No caching is being used. If you have some thoughts on caching please suggest or put some sample code. Again there is no AppServer is being used, its just a regular java process(Batch process) so I dont know how to do caching in a simple java process.
You may also wish to try the latest 9.0.4 patch release, or try the 10.1.3 version, or the latest EclipseLink 2.0 release.
Ans: Where can I find the latest patch release 9.0.4?
Any help/suggestion is really appreciated!

Number of records in DSO

Can anyone tell me how to find out the total of records that get loaded to DSO? When I clicked view data, didn't find any button to display the number of records in this DSO.

go to se11 ..give your DSO technical name...and hit F4 you should get 2 entries..
say your DSO is ZDMDTRNS then you get to see
/BIC/AZDMDTRNS00 ODS Object ZDMDTRNS : Active Records
/BIC/AZDMDTRNS40 DataStore Object ZDMDTRNS : Update

Error when deleting a record: "FRM-40202 Field must be entered"

Dear all, please I need your help in this little problem.
I am using Forms 10g , and I am having an issue when deleting a record at runtime. It is giving "FRM-40202 Field must be entered".
I have reviewed the code but still cannot guess what could be the reason.
Any idea please. Thanks
Edited by: user562674 on 02/05/2011 12:35 ص

Hi
This error is caused due to the NOT NULL constraint u have in ur db for that item...
u have 2 options to use ...
1.Either u set the Required property of that item to > no
2.Or u give it an intial value...
To get ride of this error message...
Hope this helps...
Regards,
Ammatu Allah.

Error material not maintained by purchasing when creating info record

Hi Expert,
I have an issue when creating info record, error says "Material ******* not maintained by purchasing". I've checked in MM03 purchasing view, all has been maintained and at the bottom there is message says "No plant-specific data exist". Accounting view also maintained. I've also checked in MARC table for this material and plant. It existed. I cannot see anything wrong on the material master setup but not sure why am i having this error...
Please help.
Thanks,

Hi,
Error says "Material ******* not maintained by purchasing" & you checked purchasing view has been maintained.
OK. Just cross check following optionS
Option-1: You creating info- record for material with combination of plant & vendor....check did the material have purchasing view for same plant-the info-record you are creating!
Option-2: If no purchasing view for material with same plant , just extend in t.code MM50 for E Purchasing
Option-3: Check the material for same plant, did Procurement type F (External procurement) is there
Option-4: Check Profit Center in Plantdata/ sto-2 view of material.
Regards,
Biju K

How to load a selective request from PSA to DSO using DTP?

Hi Gurus,
The PSA is having 3 requests, how to load the request number 2 from psa to DSO using DTP?
Thanks
SDP
Edited by: SDPSAP on Nov 15, 2011 7:58 PM

Let us say that requests are 1,2 and 3. 1 being the first one and 3 is the last one. Now you need to load request 2 in DSO from PSA.
- create a Delta DTP
- Tick "Only Get Delta Once"
- Tick "Get One Request Only"
- Untick "Reterive Until No More New Data"
- execute the DTP, it will load request 1 to DSO
- delete this request from DTP
- execute DTP again, it will load request 2 to DSO; this is what you need.
If DSO is write optimized, you do not need to untick "Reterive Until no More New Data"; just execute the DTP, it will create 3 requests in DSO, delete first and last and you will get only 2 in DSO.
I hope it helps.
Regards,
Gaurav

SPM Data Loads : Less number of records getting loaded in the Invoice Inbound DSO

Dear Experts,
We are working on a project, where data of different NON SAP Source Systems is being loaded into SPM, via Flat File Loads. We came across a very weird situation.
For other Master and Transaction Data objects, it worked fine, but when we loaded Invoice File, less number of records are getting loaded in the Inbound DSO. The Invoice File contained 80000 records, but the inbound DSO has 78500 records only. We are losing out on 1500 Records.
We are unable to figure out, as to which 1500 records are we missing out on. We couldn't find any logs, in the Inbound Invoice DSO. We are unable to find out if the records are erroneous, or there is any issue with something else. Is there a way to analyze the situation / Inbound invoice DSO.
If there is any issue with the Outbound DSO or Cube, We know that it is possible to check the issue with the Data Load request, but for the Inbound DSO, we are not aware, as to which the way to analyze the issue, and why Inbound DSO is taking less records.
Regards
Pankaj

Hi,
Yes, It might be happen in DSO, because the data records have the simantic keys, so in Keyfileds selection you might have less no of records.
If you have any rountines check the code(If any condetion for filtering the records).
Regards.

Issue when uploading Sales data from DSO to Cube.

Dear All,
I have an issue when I am uploading Sales data from DSO to Cube. I am using BI 7.0 and I have uploaded all sales document level data to my DSO. Then I use a transformation rule to calculate the Sales Value when I am doing DTP to cube. Cube has customer wise aggregation data.
In DSO I have NetPrice(KF) and Delivered_QTY(KF). I do a simple multiplication routine in the transformation from DSO to Cube.
RESULT = SOURCE_FIELDS-NET_PRICE * SOURCE_FIELDS-DLV_QTY .
At the moment I use Active Table(With out Archive) on the DSO to get the data since this is my first load.
Issue is that the figure (Sales Value) in the cube is incorrect. I am getting a very large values which is impossible.
Can someone please help me.
Shanka

Hi,
are you sure that cube has customer wise aggregated data..since it will always aggregate the values of the key figures for the same set of characters...
did you checked the values for the key figures as well and if even they are inflated or is the problem with this key figure only.
During the data load the records may aggregates first for the same values of characters and then multiplication will be happening....if that is the case then you may have to multiply the values before storing it in the data package and then let it aggregate....can be achived through start routine...
but first verify if other key figures are also having the same issue.
Thanks
Ajeet

WLI problem when processing a high number of records - SQLException: Data e

Hi
I'm having some trouble with a process in WLI when processing a high number of records from a table. I'm using WLI 8.1.6 and Oracle 9.2.
The exception I'm getting is:
javax.ejb.EJBException: nested exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.
I think the problem is not with the table because it's pretty simple. I'll describe the steps in the JPD below.
1) A DBControl checks to see if the table has records with a specific value in a column.
select IND_PROCESSADO from VW_EAI_INET_ESTOQUE where IND_PROCESSADO = 'N'
2) If there is one or more records, we update the column to another value (in other DBControl)
update VW_EAI_INET_ESTOQUE set IND_PROCESSADO = 'E' where IND_PROCESSADO = 'N'
3) We then start a transaction with following steps:
3.1) A DBControl queries for records in a specific condition
select
COD_DEPOSITO AS codDeposito,
COD_SKU_INTERNO AS codSkuInterno,
QTD_ESTOQUE AS qtdEstoque,
IND_ESTOQUE_VIRTUAL AS indEstoqueVirtual,
IND_PRE_VENDA AS indPreVenda,
QTD_DIAS_ENTREGA AS qtdDiasEntrega,
DAT_EXPEDICAO_PRE_VENDA AS dataExpedicaoPreVenda,
DAT_INICIO AS dataInicio,
DAT_FIM AS dataFim,
IND_PROCESSADO AS indProcessado
from VW_EAI_INET_ESTOQUE
where IND_PROCESSADO = 'E'
3.2) We transform all the records found to and XML message (Xquery)
3.3) We update again update the same column as #2 to other value.
update VW_EAI_INET_ESTOQUE set IND_PROCESSADO = 'S'   where IND_PROCESSADO = 'E'.
4) The process ends.
When the table has few records under the specified condition, the process works fine. But if we test it with 25000 records, the process fails with the exception below. Sometimes in the step 3.1 and other times in the step 3.3.
Can someone help me please?
Exception:
<A message was unable to be delivered from a WLW Message Queue.
Attempting to deliver the onAsyncFailure event>
<23/07/2007 14h33min22s BRT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction
Xid=BEA1-00424A48977240214FD8(12106298),Status=Rolled back. [Reason=javax.ejb.EJBException: nested
exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.],numRepliesOwedMe=0,numRepliesOwedOthers= 0,seconds since begin=118,seconds left=59,XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=rolledback,assigned=cgServer),xar=JMS_cgJMSStore,re-Registered =
false),XAServ erResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=
(state=rolledback,assigned=cgServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@d38a58,re-Registered =false),XAServerResourceInfo[CPCasaeVideoWISDesenv]=
(ServerResourceInfo[CPCasaeVideoWISDesenv]=(state=rolledback,assigned=cgServer),xar=CPCasaeVideoWISDesenv,re-Registered = false),SCInfo[integrationCV+cgServer]=(state=rolledback),
properties=({weblogic.jdbc=t3://10.15.81.48:7001, START_AND_END_THREAD_EQUAL=false}),
local properties=({weblogic.jdbc.jta.CPCasaeVideoWISDesenv=weblogic.jdbc.wrapper.TxInfo@9c7831, modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@9c2dc7]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=
(CoordinatorURL=cgServer+10.15.81.48:7001+integrationCV+t3+,
XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_cgJMSStore, CPCasaeVideoWISDesenv},NonXAResources={})],CoordinatorURL=cgServer+10.15.81.48:7001+integrationCV+t3+): javax.ejb.EJBException: nested exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.
        at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1844)
        at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:227)
        at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:197)
        at com.bea.wlwgen.PersistentContainer_7e2d44_Impl.ejbStore(PersistentContainer_7e2d44_Impl.java:149)
        at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(ExclusiveEntityManager.java:593)
        at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:744)
        at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1069)
        at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:118)
        at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1202)
        at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2007)
        at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:257)
        at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
        at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430)
        at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
        at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
        at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
        at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: javax.ejb.EJBException: nested exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.
        at com.bea.wlw.runtime.core.bean.BMPContainerBean.doUpdate(BMPContainerBean.java:2021)
        at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1828)
        ... 18 more

Hi Lucas,
Following is the information regarding the issue you are getting and might help you to resolve the issue.
ADAPT00519195- Too many selected values (LOV0001) - Select Query Result operand
For XIR2 Fixed Details-Rejected as this is by design
I have found that this is a limitation by design and when the values exceed 18000 we get this error in BO.
There is no fix for this issue, as itu2019s by design. The product always behaved in this manner.
Also an ER (ADAPT00754295) for this issue has already been raised.
Unfortunately, we cannot confirm if and when this Enhancement Request will be taken on by the developers.
A dedicated team reviews all ERs on a regular basis for technical and commercial feasibility and whether or not the functionality is consistent with our product direction. Unfortunately we cannot presently advise on a timeframe for the inclusion of any ER to our product suite.
The product group will then review the request and determine whether or not the functionality/feature will be included in a future release.
Currently I can only suggest that you check the release notes in the ReadMe documents of future service packs, as it will be listed there once the ER has been included
The only workaround which I can suggest for now is:
Workaround 1:
Test the issue by keep the value of MAX_Inlist_values parameter to 256 on designer level.
Workaround 2:
The best solution is to combine 'n' queries via a UNION. You should first highlight the first 99 or so entries from the LOV list box and then combine this query with a second one that selects the remaining LOV choices.
Using UNION between queries; which is the only possible workaround
Please do let me know if you have any queries related to the same.
Regards,
Sarbhjeet Kaur

FORMS 9i issue: Is there a [b]SYSTEM build-in to get the number of records?

In master-detail data blocks, a query generally return multiple records from the detail table. I'd like to know how to get the number of the records:
1. I use NEXT_RECORD to navigate these records
2. use SYSTEM.CURSOR_RECORD to know the current record
3. use SYSTEM.LAST_RECORD to know when the last record is reached.
What is missing is the total number of the records.
Thank you in advance for helping

My tip would also be the summary item

Strange issue when typing a number in Lion

Hi,
I have a very rare issue when I type a number now and since I updated my system to Lion, no matter which program am I using, Safari, textedit, mail, etc. Every time I type a number (just one), it suddently erase itself, doesn't happen when I type more than one, it's very annoying and this didn't happen when I had Snow Leopard.
Any ideas?

…and so on = 58376163294144?
Could you please answer the questions, this is like drawing hens teeth.
I have entered the numbers but since I don't know how your sequence is input I can't do the preceeding numbers to the one that changes.
…which doesn't when I do it in Pages '09 v4.05:
Peter

Issue when number of records in a DSO exceeds DTP package size

Similar Messages

Maybe you are looking for