Slow report generation

Hi,
I have a report where its results depend on what option the user chooses in a selection list. The select list option alters the where clause in the query and displays new information. The problem is that it takes a ridiculously long amount of time to display results that have a larger amount of results (~100). Even with a table with 12 results there is a noticeable delay. The query includes a subquery as well as an order by and uses links to the database which is meant to make it act slower but I don't think such a thing would affect it so badly with 100 results? By slow display I mean around 5 minutes of loading. Meanwhile a query (not in the report) without the where statement doesn't take very long. The code is as follows:
select rpad(svc_app_name,8) project,rpad(loc_name,12)location,
rpad(svc_name,10)service,svs_date size_date,
round((svs_used_sz/1024)) used_size_MB
from hkadm.srvc@HKADM2_DBAAPEX.TNTEWW.COM, hkadm.svcsize@HKADM2_DBAAPEX.TNTEWW.COM, hkadm.host@HKADM2_DBAAPEX.TNTEWW.COM, hkadm.loc@HKADM2_DBAAPEX.TNTEWW.COM
where
   svc_name = svs_svc_name
   and svs_date = (select max(svs_date) from hkadm.svcsize@HKADM2_DBAAPEX.TNTEWW.COM a
                      where a.svs_hst_ip = svcsize.svs_hst_ip
                        and a.svs_svc_name = svcsize.svs_svc_name)
and svc_app_name = :P5_Link
  and svc_hst_ip = hst_ip
  and hst_loc_code = loc_code
order by 1,2,3,4My select list has submit on click and and there's a branch to the same page on submit. Any help appreciated.
Mike

You should create a view at your remote server like this:
CREATE OR REPLACE VIEW test_view
AS
   SELECT   RPAD (svc_app_name, 8) project, RPAD (loc_name, 12) LOCATION,
            RPAD (svc_name, 10) service, svs_date size_date,
            ROUND ((svs_used_sz / 1024)) used_size_mb,
            svc_app_name
       FROM hkadm.srvc, hkadm.svcsize, hkadm.HOST, hkadm.loc
      WHERE svc_name = svs_svc_name
        AND svs_date =
               (SELECT MAX (svs_date)
                  FROM hkadm.svcsize a
                 WHERE a.svs_hst_ip = svcsize.svs_hst_ip
                   AND a.svs_svc_name = svcsize.svs_svc_name)
        AND svc_hst_ip = hst_ip
        AND hst_loc_code = loc_code
   ORDER BY 1, 2, 3, 4and query it like this:
SELECT project, LOCATION, service, size_date, used_size_mb
  FROM test_view@hkadm2_dbaapex.tnteww.com
WHERE svc_app_name = :p5_listDenes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
------------------------------------------------------------------------------

Similar Messages

  • 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 Generation Toolkit Error Quick Question

    Hi,
         I created the most awesome LabVIEW report ever at my desk using a trial version of the RGT and Office 2003.  I took this to my production machine and ")@#(&%(*#^%()^!!!"  The production machine has office 2007 and a fully licensed version of the RGT.  Both machines have LabVIEW 8.6.0.  I've read all the stuff about these errors and something about classes and dll's and whatnot's.  So my quick question, is:  Instead of matching the versions of Microsoft Office as recommended, can I just rewrite from scratch the VI that creates this world's most awesome LabVIEW report on the production machine to create the same effect? 
    Solved!
    Go to Solution.

    Hi 
    Quick Answer: Probably
    Slower answer: Microsoft changed a lot of things behind the scenes in Office 2007, but the Report Generation toolkit version 1.1.3 supports Office 2007 so you should be good to go. Depends on what functions are included in your VI. Liek the read me says "Several default settings in Microsoft Office 2007 differ slightly from previous versions. Reports you generate using Office 2007 might look different than reports you generate from other versions of Office because font sizes, cell sizes, and so on, differ."
    Best Regards
    David
    NISW

  • Report generation toolkit (1.1.2) and 8.5

    I am not as crazy as I thought!
    I wrote a program today that collects data from excel reports in many directories using cell names and it worked well.  Unitl I saved it.  I had been saving the sub vi's, but when I went to close them I got a message about unsaved changes and I guess I clicked to save the changes today.  The program never worked the same again.  I would get errors like 41106 and 41110 at random (problems with excel not opening and other stuff).  I tried adding waits which slowed everything down and worked mostly.  But the only way to not drop data and get errors was to have a copy of excel open while getting my data.
      Well I just uninstalled/reinstalled the toolkit and rebuilt the vi that was having problems with the fresh install and everything is great again.  So my question is why does the toolkit have problems when I save it in 8.5?  The warning does say that the vi's are from 7.1 and I cant find any updates so I am hoping this is the latest version that came with my 8.5 suite.

    Hi Bryan,
    There should not be a problem with saving the VIs from the Report Generation toolkit in LabVIEW 8.5. I have checked the readme files to make sure but RGT 1.1.2 should work with any version of LabVIEW later than 7.0. However, the readme does discuss an specific upgrade issue. It says if you previously created VIs that use the built-in Report Generation VIs in LabVIEW Professional, Full, or Base packages or VIs from a previous version of the Report Generation Toolkit, installing the Report Generation Toolkit 1.1.2 might break the VIs you created. If the VIs you created contain any of the following VIs, edit them so they are compatible with the Report Generation Toolkit 1.1.2.
    Append Front Panel Image to Report VI—The Image Format input of the LabVIEW 6.1 version of this VI is a different enumerated type than the current toolkit version. Right-click the input and select Create»Control or Create»Constant from the shortcut menu to create a compatible control or constant.
    Append Table to Report VI—The connector pane position of the show grid lines input changed from the Report Generation Toolkit 1.0.1 version of the VI. Reconnect the original wire to the new input location.
    Get Report Settings VI—The cluster order of the font settings input changed from the Report Generation Toolkit 1.0.1 version of the VI. Right-click the output and select Create»Indicator from the shortcut menu to create a compatible indicator.
    Report Express VI—If a VI includes the LabVIEW built-in version of the Report Express VI on the block diagram, the VI breaks after you install the Report Generation Toolkit 1.1.2. Double-click the Report Express VI to launch its configuration dialog box, then click the OK button. Reconnect all wires to the Report Express VI.
    You might need to relink the following subVIs after installation because the connector panes changed in the Report Generation Toolkit 1.1.2. Right-click the VIs and select Relink to SubVI.
    New Report
    Dispose Report
    Append Front Panel Image to Report
    Append Hypertext Link Anchor to Report
    Append File to Report
    Append Horizontal Line to Report
    Set Report Font
    One thing that might have happened is if you had created the program in an earlier version of the toolkit, then saved it in the new version of the toolkit, maybe some of the upgrade issues regarding the VIs listed aboved cause LabVIEW to start giving you errors. Also, which version of excel are you using? After you re-did the VI program, have you tried to save it again and see if the same problem occurs?
    Carla
    National Instruments
    Applications Engineer

  • Automating a report generation process

    Hello guys!
    I just took on a new role in a company which requires me to deal with SAP BEx Analyzer.
    I'm completely new to this, but having gone through the report generation process, I feel the method I'm using is horribly tedious and I believe there should be a way to automate the process since it's a recurring monthly procedure.
    What I have to do currently to get the report is:
    1. Launch SAP Logon
    2. Filter the Connection which i want to find (i'll call it "PQI").
    3. Key in my Username, Password and Language
    4. Select the third container in the folder (i'll call it "03")
    5. After I open 03, it launches Excel with BEx Analyzer add in initialized. The report is currently empty
    6. Select Change Variable Values, fill in Fiscal Year, Month and Accounting Area.
    7. After which it will take like 15minutes to query, and a about 16,000 ++ rows are generated.
        Problem #1: The format isn't good, i have to right click on every cell that writes "Result" with yellow highlight and under it's properties I have to select         "Result Rows" > "Always Suppress".  (Ref1.PNG)
         This is horribly painful considering I have to wait about 1 minute for each response (it's very slow). I have to repeat this for every yellow column in the
         report. Can this be automated or done in 1 step?
    8. After doing so for all rows, I have to right click the table and select "Query Properties" and shift all the Free Characteristics (about 10) to "Rows".
         BUT, I can't do all at once, it will say "out of memory" and crash. I have to do so 2-3 rows at a time. Each time it'll take about 10-15 minutes to
         populate. It's very painful.
    9. After it's all done, i have to repeat step 7 again, which is to Suppress all result rows (Ref2.PNG)
    10.Followed by which I have to go to Query Properties > Display Options > Uncheck "supress repeated key values"
    11. When that is done I have to generate a PivotTable on the data.
    I have to repeat the same steps on a monthly basis.
    Is there a way I can script it to run the process for me monthly? Or any other way to make it less tedious?
    Thanks so much for any input or suggestion guys!
    Warmest Regards
    Brandon

    Suppressing Result Rows can be done in Query designer itself for one time. You need not to do after you get the report every time.
    If you always expect some 10 free chars constantly, i suggest you to insert them in Rows pane in Query designer but not in Analyzer. So that your report layout will be taking care with all settings what you want to do after the report generates in Excel. I mean you will get desired layout when you run the report first time itself.
    Suppress repeated key values also can be done in Query designer itself one time.
    By doing above, your report execution will not be tedious and it will be minimizing your efforts.
    Over all, What I have understood is, you are doing all sorts of settings in Analyzer after getting such huge volume of data, by which it gives you crash error.
    With all above steps, you can run your report with all pre-defined settings.

  • BI Publisher Report generation problem in Siebel

    Hi Experts,
    Here is the scenario, let's say i have 2 BIP reports in siebel, named Report A and Report B. i tried using 1500 records to generate Report A and Report B. I view the status of the reports in My BI Publisher View in Siebel, i noticed that after 5 hours, Report A is successfully generated, and report B still doesn't show if it successful or not, after 2 days, report B still doesn't show if it is successful or not.
    Based on the scenario above, here are my questions:
    a.) is there a way that we can increase the report generation for BI Publisher integrated with Siebel? 5 hrs of generating 1500 records i think is too slow, specially if that specific report is required to be generated everyday.
    b.) do you know why Report B still doesn't show if it successfully generated eventhough both reports was generated using equal amount of records?
    Thanks in advance! :)

    Here are the two steps I took to get the VI to work on my machine:
    1) Recompiled the code by ctrl-shift-clicking on the run arrow.
    2) Changed the string in the 3rd frame of the sequence that goes into the Append Front Panel Image to Report from I Graph plot.vi to I_Graph_plot.vi.
    After making the changes I did a File->Save All.

  • Open vi error for report generation toolkt

    Originally it works fine.
    Now I upgrade to win7, LV9 and office2010.
    To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
    But still got the error as attached.
    Any suggestion, thanks.
    Attachments:
    ss.png ‏184 KB

    1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
    2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
    In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
    More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D​711E786256F3300701D01

  • Report generation toolkit and signal express user step : problem of closing reference in "Stop" event

    Hi all,
    I'm trying to make a package of Vis to easily make Excel reports with Signal Express. I'm working on LabVIEW 8.2.1.
    I'm using the report generation toolkit, so I build a .llb from my project which contains all the hierarchy of my steps, but also the hierarchy of dynamic VIs called.
    I have made some steps, like "Open Workbook", "Write Data", etc.
    My steps run well, excepts one step : "Close Workbook".
    If my "Close Workbook" step is firing on "Run" Signal Express event, I have no error, so my reference is properly closed.
    But if my "Close Workbook" step is firing on "Stop" Signal Express event, I have an error "1", from "Generate Report Objectrepository.vi".
    I feel that I'm trying to use a reference which has been killed in the "Stop" step...
    I would like to know what exactly do Signal Express on "Stop" event and why my close function does'nt run well.
    Thanks,
    Callahan

    Hi Callahan,
    SignalExpress (SE for short) does the following on the Stop event:
    1. Takes the list of parameters that SE found on your VI's connector pane, and sets the values that the user set from the "Run LabVIEW VI" configuration page, if any.
    2. Then tells the VI that SE is running the Stop event by setting the Enum found on your VI's front panel. This in turn should produce some boolean values telling your VI to execute the Stop case.
    3. The VI is then run, with those values and states.
    4. SE checks to see if any errors where returned.
    5. Since this is the Stop event, SE releases the reference to the VI which it possesses.
    Questions for you would be, is the reference to your Workbook linked to a control on your connector pane, or held in a uninitialized Shift Register. If it's held in a Shift Register, SE would not be aware of it, and would not be able to affect that reference.
    Hope that helps. Feel free to post your LLB if it doesn't.
    Phil

  • Report Generation: New Report.vi

    Running applicaion in development mode works fine.
    After compiling however I get Error 7: Open VI Reference in New Report.vi
    Why am I getting this error?

    Has the version of Office on your machine changed since you installed the Report Generation Toolkit?  The VIs will become broken if the ActiveX interface changes, and this can happen when the Office version changes.  I recommend uninstalling and reinstalling the toolkit.  Also, what version of Report Generation Toolkit are you using?  The latest version is 1.1.1.
    -D
    P.S. - I'm going to respond to your other thread that you started with a link to this one.  Instead of creating multiple messages on the same question, just wait for a response to your initial thread.
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Report Generation Toolkit Error (undefined erro)

    Does anybody know what error -214 682 7864 (0x800A01A8) means when coming from the Report Generation Toolkit.
    I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet. The error was generated all the way down in NIReportGenerationToolkit.lvlib:Excel_Get_range.vi (this is the ActiveX code).
    Any ideas? 
    nrp
    CLA

    nrp wrote:
    I have an app which has been happily ticking over for several weeks, and then this error was generated when attempting to write a table to a spreadsheet.
    Was it the first time you attempted to write the table to that spreadsheet?
    Maybe the error is due to the spreadsheet grown oversize than its limit so that it cant accomodate the table anymore.
    What is the version of MS Office you are using? I think Office 2003 can go only upto 1024 columns...
    - Partha
    LabVIEW - Wires that catch bugs!

  • Report Generation Exe Error

    Hello,
     I am using LV 8.6.1 with the 1.13 report generation toolkit and I am having problems getting my built exe to work.  I am trying to open an excel template and populate it with new data.  I have broke the vi down to just opening excel - opening the template and then fill in some data.  But at this point excel does not open at all.  And naturally everything works fine in the development environment.
    Error Code: -2147352573
    Member not found in NI_ReportgenerationToolkit.lvlib:
    Excel_open_workbook.vi
    NI_Excel.lvclass: new reportsubvi.vi
    I read a few help pages that said to add \vi.lib\utility\NIreport.llb and LVclass directories to the project folder and add them to the always include section of the build.  But no luck so far.
    Side question:  The machine I want to use this on has 8.6.1 Full which does not have the extra excel functions that my developer has.  Is there a way to install the DEV report generation toolkit in the full version?  Then I would not need to build an exe.
    UPDATE:  I just tried the exe on a different machine that has a developer suite installed and it worked fine.  So I guess I need to find out what else I need to add to the build to make it work.
    Message Edited by _Bryan on 06-16-2010 11:58 AM
    Solved!
    Go to Solution.

    There should be some info on this in the KB.
    But first you should make sure that your version of the report generation toolkit actually supports excel 2000 (which is 10 years old)
    That should be in the release notes of the toolkit
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Report-generation vi problem

    On a Windows XP system using the "Text Report Example" vi, the (read) report property node item "TextFont" (stdole.Font) at the beginning of the "Font Style" vi which is a part of the "Set Report Font" vi is returning this error:
    "-1073741819 Unknown System Error in Font Style.vi->Set Report Font.vi->Easy Text Report.vi"
    Any suggestions as to a cause and cure?

    This Knowledge Base from NI's website actually deals with this problem. The fix depends upon whether or not you have the Report Generation Toolkit for LabVIEW. There are fixes for whether or not you have the Toolkit. Hope this helps.
    J.R. Allen

  • Report Generation for Excel does not work after using the Application Builder

    I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

    Hi
    I usually build exe-files, which sometimes also have report functionality.
    Open the Application Builder and check the following things:
    1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
    2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
    These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
    Hope this helps.
    Thomas
    Using LV8.0
    Don't be afraid to rate a good answer...
    Attachments:
    report.zip ‏25 KB

  • Report Generation Toolkit producing error -2147417842, "The application called an interface that was marshalled for a different thread."

    Hi everybody,
    I've got an application that logs data to an Excel spreadsheet using the Report Generation Toolkit.  My VI's have worked fine in the past using Excel XP, but since I've upgraded to Excel 2007, I am getting COM errors like this one:
    "Error -2147417842 occurred at The application called an interface that was marshalled for a different thread. in Excel_Insert_Text.vi"  That is the exact wording, even with the weird punctuation and capitalization.
    The first occurrence of the error is not determinate.  Sometimes, up to 10 logging sessions, involving a new .xls file, can occur before this error pops up.  Once this error occurs, I must quit LabVIEW to resolve it.  If I try to do anything with Excel, I always get this error, although sometimes it comes out of different source VIs.  Excel_Open.vi is another.
    These logging VIs have worked just fine until upgrading to Excel 2007.  I checked, and I was using a really old version of the Report Generation Toolkit, v1.0.1.  I read the documentation and had a big sigh of relief when I realized I needed to upgraded to v1.1.2 to get Excel 2007 support.  However, even after upgrading, I'm still getting the same errors.  I'm using LabVIEW 8.0.1, and I'm also building these VIs into an application.   The error occurs both in the LabVIEW IDE and in the built application.  Does anybody out there have any idea what I can do to fix this?  I googled a little, and discovered this is a COM error, but I can't find any references to the Report Generation Toolkit specifically.
    Thanks,
    Phil
    Solved!
    Go to Solution.

    Hi Christian,
    I do not see that exact option listed, do you mean "user interface"?  I recognize the "Run in UI Thread" option, it's on the Call Library Function Node.
    I checked, and my top-level VI has "same as caller" set, and I believe all my VIs are set to "same as caller".  Are you suggesting I change my top-level VI preferred execution environment to "user interface", or just the logging sub-VIs that use the Report Generation Toolkit?
    Thanks,
    Phil
    Attachments:
    VI_properties.png ‏15 KB

  • Report generation for FPGA VI

    Hello..
                  I want to include the number of resources used by FPGA (LUTs, slices, blockrams etc) in my report generation. 
    After compilation is completed, a window showing these resources will occur. But, how can I add this compilation report in my report generation...
    Please let me know..
    Thanks
    Prashanth
    Solved!
    Go to Solution.

    Hi
    I made a small code which helps you achieve this functionality.
    Hope it helps!
    In this code: I read from "toplevel_gen_xst.log" file generated for the project; search for the string "Device utilization summary" and extract the part of interest Now you add this extract to your report compiled using report generation toolkit.
    regards,
    Ravi.
    Attachments:
    image.jpg ‏60 KB
    FPGA Utilization.vi ‏10 KB

Maybe you are looking for