BI publisher report is very slow

I have OBIEE 11g installed Running BI publisher report is very slow. After doing a research seems like we have increase the JAVA heap size.
Can anyone help me how to increase this value. I do not see OC4j.cmd file in my BI install folder.
Thanks in advance

Did you try to change the setDomainEnv.cmd file in $MW_HOME/user_projects/domains/<Domain>/bin as follows:
set XMS_JROCKIT_64BIT=1024 --> to the new initial heap size
set XMX_JROCKIT_64BIT=2048 --> to the new maximum heap size
If this is helpful, please mark as correct or helpful

Similar Messages

Output report XML very slow

Hi,
I designed the report output includes 40 columns and 100000 rows. However, the request and opens slow in XML format on the client very slow.
Please ask you one optimal solution to the problem above?
(Version R12)
Thank alot!
Edited by: user12193364 on 14:03 24-04-2013

Please post the details of the application release, database version and OS.
Hi,
I designed the report output includes 40 columns and 100000 rows. However, the request and opens slow in XML format on the client very slow.
Please ask you one optimal solution to the problem above?Are you running the report from the application?
Is the issue with processing the request or just with opening the output file?
What is the size of the concurrent request output file?
R12: Troubleshooting Known XML Publisher and E-Business Suite (EBS) Integration Issues [ID 1410160.1]
EBS - Technology Area - Webcast Recording 'BI Publisher / XML Publisher Overview & Best Practices - Webinar' [video] [ID 1513592.1]
Poor Performance /High Buffer Gets In FND_CONC_TEMPLATES [ID 1085293.1]
Performance Issue - PDF Generated With BI Publisher [ID 956902.1]
Overview of Available Patches for Oracle XML Publisher embedded in the Oracle E-Business Suite [ID 1138602.1]
Tuning Output Post Processor (OPP) to Improve Performance [ID 1399454.1]
Thanks,
Hussein

Report running very slow.. taking too much time

Dear Oracle Report experts,
I have developed report in oracle reports bulider 10g. while running it from report builder through main menu *** data is coming very SLOW *** within 55 Minuts.
But, If same query is executing from SQL/PLSQL deverloper it is very fast within 45 second.
Please suggest any configuration or setting ; is having Idea.
Thanks
Muhammad Salim
Query is as below: generating result in 48 second.
select cns.consultant,
sum(cns.nof_pat) noof_pat,
sum(cns.opd_amnt) opd_amnt,
sum(cns.discount_amnt) discount_amnt,
sum(cns.net_amnt) net_amnt,
sum(cns.dr_share) dr_share,
sum(cns.hosp_share) hosp_share,
sum(cns.net_dis) net_dis
from
select rec.consultant,
count(distinct rec.consultant) nof_pat,
-- rec.receipt_date, bysalim
pay_mode,
rec.patient_mrno,rec.patient,
service_name,rcpt_no,
company,rec.docno,
sum(distinct return_amnt) return_amnt,
sum(distinct rec.opd_amnt) opd_amnt,
sum(distinct dis.discount_amnt) discount_amnt,
(sum(distinct nvl(rec.opd_amnt,0))-sum(distinct nvl(dis.discount_amnt,0))/count(rec.consultant)) net_amnt,
round((((sum(distinct nvl(rec.opd_amnt,0))-sum(distinct nvl(dis.discount_amnt,0))/count(rec.consultant) ) *
max(dr_per))/100),0) dr_share,
round((((sum(distinct nvl(rec.opd_amnt,0))-sum(distinct nvl(dis.discount_amnt,0))/count(rec.consultant) ) *
max(100-dr_per))/100),0) hosp_share,
count(distinct rec.consultant) net_dis
from
select -- bokm_doc_dt receipt_date, bysalim
bil_recept_no_a rcpt_no,
fnc_org_sname(bokm_panel_comp_id) company,
0 return_amnt,
pr_mrno patient_mrno,pr_fname patient,
bokm_doc_no docno,
gcd_desc(bil_pay_mode_a) pay_mode,
fnc_service_name(rslt_tst_code) service_name,
dr_name consultant,
pt_tst_rate opd_amnt,
cons_share cons_share,
(select max((nvl(rt_dr_share,0)*(100))/nvl(rt_amount,0))
from hms_adm_dr_rt rt
where dr.dr_id = rt.rt_dr_id
and book.rslt_tst_code = rt.rt_scs_id) dr_per,
dr_on_rent dr_rent,dr_share
from hms_pat_pers pat,hms_lab_pat_mst pmst,hms_opd_book book,
hms_pat_amnt amt,hms_adm_dr dr
where pat.pr_mrno = pmst.bokm_mrno
and pmst.bokm_mrno = book.rslt_mrno
and pmst.bokm_doc_no = book.pt_pat_doc_no
and pmst.bokm_mrno = amt.bil_mrnum_a
and pmst.bokm_doc_no = amt.bil_docno_a
and pmst.bokm_ref_conusltant_id = dr.dr_id
and amt.bil_rcp_type_a = '075002'
and pmst.bokm_pat_type in('PVT_OPD','CP_OPD')
and amt.bil_void_a = 'N'
and (pmst.bokm_user_dept_code != '039')
and BOOK.CREATED_ON between '01-OCT-2011' and '17-OCT-2012'
/* and (pat.pr_curr_cont_id = :P_CONT_ID or :P_CONT_ID = '000')
and (pat.pr_curr_prvnc_id = :P_PRVNC_ID or :P_PRVNC_ID = '00')
and (pat.pr_curr_city_id = :P_CITY_ID or :P_CITY_ID = '000')
and (pat.pr_curr_area = :P_AREA_ID or :P_AREA_ID = '000')
and (pat.pr_gender = :P_GENDER or :P_GENDER = 'A')
and (pat.pr_marital_status = :P_MARITAL_STAT or :P_MARITAL_STAT = 'ALL')
and (to_char(pmst.bokm_panel_comp_id) = :P_PANEL_COMP or :P_PANEL_COMP = 'ALL')
and (pmst.bokm_ref_conusltant_id = :P_CONS or :P_CONS = 'ALL')
and (decode(pmst.bokm_panel_comp_id,'1','PVT_IPD','CP_IPD') = :P_PAT_TYPE or :P_PAT_TYPE = 'ALL')
&LPARA_RCPT_DT */
) rec,
select -- bokm_doc_dt receipt_date, bysalim
pr_mrno patient_mrno,
bokm_doc_no docno,
nvl(bil_disc_amont_a,0) discount_amnt
from hms_pat_pers pat,hms_lab_pat_mst pmst,hms_opd_book book,
hms_pat_amnt amt
where pat.pr_mrno = pmst.bokm_mrno
and pmst.bokm_mrno = book.rslt_mrno
and pmst.bokm_doc_no = book.pt_pat_doc_no
and pmst.bokm_mrno = amt.bil_mrnum_a
and pmst.bokm_doc_no = amt.bil_docno_a
and amt.bil_rcp_type_a = '075001'
and pmst.bokm_pat_type in('PVT_OPD','CP_OPD')
and amt.bil_void_a = 'N'
and (pmst.bokm_user_dept_code != '039')
and BOOK.CREATED_ON between '01-OCT-2011' and '17-OCT-2012'
/* and (pat.pr_curr_cont_id = :P_CONT_ID or :P_CONT_ID = '000')
and (pat.pr_curr_prvnc_id = :P_PRVNC_ID or :P_PRVNC_ID = '00')
and (pat.pr_curr_city_id = :P_CITY_ID or :P_CITY_ID = '000')
and (pat.pr_curr_area = :P_AREA_ID or :P_AREA_ID = '000')
and (pat.pr_gender = :P_GENDER or :P_GENDER = 'A')
and (pat.pr_marital_status = :P_MARITAL_STAT or :P_MARITAL_STAT = 'ALL')
and (to_char(pmst.bokm_panel_comp_id) = :P_PANEL_COMP or :P_PANEL_COMP = 'ALL')
and (pmst.bokm_ref_conusltant_id = :P_CONS or :P_CONS = 'ALL')
and (decode(pmst.bokm_panel_comp_id,'1','PVT_IPD','CP_IPD') = :P_PAT_TYPE or :P_PAT_TYPE = 'ALL')
and BOOK.CREATED_ON between :P_RCPT_DTFR and :P_RCPT_DTTO
-- and BOOK.CREATED_ON between :P_RCPT_DTFR and :P_RCPT_DTTO
&LPARA_RCPT_DT */
) dis
where rec.patient_mrno = dis.patient_mrno (+)
and rec.docno = dis.docno (+)
--and patient = 'SHAHMEER'
group by rec.consultant, --rec.receipt_date, bysalim
rec.patient_mrno,rec.patient,
pay_mode,service_name,rec.docno,
rcpt_no,company
order by rcpt_no,rec.consultant
) cns
group by cns.consultant
order by 1
Edited by: user6431550 on Nov 15, 2012 3:10 AM

Dear Oracle Report experts,
I have developed report in oracle reports bulider 10g. while running it from report builder through main menu *** data is coming very SLOW *** within 55 Minuts.
But, If same query is executing from SQL/PLSQL deverloper it is very fast within 45 second.
Please suggest any configuration or setting ; is having Idea.
Thanks
Muhammad Salim
Query is as below: generating result in 48 second.
select cns.consultant,
sum(cns.nof_pat) noof_pat,
sum(cns.opd_amnt) opd_amnt,
sum(cns.discount_amnt) discount_amnt,
sum(cns.net_amnt) net_amnt,
sum(cns.dr_share) dr_share,
sum(cns.hosp_share) hosp_share,
sum(cns.net_dis) net_dis
from
select rec.consultant,
count(distinct rec.consultant) nof_pat,
-- rec.receipt_date, bysalim
pay_mode,
rec.patient_mrno,rec.patient,
service_name,rcpt_no,
company,rec.docno,
sum(distinct return_amnt) return_amnt,
sum(distinct rec.opd_amnt) opd_amnt,
sum(distinct dis.discount_amnt) discount_amnt,
(sum(distinct nvl(rec.opd_amnt,0))-sum(distinct nvl(dis.discount_amnt,0))/count(rec.consultant)) net_amnt,
round((((sum(distinct nvl(rec.opd_amnt,0))-sum(distinct nvl(dis.discount_amnt,0))/count(rec.consultant) ) *
max(dr_per))/100),0) dr_share,
round((((sum(distinct nvl(rec.opd_amnt,0))-sum(distinct nvl(dis.discount_amnt,0))/count(rec.consultant) ) *
max(100-dr_per))/100),0) hosp_share,
count(distinct rec.consultant) net_dis
from
select -- bokm_doc_dt receipt_date, bysalim
bil_recept_no_a rcpt_no,
fnc_org_sname(bokm_panel_comp_id) company,
0 return_amnt,
pr_mrno patient_mrno,pr_fname patient,
bokm_doc_no docno,
gcd_desc(bil_pay_mode_a) pay_mode,
fnc_service_name(rslt_tst_code) service_name,
dr_name consultant,
pt_tst_rate opd_amnt,
cons_share cons_share,
(select max((nvl(rt_dr_share,0)*(100))/nvl(rt_amount,0))
from hms_adm_dr_rt rt
where dr.dr_id = rt.rt_dr_id
and book.rslt_tst_code = rt.rt_scs_id) dr_per,
dr_on_rent dr_rent,dr_share
from hms_pat_pers pat,hms_lab_pat_mst pmst,hms_opd_book book,
hms_pat_amnt amt,hms_adm_dr dr
where pat.pr_mrno = pmst.bokm_mrno
and pmst.bokm_mrno = book.rslt_mrno
and pmst.bokm_doc_no = book.pt_pat_doc_no
and pmst.bokm_mrno = amt.bil_mrnum_a
and pmst.bokm_doc_no = amt.bil_docno_a
and pmst.bokm_ref_conusltant_id = dr.dr_id
and amt.bil_rcp_type_a = '075002'
and pmst.bokm_pat_type in('PVT_OPD','CP_OPD')
and amt.bil_void_a = 'N'
and (pmst.bokm_user_dept_code != '039')
and BOOK.CREATED_ON between '01-OCT-2011' and '17-OCT-2012'
/* and (pat.pr_curr_cont_id = :P_CONT_ID or :P_CONT_ID = '000')
and (pat.pr_curr_prvnc_id = :P_PRVNC_ID or :P_PRVNC_ID = '00')
and (pat.pr_curr_city_id = :P_CITY_ID or :P_CITY_ID = '000')
and (pat.pr_curr_area = :P_AREA_ID or :P_AREA_ID = '000')
and (pat.pr_gender = :P_GENDER or :P_GENDER = 'A')
and (pat.pr_marital_status = :P_MARITAL_STAT or :P_MARITAL_STAT = 'ALL')
and (to_char(pmst.bokm_panel_comp_id) = :P_PANEL_COMP or :P_PANEL_COMP = 'ALL')
and (pmst.bokm_ref_conusltant_id = :P_CONS or :P_CONS = 'ALL')
and (decode(pmst.bokm_panel_comp_id,'1','PVT_IPD','CP_IPD') = :P_PAT_TYPE or :P_PAT_TYPE = 'ALL')
&LPARA_RCPT_DT */
) rec,
select -- bokm_doc_dt receipt_date, bysalim
pr_mrno patient_mrno,
bokm_doc_no docno,
nvl(bil_disc_amont_a,0) discount_amnt
from hms_pat_pers pat,hms_lab_pat_mst pmst,hms_opd_book book,
hms_pat_amnt amt
where pat.pr_mrno = pmst.bokm_mrno
and pmst.bokm_mrno = book.rslt_mrno
and pmst.bokm_doc_no = book.pt_pat_doc_no
and pmst.bokm_mrno = amt.bil_mrnum_a
and pmst.bokm_doc_no = amt.bil_docno_a
and amt.bil_rcp_type_a = '075001'
and pmst.bokm_pat_type in('PVT_OPD','CP_OPD')
and amt.bil_void_a = 'N'
and (pmst.bokm_user_dept_code != '039')
and BOOK.CREATED_ON between '01-OCT-2011' and '17-OCT-2012'
/* and (pat.pr_curr_cont_id = :P_CONT_ID or :P_CONT_ID = '000')
and (pat.pr_curr_prvnc_id = :P_PRVNC_ID or :P_PRVNC_ID = '00')
and (pat.pr_curr_city_id = :P_CITY_ID or :P_CITY_ID = '000')
and (pat.pr_curr_area = :P_AREA_ID or :P_AREA_ID = '000')
and (pat.pr_gender = :P_GENDER or :P_GENDER = 'A')
and (pat.pr_marital_status = :P_MARITAL_STAT or :P_MARITAL_STAT = 'ALL')
and (to_char(pmst.bokm_panel_comp_id) = :P_PANEL_COMP or :P_PANEL_COMP = 'ALL')
and (pmst.bokm_ref_conusltant_id = :P_CONS or :P_CONS = 'ALL')
and (decode(pmst.bokm_panel_comp_id,'1','PVT_IPD','CP_IPD') = :P_PAT_TYPE or :P_PAT_TYPE = 'ALL')
and BOOK.CREATED_ON between :P_RCPT_DTFR and :P_RCPT_DTTO
-- and BOOK.CREATED_ON between :P_RCPT_DTFR and :P_RCPT_DTTO
&LPARA_RCPT_DT */
) dis
where rec.patient_mrno = dis.patient_mrno (+)
and rec.docno = dis.docno (+)
--and patient = 'SHAHMEER'
group by rec.consultant, --rec.receipt_date, bysalim
rec.patient_mrno,rec.patient,
pay_mode,service_name,rec.docno,
rcpt_no,company
order by rcpt_no,rec.consultant
) cns
group by cns.consultant
order by 1
Edited by: user6431550 on Nov 15, 2012 3:10 AM

Report run very slow because some user accessing the same report

Dear All,
I group my table into 3 tablespace And some reports, accessing different tablespace (more than 1 table space). and these report will always be run by 5 user in the same time. and make it run very slow. Is it going to make the report very slow ? Please advice
Thanks in advance
Widhi

Hi,
i hope that may not be the actual problem..
if ur report processing includes relatively high
amount of calculations on tables..then the report
processing can be very slow...
In that case try to create a table to store ur calculations
temporarily and try to use that table in the report..

Obiee Report is very slow

Hi,
The report is looking very slow ,where should i tune it?
Thanks-Bhaskar

Hi User,
Please refer the below links for performance tuning
Performance of Report
performance tuning
Award points if Helps
Thanks,
Raj

Report run very slow

Hi
From the SE30, the system call 'fetck MKPF' consume a lot of time, the code is like below. Could anyone please advise how to improve it? Thanks
clear lt_temp1[].
   select "a~mblnr
         a~budat
         b~matnr
        b~MBLNR
        b~zeile
         b~bwart
         b~ERFMG
         b~ERFME
         c~aufnr
         c~verid
         e~text1
         f~maktx
        g~auart
    into corresponding fields of table lt_temp1
    from mkpf as a
      inner join mseg as b
        on amblnr = bmblnr
        and amjahr = bmjahr
      inner join afpo as c
        on baufnr = caufnr
        and bmatnr = cmatnr
      inner join aufk as i
        on caufnr = iaufnr
      inner join afko as d
        on iaufnr = daufnr
      inner join MKAL as e
        on cmatnr = ematnr
        and bwerks = ewerks
        and cverid = everid
      inner join MARC as h
        on ematnr = hmatnr
        and ewerks = hwerks
      inner join MAKT as f
        on ematnr = fmatnr
     inner join aufk as g
       on caufnr = gaufnr
    where a~budat in s_datum
    and   b~bwart between '101' and '102'
    and   b~werks = p_werks
    and   b~erfmg <> 0
    and   b~aufnr <> space
    and   i~AUART in gr_auart
    and   d~fevor in s_fevor
    and   d~dispo in s_dispo
    and   f~spras = sy-langu.

Hi huang,
Hope this code will be help out.
If you use more that three inner joins performence will be very slow instead of that better to use For All entreies.
*& Report ZDN_TEST_001
REPORT ZDN_TEST_001.
SELECT-OPTIONS: S_DATUM FOR SY-DATUM.
PARAMETERS: P_WERKS TYPE WERKS.
TYPES: BEGIN OF TP_MKPF,
MBLNR TYPE MKPF-MBLNR,
MJAHR TYPE MKPF-MJAHR,
BUDAT TYPE MKPF-BUDAT,
END OF TP_MKPF.
TYPES: BEGIN OF TP_MSEG,
MBLNR TYPE MSEG-MBLNR,
MJAHR TYPE MSEG-MJAHR,
ZEILE TYPE MSEG-ZEILE,
BWART TYPE MSEG-BWART,
MATNR TYPE MSEG-MATNR,
WERKS TYPE MSEG-WERKS,
ERFMG TYPE MSEG-ERFMG,
ERFME TYPE MSEG-ERFME,
AUFNR TYPE MSEG-AUFNR,
END OF TP_MSEG.
TYPES: BEGIN OF TP_AFPO,
AUFNR TYPE AFPO-AUFNR,
MATNR TYPE AFPO-MATNR,
VERID TYPE AFPO-VERID,
END OF TP_AFPO.
TYPES: BEGIN OF TP_MKAL,
MATNR TYPE MKAL-MATNR,
WERKS TYPE MKAL-WERKS,
VERID TYPE MKAL-VERID,
TEXT1 TYPE MKAL-TEXT1,
END OF TP_MKAL.
TYPES: BEGIN OF TP_MAKT,
MATNR TYPE MAKT-MATNR,
MAKTX TYPE MAKT-MAKTX,
END OF TP_MAKT.
TYPES: BEGIN OF TP_MARC,
MATNR TYPE MARC-MATNR,
WERKS TYPE MARC-WERKS,
END OF TP_MARC.
TYPES: BEGIN OF TP_AUFK,
AUFNR TYPE AUFK-AUFNR,
AUART TYPE AUFK-AUART,
END OF TP_AUFK.
TYPES: BEGIN OF TP_TEMP1,
MBLNR TYPE MKPF-MBLNR,
BUDAT TYPE MKPF-BUDAT,
MATNR TYPE MSEG-MATNR,
ZEILE TYPE MSEG-ZEILE,
BWART TYPE MSEG-BWART,
ERFMG TYPE MSEG-ERFMG,
ERFME TYPE MSEG-ERFME,
AUFNR TYPE AFPO-AUFNR,
VERID TYPE AFPO-VERID,
TEXT1 TYPE MKAL-TEXT1,
MAKTX TYPE MAKT-MAKTX,
AUART TYPE AUFK-AUART,
END OF TP_TEMP1.
DATA: IT_TEMP1 TYPE STANDARD TABLE OF TP_TEMP1.
DATA: IT_MKPF TYPE STANDARD TABLE OF TP_MKPF.
DATA: IT_MSEG TYPE STANDARD TABLE OF TP_MSEG.
DATA: IT_AFPO TYPE STANDARD TABLE OF TP_AFPO.
DATA: IT_MKAL TYPE STANDARD TABLE OF TP_MKAL.
DATA: IT_MAKT TYPE STANDARD TABLE OF TP_MAKT.
DATA: IT_AUFK TYPE STANDARD TABLE OF TP_AUFK.
DATA: IT_MARC TYPE STANDARD TABLE OF TP_MARC.
work area.
DATA: WA_TEMP1 TYPE TP_TEMP1 ,
      WA_MKPF TYPE TP_MKPF,
      WA_MSEG TYPE TP_MSEG,
      WA_AFPO TYPE TP_AFPO,
      WA_MKAL TYPE TP_MKAL,
      WA_MAKT TYPE TP_MAKT,
      WA_MARC TYPE TP_MARC,
      WA_AUFK TYPE TP_AUFK.
START-OF-SELECTION.
SELECT MBLNR MJAHR BUDAT INTO TABLE IT_MKPF FROM MKPF
WHERE BUDAT IN S_DATUM.
IF NOT IT_MKPF IS INITIAL.
    SELECT MBLNR MJAHR ZEILE BWART MATNR WERKS ERFMG ERFME INTO TABLE IT_MSEG FROM MSEG
    FOR ALL ENTRIES IN IT_MKPF
    WHERE MBLNR = IT_MKPF-MBLNR
    AND MJAHR = IT_MKPF-MJAHR
    AND BWART BETWEEN '101' AND '102'
    AND WERKS = P_WERKS
    AND ERFMG = 0
    AND AUFNR = SPACE.
ENDIF.
IF NOT IT_MSEG IS INITIAL.
    SELECT AFPOAUFNR AFPOMATNR AFPO~VERID INTO TABLE IT_AFPO FROM AFPO
    INNER JOIN AUFK
    ON AFPOAUFNR = AUFKAUFNR
    INNER JOIN AFKO
    ON AUFKAUFNR = AFKOAUFNR
    FOR ALL ENTRIES IN IT_MSEG
    WHERE AFPO~AUFNR = IT_MSEG-AUFNR
    AND MATNR = IT_MSEG-MATNR.
ENDIF.
IF NOT IT_MSEG IS INITIAL.
    SELECT MATNR WERKS VERID TEXT1 INTO TABLE IT_MKAL FROM MKAL
    FOR ALL ENTRIES IN IT_MSEG
    WHERE MATNR = IT_MSEG-MATNR
    AND WERKS = IT_MSEG-WERKS.
ENDIF.
IF NOT IT_MKAL IS INITIAL.
    SELECT MATNR WERKS INTO TABLE IT_MARC FROM MARC
    FOR ALL ENTRIES IN IT_MKAL
    WHERE MATNR = IT_MKAL-MATNR.
ENDIF.
IF NOT IT_MARC IS INITIAL.
    SELECT MATNR MAKTX INTO TABLE IT_MAKT FROM MAKT
      FOR ALL ENTRIES IN IT_MARC
      WHERE MATNR = IT_MARC-MATNR.
ENDIF.
IF NOT IT_AFPO IS INITIAL.
    SELECT AUFNR AUART INTO TABLE IT_AUFK FROM AUFK
    FOR ALL ENTRIES IN IT_AFPO
    WHERE AUFNR = IT_AFPO-AUFNR.
ENDIF.
LOOP AT IT_MKPF INTO WA_MKPF.
    WA_TEMP1-MBLNR = WA_MKPF-MBLNR.
    WA_TEMP1-BUDAT = WA_MKPF-BUDAT.
    READ TABLE IT_MSEG WITH KEY MBLNR = WA_MKPF-MBLNR
                                WERKS = P_WERKS
                                ERFMG = 0
                                AUFNR = SPACE
                                INTO WA_MSEG.
    IF SY-SUBRC = 0.
      WA_TEMP1-MATNR = WA_MSEG-MATNR.
      WA_TEMP1-ZEILE = WA_MSEG-ZEILE.
      WA_TEMP1-BWART = WA_MSEG-BWART.
      WA_TEMP1-ERFMG = WA_MSEG-ERFMG.
      WA_TEMP1-ERFME = WA_MSEG-ERFME.
      READ TABLE IT_AFPO WITH KEY AUFNR = WA_MSEG-AUFNR
                                  MATNR = WA_MSEG-MATNR
                                  INTO WA_AFPO.
      IF SY-SUBRC = 0.
        WA_TEMP1-AUFNR = WA_AFPO-AUFNR.
        WA_TEMP1-VERID = WA_AFPO-VERID.
        READ TABLE IT_AUFK WITH KEY AUFNR = WA_AFPO-AUFNR
                                    INTO WA_AUFK.
        IF SY-SUBRC = 0.
          WA_TEMP1-AUART = WA_AUFK-AUART.
        ENDIF.
      ENDIF.
      READ TABLE IT_MKAL WITH KEY MATNR = WA_MSEG-MATNR
                                  WERKS = WA_MSEG-WERKS
                                  INTO WA_MKAL.
      IF SY-SUBRC = 0 .
        WA_TEMP1-TEXT1 = WA_MKAL-TEXT1.
        READ TABLE IT_MARC WITH KEY MATNR = WA_MKAL-MATNR
                                    WERKS = WA_MSEG-WERKS
                                    INTO WA_MARC.
        IF SY-SUBRC = 0.
          READ TABLE IT_MAKT WITH KEY MATNR = WA_MARC-MATNR
                                      INTO WA_MAKT.
          IF SY-SUBRC = 0 .
            WA_TEMP1-MAKTX = WA_MAKT-MAKTX.
          ENDIF.
        ENDIF.
      ENDIF.
      APPEND WA_TEMP1 TO IT_TEMP1.
      CLEAR: WA_TEMP1 , WA_MKPF , WA_MSEG , WA_AFPO , WA_MKAL , WA_MAKT, WA_MARC , WA_AUFK.
    ENDIF.
ENDLOOP.
Thanks,
Nelson

Report running very slow compared to Query Analyzer - high TimeDataRetrieval

Hi,
I have a report in SQL Reporting Services 2005 which calls a stored proc and the report takes a very long time to run and sometimes returns zero records. But when i run the stored proc in query analyzer it takes about 4 seconds!!
I have checked the execution log on the RS using the below sql:
Code Snippet
use ReportServer
Select * from ExecutionLog with (nolock) order by TimeStart DESC
It shows that i have a large amount of time for the dataretrieval (601309ms, about 10mins) and does not return any records most likely because of a query timeout:
TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount
601309 2227 3 1 rsSuccess 4916 0
The weird thing is that when i run it in query analyzer, i get about 400 records in 4 seconds !!
I dont understand what RS is doing to take up so much time like this to retrieve data.
The report is very simple - it basically returns the records straight out into a table.
The only thing I somewhat suspected was a parameter data type conflict between RS and SQL, specifically dates. I have a start and end date parameter in the report - i tried specifying this as date and string to see if it made any difference but it didn't.
Any help would be greatly appreciated.

Hi Mark,
I didn't say it was an issue of parameter sniffing, and I didn't point you towards the good article about that <s>. I asked you whether you had read the article, described to you earlier in the thread.
What I said was that it might be an issue of appropriate and dynamic query optimization, versus a cached query plan. Parameter sniffing is only one of many ways that SQL Server tries to figure out how to optimize a query. I thought the article did a good job of discussing some of what goes on during this process, and that by absorbing that you could think of ways to handle the wider issue that would be appropriate to your code. I also pointed you to a thread in which I discussed this in more detail.
While there are truly many issues with the date controls in the default parameter interface and how they behave, I don't think that what you're experiencing with the date format is implicated in the performance issue. I guess it *might* be if (say) there is a non-default param value in your proc but your report parameter allows nulls.
Let's say the report server database has a different date default than your production database in your system. I have never sat down and tested this scenario and I guess it might cause problems, So we'll look at that first.
Whether the date format is at fault is really easy to prove one way or the other, and once proven can be pretty easy to fix:
Create a test parameter that is of string type. SQL Server is really good about dynamic conversion of string dates to date types as you probably know.
place values (formatted however you want) into this version of the parameter instead of your date control parameter. Use valid dates, in both formats.
Does your performance change?
Do you get the right results but bad performance with US format date strings versus right results with good performance with AU date values?
Do you get the WRONG results with US format date strings, or with AU date strings?
Try additional permutations involving casting/converting in your proc.
FWIW, go ahead in the Query Analyzer and put the SAME values you see in the log into your tests there (in US format, I mean). Do you get the CORRECT results? Does performance change? Hold this thought and see below.
Another thing you can do is look at the query plan as presented by the Query Analyzer when you present the arguments different ways. See #7 above -- try presenting the date in different formats. Does the plan show the same path and the same indexes in use each time, or are some not possible because of the way the date has to be converted? When this happens, the issue is usually that the conversion must be done for each line compared in the filter. You can fix this really easily in most cases by cast/convert in the procedure so that your SELECT line is only doing that work once.
If the plans are different, and perhaps the indexes used are different and you *can't* fix it by fixing the date before the SELECT, do you need to add an index, or perhaps rebuild one?
Moving on from the date format, as I said before it may be really important NOT to go by your interactive Query Analyzer performance because what you do there may not be used by SQL Server in determining a query plan to cache and re-use. In case you haven't read the other discussion that I pointed you to at (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1827775&SiteID=1), think about using RECOMPILE or other options that will force a more dynamic investigation of the query.
>L<

Report retrive very slow

dear sir,
can you help me. i found problem in oracle 8i on window 2003, it take very high time in process or report retiveal.
when i reinstall window 2003 and oracle 8i. before that one dba set some parameter in oracle and thats worked fine.
if you guid me it will be very useful me.
thanks
regd.
pankaj raval

user13541345 wrote:
dear sir,
can you help me. i found problem in oracle 8i on window 2003, it take very high time in process or report retiveal.
when i reinstall window 2003 and oracle 8i. before that one dba set some parameter in oracle and thats worked fine.
if you guid me it will be very useful me.
thanks
regd.
pankaj ravalpankaj raval,
Welcome to the forums.
You are very likely to have problems running Oracle 8i on Windows 2003 - Oracle 8i was never certified for Windows 2003, and if I recall correctly, there are problems with Java, exp (export), and possibly RMAN backups with that combination of operating system and Oracle release version.
Before you start down the path of flipping parameters, determine what is slow. From your post it appears that you have narrowed down the problem to a specific report. Find one of the sessions that will execute the report and enable a 10046 trace at level 8 or level 12. See this 3 part blog article series for help with 10046 trace files:
http://hoopercharles.wordpress.com/2009/12/01/10046-extended-sql-trace-interpretation/
With Oracle 8i you will likely need to use this syntax to enable a 10046 trace in another session
EXEC SYS.DBMS_SYSTEM.SET_EV(SID,SERIAL#,10046,12,'');Or, you can use the logon trigger that is provided in the second article in the series.
Charles Hooper
Co-author of "Expert Oracle Practices: Oracle Database Administration from the Oak Table"
http://hoopercharles.wordpress.com/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Report is very Slow,!!!

Hi Every1;
I am building a report of statements of different account holders, but it take much time as each page took more than 10 mins consisting of 25 rows only, please check my query is there any problem in it or not.
Query
i m taking the accounts name and address from the chart of account table consisting of more then 15000 account holders and taking the rest of the requirements e.g. opbal, qty, dr,cr from the other table ( t2 )consisting of more then 3000000 rows.
i think the speed slow is due to enough record.
my desktop hardware is 2 gb ram and 3.0 ghz dual core processor.
i even take the codes, name of the account holders from the same table t2 but the speed variable from 1-2 mins per page.
Any Solution for this
Regards
M. Laeeque A.

sorry for that
Query Is.
in main sql query statement ( Group 1 ) i write
select codes, dname, dadd from t1
and in
formula column cf1 ( opbal )
i write
declare
t1 number;
begin
select sum(dr)-sum(cr) into t1 from t2 where sdate < :dt1 and code = :code;
return t1;
and in cf2 i wrote
declare
t1 number;
t2 number;
begin
select sum(dr),sum(cr) into t1 from t2 where sdate between :dt1 and :dt2 and code = :code;
:cp1 := t1;
:cp2 := t2;
return :cp1;
return :cp2;
and in cf3 i wrote
declare
t1 number;
begin
select sum(qty) into t1 from t2 where sdate between :dt1 and :dt2 and code = :code;
return t1;
this is my query can any1 please help me
Oracle 9i is my database and reports 6i
Regards
M. Laeeque A.

SSRS report running very slow but query is very fast in SSMS

I am running a very basic report. I am just retrieving some data from a table and I am using a parameter in the Where clause of the query. The query runs fast (in less than 5 secs) if I hardcode the parameter in the SSRS query but if it's left as a dynamically
chosen parameter the query takes over 5 minutes to render. I have read a little about "Parameter Sniffing" but I am not sure if that applies to my case since I am only using a TSQL query and not a SP.
Any feedback would be appreciated.
PS: My query looks like below:
Select Col1, Count(*)
From Tbl1
Where Col2 = @Para1
Group By Col1
KK

Hi Kk,
Is your data retrieval takes time or report rendering takes time? Run this query in your report server database to get the above two. Select * From Executionlog2
Check the timings data retrieval time, processing time, and report rendering time.
If data retrieval takes time,
Give some default values to filters (parameters).
If parameter rendering takes time
Choose different options for parameter selection. Instead of multiselction of parameter, use like etc.
Let me know which causing this problem after running the SQL profiler or executionlog query so that I can help you more. Or you can use SQL profiler to check what query takes more time.
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

BAM tab view report is very slow on inital display (1+ minutes)

I have a BAM installation that has multiple different "dashboards" using tabbed report views to display separate metric values from one generic data object. These "dashboards" are being accessed directly through a web browser using the generated link for each report (and not through the BAM Active Viewer or Active Studio tools). Regardless of which of the "dashboards" I choose, the initial display takes a long time to complete. It takes about 20-40 seconds before the "opening..." message shows in the browser window, then another 20-30 seconds (depending on the complexity of the tabbed report and number of views) to complete the display. However, after this initial display, I can select other tabs on the current report or select a different report to display, and it will complete in 10-15 seconds. (Actually, every report display used to take over a minute, but setting the IIS - HTTP Headers - Content Expiration to "Expire after 365 days" allowed the succeeding report displays to improve. Now, it is just the initial display that takes too long).
What is being done on the initial access of the BAM report that takes such a long time? I have seen a bunch of (temporary internet) files being loaded that, if I remove them, the response time is slow again for the next "dashboard" that I display. Is there any way to improve this response time?

What kind of views are you using and what is the source of your data?
Is there too much data in your BAM DOs?
Have you created indices?

Oracle Reports running very slow

The same Oracle reports, which used to take 15 seconds to complete, now takes about 4 minutes to complete. Any ideas? Thank you.
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JS:
Thank you for your reply. Could you be more specific about network problem? We've changed our web application server and reports server settings recently. What could cause network problems? <HR></BLOCKQUOTE>
Well, I would suggest that you got to be very clear with the query. Most of the report peformace is based on the query.
1. Make sure that query is fine and note down the time it takes.
2. If first step is clear and if you are happy with the output that is process time, then you can think about tuning the report.
( You may want skip this step)
3. If that does not work you can investigate
what kind of array it uses and network speed and other thinks. I am not really familior with these set up.
Good luck with it..
Regards ...
Krishna ...
null

BO Report Generation very slow

we have BO XI R2 running on windows 2003 enterprise ed (64 bit) with 8 GB ram and oracle 10g db. the report generation time for a simple statement takes about 40-50 minutes. what are the likely cause ? we have 5 named user licence and our branch personnels are accessing through infoview. the login is very fast.
further can we configure the infoview to generate reports directly in PDF format since we are currently generating the report and then again selecting the view in PDF mode to print. this also takes considerable time.
best regards

Yes you can change default view format to PDF in Infoview preferences page which you can find in top right corner of InfoView page.
Also you can try changing Array Fetch size and Array Bind Size in Universe parameters see if it makes some difference.
-Gokul.

Report Builder very slow when using NOt Equal

When creating dataset I have to exclude some customers and use Not Equal option out of filters option. Everuthing is getting extremely slow.
How to find the way to solve the problem - exclude the player and have decent performance. The reports for end-users and they are limited to drag and drop and not going to learn MDX.
Thanks

Hi srussky,
According to your description, you used not equal in query of dataset and the report runs slow, right?
When we use =, it reduces the join operation to one single matching row from each table. When we use not equal to, it massively increased the number of pairings if 99.99 % of the rows are matched.
To troubleshoot the problem, please refer to the following steps:
Consider replacing the not equal operator with equals (=) or inequaluity operators (>,>=,<,<=) if possible.
Using Stored Procedures in dataset, then the query will be executed in database engine.
Reduce the number of member siblings in the level that is being referenced in the MDX query.
Reduce the number of member properties of the referenced member and its member siblings.
Use Drillthrough filters in the MDX query to limit the number of rows that are returned by the MDX query.
Use the XML/A Provider after warming the client cache of the provider.
Use virtual dimensions.
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support

Report Rendering Very Slow With RDLC

I am running into some horrible performance with running reports as .rdlc's
The reports themselves are fairly straightforward, save for some column and row groupings in matrices. If I have one simple column group, things run pretty quickly. If I add one or two more groupings, things slow down incredibly!
I've been doing some research and have found that several people have experienced the same problem as I.
http://prologika.com/CS/forums/p/1272/4541.aspx#4541
Unfortunately, I don't have the option to test out performance of the reports against a "real" SSRS installation. And the data source I'm working with is actually a C# dataset versus an actual SQL Server database.
We're currently running on Windows Server 2003 and are using .Net 4.0
Has anyone else experienced the same issue, and if so, how did you ultimately resolve/work around the issue? Amazing that the performance between rdlc and rdl's could be that drastic!
The developers have mentioned creating a field for each possible value for a field. For example, there is a top level group called "Plan" and a sub-group called "Unit". These are just two of the fields we are grouping on for column groups.
There are possibly 30 different plans, with possibly up to 6 units. So essentially, there would be up to 180 columns in a table. We would then need to write expressions to hide any columns/groups that have no value. Not a smart option...
A. M. Robinson

Hi Robinson,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

BI publisher report is very slow

Similar Messages

Maybe you are looking for