Report taking a lot longer to run in Live environment

Hi,
I have created a report in Discoverer Plus and in the Test environment this report takes approx 5-10secs to run.
I have exported the report using Discoverer administrator and imported it into the Live environment.
When I go to run this report in Live it is taking considerably longer to run, it is taking over 45 minutes.
Has anyone experienced this issue before and how did you manage to fix it?
Many Thanks
Martin

I dont think I have seen that poor of performance arise but one of my reports double in time and it turned out
1) There was an INDEX missing in my production system
2) Statistics needed to be ran on a couple of the tables
The worst slow down I saw was when the DBA's had brought up my TEST system. All reports were running slower than their DEVL counter parts but this dealt with an .init setting the DBA's forgot to add but I cannot envision that being the case for you on your LIVE system.
Hope this helps.

Similar Messages

Starting regular apps like google chrome is taking a lot longer. Why is this happening?

Starting regular apps like google chrome is taking a lot longer. Why is this happening?

Hey judybh,
Thanks for the question. After reviewing your post, it sounds like apps are slow to load or the Mac itself is slow. There are a number of potential causes that you can check by following this article.
OS X Mavericks: If your Mac runs slowly
http://support.apple.com/kb/PH13895
Thanks for using Apple Support Communities.
Have a nice day,
Mario

Rendering "watermark" taking a lot longer

For the past three years I've been editing a 27 minute TV show (that's now also on the web) as part of my job. For some strange reason, this season (which started last month) is taking a lot longer to render. Nothing much has changed. The show is all imported from one source (I just fine tune it, throw on some titles and transitions, etc). But all of a sudden what used to take under a half hour to render is now taking three or more times that (and a lot of the time it starts off telling me it will take 6 hours or more).
I have ruled out the titles, as if I do a render of only them (and transitions) it takes 15-25 minutes. Which leaves the 'watermark' graphic...and when I render that it does indeed take over an hour.
I initially thought it might be because I replaced the graphic with a larger image which I was then scaling down in FCP (I accidently deleted the one I used in previous seasons). But this week when I scaled it down to the exact dimensions in Photoshop, it still is taking over an hour.
Any ideas?

Equipment is all the same. But did upgrade to FCS2 over the summer (forgot to mention that). Other than that, nothing has change. The motion titles are the same, the footage is shot on same camera, edited on same device and transferred into the computer using the same player and cables into the same hard drive.
Don't know if FCP changed over the summer and there's now a setting that needs to be tweaked (or if it now takes longer because the upgrade is working on a non-intel PowerMac)

Taking a lot longer to hook up iDisk with this latest update

Every time I restart, it takes an awful long time for iDisk to show on my desktop, and while I wait for it to come up, if I do anything with the Finder, such as open the hard disk or try to access any of the menus, I get the spinning beach ball of death -
so I go to Force Quit to see if I can clear the hang up, and every time, without fail, the Finder is the one not responding and I have to restart the finder.
I still have to wait for the iDisk to be found, and then I can finally do stuff.
I never had this problem before the latest software update and battery update. I know I've got enough RAM, I don't use anything memory intensive and I am quite diligent about not having too many Apps running - I never have more than 3 at the same time, and they're usually little Apps, I certainly don't have anything like Photoshop or Word or Excel or iMovie or DVD Player or such running at the same time.
Why is it taking so long now to get the iDisk to show? I feel like I took a step back in the computer's speed lately.
Any thoughts? I've run the usual stuff, Onyx, restarted a few times, checked my Prefs, but it's the Finder, so I'm stumped. It can't be the memory!
Help.

Not enough free space on the startup disk can cause the issues you are referring to.
Control click the MacintoshHD icon on your desktop then click Get Info.
You'll see: Capacity & Available
Make sure there's at least 15% free disk space.
If it's not a disk space issue, verify the disk for errors.
Launch Disk Utility located in HD > Applications > Utilities
Select the startup disk on the left then select the First Aid tab.
Click: Verify Disk (not Verify Disk Permissions)
If Disk Utility reports problems, you will need to insert your install disc to make repairs.
And if you have not done so lately, backup all your important data just in case.

Select/Update taking far too long to run, how can I get it to go faster?

Hello all,
I am trying to do an update/select on a table that returns 16 million records. So far most of the time it takes forever to complete or never finishes. Initially I was trying to do it as one big select, but when that didnt work, i broke it down to creating a table with the "base" 16 million records, and am trying to fetch additional values for each of those records from the table i grabbed those records from. Doing a select got me no where, so I am trying to do an update of the tables with the values i find using a cursor. Even this does not seem to be working. Is there a way to do it with a batch/bulk update that would be faster? The code is as follows: (oracle 10g):
DECLARE
   CURSOR wr63993_cur IS
      SELECT   provider_id,
               din_gp_pin,
               orig_prescription_nbr,
               adjudication_date
        FROM   WR63993_BASE
       WHERE   adjudication_date BETWEEN to_date('2009/07/01', 'yyyy/mm/dd') AND to_date('2009/07/31', 'yyyy/mm/dd');
   CURSOR date_cur (v_provider_id WR63993_BASE.provider_id%TYPE,
                    v_din_gp_pin WR63993_BASE.din_gp_pin%TYPE,
                    v_orig_prescription_nbr WR63993_BASE.orig_prescription_nbr%TYPE,
                    v_adjudication_date WR63993_BASE.adjudication_date%TYPE)
      IS
      SELECT   MIN(adjudication_date) min_date
        FROM   claim_history@posi
       WHERE   provider_id = v_provider_id
         AND   din_gp_pin = v_din_gp_pin
         AND   orig_prescription_nbr = v_orig_prescription_nbr
         AND   adjudication_date >= ADD_MONTHS(v_adjudication_date, - 24);
BEGIN
   FOR wr63993_rec IN wr63993_cur LOOP
      FOR date_rec in date_cur(wr63993_rec.provider_id, wr63993_rec.din_gp_pin, wr63993_rec.orig_prescription_nbr, wr63993_rec.adjudication_date) LOOP
         UPDATE   WR63993_BASE
            SET   min_date = date_rec.min_date
          WHERE   provider_id = wr63993_rec.provider_id
            AND   din_gp_pin = wr63993_rec.din_gp_pin
            AND   orig_prescription_nbr = wr63993_rec.orig_prescription_nbr;
      END LOOP;
END LOOP;
COMMIT;
END;
/

aaah. healthcare insurance :)
The performance of these, as i'm sure you know, is tricky.
Consider the following which could help you eliminate your cursors. Here, B.adjudication_date will be the same as "MIN(adjudication_date) min_date" from your query.
I understand that this is typically outside of your control, but if it is at all possible, move all of the data to the same database so you don't need those distributed queries. Separate schemas is ok.
Select
stuff
From Wr63993_Base A
Inner Join Claim_History@Posi B On A.Provider_Id=B.Provider_Id And A.Din_Gp_Pin=B.Din_Gp_Pin And A.Orig_Nbr=B.Orig_Nbr
--the next table will allow you to get *earlier* instances of the claim where the adjudication date was in past 24 months
--we only want to see the row where there ARE NO EARLIER instances. So this LOJ will return null for that row.
Left Outer Join Claim_History@Posi C On A.Provider_Id=C.Provider_Id And A.Din_Gp_Pin=C.Din_Gp_Pin And A.Orig_Nbr=C.Orig_Nbr
and c.adjudication_date >= ADD_MONTHS(a.adjudication_date, - 24) and c.adjudication_date<b.adjudication_date
Where
A.Adjudication_Date Between To_Date('2009/07/01', 'yyyy/mm/dd')
And To_Date('2009/07/31', 'yyyy/mm/dd')
And B.Adjudication_Date >= Add_Months(A.Adjudication_Date, - 24)
and c.adjudication_date is null --only get the row where B is the earliest qualifying adjudication date.
Dave

Inventory aged reports are taking a very long time to run

We are using Standard delievered extractors for Inventory. We have build an Aged report and it is taking a very long time to run as more an more data is added. We put the inventory in buckets 0-30, 31-60, .... >365 days. We are aging based on a batch date the user enters. the problem is it has to go through every record to recalculate because they are non cumulative.
any ideas/suggestions on how to make this more efficient? New design?

Hi MM,
We can use snapshot of monthly data from Query and store it in DSO at month level.
We had used APD on Query and then Stored them in DSO1(WO)->DSO2(STD)->Cube->report based on Snap Shot.
From the New Query , calculate the Age.
Rgds
SVU

SSRS Reports taking long time to load

Hello,
Problem : SSRS Reports taking long time to load
My System environment : Visual Studio 2008 SP1 and SQL Server 2008 R2
Production Environment : Visual Studio 2008 SP1 and SQL Server 2008 R2
I have created a Parameterized report (6 parameters), it will fetch data from 1 table. table has 1 year and 6 months data,      I am selecting parameters for only 1 month (about 2500 records). It is taking almost 2 minutes and 30 seconds
to load the report.
This report running efficiently in my system (report load takes only 5 to 6 seconds) but in
production it is taking 2 minutes 30 seconds.
I have checked the Execution log from production so I found the timing for
Data retrieval (approx~)    Processing (approx~)           Rendering (approx~)
10 second                                  15 sec
        2 mins and 5 sec.
But Confusing point is that , if I run the same report at different time overall output time is same (approx) 2 min 30 sec but
Data retrieval (approx~)       Processing (approx~)                Rendering (approx~)
more than 1 min                            15 sec
more than 1 min
so 1 question why timings are different ?
My doubts are
1) If query(procedure to retrieve the data) is the problem then it should take more time always,
2) If Report structure is problem then rendering will also take same time (long time)
for this (2nd point) I checked on blog that Rendering depends on environment structure e.g. Network bandwidth, RAM, CPU Usage , Number of users accessing same report at a time.
So I did testing of report when no other user working on any report But failed (same result output is 2 min 30 sec)
From network team I got the result is that there is no issue or overload in CPU usage or RAM also No issue in Network bandwidth.
Production Database Server and Report server are different (but in same network).
I checked that database server the SQL Server is using almost Full RAM (23 GB out of 24 GB)
I tried to allocate the memory to less amount up to 2GB (Trial solution I got from Blogs) but this on also failed.
one hint I got from colleague that , change the allocated memory setting from static memory to dynamic to SQL Server
(I guess above point is the same) I could not find that option Static and Dynamic memory setting.
I did below steps
Connected to SQL Server Instance
Right click on Instance go to properties, Go to Memory Tab
I found three options 1) Server Memory   2) Other memory   3) Section for "Configured values and Running values"
Then I tried to reduce Maximum Server memory up to 2 GB (As mentioned above)
All trials failed, this issue I could not find the roots for this issue.
Can anyone please help (it's bit urgent).

Hi UdayKGR,
According to your description, your report takes too long to load on your production environment. Right?
In this scenario, since the report runs quickly in developing environment, we initially think it supposed to be the issue on data retrieval. However, based on the information in execution log, it takes longest time on rendering part. So we suggest you optimize
the report itself to reduce the time for rendering. Please refer to the link below:
My report takes too long to render
Here is another article about overall performance optimization for Reporting Services:
Reporting Services Performance and Optimization
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Discoverer report is taking a very long time

Hi All,
I need help on below discoverer issue.
discoverer report is taking a very long time for rows to be retrieved on export when it is run for India and it is required for month end. For some reason only 250 rows are retrieved at a time and retrieval is slow so it is taking 10 minutes to bring back 10,000 rows.
Regards
Kumar

Please post the details of the application release, database version and OS along with the discoverer version.
I need help on below discoverer issue.
discoverer report is taking a very long time for rows to be retrieved on export when it is run for India and it is required for month end. For some reason only 250 rows are retrieved at a time and retrieval is slow so it is taking 10 minutes to bring back 10,000 rows.Please see these links.
https://forums.oracle.com/forums/search.jspa?threadID=&q=Discoverer+AND+Long+AND+Time&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=Discoverer+AND+Performance&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=Discoverer+AND+Slow&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Rag: Query performence - Report taking long time when drill down a Char.

Hi All,
After executing the report when we try to Drilldown PO Char, then the report used to take long time nearly 60 to 90 minutes and thorough an errors that "An error is occurred during loading" or "Connection Timed Out".
The report is created on Multiprovider which is build on 7 infocubes and the data for the PO char is coming from all the 7 cubes.
So we have created Aggregates on the 5 Infocubes based on system proposal.
Then,
We checked in RSRT, the data is coming from all 5 Aggregates and also when we drill down the PO also the data is coming from 5 Aggregates itself.
But,
The report is running fine and also when we drilldown the PO to show all the PO values, then the report showing all the POu2019s details by taking nearly 15 mins only.
Here our concern is why the report is taking 15 mins when we drill a PO char.
Could any one give suggestions please.
Thanks in Adv.
Raju. E

Hi,
please check this list for query performance:
http://sapbwneelam.blogspot.com/2007/10/checklist-for-query-performance.html
Regards
Erwin

Concurrent request is taking a lots of time to run

Hi,
I have one query regarding ICM.
one of the concurrent request is taking a lots of time to run. How can I solve the issue.
Is there any steps to diagnose this issue?
Please reply.
Regards,
Manish

Hi,
How we can find that particular request are taking long time?See your other thread.
Concurrent request taking long time
Concurrent request taking long time
what is "gather statistrics schema" concurent program and what it does?See (Note: 419728.1 - How To Gather Statistics On Oracle Applications 11.5.10(and above) - Concurrent Process,Temp Tables, Manually).
Regards,
Hussein

3.x Workbooks taking longer and longer to run each week

Hey all, I have a user who has embedded 5 versions of the same query into a workbook. He runs this workbook every monday. When he first created the workbook it took 30 minutes to run. Each week that goes by the workbook takes longer and longer to run and eventually gets to the runtime of 2 hours. Periodically my user has to go and make a change to the workbook and after he recreates the workbook then it goes back to taking 30 minutes to run.
Is there some kind of a buffer that is filling up that I don't know about? Is there a way I can refresh the workbook so that the runtime doesn't creep like it is doing?
Thanks
Adam

Guess I posted prematurely. Looking closer I realized there was a select happening during this process against a text column without an index. The slowdown was just the increasing cost of looping through the the entire dataset looking at strings that often shared a fairly sizable starting substring. Chalk another problem up to the importance of appropriate indexes in your db!

Sql query taking too long to run

I am not sure what to do. My app takes two long to run and the reason is right in front of me, but again, I don't know what to do or where to go. (VB.Net VS 2005)
The main part of my query takes about 15 to 20 seconds to run. When I tack on this other part it slows the response to over 2 minutes.
Even running this other part alone takes 2+ minutes. The query as two sum functions. Is it possible, some how, that this query can run building it's results into another table and then I use this new table with the results all ready to go and join into the first part of the main query?
I am using oracle 9i with a Sql Developer. Which I am new to. Below is the culprit: Thanks
Select adorder.primaryorderer_client_id,
(sum(Case When insertion.insert_date_id >= 2648 and insertion.insert_date_id < 2683
Then insertchargedetail.Amount_insertDetail Else 0 End)) As CurRev,
(sum(Case When insertion.insert_date_id >= 2282 and insertion.insert_date_id < 2317
Then insertchargedetail.Amount_insertDetail Else 0 End)) As LastRev
from Adorder
Inner Join insertion On Adorder.id=insertion.Adorder_id
Inner Join insertchargesummary On insertion.id=insertchargesummary.insertion_id
Inner Join insertchargedetail On insertchargesummary.id=insertchargedetail.insertchargesummary_id
where ((insertion.insert_date_id >= 2282 and insertion.insert_date_id < 2317)
Or (insertion.insert_date_id >= 2648 and insertion.insert_date_id < 2683))
group by adorder.primaryorderer_client_id;

How to post a tuning request:
HOW TO: Post a SQL statement tuning request - template posting

Snapshot Report taking long time

Hi,
We have snapshot collection every 1 hour in our db and the process is taking 1/2 hour to run and it is the highest resource hog while it is running. what can we do to avoid this scenario ? Quick help ismuch appreciated. We use oem 11g for a 9.2.0.4 db.
Thanks
Prasad

Hi,
We have snapshot collection every 1 hour in our db and the process is taking 1/2 hour to run and it is the highest resource hog while it is running. what can we do to avoid this scenario ? Quick help ismuch appreciated. We use oem 11g for a 9.2.0.4 db.
Thanks
Prasad

Simple select query is taking a lot of time

hi gems...
my table has 7267563 rows...and i am doing a simple select * from table;
but it is taking a lot of time nearly 25minutes but not completed...
when i did select count(1) from table then it gave the result instantly also select * from table where rownum < 10 is also fine...even when i am selecting all the records using rownum i.e. select * from table where rownum < 7267563 is also giving result instantly...
but the entire table is not getting result i.e. select * from table...also there is no lock in the table(though i know that select is nothing to do with lock)..
what may be the issue..please suggest...thanks in advance...
Edited by: user12780416 on Dec 12, 2011 11:08 PM

Hi;
Please see below thread
query takes too long ...
help in solving long run query
HOW TO: Post a SQL statement tuning request - template posting
Hope it helps
Regard
Helios

My ipod was disabled and i tried to restore it, now i am downloading an apple software update which is taking a **** lot of time and ipod is still disabled.. will it be ok after the download ends? help please..!!

my ipod was disabled and i tried to restore it, now i am downloading an apple software update which is taking a **** lot of time and ipod is still disabled.. will it be ok after the download ends? help please..!!

We need to know more about your system, please download EtreCheck and run the report and please post it on your next reply. Then we can see how your system is configured, what apps are on it and look for anything obvious. We will look forward to seeing your report.

Report taking a lot longer to run in Live environment

Similar Messages

Maybe you are looking for