Mail slow to send after upgrading to Leopard

Since upgrading to Leopard from Tiger, Mail has been very slow to send. I can create a message "test 123" and click Send and it takes 30 seconds or more before I hear the whoosh. It was almost immediate when sending from Tiger. I can send from my Windows PC on the same network nearly instantly. I have checked the account settings and everything is the same as before the upgrade.

Figured it out, DNS was set to my DSL modem's ethernet gateway 192.168.1.254. I set it to ISPs DNS server on the WAN side and it sends immediately again. Tiger was always set to the DSL gateway though and didn't have any issues.

Similar Messages

  • Mac Mail slow to sync after upgrade Yosemite 10.10.2 and OS X Server 4.0.3

    We have deployed server OS X Server 4.0.3 and all client computer configured with DNS, Open Directory and Mail Server of OS X Server 4.0.3. It is quick to deliver mail before upgrade. And it is quick to deliver mail from iOS now. But it too slow to use Mac Mail. Even send to myself from intranet it costs 3 mins.

    I have no solution but have experienced failing sync settings (quite often) in both 10.6 Server and 10.9 + Server 3 (upgraded from 10.6 Server) in the same way as you described, it syncs too much. We have given up on synched home folders and will cut them and use other backup methods since we’re not so dependant on switching between different devices. Our users usually have one computer, one iPhone, one iPad and stay with those until it’s time to exchange them.

  • Mail not working properly after upgrade to  Leopard

    Hopefully this will be a common issue easily solved!
    After updating from 10.3.9 to Leopard 10.5.6 Mail has become unresponsive after opening - the programme opens but the message window does not appear, the address viewer and connection activity monitor will appear, it does not receive mail either
    If anyone has any ideas would be much appreciated!
    TIA

    The problem you are having following the upgrade to Leopard (10.5.6) from 10.3.9 is similar to those of people who have upgraded from Tiger, and has been covered by the support document at the link below:
    http://support.apple.com/kb/TS2537
    Your issue will be due to files named to include MessageSorting (which would mean you once have upgraded from a version of OSX earlier than 10.4), remove those, also, but never restore those. You will not have the files named to include MessageRules because you have not used Tiger.
    To find the correct location for the Mail folder, open a Finder window, click on the icon of a house in the Sidebar (this is known often as "Home"), click on Library in that Home user directory, and then to open the Mail folder found there.
    Ernie

  • Connection to file server slow and unreliable after upgrading to Leopard

    I have a client with a G5 PowerMac (3 GB memory) who has been connecting reliably to a network file server (Windows based) at her company for years. Upon upgrading to Leopard the connections is slower. Or, rather, opening the root level directory is fast. The second level folder is fast. The third level is fast. Beyond that she gets the spinning cursor and it can take a long time to open, even if there are only a couple files inside. Also, navigating back to the first level I see a spinning cursor and "Connecting..." as though the Mac had lost connection with the file server simply by opening the volume. Sometimes she has to Force Quit the Finder (which reports "not responding". Weird. Any ideas out there?

    Hi Greg,
    It was my second visit to this company, and it was for something else that I was focussed on. I don't know what kind of server they are running. It's a PC house running Exchange servers so it's probably some kind of Microsoft system. If the problem persists I'l get more info next week when they reopen after the holiday.

  • Mail will not launch after upgrade to Leopard

    I just installed the Leopard OS. My previous OS had been Tiger 10.4.10 and had been recently updated. Now, the Mail program will not launch. When I click the Mail icon, the little blue ball under the icon flashes a few times, then stops. A window opens to say that Mail has unexpectedly quit and asks if I want to send a report to Apple. I sent the report, but this of course does not help me to access my e-mail. Any ideas?

    Exact same problem, resolved thus just now:
    Finder, Search for Mail.app. Open the version 3.0 (Quick Look from Finder/File will help here...) and you'll be prompted to upgrade your mail stuff; from there, you're happy.
    My guess is that the Sidebar didn't upgrade correctly. Mine evidently still references v2.1 of Mail.
    On to that problem next...

  • Mail will not open after upgrade to Leopard

    We just tried to upgraded my wife's 20 inch iMac to Leopard. the computer had been running Tiger from the day we purchased it from Apple. She is unable to open her Mail program all the way. The only window that opens is the "send" window from the pull down window and she cannot send and to close the Mail program we must force quit. While I am at it I have am unable to use my "f" numbers with my new iMac 24. Any thought there? I havet the full key board not the small keyboard with the fn key.

    try this links
    http://support.apple.com/kb/TS2537
    http://support.apple.com/kb/TS2486

  • Mail won't send after upgrade to iOS 5.0.1

    I upgraded the OS software on my iPhone 3GS to iOS 5.0.1 and after this upgrade I am unable to send emails from my phone when using Bell cellular.
    I can still send emails from my phone using my home WiFi..
    Any ideas?

    I just called Bell and we switched Bell to my primary SMTP and my home to the secondary and now I can send email from my iPhone again.
    Not sure why this changed with iOS 5.0?

  • Mail unable to start after upgrading to Leopard

    I upgraded to OS X10.5.5. last week and it went really smooth! I was thrilled to see how easy it was compared to those ugh! years spent on Windows!! Only, I started up Mail and get an error message stating that the version of Mail cannot run under 10.5.5. I thought all these applications got upgraded when the OS got installed but obviously it did not! I cannot see how to upgrade only the Mail program as I cannot even start it.
    Now, I did exactly the same upgrade on my Macbook (similar config) and it all went well with all programs working fine..
    Can someone help please? Should I try to use the OS Leopard DVD and reinstall/repair the Mail program or ???
    Thanks in advance,
    Satish

    It's not always a guarantee to fix the issue, but you could try re-installing the application from the OS X Install disk. When you insert the disk, there should be folder named "optional installs" and with "optional installs.mpkg" inside. Run that installer package - continue through all the introduction, license, etc screens - and select the appropriate destination. Under Applications, Mail should be listed. Just check the box and continue. Wouldn't hurt to try this first.

  • Outgoing mail won't send after upgrading to Mountain Lion

    I've just upgraded to Mountin Lion from 10.6.8 and can't send mail out. I've checked all my username and password details are correct but it still won't work. Doesd anyone have any suggestions. IN coming mail sems to be fine.
    Thanks Adam

    Many Users who have Upgraded to Mountain Lion are having the problem that you are having, myself included.  The following solution helped me. 
    It sounds like you may need to go into Mail>Preferences>Accounts and Complete setting up you Gmail account.  It may not be finished being setup.  For instance, note the line below to be selected from the drop down list in "Outgoing Mail Server (SMTP", then click on "Edit SMTP Server List" and complete all of the required Gmail information in the next windows:
    Hope this helps

  • Fonts Missing in Mail after upgrading to Leopard

    After upgrading to Leopard, the fonts are missing in the font window in Mail program. I can compose only using what looks like helvetica. This is true only with this program. Any suggestions? Thanks

    After an elimination process, it appeared that there was a conflict of some sort on one of the accounts I had and unfortunately, that was the one with the most messages. Its a pain but my only work around it was to start all over again with Mail. If it helps yo, this is what I did: a) backed up my Mail : user/library/mail and backed up the preference file : user/library/preferences/com.apple.mail.plist
    b) removed the Mail preference : user/library/preferences/com.apple.mail.plist
    c) restarted Mail and created the accounts all over again via the setup helper
    d) imported the mail boxes from where I saved them including those in the 'pop' folder
    Now I have they old messages available in a folder I renamed 'archived' that is in the "ON MY MAC" section of the side bar.
    IT IS TEDIOUS AND I AM PRETTY SURE THERE IS A MORE ACCURATE SOLUTION OUT THERE TO THIS PROBLEM.

  • 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

  • MacBook Pro spontaneously wakes from sleep after upgrading to Leopard?

    For some reason, after I upgraded to Leopard, then whenever I put my MacBook Pro to sleep, it spontaneously wakes up after some time (can be from a few minutes to an hour or two.) I don't know why this is happening, but I know for sure that it's related to Leopard since I put my laptop to sleep every night (it's in my bedroom) and after upgrading to Leopard, it started to just wake up a short while after putting it to sleep.
    At first I thought it could be Time Machine, so I disconnected all my external drives, but that didn't seem to work.
    Does anyone know why this is happening?
    Thanks in advance!

    I have the same issue. Installed Leopard last night on my first-gen 1.83 MacBook. The next morning the Mac was a little slow in wanting to wake up. After that it stalled on transferring a large file from my G5 and I had to issue a reboot command via the shell to get it out of that. A few minutes later the computer locked up when trying to apple > tab through the application.
    I put it to sleep after restarting the Mac from that freeze. A while later while walking out of the house I happened to glance at the Macbook and saw the apple glowing while the lid was shut and then it went back to sleep.
    Tonight I put the Macbook to sleep on the way out to dinner. I noted that I had 84% of my battery left. A few hours later when I got home the MB was warm, the apple was glowing and I had 9% of my battery left.
    Looks like there is some work to be done asap for 10.5.1

  • Mail won't work after upgrade to 3.0

    I cannot get my Mail program to work after upgrading to 3.0. It starts, searched for new mail, then quits. I cannot get or send new mail. The program does not operate. Suggestions, please?

    I get the exact same thing. The status just keeps showing "Connecting..." and it never seems to connect. Oddly enough, I just updated to the new OS on my iMac at home and immediately after, I couldn't connect to mail from the computer. I had to manually download a component of the update and once I did that, mail worked just fine. Probably just an odd coincidence having nothing to do with the mail issues on the iPhone but I thought I'd mention it.

  • Can't use Airport Express after upgrading to Leopard

    I use Airport Express for wireless printing and AirTunes via powered speakers/hifi. It was working very reliably until I upgraded to Leopard. Now, I am unable to use Airport Express. I get the blinking orange light, but when I scan with Airport Utility, Airport Express is not detected. Manual setup is grayed out, so I can't set it up at all. I am using Airport Utility Version 5.2.2 (522.3), and there does not seem to be any updates or patches to apply at the moment. I have tried on my iMac G5 and MacBook, with the same result on both computers.
    I am also reading that many others are having problems with Airport Express after upgrading to Leopard, perhaps not with my specific hardware configuration, but this is very disappointing.
    I am open to suggestions to try a few things to get it working, so any help is appreciated.
    Message was edited by: a j

    From the Mail menu, select "Preferences". Hit the Accounts tab. Select the Account. Under Account Information, reapply the user name and password.
    Check with the provider if the account needs authentication. This is in the Advanced tab. Usually just a repeat of user name and password.

  • IPhone won't sync after upgrading to Leopard

    My iPhone won't sync, or even show up in iTunes, after upgrading to Leopard. I've tried restarting my Macbook Pro, trying different USB slots, closing and reopening iTunes, everything. Has anyone else had this problem??
    I've tried everything apple suggests:
    1. The iPhone battery might need to be recharged. For information about charging iPhone, see "Charging the Battery" in the iPhone User's Guide.
    2. If that doesn't work, disconnect other USB devices from your computer and connect iPhone to a different USB 2.0 port on your computer (not on your keyboard).
    3. If that doesn't work, turn iPhone off and turn it on again. Press and hold the Sleep/Wake button on top of iPhone for a few seconds until a red slider appears, and then slide the slider. Then press and hold the Sleep/Wake button until the Apple logo appears.
    Note: If you enter the PIN incorrectly three times, you may need to contact your carrier for a Personal Unlocking Key (PUK) to enable your SIM card again.
    4. If that doesn't work, restart your computer and reconnect iPhone to your computer.
    5. If that doesn't work, download and install (or reinstall) the latest version of iTunes from www.apple.com/itunes.

    You might need to remove and reinstall the Apple Mobile Device Service. Follow the link below for info on how to do this.
    http://docs.info.apple.com/article.html?artnum=306637

Maybe you are looking for