Exporting taking extremely long time

Hi,
I have been working with FCPX for about a year and all of the sudden, my files are taking forever to export. I'm exporting the ProRes timeline files by using the Share option. I always export the file with current settings to the desktop. Once it's finished on the desktop, I convert the file to H.264 using a Compressor droplet. I've read that this process is supposed to be faster then exporting H.264 directly from FCP. The files I'm using are about 1-2 hours of 1080i ProRes. For the file I'm exporting now, the estimated export size is 140 GB and in 24 hours of export time it has exported 45% of the file.
I know these are big files, but it never used to take this long to export them. What can I do to speed up this process?
Here's what I'm working with:
Computer:
MacPro5,1
OSX Version 10.6.8
Processor - 2 x 2.4 GHz Quad-Core Intel Xeon
16 GB 1066 DDR3
FCP X - Version 10.0.8
Compressor - 4.0.7
This is my first time posting a question to this community but I have found answers to many questions here before, so thank you.
J

Suggestions:
Check the amount of free space on your boot drive and media drives. If they have less than 20%, do some archiving. If there is plenty of free space, check the drive speeds by downloading on of the speed apps from AJA or Blackmagic. Also Verify disks and repair permissions in Disk Utility.
While exporting, open Activity Monitor to make sure that you don't have a memory leak. Check free memory and Page Outs.
Russ

Similar Messages

Using expdp to do a schema export is taking extremely long time

I am using expdp in schema mode to export a 300 gigbyte database.
The job status report 99% complete after about 2 hours .
But now the job has been running 30 hours and is not finish.
I can see that it is exporting the domain indexes and had been exporting
the last index for the last 5 hours. Something is not working because I
looked at the table the index is using and it has no data. So, why is it taking
so long to export an index that has no data?
Can someone tell if there is a way to bypass exporting indexes and a easy way
to recreate the indexes if you do?
I am using oracle 11g and expdp utility.

I checked the log file and there are no errors in the file.
There are no ORA- xxxx error messages.
The last line in the log file is as follows:
"Processing object type schema_export/table/index/domain_index/index "
I just checked the export job run this morning and it is still on the same
index object "A685_IX1" . This is a spatial index. It has been sitting at
this same object according to the job status for at least 24 hours.

ITunes taking extremely long time to import songs via various downloads...

I'm a DJ so I download music from a various amount of sources. When I try to drag and drop them into iTunes, I usually get the pinwheel of death for a while and sometimes the song shows up, other times the program just doesn't respond. I've tried clearing all my cache files (I think most of them) to speed up the process but to no avail. I have my iTunes folder on my 1TB LaCie Rugged external with a little less than half free space and my hard drive itself has plenty of room. I'm not running more than iTunes and Safari and this is still taking WAY too long. I have to load albums one song at a time and it still takes about 5-15 min per song. Any suggestions on how to remedy this?

Does this happen also with other CD rippers, like Windows Media Player, Real Player, CDEX etc etc...
Maybe you have enabled 'Use error correction when reading CD's' That can slow things down quite a bit.
Also see if you have set your audio encoding to import as VBR. This can also slow things down.

Quicktime Export taking a long time

I rendered a project. Took 4 hours. Quicktime Export took the same after the render. Did NOT export self-contained. Usually a Quicktime Export is a matter of minutes, not hours.

I've had a similar problem before. (after render) I ask it to export as a reference movie, but it still takes forever. However, when I check the supposed reference file, it turns out that it's self contained (you can tell by the size). So, check the file that was exported...if it's huge then that's a good indicator that FCP didn't recognize the referenced video command. Maybe it's time to trash preferences or some other kind of troubleshooting? Then again, this problem has been random for me, happening on some projects but not others. --David
Message was edited by: daabomb101

Time Machine backups taking extremely long time and disrupting other computing activity

I have an iMac running the latest version of Lion (10.7.4) and which I have upgraded to a one terabyte hard drive and full memory capability. I back up to a My Book 2 terabyte external hard drive using Time Machine. My iMac is often very sticky, though I've done most of the diagnostics I know of and preferences etc. are seemingly all OK and fcuk -fs gives a positive result! The Mac is often hard to wake from sleep and in particular seems to spend a lot of time backing up very-very slowly, with the result that it frustratingly seems to be backing up most of the time with the consequent effercts on using other programmes. Also the whole thing seems to grind to a halt after a hard days work with quite a few applications open. I'm wondering what can be causing this and what I can do to overcome this very frustrating and debilitating problem?

Hi
I would try the following for now and I am sorry, yes you were clear that it's an external drive.
Rebuild Spotlight
-Rebuild the spotlight index as per http://support.apple.com/kb/ht2409 as a first step. Spotlight indexes play a role in healthy backups so this is why this could be a good thing to do.
- When conducting the next backup, after the spotlight re-index, consider connecting to your mac only the external hard drive and disconnect all other devices to rule out other devices affecting things. I suggest connecting devices back one at a time followed by a triggered backup until the issue fails to reproduce itself.
General Performance Issues
- Some performance issues can also be cured through an SMC reset. This article can help in this regard, note that the steps differ depending on the model mac you use: http://support.apple.com/kb/HT3964
--In terms of the mac's general sluggishness
- SMC can help
- open Activity Monitor and check to see if CPU usage is abnormally high or any particular process is consuming an elevated amount of CPU cycles, see http://support.apple.com/kb/PH5146
Check External HD (backup drive)
- If you've run disk utility and have done a repair permissions and repair disk as per user "Radiation Mac" then there is no point doing it again but this should just be a reminder incase you missed it.
-- on a related note to disk utility try;
1) Mount your external hard drive.
2) In Disk Utility, locate your external backup drive. Your backup drive should mount in the Disk Utility sidebar when attached to your Mac.
3) Select your external backup drive.
4) Click Repair.
Test Time Machine backups against a different drive
--If you have a spare hard drive or even a small USB stick, you could back up only a very small amount of data to this second hard drive or USB stick as a test. This article outlines how to exclude from backups, http://support.apple.com/kb/HT1427
Further Ideas
Seeing the logs would be useful if the issue persists. There maybe a reason for the issue but it appears only in the logs which we may eventually need.
I almost forgot
-make sure everything is uptodate with Apple software/firmware and any firmware for your drive if applicable.
If anything is unclear, feel free to let me know, I will provide more details.

Backing up during sync taking extremely long time

i unboxed my iPad, activated, then downloaded some apps straight on the device. went back to sync about 3 hours ago and its about 75% done with the "Backing up" stage in iTunes. its definitely moving, just ever so slowly. reminds me of the slow backups in iPhone OS 2.0
anyone else seeing this?
Message was edited by: nabilshahid

My initial restore from my iPhone backup to my iPad took over an hour. I then added seven movies (~12GB) and synched the configuration changes I wanted on the iPad. That backup only took ~5 minutes on my 2.8GHz iMac with 4GB memory. I plugged directly into a USB jack on the back of the iMac.

Report script taking very long time to export in ASO

Hi All,
My report script is taking very long time to execute and finally a message appears as timed out.
I'm working on ASO Cubes and there are 14 dimensions for which i need to export all data for all the dimensions for only one version.
The data is very huge and the member count in each dimension is also huge, so which is making me difficult to export the data.
Any suggestions??
Thanks

Here is a link that addresses several ways to optimize your report script. I utilize report scripts for Level 0 exports in an ASO environment as well, however the majority of our dimemsions are attribute dimensions.
These are the most effective solutions we have implemented to improve our exports via report scripts:
1. Make sure your report script is written in the order of how the Report Extractor retrieves data.
2. Supressing Zero and Missing Data
3. We use the LINK command within reports for some dimensions that are really big and pull at Level 0
4. Using Symmetric reports.
5. Breakout the exports in multiple reports.
However, you may also consider some additional solutions outlined in this link:
1. The MDX optimizing commands
2. Back end system settings
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/drpoptim.htm
I hope this helps. Maybe posting your report script would also help users to provide feedback.
Thanks
Edited by: ronnie on Jul 14, 2011 9:25 AM
Edited by: ronnie on Jul 14, 2011 9:53 AM

Importing Assets from ALER to export to OER is taking so long time

Guys,
I am importing Service Bus Projects from ALSB ant trying to export it to Oracle Enterprise Repository 11g. But when I try to export the configuration jar to Oracle Enterprise Repository using the Harvester tool it is taking so long time.
I have more than 1500 WSDL and XSD (with some circular reference), it is running for 48 hours without finish it.
What can I do to Harvester and Oracle ER be faster ?
Do we have some configuration to turn off validation or something like this ?
Thanks in advanced.
Edited by: rrocha on 18/04/2011 14:11

Welcome to the Apple Community.
Itunes library or iTunes store.

Extremely long time when executing an export transaction data package link

Hi,
I am working in a packagelink to export transaction data to the application server. The package which I am currently using is /CPMB/EXPORT_TD_TO_APPL. I use it to generate an output file which I later use in a different appliation to register modifications applied in BPC.
It has been working correctly without problems for a time. The problem is that suddenly it stopped working. Maybe because of some changes in the dimension library (is it feasible?) . I defined and scheduled again the packagelink and it began working correctly again, but the time it takes to execute the process is really long. Approximately it takes above 10 hours, which is an extremely long time for the process. In the beginning, the packagelink was executed in an hour and a half. Could anybody tell me any idea about what can be the reason of this problem?
Any help will b much appreciated.

>      Database error text........: "POS(1) System error: BD Index not accessible"
>      Database error code........: "-602"
>      Triggering SQL statement...: "INSERT INTO "/BIC/SZD_PROD" ( "/BIC/ZD_PROD",
>       "SID", "CHCKFL", "DATAFL", "INCFL" ) VALUES ( ? , ? , ? , ? , ? )"
Hi Hari,
looks like you are hitting a BAD index.
Check the [DB50|http://help.sap.com/saphelp_nw04s/helpdata/en/9c/ca5bb3d729034aaf6f4cea2627c2f2/frameset.htm] or the DBMGUI - there should be warnings about this.
To fix this issue, either use the DBMGUI -> Recover -> [Indexes|http://maxdb.sap.com/doc/7_6/30/5ada38596211d4aa83006094b92fad/frameset.htm] function or logon to dbmcli, get an SQL session ([sql_connect|http://maxdb.sap.com/doc/7_6/11/8af4411cf5c417e10000000a155106/content.htm]) and use the [sql_recreateindex|http://maxdb.sap.com/doc/7_6/30/f7c7f25be311d4aa1500a0c9430730/content.htm] command.
Regards,
Lars

Time Machine Taking a Long Time to Index / Back Up

Hi everyone.
I noticed this on the latest backup to my Time Capsule device. I'm backing up over a WiFi connection to a time capsule device. It is taking a long time to index the backup. Here's the code from the latest backup.
10/17/12 9:43:03.799 PM com.apple.backupd: Starting standard backup
10/17/12 9:43:04.091 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:12.657 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
10/17/12 9:43:34.015 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
10/17/12 9:43:37.440 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
10/17/12 9:43:37.459 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
10/17/12 9:45:23.296 PM com.apple.backupd: 500.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:48.844 PM com.apple.backupd: Copied 1436 files (3.4 MB) from volume Macintosh HD.
10/17/12 9:46:51.897 PM com.apple.backupd: 448.1 MB required (including padding), 3.27 GB available
10/17/12 9:46:51.898 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:47:53.681 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:48:55.642 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:49:56.511 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:50:56.564 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:51:57.643 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:52:57.903 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:53:59.341 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:55:01.281 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:56:03.171 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:57:03.966 PM com.apple.backupd: Waiting for index to be ready (100)
10/17/12 9:58:33.083 PM com.apple.backupd: Copied 824 files (1.2 MB) from volume Macintosh HD.
10/17/12 9:58:40.359 PM com.apple.backupd: Starting post-backup thinning
10/17/12 9:59:51.851 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-213620 (5.6 MB)
10/17/12 10:00:17.440 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-113505 (1.6 MB)
10/17/12 10:00:30.046 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-103509 (1.6 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-10-16-093513 (1.3 MB)
10/17/12 10:00:43.781 PM com.apple.backupd: Post-back up thinning complete: 4 expired backups removed
10/17/12 10:00:45.207 PM com.apple.backupd: Backup completed successfully.
10/17/12 10:00:56.988 PM com.apple.backupd: Ejected Time Machine disk image.
10/17/12 10:00:57.550 PM com.apple.backupd: Ejected Time Machine network volume.
I am just curious as to why this is, and what I might do to fix it. I did see one suggestion in another website suggesting diabling spolight indexing of the backup image with sudo mdutil -i off /Volumes/Time Machine Backups, but don't know where to type that in. It then states to reenable it, but don't know where to type that in, either. Any advice would be helpful. I did run a verification not too long ago, and here's that code.
10/14/12 3:44:14.289 PM com.apple.backupd: Backup verification requested by user.
10/14/12 3:44:41.503 PM com.apple.backupd: Running backup verification
10/14/12 4:04:31.602 PM com.apple.backupd: Backup verification passed!
If any of you have or had a similar problem, I'd appreciate your help. For the time being, I may just disable time machine during the evening, and only have it run during the day when I'm at work.

Is your sig still current (10.7.3)? Or did you update to 10.7.5? Because 10.7.5 had a Spotlight/Time Machine bug that slowed down a lot of backups. If that's what it is, there's now a 10.7.5 Supplemental Update that fixes the slow Time Machine problem.
If it isn't 10.7.5, I don't know what the problem might be.

Time Machine Taking a Long Time to Index

Hi everyone.
I first noticed this today. My Time Machine is taking a long time to index. It's stuck on "Waiting for index to be ready (100)" for about 10 minutes at least, it seems. I did notice earlier today that it had to delete old backups to make space for new backups, and I'm wondering if that has anything to do with it. I'm in the process of doing a verification now, but here's the code from two backups earlier today.
Here's the one where it had to delete backups to make room for new and future backups.
1/30/13 5:48:13.069 PM com.apple.backupd: Starting standard backup
1/30/13 5:48:13.267 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 5:48:13.749 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 5:48:35.120 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 5:48:40.280 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 5:48:40.407 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 5:54:50.703 PM com.apple.backupd: 500.8 MB required (including padding), 403.3 MB available
1/30/13 5:55:00.163 PM com.apple.backupd: Ejected disk image: /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle
1/30/13 5:55:00.163 PM com.apple.backupd: Compacting backup disk image to recover free space
1/30/13 5:58:52.014 PM com.apple.backupd: Completed backup disk image compaction
1/30/13 5:58:52.016 PM com.apple.backupd: Starting standard backup
1/30/13 5:58:52.065 PM com.apple.backupd: Network destination already mounted at: /Volumes/Time Machine Backups
1/30/13 5:59:13.694 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 5:59:17.577 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 5:59:17.673 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 6:01:22.433 PM com.apple.backupd: 500.9 MB required (including padding), 424.6 MB available
1/30/13 6:02:40.909 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2013-01-28-225651 containing 5.8 MB; 430.4 MB now available, 500.9 MB required
1/30/13 6:02:40.909 PM com.apple.backupd: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
1/30/13 6:25:09.045 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-12-095019 containing 1.08 GB; 1.50 GB now available, 500.9 MB required
1/30/13 6:25:09.045 PM com.apple.backupd: Deleted 2 backups containing 1.09 GB total; 1.50 GB now available, 500.9 MB required
1/30/13 6:25:09.045 PM com.apple.backupd: Backup date range was shortened: oldest backup is now May 20, 2012
1/30/13 6:28:35.009 PM com.apple.backupd: Copied 2289 files (7.3 MB) from volume Macintosh HD.
1/30/13 6:28:35.920 PM com.apple.backupd: 494.0 MB required (including padding), 424.6 MB available
1/30/13 6:28:35.921 PM com.apple.backupd: No expired backups exist - deleting oldest backups to make room
1/30/13 6:30:36.145 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-20-194752 containing 55.0 MB; 479.6 MB now available, 494.0 MB required
1/30/13 6:30:36.146 PM com.apple.backupd: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
1/30/13 6:33:16.203 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-27-093117 containing 64.5 MB; 544.0 MB now available, 494.0 MB required
1/30/13 6:33:16.203 PM com.apple.backupd: Deleted 2 backups containing 119.4 MB total; 544.0 MB now available, 494.0 MB required
1/30/13 6:33:16.203 PM com.apple.backupd: Backup date range was shortened: oldest backup is now Jun 7, 2012
1/30/13 6:34:11.232 PM com.apple.backupd: Copied 1171 files (2.5 MB) from volume Macintosh HD.
1/30/13 6:34:44.355 PM com.apple.backupd: Backup completed successfully.
1/30/13 6:34:54.258 PM com.apple.backupd: Ejected Time Machine disk image.
1/30/13 6:34:54.493 PM com.apple.backupd: Ejected Time Machine network volume.
And here's the one where it started to take awhile to index.
1/30/13 7:21:11.358 PM com.apple.backupd: Starting standard backup
1/30/13 7:21:11.955 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 7:21:12.540 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 7:21:38.074 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 7:21:41.754 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 7:21:41.768 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 7:23:47.444 PM com.apple.backupd: 452.8 MB required (including padding), 401.2 MB available
1/30/13 7:23:56.687 PM com.apple.backupd: Ejected disk image: /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle
1/30/13 7:23:56.687 PM com.apple.backupd: Compacting backup disk image to recover free space
1/30/13 7:27:52.753 PM com.apple.backupd: Completed backup disk image compaction
1/30/13 7:27:52.754 PM com.apple.backupd: Starting standard backup
1/30/13 7:27:52.898 PM com.apple.backupd: Network destination already mounted at: /Volumes/Time Machine Backups
1/30/13 7:28:14.638 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 7:28:18.207 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 7:28:18.309 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 7:34:32.780 PM com.apple.backupd: 399.3 MB required (including padding), 937.6 MB available
1/30/13 7:34:32.780 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:35:32.919 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:36:34.779 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:37:36.419 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:38:37.465 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:39:39.420 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:40:40.628 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:41:41.317 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:42:42.105 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:43:42.982 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:45:20.244 PM com.apple.backupd: Copied 1381 files (6.4 MB) from volume Macintosh HD.
1/30/13 7:45:21.507 PM com.apple.backupd: 382.5 MB required (including padding), 826.5 MB available
1/30/13 7:45:21.508 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:46:22.938 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:47:24.914 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:48:25.931 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:49:26.589 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:50:27.743 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:51:27.952 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:52:28.736 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:53:29.707 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:54:30.516 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:55:31.297 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:56:33.290 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:57:35.031 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:58:36.765 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:59:37.721 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 8:00:38.577 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 8:01:48.483 PM com.apple.backupd: Copied 1069 files (5.6 MB) from volume Macintosh HD.
1/30/13 8:02:02.230 PM com.apple.backupd: Starting post-backup thinning
1/30/13 8:02:46.083 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2013-01-29-183909 (5.4 MB)
1/30/13 8:02:46.083 PM com.apple.backupd: Post-back up thinning complete: 1 expired backups removed
1/30/13 8:02:46.083 PM com.apple.backupd: Warning: backup disk now has only 644.1 MB free without removing old backups
1/30/13 8:02:46.259 PM com.apple.backupd: Backup completed successfully.
1/30/13 8:02:58.025 PM com.apple.backupd: Ejected Time Machine disk image.
1/30/13 8:02:58.407 PM com.apple.backupd: Ejected Time Machine network volume.
I'm backing up to a Time Capsule over WiFi. This time capsule has a total of 3 laptops that are backed up on it.

Never mind. Whatever it was, it's fine now. We'll see what happens when it has to delete old backups to make space. It's down to about 720 MB free without removing old backups.

Taking a long time to do JNDI lookup

Hi,
I have something like this for my JNDI lookup:
myEJBHome home = (myEJBHome) PortableRemoteObject.narrow(context.lookup("mybean") ,myEJBHome.class);
and
myEJB session = (myEJB)home.create();
Recently it's taking an EXTREMELY long time to do these 2 operations (before it took milliseconds, now it's like 10 minutes...but I haven't changed anything at all).
Any idea why?
Thanks

If the bean is in another machine more than likely the connection or firewall issue?
PC

Discoverer report taking too long time to open.

HI,
Discovere reports are taking too long time to open. Please help to resolve this.
Regards,
Bhatia

What is the Dicoverer and the Application release?
Please refer to the following links (For both Discoverer 4i and 10g). Please note that some Discoverer 4i notes also apply to Discoverer 10g.
Note: 362851.1 - Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=362851.1
Note: 68100.1 - Discoverer Performance When Running On Oracle Applications
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=68100.1
Note: 465234.1 - Recommended Client Java Plug-in (JVM/JRE) For Discoverer Plus 10g (10.1.2)
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=465234.1
Note: 329674.1 - Slow Performance When Opening Plus Workbooks from Oracle 11.5.10 Applications Home Page
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=329674.1
Note: 190326.1 - Ideas for Improving Discoverer 4i Performance in an Applications 11i Environment
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=190326.1
Note: 331435.1 - Slow Perfomance Using Disco 4.1 Admin/Desktop in Oracle Applications Mode EUL
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=331435.1
Note: 217669.1 - Refreshing Folders and opening workbooks is slow in Apps 11i environment
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=217669.1

Taking too long time to get LOV

HI,
I have created a customer folder in which the query retuns 0.5 million records.
I have created a item class in airline_name column which is being used in the worksheet as parameter.
The problem is it is taking too long time near about 2 min to get LOV when the user wants to search the exact name.
Thanks,
Himanshu Tiwari

Hi,
Usually, you should not use the folder that the report is based on to define the LOV. You should use a separate folder to define the LOV that is optimised to return the content of the LOV.
Rod West

Discoverer reports taking a long time!!!

Hi all,
One of our clients is complaining that the discoverer reports are taking a long time to run for the last few days, the report used to take 30 minutes before but now is running for hours!!
I have checked the SGA and I have killed the idle sessions but still there was no improvement in the performance.
The version of BI discoverer is 10 and database also is 10g and the platform is win server 2003.
I have checked the forums and they talk about explain plan and tkprof and other commands, but my problem is that i am unable to find the query that discoverer is running i mean once the report is clicked the query runs and gives the estimate time it would take. can some one tell me where this query is stored so that i can check this query,
Also there were no changes made in the query or to the database.
The temp space fills up 100%, i increased the size of temp space but still it goes to 100% also i noticed that the CPU utilisation goes to 100%
i also increased the SGA but still no go.
can someone kindly help me as to what could be causing this problem
also kindly guide me to some good documents for tuning the discoverer.
thanks in advance,
regards,
Edited by: user10243788 on Jan 4, 2010 12:47 AM

Hi,
The fact that the report used to work fast and now not can be related to many things but my guess is that the database statistics were changed and so the explain plan has changed.
This can be done due to change in the volume of the data that crossed a level were oracle optimizer change the behavior but it can be other things as well.
Anyway it is not relevant since it will be easier to tune the SQL than to find what have changed.
In order to find whether the problem is with the discoverer or in the SQL extract the SQL as described above and run it in SQL tool (SQL Plus, TOAD, SQL Developer and so on).
The best way to get to the problem is run a trace on your session and then use the TKPROF command to translate it to a text file you can analyze - you can assist your DBA team they should have no problem doing that.
By doing that you will get the problematic statements/ functions/ procedures that the report uses.
From there you can start working on improving the performance.
Performance is expertise for itself so i'm sorry i don't know to tell you where to start from, I guess the start will be from understanding the meaning of the explain plan.
Hope I helped a little although I wish Ii had a magic answer for you
BTW, until you resolve that problem you can use the discoverer scheduler to run the reports in the background and so the users will get the data.
Tamir

Exporting taking extremely long time

Similar Messages

Maybe you are looking for