Processing of large number of records using JDBC Sender Channel

Hi experts,
We have a JDBC-File scenario where in the tables contain about 500K records on an average.
I used multimapping to generate a flat file for every 10K. The problem is ..when I start the JDBC Sender CC, the memory goes up and the J2EE engine restarts. In the Sender CC, I gave the Disconnect from the database option too. The query is SELECT * from TABLE and the Update statement is <TEST>. Please help me out how to solve this.
Regards.

Hi
Use the below query,
// Oracle
SELECT Statement : select colname from tblname where rownum<=1000 ;
// MSSQL
select top 1000 colname from tblname
Regards
Ramg

Similar Messages

How do I process a large number of rows using ADO?

I need to iterate through a table with about 12 million records and process each row individually. The project I'm doing cannot be resolved with a simple UPDATE statement.
My concern is that when I perform the initial query that so much data will be returned that I'll simply crash.
Ideally I would get to a row, perform my operation, then go to the next row ... and so on and so on.
I am using ADO / C++

I suggest you simply use the default fast-forward read-only (firehose) cursor to read the data. This will stream data from SQL Server to your application and client memory usage will be limited to the internal API buffers without resorting to paging.
I ran a quick test of this technique using ADO classic and the C# code below and it ran in under 3 minutes (35 seconds without the file processing) on my Surface Pro against a remote SQL Server. I would expect C++ to be a significantly faster
since it won't incur the COM interop penalty. The same test with SqlClient ran in under 10 seconds.
static void test()
var sw = Stopwatch.StartNew();
Console.WriteLine(DateTime.Now.ToString("HH:mm:ss.fff"));
object recordCount;
var adoConnection = new ADODB.Connection();
adoConnection.Open(@"Provider=SQLNCLI11.1;Server=serverName;Database=MarketData;Integrated Security=SSPI");
var outfile = new StreamWriter(@"C:\temp\MarketData.txt");
var adoRs = adoConnection.Execute("SELECT TOP(1200000) Symbol, TradeTimestamp, HighPrice, LowPrice, OpenPrice, ClosePrice, Volume FROM dbo.OneMinuteQuote;", out recordCount);
while(!adoRs.EOF)
outfile.WriteLine("{0},{1},{2},{3},{4},{5},",
(string)adoRs.Fields[0].Value.ToString(),
((DateTime)adoRs.Fields[1].Value).ToString(),
((Decimal)adoRs.Fields[2].Value).ToString(),
((Decimal)adoRs.Fields[3].Value).ToString(),
((Decimal)adoRs.Fields[4].Value).ToString(),
((Decimal)adoRs.Fields[5].Value).ToString());
adoRs.MoveNext();
adoRs.Close();
adoConnection.Close();
outfile.Close();
sw.Stop();
Console.WriteLine(DateTime.Now.ToString("HH:mm:ss.fff"));
Console.WriteLine(DateTime.Now.ToString(sw.Elapsed.ToString()));
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Not receiving email when sending large number of records using a FM?

Hi..
I am using the function module " SO_DOCUMENT_SEND_API1 " to send email....
When a single record is there.. or around 5-6 records are there... email is coming successfully...
But when there are more records..say around 100, the email is not coming... I checked SOST transaction and the status there is in red..and the error message is " Internal error: SO_OBJECT_MIME_GET Exception: 2 ".........
What could be the reason behind this problem....... ??
I have another problem... my output has over 60 fields, but in the email which i am receiving has only around 10 fields... how to solve this problem...??
Plz help...

Well... right now i am tryin to get only the first 2 fields.. but even in this case... i am not getting the email if around 15 records are there......
I am using the code which is given below which i found in SDN only......In this code.. data is getting selected from EKPO... i tried changing the number of rows getting selected.. and in this case, the attachement is coming as desired... but when i use the same code for my prog.. i am not getting the mail.. even if there are only 10 records or so...
*& Report ZT062108   ALV Header                                    *
REPORT zt062108.
TABLES: ekko.
PARAMETERS: p_email   TYPE somlreci1-receiver
                                  DEFAULT '<give email here>'.
TYPES: BEGIN OF t_ekpo,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
aedat TYPE ekpo-aedat,
matnr TYPE ekpo-matnr,
END OF t_ekpo.
DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,
      wa_ekpo TYPE t_ekpo.
TYPES: BEGIN OF t_charekpo,
ebeln(10) TYPE c,
ebelp(5) TYPE c,
aedat(8) TYPE c,
matnr(18) TYPE c,
END OF t_charekpo.
DATA: wa_charekpo TYPE t_charekpo.
DATA:   it_message TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
                WITH HEADER LINE.
DATA:   it_attach TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0
                WITH HEADER LINE.
DATA:   t_packing_list LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,
        t_contents LIKE solisti1 OCCURS 0 WITH HEADER LINE,
        t_receivers LIKE somlreci1 OCCURS 0 WITH HEADER LINE,
        t_attachment LIKE solisti1 OCCURS 0 WITH HEADER LINE,
        t_object_header LIKE solisti1 OCCURS 0 WITH HEADER LINE,
        w_cnt TYPE i,
        w_sent_all(1) TYPE c,
        w_doc_data LIKE sodocchgi1,
        gd_error    TYPE sy-subrc,
        gd_reciever TYPE sy-subrc.
*START_OF_SELECTION
START-OF-SELECTION.
*   Retrieve sample data from table ekpo
PERFORM data_retrieval.
*   Populate table with detaisl to be entered into .xls file
PERFORM build_xls_data_table.
*END-OF-SELECTION
END-OF-SELECTION.
* Populate message body text
perform populate_email_message_body.
* Send file by email as .xls speadsheet
PERFORM send_file_as_email_attachment
                               tables it_message
                                      it_attach
                                using p_email
                                      'Example .xls documnet attachment'
                                      'TXT'
                                      'filename'
                             changing gd_error
                                      gd_reciever.
*   Instructs mail send program for SAPCONNECT to send email(rsconn01)
PERFORM initiate_mail_execute_program.
*&      Form DATA_RETRIEVAL
*       Retrieve data form EKPO table and populate itab it_ekko
FORM data_retrieval.
SELECT ebeln ebelp aedat matnr
   UP TO 1000 ROWS
    FROM ekpo
    INTO TABLE it_ekpo.
ENDFORM.                    " DATA_RETRIEVAL
*&      Form BUILD_XLS_DATA_TABLE
*       Build data table for .xls document
FORM build_xls_data_table.
* CONSTANTS: con_cret TYPE x VALUE '0D'. "OK for non Unicode
*             con_tab TYPE x VALUE '09'.   "OK for non Unicode
*If you have Unicode check active in program attributes thnen you will
*need to declare constants as follows
*class cl_abap_char_utilities definition load.
constants:
    con_tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB,
    con_cret type c value cl_abap_char_utilities=>CR_LF.
CONCATENATE 'EBELN' 'EBELP' 'AEDAT' 'MATNR'
         INTO it_attach SEPARATED BY con_tab.
CONCATENATE con_cret it_attach INTO it_attach.
APPEND it_attach.
LOOP AT it_ekpo INTO wa_charekpo.
    CONCATENATE wa_charekpo-ebeln wa_charekpo-ebelp
                wa_charekpo-aedat wa_charekpo-matnr
           INTO it_attach SEPARATED BY con_tab.
    CONCATENATE con_cret it_attach INTO it_attach.
    APPEND it_attach.
ENDLOOP.
ENDFORM.                    " BUILD_XLS_DATA_TABLE
*&      Form SEND_FILE_AS_EMAIL_ATTACHMENT
*       Send email
FORM send_file_as_email_attachment tables pit_message
                                          pit_attach
                                    using p_email
                                          p_mtitle
                                          p_format
                                          p_filename
                                          p_attdescription
                                          p_sender_address
                                          p_sender_addres_type
                                 changing p_error
                                          p_reciever.
DATA: ld_error    TYPE sy-subrc,
        ld_reciever TYPE sy-subrc,
        ld_mtitle LIKE sodocchgi1-obj_descr,
        ld_email LIKE somlreci1-receiver,
        ld_format TYPE so_obj_tp ,
        ld_attdescription TYPE so_obj_nam ,
        ld_attfilename TYPE so_obj_des ,
        ld_sender_address LIKE soextreci1-receiver,
        ld_sender_address_type LIKE soextreci1-adr_typ,
        ld_receiver LIKE sy-subrc.
ld_email   = p_email.
ld_mtitle = p_mtitle.
ld_format              = p_format.
ld_attdescription      = p_attdescription.
ld_attfilename         = p_filename.
ld_sender_address      = p_sender_address.
ld_sender_address_type = p_sender_addres_type.
* Fill the document data.
w_doc_data-doc_size = 1.
* Populate the subject/generic message attributes
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle .
w_doc_data-sensitivty = 'F'.
* Fill the document data and get size of attachment
CLEAR w_doc_data.
READ TABLE it_attach INDEX w_cnt.
w_doc_data-doc_size =
     ( w_cnt - 1 ) * 255 + STRLEN( it_attach ).
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name   = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle.
w_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
t_attachment[] = pit_attach[].
* Describe the body of the message
CLEAR t_packing_list.
REFRESH t_packing_list.
t_packing_list-transf_bin = space.
t_packing_list-head_start = 1.
t_packing_list-head_num = 0.
t_packing_list-body_start = 1.
DESCRIBE TABLE it_message LINES t_packing_list-body_num.
t_packing_list-doc_type = 'RAW'.
APPEND t_packing_list.
* Create attachment notification
t_packing_list-transf_bin = 'X'.
t_packing_list-head_start = 1.
t_packing_list-head_num   = 1.
t_packing_list-body_start = 1.
DESCRIBE TABLE t_attachment LINES t_packing_list-body_num.
t_packing_list-doc_type   = ld_format.
t_packing_list-obj_descr = ld_attdescription.
t_packing_list-obj_name   = ld_attfilename.
t_packing_list-doc_size   = t_packing_list-body_num * 255.
APPEND t_packing_list.
* Add the recipients email address
CLEAR t_receivers.
REFRESH t_receivers.
t_receivers-receiver = ld_email.
t_receivers-rec_type = 'U'.
t_receivers-com_type = 'INT'.
t_receivers-notif_del = 'X'.
t_receivers-notif_ndel = 'X'.
APPEND t_receivers.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
       EXPORTING
            document_data              = w_doc_data
            put_in_outbox              = 'X'
            sender_address             = ld_sender_address
            sender_address_type        = ld_sender_address_type
            commit_work                = 'X'
       IMPORTING
            sent_to_all                = w_sent_all
       TABLES
            packing_list               = t_packing_list
            contents_bin               = t_attachment
            contents_txt               = it_message
            receivers                  = t_receivers
       EXCEPTIONS
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8.
* Populate zerror return code
ld_error = sy-subrc.
* Populate zreceiver return code
LOOP AT t_receivers.
    ld_receiver = t_receivers-retrn_code.
ENDLOOP.
ENDFORM.
*&      Form INITIATE_MAIL_EXECUTE_PROGRAM
*       Instructs mail send program for SAPCONNECT to send email.
FORM initiate_mail_execute_program.
WAIT UP TO 2 SECONDS.
SUBMIT rsconn01 WITH mode = 'INT'
                WITH output = 'X'
                AND RETURN.
ENDFORM.                    " INITIATE_MAIL_EXECUTE_PROGRAM
*&      Form POPULATE_EMAIL_MESSAGE_BODY
*        Populate message body text
form populate_email_message_body.
REFRESH it_message.
it_message = 'Please find attached a list test ekpo records'.
APPEND it_message.
endform.                    " POPULATE_EMAIL_MESSAGE_BODY

Best way to delete large number of records but not interfere with tlog backups on a schedule

Ive inherited a system with multiple databases and there are db and tlog backups that run on schedules. There is a list of tables that need a lot of records purged from them. What would be a good approach to use for deleting the old records?
Ive been digging through old posts, reading best practices etc, but still not sure the best way to attack it.
Approach #1
A one-time delete that did everything. Delete all the old records, in batches of say 50,000 at a time.
After each run through all the tables for that DB, execute a tlog backup.
Approach #2
Create a job that does a similar process as above, except dont loop. Only do the batch once. Have the job scheduled to start say on the half hour, assuming the tlog backups run every hour.
Note:
Some of these (well, most) are going to have relations on them.

Hi shiftbit,
According to your description, in my opinion, the type of this question is changed to discussion. It will be better and
more experts will focus on this issue and assist you. When delete large number of records from tables, you can use bulk deletions that it would not make the transaction log growing and runing out of disk space. You can
take the table offline for maintenance, a complete reorganization is always best because it does the delete and places the table back into a pristine state.
For more information about deleting a large number of records without affecting the transaction log.
http://www.virtualobjectives.com.au/sqlserver/deleting_records_from_a_large_table.htm
Hope it can help.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

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

Problem fetch large number of records

Hi
I want to fetch large number of record from database.and I use secondary index database for improve performance for example my database has 100000 records and query fetch 10000 number of records from this database .I use secondary database as index and move to secondary database until fetch all of the information that match for my condition.but when I move to this loop performance terrible.
I know when I use DB_MULTIPLE fetch all of the information and performance improves but
I read that I can not use this flag when I use secondary database for index.
please help me and say me the flag or implement that fetch all of the information all to gether and I can manage this data to my language
thanks alot
regards
saeed

Hi Saeed,
Could you post here your source code, that is compiled and ready to be executed, so we can take a look at the loop section ?
You won't be able to do bulk fetch, that is retrieval with DB_MULTIPLE given the fact that the records in the primary are unordered by master (you don't have 40K consecutive records with master='master1'). So the only way to do things in this situation would be to position with a cursor in the secondary, on the first record with the secondary key 'master1' retrieve all the duplicate data (primary keys in the primary db) one by one, and do the corresponding gets in the primary database based on the retrieved keys.
Though, there may be another option that should be taken into consideration, if you are willing to handle more work in your source code, that is, having a database that acts as a secondary, in which you'll update the records manually, with regard to the modifications performed in the primary db, without ever associating it with the primary database. This "secondary" would have <master> as key, and <std_id>, <name> (and other fields if you want to) as data. Note that for every modification that your perform on the std_info database you'll have to perform the corresponding modification on this database as well. You'll then be able to do the DBC->c_get() calls on this database with the DB_MULTIPLE flag specified.
I have other question.is there any way that fetch information with number of record?
for example fetch information that located third record of my database.I guess you're refering to logical record numbers, like the relational database's ROW_ID. Since your databases are organized as BTrees (without the DB_RECNUM flag specified) this is not possible directly.You could perform this if use a cursor and iterate through the records, and stop on the record whose number is the one you want (using an incrementing counter to keep track of the position). If your database could have operated with logical record numbers (BTree with DB_RECNUM, Queue or Recno) this would have been possible directly:
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/am_conf/logrec.html
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/am_conf/renumber.html
Regards,
Andrei

Lookups with large number of records do not return the page

Hi,
I am developing an application using Oracle JHeadstart 10.1.3 Preview Version 10.1.3.0.78
In my application I created a lookup under domains and used that lookup for an attribute (Display Type for this attribute is: dropDownList) in a group to get the translation fro this attribute. The group has around 14,800 records and the lookup has around 7,400 records.
When I try to open this group (Tab), the progress shows that it is progressing but it does not open even after a long time.
If I change the Display Type for the attribute from dropDownList to textInput then it works fine.
I have other lookups with lower number of records. Those lookups work fine with dropDownList Display Type.
Only I have this kind of problem when I have a lookup with large number of records.
Is there any limitation of record number for lookups under Domains?
How I can solve this?
I need to translate the attribute (get the description from another table using the code).
Your help would be appreciated.
Thanks
Syed

We have also faced similar issue, but us, it was happening when we were using the dropDownList in a table, while the same dropDownList was working in table format. In our case the JVM is just used to crash and after google'ing it here in forums, found that it might be related to some JVM issue on Windows XP machines without Service Pack 2.
Anyway... the workaround that we taken to get around the issue is to use LOV instead of a dropDownList in your jHeadStart.
Hope this helps...
- rutwik

Empty CLOB field value from Oracle database using JDBC Sender

Hi All,
I am selecting a CLOB field from Oracle database table using JDBC Sender adapter and getting error "NullPointerException"
Seen SAP note 1283089 but its not applicable for my support pack PI 7.0 SP 12 and client dont want to upgrdate SP 17 right now.
I tried rpad(1,0)Column_Name funciton in JDBC select query but it selcting blank value for every record even those having some value for this CLOB field so not useful
Could anybody suggest possible way? client dont want to change anything at database side.
Thanks,
Dharamveer

What is the Oracle driver version installed? You might need to install 10.x driver if not already using it.

JDBC Sender channel not processing the messages

Hello,
From yesterday onwards JDBC Sender channel not processing the messages. In CC monitoring it is showing in Green Led and status is functioning. Cahnnel is polling for messages to DB server as per polling interval. But it is not processing the msg's. Under Processing detials for cluster node it is showing only "Processing Started" for each polling interval.
I have done the check in DB server by executing the query in the channel, whether there are any records are exisitng or not. There are 1000+ records.
Previously the parameter "Disconnect from DB after processing each message" was not set. I have set the parameter and activated in Productiion. Still the messages are not processing by channel
What was the problem? How to rectify with this.
Cheers
Veera

Check in the Visual Admin >Cluster> "LOCKING ADAPTER"
we get a option of Display Locks .Check for an entry with
NAME : $XIDBAD.JDBC2XI
reset the locks and restart the CC ,now it works fine.
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)

How to update two tables in a single call using JDBC Sender adapter

Hello All,
The scenario is, database entries have to be selected from two tables and at the same time those tables have to be udpated with the flag.
We are using JDBC sender adapter and in Select Query, we are fetching the data by joinin the two tables.
Update Statemtent: We can only update one table using this statement.
Is it possible to update two tables using the Update Statement without using Stored Procedures.
Let me know.
Regards,
Sreenivas.

Hi Sreenivas,
> Is it possible to update two tables using the Update Statement without using Stored Procedures.
Yes its possible through join statement
Check this links
Update in JDBC Sender adapter for more than one table
data from 2 tables for jdbc sender adapter
Regards
Ramesh

Storedprocedure trigger using JDBC sender adapter.

Hi All,
How can i execute the storedprocedure using JDBC sender adapter. I need to trigger the storedprocedure once in every hour. so i would like to use the JDBC sender adapter. My question is what is the SQL i need use in the SQLstatement parameter..?? I don't want to send parameters and not expecting any return values. It should just trigger the procedure.
Thanks in adv.
Regards,

Hi Murali,
it is possible to execute a stored porcedure using a sender JDBC adapter.
Just Specify an SQL EXECUTE statement to execute a stored procedure, which contains exactly one SELECT statement.
This will have to be done for your SELECT statement in JDBC adapter. ALso, make the UPDATE as either TEST, if you dont want any updations or give an UPDATE statement for the UPDATE query.
Set the polling interval of your JDBC adapter to 1 hour and it will work like u want.
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
Regards,
Bhavesh

Jdbc sender channel memory size issue

Hi Experts,
We are facing the below error in connect to jdbc sender channel from XI . Could anyone of you suggest me the right action to be taken in this regard.
Database-level error reported by JDBC driver while executing statement 'select * from*********where posted = '0''. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: The system is out of memory. Use server side cursors for large result sets:Java heap space. Result set size:614,143,127. JVM total memory size:1,031,798,784.'. For details, contact your database server vendor.
Appreciate your quick help.
Thanks & Regards,
Ranganath.

Regulate the number of records returned by Select statement for permanent fix.
Few more things....
a)If you want to select only some fields, then dont use Select * from table. Rather specify select a,b,c from tablename
b) specify some flag in the table so that read some records each time and in the update statement update the flag for those records already read. So that you will not reread the same records in the next message.
Hope you understand.
c) Increasing java heap size is temporary fix.

JDBC sender channel running but not picking up the data from sp

Hi,
One of the jdbc sender channels in production is running at its schedule time but it is not picking up the data from the sql side, we have checked with the sp side and they are saying that sp is running fine. No changes have been done in its configuration. Last message coming in RWB is Retry interval started but that is of 1 day and its already been 3 days. I tried by starting and stopping the channel but of no use. The channel was re activated but that also didn't help.
Please help, what can be the reason for the same.
thanks.

Hi,
The JDBCadapter ( The respective channel) is definitely locked in PI . Ideally for each polling interval a lock is being created and once the processing is over , the lock should be released/deleted automatically to allow further polling interval. If the lock is not released by the system automatically,further polling will not happen as expected. ( This may affect all sender JDBC adapters as well. I would recommend to do a check in all sender JDBC communication channels)
You can see/delete the locks in Visual admin.
Go to Server>Services->Locking adapter and click refresh
The entries for JDBC adapter ( with name $XIDBAD.JDBC2XI) should be deleted by selecting those particilar entries and click delete selected locks.
If you have more than one node, then same should be done in all server nodes.
The temprory solution would be creating/copy the existing channel in ID with same properties and assign it into particular sender agreement.
But, the lock may be created again which potentailly stops all your database interfaces. Hence i would suggest to use Disconnect From Database After processing of Each messages in Advanced tab in the sender JDBC adapter.
Hope this solves your issue.
PS: The same bahaviour would expected for all file adapter as well

JDBC Sender Channel polling before polling interval is complete

Hi all,
On our Production Server, we have found that a few JDBC Sender Channels are polling multiple times within one polling interval.
Eg: Suppose for one channel, the polling interval is 7200 secs. It polls once and the polling interval starts. But it polls again 1 or 2 times more maybe just 5 secs later before its next scheduled poll in 7200 secs.
Unfortunately, our scenarios are such that when there are multiple polls within a short span of time, there are data anomolies, causing inconsistancies on Receiver side DB. Hence this is a serious uissue.
Please Help. FYI, all the affected channels run on the same schedule. I am not sure if that can be causing this abnormality.

H Varun
I have not come across this behavior earlier. But if you are polling same data base using multiple channel at same time data inconsistency can be there. We always prefer to poll the same data base tables with different timings. Setting up poll timings always consider peak loads. Try to change the polls and see if the same behavior exists.
For performance and JDBC issues
Check https://service.sap.com/sap/support/notes/831162
Specially Q 14
Thanks
Gaurav

JDBC Sender Channel problem. Pls help

Hi,
In JDBC Sender Channel in Connectiion String I am giving value
jdbc:oracle:thin:@cscappnoi022.asiapac.globalcsc.net:1527:IS1
where cscappnoi022.asiapac.globalcsc.net---is where Oracle server is installed
1527 --- is my Port
IS1 is my system SID --- Pls let me what value should come here and how to find.
I am getting error
"Error during database connection to the database URL 'jdbc:oracle:thin:@cscappnoi022.asiapac.globalcsc.net:1527:IS1' using the JDBC driver 'oracle.jdbc.driver.OracleDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@cscappnoi022.asiapac.globalcsc.net:1527:IS1': SQLException: Io exception: The Network Adapter could not establish the connection'"
Regards

hi,
Your connection should be :
jdbc:oracle:thin:hutting/[email protected]:1521:pnt
jdbc driver should be:
oracle.jdbc.driver.OracleDriver
Regards
joel.
I only hope that your other jdbc scenarios are working fine , this is just to rule out the possibility of driver related errors.

Processing of large number of records using JDBC Sender Channel

Similar Messages

Maybe you are looking for