Snow Leopard slow to sleep after upgrade install
I installed the new 10.6 on two iMacs, one that had Tiger and one Leopard. the Tiger upgrade takes the normal time - about 2 seconds -when putting it to sleep, but the Leopard upgrade takes 30 seconds.
what happened? Or Why? How to fix?
I have the same problem with an MBA that takes 30s to go to sleep. I tried the terminal session you suggested and got the following back as the only entry with 30000 in it:
* Domain: applicationresponse.timedout
- Message: Kernel cupsd com.apple.powermanagement.applicationresponse.timedout 30000 ms
- Time: 17/05/2011 15:16:54 GMT+01:00
- Signature: cupsd
- UUID: 348D380F-4A44-4B7F-A113-3BDA08B5843E
- Result: Noop
- Response time (ms): 30000
Trouble is I am not sure how to interpret this into a next action.
Similar Messages
-
Macbook Pro is slow to sleep after upgrading to Lion; pmset -g question
Two months ago I updated from early '08 MBP from Snow Leopard to Lion and increased my memory from 2GB to 4GB. In doing so, I noticed that my MBP will sometimes take 30 seconds to go to sleep, regardless of what applications are running. I've put in an Apple Support ticket, and I have done everything from uninstalling and reinstalling Lion, SMS resets, and last erase harddrive and rei-install Lion and then migrate my user and apps back over. Incidentally I noticed that when I erased hard drive and re-installed Lion prior to migrating my user and apps over my MBP performed normally (as far as instant sleep is concerned). After I migrated my apps and user profile back over, the slow to sleep issue re-appeared.
I've seen several articles on the forum regarding pmset -g commands and terminal. However I'm not familiar with the pmset commands and what they actually mean. I've also seen articles about chaning the pmset -g, but mostly those are related to MBP with retinas running Mountain Lion. I did come acress an article that suggested I review my pmset -g assertions to see what may be preventing the slow to sleep issue. I'm posting this below:
Assertion status system-wide:
PreventUserIdleDisplaySleep 0
CPUBoundAssertion 0
DisableInflow 0
ChargeInhibit 0
PreventSystemSleep 0
PreventUserIdleSystemSleep 1
ExternalMedia 0
DisableLowPowerBatteryWarnings 0
EnableIdleSleep 1
NoRealPowerSources_debug 0
UserIsActive 0
ApplePushServiceTask 0
Listed by owning process:
pid 8391: [0x000020c7012c0040] PreventUserIdleSystemSleep named: "Address Book Source Sync"
My question concerns the Listed by owning process. It appears my "Address Book Source Sync" may be interfering with my system sleep. If so, can someone confirm if my assumption is correct? It should be noted that I have disabled my iCloud and Exchange address book and yet I still get the sporadic slow to sleep. Can you tell me what the "Address Book Source Sync" means and what this command means, and if this may be interfering with my sleep?
I'm waiting on a call back from an Apple Senior Technician regarding my case. Up until now, the technician has seemed to disregard looking at my pmset settings.
Thanks.Not enough free space on the startup disk can slow the system down.
Click the Apple menu icon top left in your screen. From the drop down menu click About this Mac > More Info > System Report then select Storage on the left under Hardware.
You'll see Available and Capacity. Make sure there's at least 15% free disk space. -
Macbook Pro is slow to sleep after upgrading to Lion
I just updated my Early 2008 15-inch Macbook Pro 2.4 Ghz from 2 GB to 4 GB as well as upgraded my OSX to Lion (10.7.5) from Snow Leopard (10.6.8). I have noticed since the memory and OSx upgrade my Mac is slow to go to Sleep. It may take up to 30-40 seconds for it to go Sleep. Sometimes it will instantly go to Sleep, however most of the time there is a significant delay. I have not experienced any delay or issues when waking up my Mac from sleep status, but it is very slow to go to Sleep now. In prior versions of OSx my Mac would always instantly go to sleep. I've researched some discussion threads and I've found some topics relating to resetting the pmset code. I was hoping someone a lot more knowledgeable than me can help me troubleshoot this issue. If it is the pmset, can someone give me detailed instructions on what to review and how to correct? I see where this was posted from a previous thread but alas I'm at a loss on how to correct...https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages /10.7/man1/pmset.1.html. Thanks.
EricNot enough free space on the startup disk can slow the system down.
Click the Apple menu icon top left in your screen. From the drop down menu click About this Mac > More Info > System Report then select Storage on the left under Hardware.
You'll see Available and Capacity. Make sure there's at least 15% free disk space. -
Macbook pro 2011 slow to sleep after upgrade from SL to Maveriks
Hi
i have a problem...after upgrade to Mav. (from the app store) my computer need 50+ sec to go to sleep mode. why?
i search for the causes here: http://support.apple.com/kb/HT1776 but nothing.....
i think that the only way is by terminal with "pmset -g log" but i don't understand.I have noticed this exact same issue last night/today. I upgraded last night as well.
I have been chatting with apple support and have tried Safe boot, SMC reset, PRAM/NVRAM reset, testing on a new user account.
Nothing seems to be fixing it, is it a known OS issue. As having a mechanical HDD with a sleep time of 30 seconds is potentially a problem.
I upgraded from Snow Leopard which had a shutdown/sleep time of a 1-2 seconds. I'm considering going back to Snow Leopard. -
While installing snow leopard 10.6 on macbook pro, install begins then disc is ejected after a few minutes?
Does the disc look like this DVD?
-
If I upgrade to Snow Leopard, will I have to re-install software such as Logic Studio?
If I upgrade to Snow Leopard, will I have to re-install software such as Logic Studio? Do I lose EVRYTHING?
You normally will not lose anything, but you may have to reinstall some applications since some applications place files in locations that may not be carried over to the new installation. Logic Studio may well fall into this category, though I don't know for sure. You should confirm compatability of your applications with Snow Leopard before you upgrade, since some applications may require upgrading to work properly (or at all). You should also have a good backup - I usually suggest making a complete clone of your current hard drive to an external drive - before attempting the upgrade.
Regards. -
I am currently using Leopard but need Snow Leopard to be able to get Mountain Lion. I can see this is no longer available from Apple. How would I get it so I could then get Mountain Lion. I want the Logic 9 Mac App Store App as I don't want to have to buy the whole Logc 9 from Studio 8.
Some help would be much appreciated.
Thanks
AdamUpgrading to Mountain Lion
You can upgrade to Mountain Lion from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99. To access the App Store you must have Snow Leopard 10.6.6 or later installed.
If you need to purchase Snow Leopard contact Customer Service: Contacting Apple for support and service. The price is $29.00 plus tax. You will receive physical media - DVD - by mail.
Third-party sources for Snow Leopard are:
Snow Leopard from Amazon.com
Snow Leopard from eBay
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store.
If you need to purchase Lion contact Customer Service: Contacting Apple for support and service. The cost is $19.99 (as it was before) plus tax. It's a download.
Be sure your computer meets the minimum requirements:
Apple - OS X Mountain Lion - Read the technical specifications.
Macs that can be upgraded to OS X Mountain Lion
iMac (Mid 2007 or newer)
MacBook (Late 2008 Aluminum, or Early 2009 or newer)
MacBook Pro (Mid/Late 2007 or newer)
MacBook Air (Late 2008 or newer)
Mac mini (Early 2009 or newer)
Mac Pro (Early 2008 or newer)
Xserve (Early 2009)
Are my applications compatible?
See App Compatibility Table - RoaringApps - App compatibility and feature support for OS X & iOS.
For a complete How-To introduction from Apple see Apple - Upgrade your Mac to OS X Mountain Lion. -
HT1338 Where can I buy Snow Leopard so that I may upgrade to Lion?
Where can I buy Snow Leopard so that I may upgrade to Lion?
If you need to purchase Snow Leopard contact Customer Service: Contacting Apple for support and service. The price is $29.00 plus tax. You will receive physical media - DVD - by mail.
Third-party sources for Snow Leopard are:
Snow Leopard from Amazon.com
Snow Leopard from eBay
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store.
If you need to purchase Lion contact Customer Service: Contacting Apple for support and service. The cost is $19.99 (as it was before) plus tax. It's a download. -
I have a Macbook pro 2009 with Snow Leopard. Which system can I install without running into complicated problems which I will not be able to solve by myself- a person with limited problem solving abilities. (Mountain Lion, Mavericks, Yosemite?)
It will make it easier to help you w/ your problem to know the size and RAM installed.
"Yesterday I couldn't update the maps on my Garmin because it said the OS I had wouldn't work"
What OS will your Garmin work with? Funny there was someone else that did that and upgraded to Yosemite and regretted it.
I'd say Lion if your Garmin is compatible.
Both Lion and Mountain Lion are downloadable from the Apple Store:
http://store.apple.com/us/product/D6106Z/A/os-x-lion
http://store.apple.com/us/product/D6377Z/A/os-x-mountain-lion
The OSs will get more resource hungry the higher you go. -
Need Snow Leopard (in 2013), to then upgrade further. How to get it?
I have Leopard (10.5.8), from 2009. I need to upgrade to Snow Leopard in order to then upgrade to Lion, then Mountain Lion. How can I get / access / purchase / download / install Snow Leopard today, in 2013?
I live in Switzerland (nearly 3 hours away from the nearest Apple Store). I no longer have any guarantee or warranty so cannot get telephone advice without paying a lot. Looking forward to hear your suggestions!Start by checking if you can run Snow Leopard:
Requirements for OS X 10.6 'Snow Leopard'
http://support.apple.com/kb/SP575
The OS 10.6 Snow Leopard install DVD is available for $19.99 from the Apple Store:
http://store.apple.com/us/product/MC573/mac-os-x-106-snow-leopard
and in the UK:
http://store.apple.com/uk/product/MC573/mac-os-x-106-snow-leopard
but nobody knows for how long it will be available.
When you have installed it, run Software Update to download and install the latest updates for Snow Leopard.
You should now see the App Store icon, and you now need to set up your account:
http://support.apple.com/kb/HT4479
To use iCloud you have to upgrade at least to Lion, but some functions are only available in Mountain Lion:
http://support.apple.com/kb/HT4759
You can also purchase the code to use to download Lion (Lion requires an Intel-based Mac with a Core 2 Duo, i3, i5, i7 or Xeon processor and 2GB of RAM, running the latest version of Snow Leopard), or you can purchase Mountain Lion from the App Store - if you can run that:
http://www.apple.com/osx/specs/ -
Hi! Just bought Snow leopard 10.6.3 and upgraded my 2008 iMAC; now want to use the free upgrade to Mavericks like I was advised in the Apple/Switch store... is that possible? I read compatibility requirement of 10.6.8 or later...???? Thanks for any guidance!
Before installation you should back up all your data.
When you have installed it, run Software Update to download and install the latest updates for Snow Leopard to bring it up to 10.6.8, or download the combo update from here:
http://support.apple.com/kb/DL1399
Check via Software Update whether any further updates are required, particularly to iTunes (you will need the latest version in order to synch with mobile devices).
You should now see the App Store icon in iTunes, and you now need to set up your account:
http://support.apple.com/kb/HT4479
You can now upgrade to Mavericks OS 10.9 for free IF you have one of the following Macs, with not less than 2GB of RAM, and at least 8GB of available space on your hard drive:
iMac (Mid-2007 or later)
MacBook (13-inch Aluminum, Late 2008), (13-inch, Early 2009 or later)
MacBook Pro (13-inch, Mid-2009 or later), (15-inch, Mid/Late 2007 or later), (17-inch, Late 2007 or later)
MacBook Air (Late 2008 or later)
Mac Mini (Early 2009 or later)
Mac Pro (Early 2008 or later)
Xserve (Early 2009)
iCloud system requirements:
http://support.apple.com/kb/ht4759
If you cannot run Mavericks you can purchase the code to use to download Lion from the App Store (Lion requires an Intel-based Mac with a Core 2 Duo, i3, i5, i7 or Xeon processor and 2GB of RAM, running the latest version of Snow Leopard):
http://store.apple.com/us/product/D6106Z/A/os-x-lion
or Mountain Lion:
http://store.apple.com/us/product/D6377Z/A/os-x-mountain-lion -
I just bought snow leopard is mountain lion after that?
I just Purchased snow leopard. I was told i need it to download the new itunes, so my iphone 5 can get my contacts.
Itunes says I need 10.6.8
Im confused?That is correct. Install Snow Leopard on your computer. Download and install Mac OS X 10.6.8 Update Combo v1.1.
This will give you access to the App Store where you can purchase and download Mountain Lion. See:
You can upgrade to Mountain Lion from Lion or directly from Snow Leopard. Mountain Lion can be downloaded from the Mac App Store for $19.99. To access the App Store you must have Snow Leopard 10.6.6 or later installed.
Upgrading to Lion
If your computer does not meet the requirements to install Mountain Lion, it may still meet the requirements to install Lion.
You can purchase Lion by contacting Customer Service: Contacting Apple for support and service - this includes international calling numbers. The cost is $19.99 (as it was before) plus tax. It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
Lion System Requirements
1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
or Xeon processor
2. 2GB of memory
3. OS X v10.6.6 or later (v10.6.8 recommended)
4. 7GB of available space
5. Some features require an Apple ID; terms apply.
Upgrading to Mountain Lion
To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
OS X Mountain Lion - System Requirements
Macs that can be upgraded to OS X Mountain Lion
1. iMac (Mid 2007 or newer)
2. MacBook (Late 2008 Aluminum, or Early 2009 or newer)
3. MacBook Pro (Mid/Late 2007 or newer)
4. MacBook Air (Late 2008 or newer)
5. Mac mini (Early 2009 or newer)
6. Mac Pro (Early 2008 or newer)
7. Xserve (Early 2009)
Are my applications compatible?
See App Compatibility Table - RoaringApps - App compatibility and feature support for OS X & iOS.
Am I eligible for the free upgrade?
See Apple - Free OS X Mountain Lion upgrade Program. -
Slow down Database after upgrading to 10.2.0.5
Hi
I am having performance problems after upgrading to 10.2.0.5
At the beginning I thought the problem was sga too smalle ( ini: 598M , now 1408M ) but even after recreating the database with the new value the problem remains.
I am sending reports so that someone could give me an idea.
Thanks in advance!
DETAILED ADDM REPORT FOR TASK 'TASK_240' WITH ID 240
Analysis Period: 22-JUN-2011 from 08:34:06 to 16:00:13
Database ID/Instance: 2462860799/1
Database/Instance Names: DXT/DXT
Host Name: thoracle
Database Version: 10.2.0.5.0
Snapshot Range: from 71 to 78
Database Time: 6726 seconds
Average Database Load: .3 active sessions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FINDING 1: 38% impact (2540 seconds)
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
PLAN_HASH 2734400036
select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
:"SYS_B_01" from sys.all_objects a where a.object_type IN
(:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
and c.table_name = a.object_name and a.object_type IN
(:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
min(b.position), max(b.overload) from sys.all_arguments b where
b.package_name IS NOT NULL and b.owner
like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
b.object_name), min(b.position), max(b.overload) from
sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
and c.table_name = b.package_name and b.package_name IS NOT NULL and
c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
and c.table_owner=b.package_name and c.table_name=b.object_name and
c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
times and had an average elapsed time of 0.036 seconds.
RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
"Concurrency" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "30rku9qg2y30j".
RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
times and had an average elapsed time of 32 seconds.
RECOMMENDATION 3: SQL Tuning, 14% benefit (926 seconds)
ACTION: Use bigger fetch arrays while fetching results from the SELECT
statement with SQL_ID "7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
FINDING 2: 37% impact (2508 seconds)
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
RECOMMENDATION 1: SQL Tuning, 26% benefit (1763 seconds)
ACTION: Investigate the SQL statement with SQL_ID "30rku9qg2y30j" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 30rku9qg2y30j and
PLAN_HASH 2734400036
select a.owner, a.object_name, INSTR(a.object_type, :"SYS_B_00"),
:"SYS_B_01" from sys.all_objects a where a.object_type IN
(:"SYS_B_02",:"SYS_B_03") and a.status = :"SYS_B_04" and a.owner
like:"SYS_B_05"escape:"SYS_B_06" and a.object_name
like:"SYS_B_07"escape:"SYS_B_08" union all select c.owner,
c.synonym_name, INSTR(a.object_type, :"SYS_B_09"), :"SYS_B_10" from
sys.all_objects a, sys.all_synonyms c where c.table_owner = a.owner
and c.table_name = a.object_name and a.object_type IN
(:"SYS_B_11",:"SYS_B_12") and a.status = :"SYS_B_13" and c.owner
like:"SYS_B_14"escape:"SYS_B_15" and c.synonym_name
like:"SYS_B_16"escape:"SYS_B_17" union all select distinct b.owner,
CONCAT(b.package_name, :"SYS_B_18" || b.object_name),
min(b.position), max(b.overload) from sys.all_arguments b where
b.package_name IS NOT NULL and b.owner
like:"SYS_B_19"escape:"SYS_B_20" and b.package_name
like:"SYS_B_21"escape:"SYS_B_22" group by b.owner,
CONCAT(b.package_name, :"SYS_B_23" || b.object_name) union all select
distinct c.owner, CONCAT(c.synonym_name, :"SYS_B_24" ||
b.object_name), min(b.position), max(b.overload) from
sys.all_arguments b, sys.all_synonyms c where c.table_owner = b.owner
and c.table_name = b.package_name and b.package_name IS NOT NULL and
c.owner like:"SYS_B_25"escape:"SYS_B_26" and c.synonym_name
like:"SYS_B_27"escape:"SYS_B_28" group by c.owner,
CONCAT(c.synonym_name, :"SYS_B_29" || b.object_name) union all select
distinct c.owner, c.synonym_name, min(b.position), max(b.overload)
from sys.all_arguments b, sys.all_synonyms c where c.owner = b.owner
and c.table_owner=b.package_name and c.table_name=b.object_name and
c.owner like:"SYS_B_30"escape:"SYS_B_31" and c.synonym_name
like:"SYS_B_32"escape:"SYS_B_33" group by c.owner, c.synonym_name
RATIONALE: SQL statement with SQL_ID "30rku9qg2y30j" was executed 12270
times and had an average elapsed time of 0.036 seconds.
RATIONALE: Waiting for event "cursor: pin S wait on X" in wait class
"Concurrency" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "30rku9qg2y30j".
RATIONALE: Average CPU used per execution was 0.036 seconds.
RECOMMENDATION 2: SQL Tuning, 23% benefit (1550 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7yv1ba0c8y86t".
RELEVANT OBJECT: SQL statement with SQL_ID 7yv1ba0c8y86t and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "7yv1ba0c8y86t" was executed 47
times and had an average elapsed time of 32 seconds.
RATIONALE: Average CPU used per execution was 32 seconds.
RECOMMENDATION 3: SQL Tuning, 5.8% benefit (390 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"cbtd2nt52qn1c".
RELEVANT OBJECT: SQL statement with SQL_ID cbtd2nt52qn1c and
PLAN_HASH 2897530229
Select DAE_.ROWID, DAE_.*, HAE_.*
From THPR.GACCENTRYD DAE_, THPR.GACCENTRY HAE_ Where ((HAE_.TYP_0(+)
= DAE_.TYP_0) AND (HAE_.NUM_0(+) = DAE_.NUM_0))
And HAE_.CPY_0 = :1 And HAE_.ACCDAT_0 >= :2 And HAE_.ACCDAT_0 <= :3
And DAE_.ACC_0 = :4 And HAE_.FCY_0 >= :5 And HAE_.FCY_0 <= :6
Order by DAE_.BPR_0,DAE_.CUR_0,DAE_.ACC_0
RATIONALE: SQL statement with SQL_ID "cbtd2nt52qn1c" was executed 12980
times and had an average elapsed time of 0.03 seconds.
RATIONALE: Average CPU used per execution was 0.029 seconds.
RECOMMENDATION 4: SQL Tuning, 2.1% benefit (138 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"33t7fszkr29gy".
RELEVANT OBJECT: SQL statement with SQL_ID 33t7fszkr29gy and
PLAN_HASH 2684283631
Select WSTJ_.ROWID, WSTJ_.*, WMVD_.*
From THPR.STOJOU WSTJ_, THPR.SMVTD WMVD_ Where ((WMVD_.VCRTYP_0(+) =
WSTJ_.VCRTYP_0) AND (WMVD_.VCRNUM_0(+) = WSTJ_.VCRNUM_0) AND
(WMVD_.VCRLIN_0(+) = WSTJ_.VCRLIN_0))
And WMVD_.CCE2_0 = :1 And WSTJ_.IPTDAT_0 <= :2 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_0",:"SYS_B_1") <> :3 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_2",:"SYS_B_3") <> :4 And
Substr(WMVD_.ITMDES1_0,:"SYS_B_4",:"SYS_B_5") <> :5 And
(((WSTJ_.TRSFAM_0 = :6) Or (WSTJ_.TRSFAM_0 = :7)))
Order by WSTJ_.STOFCY_0,WSTJ_.UPDCOD_0,WSTJ_.ITMREF_0,WSTJ_.IPTDAT_0
Desc,WSTJ_.MVTSEQ_0,WSTJ_.MVTIND_0
RATIONALE: SQL statement with SQL_ID "33t7fszkr29gy" was executed 1
times and had an average elapsed time of 136 seconds.
RATIONALE: Average CPU used per execution was 138 seconds.
FINDING 3: 15% impact (1008 seconds)
SQL statements with the same text were not shared because of cursor
environment mismatch. This resulted in additional hard parses which were
consuming significant database time.
RECOMMENDATION 1: Application Analysis, 15% benefit (1008 seconds)
ACTION: Look for top reason for cursor environment mismatch in
V$SQL_SHARED_CURSOR.
ADDITIONAL INFORMATION:
Common causes of environment mismatch are session NLS settings, SQL
trace settings and optimizer parameters.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
FINDING 4: 8.5% impact (570 seconds)
Wait class "User I/O" was consuming significant database time.
NO RECOMMENDATIONS AVAILABLE
ADDITIONAL INFORMATION:
Waits for I/O to temporary tablespaces were not consuming significant
database time.
The throughput of the I/O subsystem was not significantly lower than
expected.
FINDING 5: 5.3% impact (355 seconds)
The SGA was inadequately sized, causing additional I/O or hard parses.
RECOMMENDATION 1: DB Configuration, 3.2% benefit (215 seconds)
ACTION: Increase the size of the SGA by setting the parameter
"sga_target" to 1740 M.
ADDITIONAL INFORMATION:
The value of parameter "sga_target" was "1392 M" during the analysis
period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(8.5% impact [570 seconds])
INFO: Waits for I/O to temporary tablespaces were not consuming
significant database time.
The throughput of the I/O subsystem was not significantly lower
than expected.
FINDING 6: 4.2% impact (281 seconds)
Cursors were getting invalidated due to DDL operations. This resulted in
additional hard parses which were consuming significant database time.
RECOMMENDATION 1: Application Analysis, 4.2% benefit (281 seconds)
ACTION: Investigate appropriateness of DDL operations.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Hard parsing of SQL statements was consuming significant
database time. (20% impact [1336 seconds])
SYMPTOM: Contention for latches related to the shared pool was
consuming significant database time. (2% impact [135
seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of
database time.
SYMPTOM: Wait class "Concurrency" was consuming significant
database time. (2.3% impact [154 seconds])
FINDING 7: 4% impact (266 seconds)
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
RECOMMENDATION 1: Host Configuration, 4% benefit (266 seconds)
ACTION: Investigate the possibility of improving the performance of I/O
to the online redo log files.
RATIONALE: The average size of writes to the online redo log files was
26 K and the average time per write was 2 milliseconds.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Commit" was consuming significant database time.
(4% impact [266 seconds])
FINDING 8: 2.9% impact (192 seconds)
Soft parsing of SQL statements was consuming significant database time.
RECOMMENDATION 1: Application Analysis, 2.9% benefit (192 seconds)
ACTION: Investigate application logic to keep open the frequently used
cursors. Note that cursors are closed by both cursor close calls and
session disconnects.
RECOMMENDATION 2: DB Configuration, 2.9% benefit (192 seconds)
ACTION: Consider increasing the maximum number of open cursors a session
can have by increasing the value of parameter "open_cursors".
ACTION: Consider increasing the session cursor cache size by increasing
the value of parameter "session_cached_cursors".
RATIONALE: The value of parameter "open_cursors" was "800" during the
analysis period.
RATIONALE: The value of parameter "session_cached_cursors" was "20"
during the analysis period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Contention for latches related to the shared pool was consuming
significant database time. (2% impact [135 seconds])
INFO: Waits for "cursor: pin S wait on X" amounted to 1% of database
time.
SYMPTOM: Wait class "Concurrency" was consuming significant database
time. (2.3% impact [154 seconds])
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ADDITIONAL INFORMATION
Wait class "Application" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 100% of the analysis
period.
The analysis of I/O performance is based on the default assumption that the
average read time for one database block is 10000 micro-seconds.
An explanation of the terminology used in this report is available when you
run the report with the 'ALL' level of detail.user12023161 wrote:
I have upgraded 10.2.0.3.0 to 10.2.0.5.0 and facing same issue. The database is slow in general after upgrade compared to 10.2.0.3.0.Try setting OPTIMIZER_FEATURE_ENABLE parameter to 10.2.0.3.
Refer following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams142.htm -
Hello, I just bought a Snow Leopard and I have tried to install this on my macbook pro 2008 (10.5.8) and I can not do it. I have to erase the hard drive before in order to succeed. Please tell me step by step what to do. I appreciate very much your help.
ThanksHere are the directions:
http://support.apple.com/kb/HT3910?viewlocale=en_US
Ciao. -
I just purchased a ipad2, it would not work on my MacBook 10.4.1 I purchased and installed OSX snow leopard 10.6.3 downloaded and installed the latest itunes, set up an itunes account, purchased some music and apps. When i plug in my ipod it shows up and works, but when i plug in my new ipad the ipad screen comes up with a display of a cable and itunes but does not show in devises, i have tried all the resets and different USB ports with no success. Any ideas short of selling it on ebay or buying a new computer?
If you've already tried the usual rebooting of the computer and ports and stuff, there is only a few things left I can think of. It's possible that when you updated iTunes it didn't fully replace all the files, so I suggest just manually removing iTunes and then reinstalling it.
Try removing iTunes manually first http://support.apple.com/kb/HT1224 then download a fresh copy, make sure it is 10.3.1
It is essential that you go through Finder to remove those files it mentions. Otherwise they won't be reinstalled when you run the installer again.
Maybe you are looking for
-
How to create a report where records are seperated
Hi I am busy creating a Shareholders GL Account CR based off OACT, OJDT, JDT1. The fields to be displayed on the report will be OJDT.RefDate, OJDT.Memo, Amount (Formula = JDT1.Debit - JDT1.Credit), Balance (Running Total based off @Amount field, summ
-
How do I populate the address book when trying to send a photo(s) by email?
How do I populate the address book when trying to send a photo(s) by email?
-
ScoreBook Lite 8.1 App not Showing in Search Results
This app was initially published about two weeks ago with a few updates since then. Although I go directly to the app with the provide link it is not showing up in store search results? Is using keywords enough for search or should there be the sam
-
When I try to edit a photo from LR 2.0 in PS CS4 PS starts up but nothing further happens. This is the case in all cases except when I choose "edit original". Then everything works fine. Help!! thnx, Saam
-
HOW DO I GET RID OF MOBLEME AND START USING MY OUTLOOK WITHOUT A 2 MINUTE DELAY AND MULTIPLE "CLOSE PROGRAM CLICKS"?