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

Question

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

Answer 1

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