RMAN BACKUPS  TAKING A LONG TIME IN 11.1.0.6

Its almost 4 days since the RMAN Full Backup is running and it has completed almost 91% and is stuck at this point since last 2 days, so now we killed the RMAN backup Process and started the RMAN Full Backup on Disk. We need to take the RMAN Backups on Tapes.
When we take the RMAN Full Backup to Tape manually with the same script attached, the Backup runs successfully withing Hours. While if the RMAN Full Backup is running through Cronjobs , then it takes days and it gets hung.
Initially it happened with Full backup , now Incremental Backup is also not working.
Log File of Current RMAN Incremental Backup Running and in Hung state
Recovery Manager: Release 11.1.0.6.0 - Production on Mon Nov 5 20:00:02 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ZSBO (DBID=4052190355)
RMAN>
2>
3>
4> run{
5> allocate channel t1 type 'SBT_TAPE'
6> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
7> allocate channel t2 type 'SBT_TAPE'
8> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
9> allocate channel t3 type 'SBT_TAPE'
10> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
11> allocate channel t4 type 'SBT_TAPE'
12> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
13> backup
14> incremental level 2
15> format 'Incremental_zsbo_%U_%t'
16> (database);
17> sql "alter system archive log current";
18> backup
19> format 'arch_zsbo_%d_%s_%p_%t'
20> (archivelog from time 'sysdate-1' all delete input);
21> release channel t1;
22> release channel t2;
23> release channel t3;
24> release channel t4;
25> }
26>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=2086 device type=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: t2
channel t2: SID=2075 device type=SBT_TAPE
channel t2: NMO v4.5.0.0
allocated channel: t3
channel t3: SID=2069 device type=SBT_TAPE
channel t3: NMO v4.5.0.0
allocated channel: t4
channel t4: SID=2061 device type=SBT_TAPE
channel t4: NMO v4.5.0.0
Starting backup at 05-NOV-12
channel t1: starting incremental level 2 datafile backup set
channel t1: specifying datafile(s) in backup set
input datafile file number=00096 name=/data13/oradata/zsbo/A0186LA2591_00_CURR_12.dbf
input datafile file number=00058 name=/data17/oradata/zsbo/A0436IL2022_00_PREV_01.DBF
input datafile file number=00014 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_01.dbf
input datafile file number=00087 name=/data7/oradata/zsbo/A1086IL2502_00_PREV_01.dbf
input datafile file number=00045 name=/data7/oradata/zsbo/A1143BO2515_00_CURR_IDX_01.dbf
input datafile file number=00130 name=/data7/oradata/zsbo/A0171LA2034_01_DEMO_IDX_01.dbf
input datafile file number=00080 name=/data7/oradata/zsbo/A0436IL2022_00_CURR_IDX_02.DBF
input datafile file number=00119 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_05.dbf
input datafile file number=00136 name=/data5/oradata/zsbo/A1225NY2502_00_TEMP_11.dbf
channel t1: starting piece 1 at 05-NOV-12
channel t2: starting incremental level 2 datafile backup set
channel t2: specifying datafile(s) in backup set
input datafile file number=00095 name=/data12/oradata/zsbo/A0186LA2591_00_CURR_11.dbf
input datafile file number=00075 name=/data17/oradata/zsbo/A0186LA2591_00_CURR_IDX_02.dbf
input datafile file number=00094 name=/data6/oradata/zsbo/A0186LA2591_00_CURR_10.dbf
input datafile file number=00151 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_06.dbf
input datafile file number=00148 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_02.dbf
channel t2: starting piece 1 at 05-NOV-12
channel t3: starting incremental level 2 datafile backup set
channel t3: specifying datafile(s) in backup set
input datafile file number=00127 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_01.dbf
input datafile file number=00018 name=/data15/oradata/zsbo/A1225NY2502_00_TEMP_05.dbf
input datafile file number=00062 name=/data15/oradata/zsbo/A0436IL2022_00_TEMP_02.dbf
input datafile file number=00081 name=/data15/oradata/zsbo/A1110CH2505_00_PREV_01.dbf
input datafile file number=00137 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_12.dbf
input datafile file number=00065 name=/data18/oradata/zsbo/A1086IL2003_00_CURR_01.dbf
input datafile file number=00103 name=/data2/oradata/zsbo/A0186LA2591_00_PREV_05.dbf
channel t3: starting piece 1 at 05-NOV-12
channel t4: starting incremental level 2 datafile backup set
channel t4: specifying datafile(s) in backup set
input datafile file number=00059 name=/data6/oradata/zsbo/A0436IL2022_00_PREV_02.DBF
input datafile file number=00068 name=/data5/oradata/zsbo/A0186LA2591_00_CURR_01.dbf
input datafile file number=00071 name=/data9/oradata/zsbo/A0186LA2591_00_CURR_04.dbf
input datafile file number=00078 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_01.dbf
channel t4: starting piece 1 at 05-NOV-12 ----> No Progress since last 10 hours
Any help will be appreciated.
Regards,
Mohit
Edited by: 969777 on Nov 6, 2012 4:29 AM

Hi,
We have upgraded our database from 10.2.0.3 to 11.1.0.6.
The Script runs fine when we take command line backup on disk which we took 6 days backup, but when we schedule the same on cronjob RMAN Full Backup completes till 91% and it hangs forever. Everything was running fine with Incremental backup which we took 2 days before and it ran successfully but the above log is of Incremental Backup which is still in Hang state from the last 10 Hours , but still showing no Errors.
Please let me know if anything you want to confirm.
Thanks for ur prompt response,
Mohit

Similar Messages

  • Rman restore taking unexpectedly long time

    Dear ALL,
    I have 3 TB of database which I am restoring from a hot backup on tape drive.
    Backup of this database took 7 hours but restoration of a single tablespace(800 GB) takes more than 3 days.
    Any idea ,why it is taking so much time.
    Just out of curiosity : Which is faster- restore database/restore tablespace /restore datafile in terms of bytes restored per second?
    Regards
    Saket Bansal
    Edited by: saket bansal on 11-Feb-2010 04:05

    Not enough information to advise. Your bottleneck may be on the Tape read, IO write, or even network.
    Depending on where the bottleneck is, you may increase speed by restoring from multiple channels, to faster disk, or from compressed backup pieces.
    Restore database should be faster because then rman can decide the fastest way to restore.

  • Backup taking a long time

    My time machine backup has been taking a really long time. According to Time Machine Buddy the latest back up started yesterday at 1:02 am and it is now 1:49 pm. So over 36 hours and it is only 9.6 Megs into 1GB, at least according to the TM drop down menu in the menu bar.
    The log shows the following. So I'm wondering what the problems are with spotlight and I'm wondering why the number of items has changed. Also why does it show different GB sizes than reported in the drop down?
    Copied 3.8 GB of 9.5 GB, 9601 of 21446 items
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Copied 3.9 GB of 9.5 GB, 11141 of 21446 items
    Copied 3.9 GB of 9.5 GB, 11860 of 21446 items
    Copied 3.9 GB of 9.5 GB, 12606 of 21446 items
    Copied 3.9 GB of 9.5 GB, 13227 of 21446 items
    Copied 3.9 GB of 9.5 GB, 13968 of 21446 items
    Copied 3.9 GB of 9.5 GB, 14740 of 21446 items
    Bulk setting Spotlight attributes failed.
    Copied 3.9 GB of 9.5 GB, 15515 of 21446 items
    Copied 3.9 GB of 9.5 GB, 16235 of 21446 items
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Copied 3.9 GB of 9.5 GB, 16723 of 21446 items
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Copied 3.9 GB of 9.5 GB, 18358 of 21446 items
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Copied 3.9 GB of 9.5 GB, 19741 of 21446 items
    Bulk setting Spotlight attributes failed.
    Bulk setting Spotlight attributes failed.
    Copied 3.9 GB of 9.5 GB, 21858 of 21858 items
    Bulk setting Spotlight attributes failed.
    Copied 4.1 GB of 9.5 GB, 23890 of 23890 items
    Copied 4.3 GB of 9.5 GB, 26074 of 26074 items
    Copied 4.5 GB of 9.5 GB, 28175 of 28175 items

    It's clearly stuck. Cancel the backup (if it won't cancel, see #D6 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum).
    Is this your first backup to this destination? If so, make sure your drive is set up properly, per #C1 in the Troubleshooting Tip.
    Otherwise, this looks like a problem with your TM drive, or communicating with it. Try the things in #D2 of the Troubleshooting Tip. If that doesn't help, try a +*Verify Disk+* (not permissions) on your internal HD, per #A5 there. As it says, if that shows errors, you'll have to use the procedure in the yellow box there to repair them.
    If none of those help, post back with all the messages from the latest attempt (but don't let it run anywhere near that long with no progress), and details of the destination for your backups.

  • Backup taking a LONG time, excruciating

    Hello,
    I'm using Time Machine to backup my MBP to a Time Capsule disk, and it is taking absolutely forever.
    It started at 7:30 this morning, doing that "deep traversal" thing, and then started copying files at around 9:15. Now, at 12:00, it has gotten all the way up to "609 KB of 46.2 GB". I have excluded the backup disk from Spotlight indexing.
    Does anyone have any idea what is going on?
    Thanks...

    The "deep traversal" thing means that TM isn't sure that what's on your internal HD matches it's records. So it has to look at every file and folder on your system, and compare them to what's on your TM backups just to figure out what needs to be backed-up. That's a long process on a F/W 800 disk; but, as you see, excruciating on a TC.
    As NeroWolfe says, plugging your TC directly to your Mac with the Ethernet cable can speed this up greatly.
    The "deep traversal" can be caused by several things. The usual suspects are an improper shutdown (which can also corrupt data on your internal HD), certain hardware repairs, a full restore, or going several days without a successful backup.
    If you see this when you think you shouldn't, you need to post back and investigate the cause.
    By the way, you should also exclude your TM disk from any anti-virus scanning.

  • 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.

  • Restore from backup of my iphone is taking a long time

    Restore from backup of my iphone is taking a long time, so far about 12 hours! Is this normal?
    I updated to ios5 and all seemed fine, later I realised that my music wasnt on the iphone, so pluged back into my computer and it said that the restore of the iphone had not completed successfully (or something along those lines). I went to restore from backup and selected restore from a back up of my iphone. All appeared to be going ok with the time remaining coming down to less that 10 seconds now for the past 11 hours it has been increasing and now the time remaining is about 17 minutes!
    Anyone know whats happening? Or what I should do? If anything, or should I just leave it restoring??
    Thanks for any help.

    A bit late, but I wonder if a Reset would be enough? Or even just turning it off and back on?
    Phil

  • 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.

  • Computer still taking a long time to boot

    I have a late 2013 21.5” iMac (Model: ME087LL/A) with a 1TB hard drive (5400 rpm).  I just switch from Windows to Mac, so I tried to keep everything as simple as possible on the transfer of files.  I had only added Kaspersky Antivirus and Western Digital Tools. 
    Boot times and operation seemed normal so I transferred my music, pictures, and some files.  My computer started running slow with just one user and started taking a long time to boot.  I found that since I added about 24,000 pictures to iPhoto, the Mac was trying to send all these pictures to iCloud in the background.  I stopped using iCloud for iPhoto and that seemed to speed up the normal operation once the computer is booted. 
    The computer still seemed to take a very long time to boot.  It would now take 3 minutes to get from turning it on to being able to use Safari.  I uninstalled Kaspersky Antivirus and Western Digital Tools using each company’s uninstallers so I know they are completely off the computer. 
    Any ideas on how to get back to the fast boot time?  I am only using about 150 GBs of the 1 T drive so I don’t think that is causing the issue.  What should I expect for a boot time on a brand new Late 2013 iMac?  Or should I try to re-install Maverick and try to get a fresh start?
    Any advice would be appreciated so I don’t feel like I made the wrong choice going to Mac.  I'm kicking myself because the computer was so fast when I just got it.

    Seventy one thanks for trying to help me out.  I really appreciate it.  Log is below.  You are absolutely right. Kaspersky and WD look like they still have something (as well as google??).  Is there anything else that stands out?  How would I go about getting rid of them?  Re-Install?  Clean Re-Install?
    EtreCheck version: 1.9.12 (48)
    Report generated June 16, 2014 at 6:19:51 PM EDT
    Hardware Information:
              iMac (21.5-inch, Late 2013) (Verified)
              iMac - model: iMac14,3
              1 2.9 GHz Intel Core i5 CPU: 4 cores
              8 GB RAM
    Video Information:
              NVIDIA GeForce GT 750M - VRAM: 1024 MB
                        iMac 1920 x 1080
    System Software:
              OS X 10.9.3 (13D65) - Uptime: 0 days 0:8:41
    Disk Information:
              APPLE HDD HTS541010A9E662 disk0 : (1 TB)
                        EFI (disk0s1) <not mounted>: 209.7 MB
                        Macintosh HD (disk0s2) / [Startup]: 999.35 GB (847.45 GB free)
                        Recovery HD (disk0s3) <not mounted>: 650 MB
    USB Information:
              Apple Inc. BRCM20702 Hub
                        Apple Inc. Bluetooth USB Host Controller
              Apple Inc. FaceTime HD Camera (Built-in)
    Thunderbolt Information:
              Apple Inc. thunderbolt_bus
    Gatekeeper:
              Mac App Store and identified developers
    Kernel Extensions:
              [loaded] com.kaspersky.kext.klif (3.0.3a40) Support
              [loaded] com.kaspersky.nke (1.6.3a13) Support
    Launch Daemons:
              [loaded] com.adobe.fpsaud.plist Support
              [loaded] com.microsoft.office.licensing.helper.plist Support
              [loaded] com.westerndigital.ErasePrivilegedHelper.plist Support
    User Launch Agents:
              [loaded] com.google.keystone.agent.plist Support
    User Login Items:
              None
    Internet Plug-ins:
              SharePointBrowserPlugin: Version: 14.4.2 - SDK 10.6 Support
              FlashPlayer-10.6: Version: 14.0.0.125 - SDK 10.6 Support
              Flash Player: Version: 14.0.0.125 - SDK 10.6 Support
              QuickTime Plugin: Version: 7.7.3
              Default Browser: Version: 537 - SDK 10.9
    Audio Plug-ins:
              BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
              AirPlay: Version: 2.0 - SDK 10.9
              AppleAVBAudio: Version: 203.2 - SDK 10.9
              iSightAudio: Version: 7.7.3 - SDK 10.9
    iTunes Plug-ins:
              Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
    3rd Party Preference Panes:
              Flash Player  Support
    Time Machine:
              Skip System Files: NO
              Mobile backups: OFF
              Auto backup: YES
              Volumes being backed up:
                        Macintosh HD: Disk size: 930.71 GB Disk used: 141.47 GB
              Destinations:
                        Mac Backup [Local] (Last used)
                        Total size: 2 
                        Total number of backups: 5
                        Oldest backup: 2014-06-08 00:03:53 +0000
                        Last backup: 2014-06-16 03:07:06 +0000
                        Size of backup disk: Adequate
                                  Backup size 2  > (Disk used 141.47 GB X 3)
              Time Machine details may not be accurate.
              All volumes being backed up may not be listed.
    Top Processes by CPU:
                   2%          WindowServer
                   1%          fontd
                   0%          hidd
                   0%          dpd
    Top Processes by Memory:
              98 MB          Finder
              74 MB          WindowServer
              66 MB          ocspd
              66 MB          mds_stores
              66 MB          Dock
    Virtual Memory Information:
              5.37 GB          Free RAM
              1.69 GB          Active RAM
              233 MB          Inactive RAM
              731 MB          Wired RAM
              233 MB          Page-ins
              0 B          Page-outs

  • Time machine taking a LONG time

    I have a IMac with OS Mountain Lion, and I backup automatically through Time Machine to a My Book.  Ever since I updated the OS the backups are taking a long time.  The initial backup after updating the OS took 3 1/2 days.  It did finally end and then they seemed to be taking the "normal" amount of time, minutes versus hours or days.  The last backup has been running since last Thursday night, and today is Tuesday.  It is showing "backing up 3.21GB of 3.53 GB".  I have been writing down where it is at before going to bed and last night it was 3.20 GB of 3.53 GB.  At 1 GB per day I have about 22 days left.  That seems a bit strange.  This last backup had been taking a long time and I've stopped it once and restarted.    Is this a current issue with the latest OS?  Any suggestions?

    Ok, I was trying to check something else and accidentally stopped the backup that had been running from last Thursday.   I restarted my computer and began another backup.  It is running now and here are the messages from the "console" from when I began the back up.  It is still running.  It started at 213.1 mb of 1.68 gb and has gone up to  11.91 gb of 13.10 gb.
    8/21/12 9:21:18.367 PM com.apple.backupd[320]: Starting manual backup
    8/21/12 9:21:19.110 PM com.apple.backupd[320]: Backing up to: /Volumes/My Book/Backups.backupdb
    8/21/12 9:21:24.179 PM com.apple.backupd[320]: Using file event preflight for Macintosh HD
    8/21/12 9:21:34.000 PM kernel[0]: Sandbox: sandboxd(325) deny mach-lookup com.apple.coresymbolicationd
    8/21/12 9:21:35.247 PM sandboxd[325]: ([324]) mdworker(324) deny file-write-create /private/var/folders/f1/9cxkqg6s73j_63tfftkrcktw0000gn/T/TemporaryItems (import fstype:hfs fsflag:480D000 flags:240000005E diag:0 uti:com.apple.iphoto.ipspot plugin:/Library/Spotlight/iPhoto.mdimporter - find suspect file using: sudo mdutil -t 8935199)
    8/21/12 9:21:35.251 PM sandboxd[325]: ([324]) mdworker(324) deny file-write-create /Users/VandenHeuvel/Pictures/iPhoto Library/.ipspot_update.sb-4015bbeb-kVJcRk (import fstype:hfs fsflag:480D000 flags:240000005E diag:0 uti:com.apple.iphoto.ipspot plugin:/Library/Spotlight/iPhoto.mdimporter - find suspect file using: sudo mdutil -t 8935199)
    8/21/12 9:21:35.278 PM com.apple.backupd[320]: Will copy (1.53 GB) from Macintosh HD
    8/21/12 9:21:35.774 PM com.apple.backupd[320]: Found 7193 files (1.53 GB) needing backup
    8/21/12 9:21:35.829 PM com.apple.backupd[320]: 3.24 GB required (including padding), 746.69 GB available
    8/21/12 9:21:50.673 PM mdworker32[326]: CGSGetDisplayBounds: Invalid display 0x00000000
    8/21/12 9:24:10.720 PM mdworker[302]: FontImporter: Validation failed - "/Library/Application Support/Adobe/PDFL/9.0/Fonts/Adobe Sans MM".
    8/21/12 9:24:10.000 PM kernel[0]: Sandbox: sandboxd(348) deny mach-lookup com.apple.coresymbolicationd
    8/21/12 9:24:10.721 PM mdworker[302]: FontImporter: Validation Result - "(
        kATSFontTestSeverityFatalError
    8/21/12 9:24:10.756 PM mdworker[302]: FontImporter: Validation failed - "/Library/Application Support/Adobe/PDFL/9.0/Fonts/Adobe Serif MM".
    8/21/12 9:24:10.757 PM mdworker[302]: FontImporter: Validation Result - "(
        kATSFontTestSeverityFatalError
    8/21/12 9:24:10.766 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.771 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.776 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.782 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.787 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.807 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.811 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.815 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.818 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.822 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.825 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.829 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSanMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994784)
    8/21/12 9:24:10.833 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.836 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.840 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.844 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.847 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.851 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.855 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.858 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM/..namedfork/rsrc (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:10.862 PM sandboxd[348]: ([302]) mdworker(302) deny file-read-data /Library/Application Support/Adobe/PDFL/9.0/Fonts/AdobeSerMM (import fstype:hfs fsflag:480D000 flags:200000056 diag:0 uti:com.apple.font-suitcase plugin:/Library/Spotlight/Font.mdimporter - find suspect file using: sudo mdutil -t 994785)
    8/21/12 9:24:12.070 PM mdworker[302]: FontImporter: Validation failed - "/Library/Application Support/Adobe/PDFL/9.0/Fonts/Symbol".
    8/21/12 9:24:12.070 PM mdworker[302]: FontImporter: Validation Result - "(
        kATSFontTestSeverityFatalError
    8/21/12 9:29:12.941 PM mdworker32[369]: CGSGetDisplayBounds: Invalid display 0x00000000
    8/21/12 9:31:50.000 PM kernel[0]: (default pager): [KERNEL]: ps_allocate_cluster - send HI_WAT_ALERT
    8/21/12 9:31:50.000 PM kernel[0]: macx_swapon SUCCESS
    8/21/12 9:32:09.604 PM Dock[218]: no information back from LS about running process
    8/21/12 9:34:41.169 PM firefox[423]: -_scrollPhase is deprecated for NSScrollWheel. Please use -momentumPhase.
    8/21/12 9:34:41.169 PM firefox[423]: -_continuousScroll is deprecated for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
    8/21/12 9:34:41.170 PM firefox[423]: -deviceDeltaY is deprecated for NSScrollWheel. Please use -scrollingDeltaY.
    8/21/12 9:34:41.170 PM firefox[423]: -deviceDeltaX is deprecated for NSScrollWheel. Please use -scrollingDeltaX.
    8/21/12 9:41:43.490 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:41:43.491 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:41:43.513 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:41:43.513 PM helpd[268]: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
    8/21/12 9:44:02.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
    8/21/12 9:44:02.000 PM kernel[0]: macx_swapon SUCCESS

  • Update of latest ios taking a long time

    I have the first ipad and am doing the update to the latest ios version through a PC.  I am trying to install the download; however, it is taking a long time (more than an hour) and seems to be stuck on the backing up stage.  I'm afraid to stop it because it took me five times already just to download the update (over an hour long each) before I realized that I needed to turn off my antivirus to have it download successfully.  Now that it's stuck trying to do the actual update, do I try to stop it and start over or should I just let it run?  Is there something else I should be turning off to have this run more quickly or successfully?

    I finally decided to stop the install because it didn't appear to have any activity in the CPU.  After doing this, it had trouble stopping as well and I had to force a shut down of iTunes.  Then I had issues trying to rerun the install because it would tell me that it was having trouble starting a session for the backup.  To resolve this, I deleted all the backups in iTunes and had to restart my iPad.  After restarting, I was able to do a normal, manual backup of the iPad, so I then tried running the installation again and was successful.

  • 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

  • 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

Maybe you are looking for