UPgrade qs from 4.6 c to ECC 6.0

My client is looking to move from 4.6C to ECC 6.0.
Now, it is using BAs as the legal entities instead of compay codes, its also using Internal Orders to capture all the revenue and cost centers for expenses as well as balance sheet items (changing the Field Status Grp and using cost elements with category 90 and supressing the warning).
In the "to be" world they would like to be with Company Code as legal entity and use Profit centers for B/s Items, and use Internal orders sparingly - only where it should be used.
I believe the most appropriate scenario is to have a reimplementation with the correct config.
According to another consultant, they can do a technical upgrade and simply do a "reorg" (whatever that means) in the upgraded ECC system to move from BAs to Company Codes and the new config.
To me this sounds a little too fantastic. Any thoughts?

Hi All,
We are in the process of upgrading our system from 4.6 c to ECC 6.0.
During the configuration phase i want to select Manual Selection of Parameters,
once we do that i will be asked for number of R3 Trans ,R3 Load, Maximum Uptime ,
Batch process. I understand that these vary accordingly as per the server configuration.
I want to calculate the number of proceses for my system.
Regards,
Ershad Ahmed.

Similar Messages

  • BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

    Background:
    I am relatively new to BW team and will be going through my 1st source system upgrade.
    We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
    We are upgrading to the source system to ECC 6.0.
    In Development and QA Environments:
    we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
    We have a opportunity to compare the BW Objects, data flow and data loading from
    both source systems.
    In Production, however, we will just upgrade over 3 days downtime.
    One Question that comes to mind in this regard...
    What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
    Some of the suggestions that were given to me include following points.
    Before Upgrade:
    1 Check data, taking pre images of it for testing with post upgrade.
    2. Perform proper analysis of Source system related BW objects.
      - A complete listing of actively used Datasources,.. etc.
    3. Make delta queues empty,
    Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
    4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
    After Upgrade:
    1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
    (depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
    2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
    3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
    Maintain Control Parameters for Data Transfer
    http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
    4. Check for Changes to extract structures in LBWE Customizing Cockpit 
        - OSS Notes 328181, 396647, 380078 and 762951
    5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
    7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc. 
    Below is a link for some useful programs in this regard.
    https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
    6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
    As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
    7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
    new/changed datasources,if needed. 
    8. Check all CMOD enhancements.
    If we are using a customer exit with the extractor in the OLTP, see Note 393492.
    7. Check for unicode (all custom programs or Function Modules for DataSources)
    5.  Check all the queues in RSA7, start delta runs and test data consistency.
    For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
    9. Take back up of data posted during upgrade for contingency planing.
    10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
    Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

    Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
    We have similar scenario -
    We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
    Our strategy in ECC deployment  ->
    In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
    In production we are going to use same system PRXX upgraded from 4.7 to ECC.
    Now we are in testing phase of ECC with all interfaces like BI in Dev.
    My questions are below ->
    How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
    Also in new ECC sourcesystem copy  we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
    Is there any easy way for above scenario ?
    Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
    I have found some other links which have some pieces of information regarding the topic -
    Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
    BI 7.0: Source System upgrade  from R/3 Enterprise to ECC 6.0
    Re: ECC 6.0 Upgrade
    Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
    ECC 5.0 to ECC 6.0 upgrade
    Thanks
    Prasanth

  • Upgrade project : from SAP R/3 4.6C to ECC 6.0 by using SAP Data Services

    Hi All,
    My client is upgrading from SAP R/3 4.6C to ECC 6.0
    We are planning to use SAP Data Services(Data Integrator) in the upgrade plan from SAP R/3 4.6C to ECC 6.0 for Data Migration.
    we have no idea whether we can use this SAP Data Services(Data Integrator) in SAP upgrade data migration.
    The bottom line is we have to make use this Data Services (Data Integrator) product in our upgrade plan for Data Migration.
    Please tell us if anybody already used it such kind of scenario in a data migration project with Data Services(Data Integrator).
    If we can use Data Service(Data Integrator) what are the pros and cons in using this Data Services(Data Integrator).
    Thank You,
    Ashok

    My opinion is you would want to utilize SAP tools to port the data - our SAP BASIS administrator is out this week but we can provide exact tool names when he returns.  ELM (External List Management), IDOC are some of the tools.
    You could use DS/DI to export, cleanse, deduplicate the records prior to importing with SAP tools if that is your end goal.
    We also offer a data quality tool that extends DS/DI to cleanse/deduplicate name/address records as they are entered into the system.  It also comes with batch tools to cleanse/dedup the entire systems name/address information.  See Data Quality Management for SAP for further details.

  • Upgrade CFM from Sap R/3 Enterprise (4.7) Sap to ECC 6.00

    Hello,
    We are in a project of upgrade Sap from Sap R/3 Enterprise (4.7) to Sap ECC 6.00. Our question is particularly for CFM component migration/upgrade.
    As we checked we have activate the extension set:
    EA-FIN: Financials Extension
    EA-FS: Financial Services
    According with the Component Version Data the extension set EA-FINSERV has the release 2.00. However, in order to execute the CFM migration with transaction TPM_MIGRATION we are not sure if our CFM installation is on release 1.00 or 2.00.
    In the other OSS note 858966 mentions the following conditions to start points migration:
    1. The start release of the upgrade is SAP R/3 Enterprise 4.70 with SAP
    R/3 Enterprise extension set 1.10 or earlier.
    2. The target release of the upgrade is SAP R/3 Enterprise 4.70 with SAP
    R/3 Enterprise extension set 2.00 or higher.
    Do you know a transaction o report Sap which provides this information?
    Thank in advance.
    Sergio

    Within SAP, select System -> Status...  In the pop-up box, click the details button in the SAP System data section and you'll get another pop-up with system component information.  It's been a couple of years since I did the Treasury migration for our upgrade from 4.7 to 6.0, but I believe the component you're looking for is EA-FIN.  The Release column will have either 110 (for extension set 1.10) or 200 for (2.00).
    Regards,
    Shannon

  • Issues during technical upgrade from  version 4.6C to ECC 6.0

    Dear All,
    We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
    In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
    In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
    Request to kindly suggest the alternative to carry out the same in ECC 6.0.
    Thanks in advance.
    Regards,
    Dhawal

    Hi Akshya,
    Please find answers below.
    1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
    Yes you can.
    If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
    But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
    2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
    Yes you can activate it.
    3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
    After the upgrade and unicode conversion you can install the java stack.
    Regards,
    Ravi.

  • Regarding Upgradation From 4.6 C To ECC 6.0-Urgent

    Hi all
    can anybody let me know what is procedure to upgrade the SAP From 4.6 C To ECC 6.0 from MM and CIN point of view
    --is Up gradation is just like an implementation or Enhancement process
    any help would be appreciable
    thanks in Advance
    Edited by: JAM SAP on Feb 27, 2008 8:47 AM

    Upgrading project mostly involves testing with the existing system with the new system.SAP already released the release notes for this Upgrading ECC 6.0.
    (1). YOu have to do unit test/Integration test/Regression test in your new system based on the business process documents prepared for your present system.
    (2). You mostly encounter Interface issues(If exist)/Authorization issues/Enhanced naming issues/Usage issues.
    (3). In 46C you have to do external configuration for CIN.However In ERP 2005, It is already in built.Hence Knowledge of CIN will be more than sufficient to manage the CIN issues.
    (4). More over you must be very confident in the business process.Unless you will receive many UAT issues.
    (5). I strongly advice you based on my experience, Whenever you do unit test and Integration test, use your user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id.Using this new id you do the Regression testing.This will avoid many problems.
    (6). Another Imprtant big issue is patch work infomation.After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system.These patches are already in in built in ECC 6.0, hence you will get diff.result when you do testing.If such a case, advice the user about the patch work, and proceed. In most of my cases , SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
    (7).Give me your mail id ,I will send you the release notes.
    (8).Note down my forum discussion to know about the some of the issues.
    Hopefully it will be helpful, Let me know, If you need more Information.Thanks
    Reward If useful!

  • Upgrade procedure from 4.6c to ECC 6.0

    Hi
    I had gone through SAP solution browser tool and observed the differences for 4.6C and 6.0
    Can u please let me know How to start and end  the upgrade project i.e sequence of activities.
    1) should the configuration be done in ECC 6.0 same as 4.6C?
    2)master data upload?
    3)Z-objects movement from 4.6C to 6.0....?
    4)Open PO's and stock upload......in ECC 6.0 ?
    5) what are the precautions to be taken before Go-live?
    Please send any links for upgrade procedure from 4.6C to 6.0 i.e sequence of activities.........
    Thanking you
    Deepak

    Hi,
    About your questions:
    1) should the configuration be done in ECC 6.0 same as 4.6C?
    The configuration (if you mean how the system is configured from the Basis point of view) will be almost the same as you had in 4.6C. Of course you will find new aspects you don't have in the old version (for example the integrated ITS, ICM, etc.), but you will have the system running after the upgrade.
    2)master data upload?
    Master data will be adapted to new version during the upgrade. Unless you need fresh data, you won't need to reload master data.
    3)Z-objects movement from 4.6C to 6.0....?
    Z objects are not touched by the upgrade process. It's your responsibility to keep them running after the upgrade.
    4)Open PO's and stock upload......in ECC 6.0 ?
    Same as question 2). Business data remains in the system after the upgrade.
    5) what are the precautions to be taken before Go-live?
    It is recommended to carry out functional tests, as well as connection tests with external interfaces. In any case, you shouldn't take any special precaution, at least not so different from those you would take in a normal installation.
    Regards
    Francisco

  • Upgrade from 4.6 B to ECC 6.0

    Hi Gurus,
    Well and I would like to inform to our gurus that currently we are in the Phase of upgrading form 4.6 B to ECC 6.0
    I this regarding, can any one of our Guru's guide me regarding the following doubts.
    1. How to do Upgrade from 4.6 B to ECC 6.0?
    2. If you have any documents in this regard?
    3. Do you have any documentation for ECC 6.0?
    I request you to kindly forward the information to mail id: [email protected]
    Thanks with regards,
    Bala

    Hi,
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences pls refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
    and also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps you.
    Please assign points if it useful.
    Regards
    Ravinah Boni

  • Recommended upgrade method from ECC5 to ECC6 for lowest production downtime

    Hello everybody,
    I've been looking through multiple documents concerning a system upgrade and I am still unable to figure out the recommended method for upgrading a system with minimum downtime.
    My scenario requires that tests as rigid as possible will be performed and that development will be halted for the shortest time possible , therefore development must be continued after the initial upgrade.
    We are currently debating the required way to do this - what should be done with the change requests that currently reside in the DEV system, in which steps the incomptabilities are fixed and so on.
    I've decided that I'll share my thoughts with you and maybe you guros will be able to point out mistakes in the methodology.
    1. ECC 5 Production System is copied aside, lets call this system EPC
    2. Change requests from DEV ECC5 are copied to this EPC System.
    3. EPC  system is upgraded to ECC6.
    4. Bugs and incomptabilities such as unicode incomptabilities are fixed and merged in a change request
    This ends the preperation step and in my opinion is sort of a preperation step.
    During the whole preparation step, which to my estimate could take at least one month, development in the original system must be continued, so this is my main trouble.
    What is the recommended procedure from here?
    I assume that another production must be done on the day of the actual upgrade start, then the fixes from the previous preperation system are copied to this actual ECC6 Production, but I am rather lost as far as it goes to having an ECC6 Dev with most current change requests.
    I would appreciate any hints and help,
    thanks in advance,
    Eli.

    Ok, your idea of having a production copy for development and tests is a good upgrade strategy, we have done this twice due high quantity of developments and configuragion changes but I don´t see why you wrote " copy change requests from DEV to EPC " your whole configuration, programs, etc, are already in EPC once you copy the system.
    In this scenario every change made in DEV ECC 5.0 must be also replicated and tested in EPC 6.0 because you cannot use the change requests from 5.0 in 6.0 once in productive upgrade, let me list the global steps:
    1.- Homogeneous system copy from PRD to EPC, you will get a working test platform
    2.- Upgrade EPC to 6.0
    3.- Developers and functionals will do all respective changes and generate chage requests.
    Once EPC is ready
    4.- Upgrade DEV system to 6.0 transport change requests created in EPC to upgraded DEV, from this point you should only do emergency changes using Q&A system.
    5.- Upgrade Q&A system, transport change requests from DEV, no changes are permited from now until PRD is upgraded.
    6.- Do all tests very carefully
    7.- Upgrade PRD transport change requests
    Then you are ready. the downtime can be tune trough EPC, DEV and Q&A systems so you can determine what you shoud do to assure the shortest method.
    I recomend you to use the downtime minimized upgrade method and from every upgrade take a deep look at the upgrade report generated after the whole process is completed.

  • OM and PA data transfer from SAP 4.7 to ECC 6.0

    Dear Experts,
    hi
    i am working on one project where i will need to design the data transfer from SAP 4.7 to ECC 6.0. this is not a upgrade project.
    the data of PA and OM are in 4.7 which is existing system. i need to transfer entire data into ECC 6.0 so i can use that data for my E-Recruitment module ( we are doing E-rec fresh implementation.)
    we will keep both the systems (4.7 and ECC 6.0). ECC 6.0 will be used for E-Rec and OM only. for PA and Payroll we will use 4.7.
    can some one tell me,
    1. what are the key points to keep in consideration from OM point of view ?
    2. which is the best method to transfer the OM structure and data from 4.7 to ECC?
    3. what are the risks?
    4. which system we should make master system and which will be the slave system? why ?
    your input will be much appreciated.
    thanks and regards
    chandra

    Hi Chandra,
    I was under the impression that you are planning to use PA & OM from 4.7, now I read it again.
    Now its advisable to keep ECC 6 as a master system, becoz OM is the stating point of the HR processes where all Orgnization unit, job, position exists. Later the same data can flow to the slave system for PA use. As OM is the starting point, this system should be the master system.
    Abou the IDoc interface.
    Check the basic type HRMS_A05, whether it has all the data you need to transmit. T-Code WE30
    If you need to add something you can create a Z version in WE31. I selected HRMS_A05 as it is present in both the SAP version.
    Next there are series of transaction you need to process. Check with technical person who hands IDoc interafcing.
    Steps are:
    Assigning Message type to IDOC Type with extension. T-Code WE82
    Create Logical System:
    T-Code SALE-> Basic Settings-> Logical Systems-> Define Logical System
    It is required to configure in the sending system as well as in the receiving system
    Assign Logical System to Client:
    T-Code SALE-> Basic Settings-> Logical Systems-> Assign Logical System to Client
    Create RFC Destinations:
    T-Code SM59, select ABAP connection of type 3.
    Create Distribution Model: T-Code BD64
    Generate Partner Profile: T-Code BD82
    Maintain sending system partner profile: T-Code WE20
    Link Message Type to Function Module T-Code WE57 in receiving system only
    Hope this will help.
    Let me know if you need anything else.
    BR/Manas

  • Upgrading script from 4.6 to 5.0

    hi all,
    please help me with procedure to upgrade script from 4.6c to ecc 5.0.
    reply ASAP.
    thanks in advance .
    pavani.

    Hi,
    You can use the RSTXSCRP, this will Save a SAPScript layout set to disk, then come back to ECC version and run the same program again and do the Upload
    Regards
    Sudheer

  • How to manage upgrade project from 4.6c version to 6.0 version

    1) The client would like us to do a prototype of the upgrade (from 4.6 C to ECC 6.0) and selectivly modify certain complex customised objects. Is it possible to do it? If yes how?
    2) How do we identify which objects have obsolete syntax/function modules, etc that needs to be corrected? Does SAP correct these automatically or do we have to do it manually?
    3) How do we identify which all screens which require changing, both SAP and customised screens
    4) In version 4.6 C we are using userexits, whereas in ECC 6.0, we understand that user exits are replaced by BADIS. How do we know which all user exits require to be changed and which BADIS we need to implement?
    5) After using SPDD and SPAU errors will come how can we resolve it.
    Thanks in advance,
    shilpa

    Hi,
    1) The client would like us to do a prototype of the upgrade (from 4.6 C to ECC 6.0) and selectivly modify certain complex customised objects. Is it possible to do it? If yes how?
    ans ->Get all the custom objects from ur client..Compare the output in 4.6c and ECC 6.0 and see the if the output is coming correctly.if u won't get the desired result u have to check the functionality and then modify ur programs.
    2) How do we identify which objects have obsolete syntax/function modules, etc that needs to be corrected? Does SAP correct these automatically or do we have to do it manually?
    3) How do we identify which all screens which require changing, both SAP and customised screens
    ans ->Check the screen flow in both versions.
    4) In version 4.6 C we are using userexits, whereas in ECC 6.0, we understand that user exits are replaced by BADIS. How do we know which all user exits require to be changed and which BADIS we need to implement?
    and ->In ECC 6.0 also u are having userexits ,so u need to check if ur userexit is working well in ECC 6.0 , if not then u have to see for Badi's.
    5) After using SPDD and SPAU errors will come how can we resolve it.
    ans->if u get erros then u have to manually chnage the code , if u get warnings then SAP will take care...
    Regards,
    Nagaraj

  • Upgrade effort from 15.7 to 16

    At London's TechSelect, I asked if the upgrade effort from 15.7 to 16 was anything like the effort from 12.5.4 to 15.7. I was given a very reassuring "no".
    Do any of you mind sharing your experiences?
    Thanks,
    John

    Hello,
    for your questions in the posts , answeres given below :
    (1)I want to know what is the impact on security?
    Ans : The impact on security in terms of password length is there and it is also case sensitive one you upgrade to ECC6.0
    (2)Where I can download a list of all transactions for ECC6
    Ans : there is no way to find out the list of all transacions of ECC6.0 untill u upgrade it..by the way i dont think any requirement of it.....SE93? It depends on which type of T-code u want to compare in 4.7 and ECC 6.0 , but most of the standard t-codes are there in ECC6.0.
    (3)what If I have solution specific transactions, How do they get affected
    Ans : solution specific transaction means customized one? if so then  for identifying the effects do upgrade on test system first ..then identifying that all u r customized t-codes gives the correct o/p as it was given previousply or not ?
    If you want to focus on particaular module during update (HR, MM,PP) then u can also check on service.sap.com for that.
    The last thing i want to know is : security in terms of what ?? Authorization ? User level? T-code level? plz. calrify this first.
    Regards,
    kamlesh

  • Upgrade to  EhP4/NW 7.01 in ECC

    We are on ECC 6 and BI 700.The Basis team is planning for an upgrade to  EhP4/NW 7.01 in ECC . Does that mean the bi 7 is upgraded with EHP1? Can some one please clear this. What does NW 7.01 in ECC mean?
    Thanks,

    Hi,
    ABA Support Package 20 for 7.00
    Basis Support Package 20 for 7.00
    BW Support Package 22 for 7.00
    It appears that the BI system is separate as the component levels here do appear to be
    from BI system rather than having ECC components also.
    Your SP stack level looks to be SPS20 which is quite old and should be updated before
    updating system to EHP1.
    Please refer to the following documentation:
    1142832 - Installation Enhancement Package 1 for Netweaver 700
    1146578 - Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1
    1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1
    1248905 - SP Equivalence for update/upgrade to EHP 1 for SAP NW 7.0
    Also you can refer to the Ehancement Package Upgrade Guide at
    service.sap.com/instguides
    -> Installation & Upgrade Guides
    -> SAP NetWeaver
    -> SAP NetWeaver 7.0 (2004s)
    -> Upgrade
    Regards,
    Aidan

  • Sometimes my computer takes too long to connect to new website. I am running a pretty powerful work program at same time, what is the best solution? Upgrading speed from cable network, is it a hard drive issue? do I need to "clean out" the computer?

    Many times my computer takes too long to connect to new website. I have wireless internet (time capsule) and I am running a pretty powerful real time financial work program at same time, what is the best solution? Upgrading speed from cable network? is it a hard drive issue? do I only need to "clean out" the computer? Or all of the above...not to computer saavy.  It is a Macbook Pro  osx 10.6.8 (late 2010).

    Almost certainly none of the above!  Try each of the following in this order:
    Select 'Reset Safari' from the Safari menu.
    Close down Safari;  move <home>/Library/Caches/com.apple.Safari/Cache.db to the trash; restart Safari.
    Change the DNS servers in your network settings to use the OpenDNS servers: 208.67.222.222 and 208.67.220.220
    Turn off DNS pre-fetching by entering the following command in Terminal and restarting Safari:
              defaults write com.apple.safari WebKitDNSPrefetchingEnabled -boolean false

Maybe you are looking for