HCL's Best Practices in PeopleSoft Upgrade

HCL is organizing a series of global web conferences on “PeopleSoft Upgrade Decision Maker Series”. HCL Technologies, is one of the Global Certified Advantage Partner with Oracle.
Upgrade is more than a necessity; it can help you realize your vision of the enterprise of the future. Discover the "Why", "How" and "What" of PeopleSoft Enterprise Applications 9.0 Upgrade.
To Register: http://www.hcltech.com/webinars/upcoming/registrations/?id=13044

Similar Messages

SAP Best Practice For Unicode Upgrades - NetWeaver 2004s

Team SAP,
I have a customer that is starting to plan for a Unicode upgrade. The question from the customer is as follows:
What is the SAP Best Practice for Unicode Upgrades? They will be upgrading from a BW 3.5 System to NetWeaver 2004s, and their question is ... should they:
a) Perform the Unicode Upgrade At The Same Time As Their BW 3.5 > NetWeaver 2004s Upgrade, or
b) Perform NetWeaver 2004s Upgrade first, and then at a later date, perform the Unicode Upgrade?
Thank you in advance for any guidance or counsel you may be able to offer.
-M

Hi Michael,
Check these links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee7407a0-0501-0010-81ae-e329029b1074
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7e259990-0201-0010-6085-e7c5aec5af1d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5411d290-0201-0010-b49b-a6145fb16d15
Bye
Dinesh

Best Practice for config upgrade

Hi
Is there a best practice guide to follow to performing a network upgrade. So I am replacing a stack of 5 3750 switches and replacing with 2 stacks of 2 3750x switches, but then also introducing a 4500x vss pair aswell as the new core. Is there an easy migration process to migrate the config or do I have to understand what the current network is configured as and build a new config for the new topology.
Im new to this process so just wondering if I can find an easier way, Thanks

Is there an easy migration process to migrate the config or do I have to understand what the current network is configured as and build a new config for the new topology.
You really need to understand how the current network is configured before you can do the upgrade otherwise if something doesn't work you will have no idea of where to begin troubleshooting.
That doesn't mean you need to build an entirely new configuration because you may well be able to apply most of the configuration on your existing switches to the new switches although it's not clear what functions the new switches will be doing ie.
currently you have a stack of 3750s doing what ? eg. access for users, routing for vlans etc.
you are replacing them with 3750x's switches and 4500x switches so are you splitting up the functions of the 3750s between them.
If you are then obviously you cannot take the existing configuration and copy it to both the 3750x and the 4500x switches.
When I did upgrades like this I would download the existing configurations to my laptop and make any necessary edits. If I couldn't use the existing configuration I just created new ones. When I came to upgrade I had all the configurations ready to load onto the switches.
Bear in mind that some configuration just won't copy across ie. if you have QOS on your current switches and you try to copy that to the 4500x it probably wont work as they use different commands for a lot of the same functions.
But the key thing is you must understand what you are trying to do ie. simply trying to copy across configurations without the understanding could create a lot of problems.
Jon

Best practice for R12 upgrade middle of the period

Does anyone know of where I can find an Oracle documented best practice on when to perform the 12.1.1 upgrade? We are considering if we can upgrade in the middle of a period or if we should wait until the period close.

Best practice is to read the name of a forum before you post into it.
This forum is titled: "Oracle Database General Questions."
My suspicion is your question relates to EBS.

Looking for information on best practices using Live Upgrade to patch LDOMs

This is in Solaris 10. Relatively new to the style of patching... I have a T5240 with 4 LDOMS. A control LDOM and three clients. I have some fundamental questions I'd like help with..
Namely:
#1. The Client LDOMS have zones running in them. Do I need to init 0 the zone or can I just +zoneadm zone halt+ them regardless of state? I.E. if it's running a database will halting the zone essentially snapshot it or will it attempt to shut it down. Is this even a nessessary step.
#2. What is the reccommended reboot order for the LDOMs? do I need to init 0 the client ldoms and the reboot the control ldom or can I leave the client LDOM's running and just reboot the control and then reboot the clients after the control comes up?
#3. Oracle. it's running in several of the zones on the client LDOM's what considerations need to be made for this?
I am sure other things will come up during the conversation but I have been looking for an hour on Oracle's site for this and the only thing I can find is old Sun Docs with broken links.
Thanks for any help you can provide,
pipelineadmin+*

Before you use live upgrade, or any other patching technique for Solaris, please be sure to read http://docs.oracle.com/cd/E23823_01/html/E23801/index.html which includes information on upgrading systems with non-global zones. Also, go to support.oracle.com and read Oracle Solaris Live Upgrade Information Center [ID 1364140.1]. These really are MANDATORY READING.
For the individual questions:
#1. During the actual maintenance you don't have to do anything to the zone - just operate it as normal. That's the purpose of the "live" in "live upgrade" - you're applying patches on a live, running system under normal operations. When you are finisihed with that process you can then reboot into the new "boot environment". This will become more clear after reading the above documents. Do as you normally would do before taking a planned outage: shut the databases down using the database commands for a graceful shutdown. A zone halt will abruptly stop the zone and is not a good idea for a database. Alternatively, if you can take application outages, you could (smoothly) shutdown the applications and then their domains, detach the zones (zoneadm detach) and then do a live upgrade. Some people like that because it makes things faster. After the live upgrade you would reboot and then zoneadm attach the zones again. The fact that the Solaris instance is running within a logical domain really is mostly besides the point with respect to this process.
As you can see, there are a LOT of options and choices here, so it's important to read the doc. I ***strongly*** recommend you practice on a test domain so you can get used to the procedure. That's one of the benefits of virtualization: you can easily set up test environments so you cn test out procedures. Do it! :-)
#2 First, note that you can update the domains individually at separate times, just as if they were separate physical machines. So, you could update the guest domains one week (all at once or one at a time), reboot them into the new Solaris 10 software level, and then a few weeks later (or whenever) update the control domain.
If you had set up your T5240 in a split-bus configuration with an alternate I/O domain providing virtual I/O for the guests, you would be able to upgrade the extra I/O domain and the control domain one at a time in a rolling upgrade - without ever having to reboot the guests. That's really powerful for providing continuous availability. Since you haven't done that, the answer is that at the point you reboot the control domain the guests will lose their I/O. They don't crash, and technically you could just have them continue until the control domain comes back up at which time the I/O devices reappear. For an important application like a database I wouldn't recommend that. Instead: shutdown the guests. then reboot the control domain, then bring the guest domains back up.
3. The fact that Oracle database is running in zones inside those domains really isn't an issue. You should study the zones administration guide to understand the operational aspects of running with zones, and make sure that the patches are compatible with the version of Oracle.
I STRONGLY recommend reading the documents mentioned at top, and setting up a test domain to practice on. It shouldn't be hard for you to find documentation. Go to www.oracle.com and hover your mouse over "Oracle Technology Network". You'll see a window with a menu of choices, one of which is "Documentation" - click on that. From there, click on System Software, and it takes you right to the links for Solaris 10 and 11.

EP Upgrade - SP14 - Best Practice for Modification File Comparison

SDN Experts -
We are upgrading our EP from SP14 - SP16. SAP offers a file "diff" tool that is only useful for Java application files to assist in re-applying our mods on top of the new code stack.
We are looking for best practices in Portal upgrades to do the following:
- Identify all files that we have modified on existing SP
- Diff all source code files (java, XML, GUI, other) between Current SP14 and SP16
We are also looking for documentation that identifies the local directory structure for NWDS. This would aid us in creating a batch process to "diff" our source code libraries.
Any recommendations are appreciated.
Thanks

I'm not realy getting your question because you already state what to do:
We are looking for best practices in Portal upgrades to do the following:
Identify all files that we have modified on existing SP
Diff all source code files (java, XML, GUI, other) between Current SP14 and SP16
You should know by documentation what is changed I guess? Then start diff-ing the code and recompile or repackage. NWDS also has diff functionalities.
Good luck,
Benjamin

Best Practices for 11i to R12 Upgrade

Hi,
We are in the process of doing an upgrade from 11.5.7 to R12.
Please share the Best Practices available for upgrade from 11.5.7 to R12.
Regards,
Narayan

Hi Narayan;
Please see:
Interesting Documents Concerning E-Business Suite 11i to R12 Upgrades [ID 850008.1]
Upgrade Advisor: E-Business Suite (EBS) Technology Stack Upgrade from 11.5.10.2 to 12.1.2 [ID 253.1]
Those should helps you
I suggest also use search mechanisim and make search on EBS forum, you can see our previous topic which is mention same&similar issues
Regard
Helios

Best practice to update to Snow Leopard

I just placed my family pack order on Amazon.com for Snow Leopard. But this will be the first time for me doing an OS upgrade on a Mac (all 4 Macs in my house came with Leopard on them so we've only done the "software update" variety). I am a reformed PC guy so humor me!
What is the best practice to upgrade from 10.5.8 to 10.6? On a PC, my inclination would be to back up my data, reformat the whole drive and install Windows fresh... then all my apps.. then the data. I hate that and it takes hours.
What is the best practice way to upgrade the Mac OS?

The best option is Erase and Install. The next best option is Archive and Install. Use the latter if you do not want to or can't erase your startup volume.
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Firmware Best practices

Any suggestions on best practices for firmware upgrading. Currently using a combination of SF200 switches (SF200-48, SF200-24, SF200-24P, SF200-24FP), WAP561, and WAP321. The question is should I step the updates from the current to the most recent or can I just update to newest release?

Hello,
For the switches please bear in mind the following upgrade steps:
https://supportforums.cisco.com/document/12321266/firmware-upgrade-troubleshooting-300-and-500-series-managed-switches
Please note that with boot code 1.3.5.06 there are quite important change in file system so before proceeding to 1.4.0.88 you will have to upgrade switch to 1.3.7 firmware not boot code 1.3.5.06.
For the access points it is not the same case however please always check release notes of the latest firmware for special instructions.
Regards,
Aleksandra

Best practice for upgrading task definition without deleting task instances

best practice for upgrading task definition in production system without deleting or terminating task instances
If I try and update a task definition with task instances running I get the following error:
Task definition 'My Task - Add User' may not be modified while there are active task instances
Is there a best practice to handle this. I tried to force an update through the console but that didn't work. I tried editing the task from the debug page and got the same error.

1) Rename the original task definition.
2) Upload the new task definition with the original name.
3) Later, after all the running tasks have timed out, delete the old definition.
E.g., if your task definition is "myWorkflow":
1) Rename "myWorkflow" to "myWorkflow-old-2009-07-28"
2) Upload the new task definition as "myWorkflow".
Existing tasks will stay linked to the original (renamed) workflow definition.
New tasks will use the new definition.
As the previous poster notes, depending on the changes you are making, letting the old task definitions stay active could have bad side-effects and might be better avoided.

Upgraded to CS5, CS4 apps still in place. OK to remove? Best practice?

No problem to report just a minor dilema.
Upgrade to CS5 is completed and all the previous CS4 application folders are still in place and functional.
What is the best practice regarding the previous version?
Leave them be.
Move to trash.
Uninstall (when provided).
Thanks for your help.
Pete
iMac • Intel Core i7 • 2.8 GHz • 8 GB RAM • OS X 10.6.7

Bob,
One follow-up question. What about the earlier Acrobat component? Backward compatibility isn't problematic in the case of Acrobat correct?
Thanks for your time.
Pete
iMac • 2.8 GHz Intel Core i7 • 8 GB RAM • OS X 10.6.7
Adobe CS5.x Design Premium

Best Practice for upgrading to 11.1.1.3

Hi,
Can anyone tell me what is the best practice to upgrade FMW to 11.1.1.3...
I followed the following steps to set up FMW 11.1.1.3.
1. Oracle Enterprise edition Database 10.2.0.1 and applied 10.2.0.4 patch
2. Installed RCU 11.1.1.3
3. Installed Weblogic server 10.3.3 (11gR1)
4. Installed Soa Suite 11.1.1.2 and applied patch for 11.1.1.3
Is this the right way of installation or do i have to install 11.1.1.2 first f and then install 11.1.1.3..
Regards,
Sundar

Yes, that seems to be fine.
regards

Best practice for upgrading task definition in production system

If I try and update a task definition with task instances running I get the following error:
Task definition 'My Task - Add User' may not be modified while there are active task instances
Is there a best practice to handle this. I tried to force an update through the console but that didn't work. I tried editing the task from the debug page and got the same error.

The best way for upgrade purposes is to use the rename function of the TaskDefinition from the lh command line utility.
Basically renames all current task instances with the TaskDefinition name. You can then alter the existing TaskDefinition and upload into identity manager.

Best Practice in Upgrade from ECC 5.0 to ECC 6.0

Dear All,
Can someone help in looking for Best practice in Upgrade from ECC 5.0 To ECC 6.0 Project from Functional FI and CO Side.
Thanks

Moved to a different forum.

Best Practice for Installation of Both Leopard and Aperture 2 upgrade.

I've finally bought the bullet and purchased both Leopard and Aperture 2.0 upgrade. I've tried searching for a best practice to install both, but haven't been able to find one--only trouble shooting type stuff. Any suggestions, things to avoid, etc would be greatly appreciated. Even a gentle shove to a prior thread would be helpful. . . .
Thanks for pointing me in the right direction.
Steve

steve hutchcraft wrote:
I've tried searching for a best practice to install...
• First be really sure that all your apps work well with 10.5.3 before you leave 10.4.11, which is extraordinarily stable.
• Immediately prior to and immediately after every installation of any kind (OS, apps, drivers, etc.) got to Utilities/Disk Utility/First Aid, and Repair Permissions. Repairing Permissions is not a problem fixer per se, but anecdotally many folks with heavy graphics installations (including me) who follow that protocol seem to maintain better operating environments under the challenge of heavy graphics than folks who do not diligently do so.
• When you upgrade the OS do a "clean install."
• RAM is relatively inexpensive and 2 GB RAM is limiting. I recommend adding 4x2 GB RAM. One good source is OWC: http://www.owcomputing.com/.
• After you do your installations check for updates to the OS and/or Aperture, and perform any upgrades. Remember to Repair Permissions immediately prior to and immediately after the upgrade installations.
• If you are looking for further Aperture performance improvement, consider the Radeon HD 3870. Reviews at http://www.barefeats.com/harper16.html and at http://www.barefeats.com/harper17.html.
Good luck!
-Allen Wicks

HCL's Best Practices in PeopleSoft Upgrade

Similar Messages

Maybe you are looking for