Dear Sean, Option 1: 1. Perform a database backup of the ARSystem database on your production V5 server 2. Restore the above database backup to new server machine 3. Install AR System 6.3 onto new server machine, when it asks to overwrite the database or upgrade, select upgrade. 4. Download the latest patch for AR System 6.3 and install (server, user and admin tool patch) 5. Export all active links and menus to a DEF file using the 6.3 admin tool 6. Run arclean against the DEF file (you may need to run several times to look for all the different server references you have) 7. Import the character menus and active links back into the system using the 6.3 admin tool. 8. Then *test* the application - ALL aspects to ensure it is functioning - all menus, workflow and as the different users of the system to ensure their permissions and functionality is the same as the existing production system. A test plan is a good idea so you know how it functions in the existing environment and to ensure it functions the same in the new environment.
Option 2: 1. Install your database and AR System 6.3 on your new server machine 2. Download the latest patch for AR System 6.3 and install (server, user and admin tool patch) 3. Identify all changes to the group/user forms and added menus/workflow as compared to the 6.3 group/user. 4. Apply the group/user changes by hand to the 6.3 group and user forms using the 6.3 admin tool. 5. Using your V5 admin tool export your forms and related workflow to a DEF file. 6. Run ARCLEAN against the above DEF file - you may need to run several times for each server reference you want to remove. 7. Using the 6.3 admin tool import the forms from the above DEF file. 8. Using the 6.3 admin tool import the menus from the above DEF file. 9. Using the 6.3 admin tool import the filters, active links and escalations from the above DEF file. 10. Then *test* the application - ALL aspects to ensure it is functioning - all menus, workflow and as the different users of the system to ensure their permissions and functionality is the same as the existing production system. A test plan is a good idea so you know how it functions in the existing environment and to ensure it functions the same in the new environment. Option 3: 1. Install your database and AR System 6.3 on your new server machine 2. Download the latest patch for AR System 6.3 and install (server, user and admin tool patch) 3. Purchase and Install Migrator product to perform the migrator between the two servers. This product also can produce differences reports as well. It functions at the API level. 4. Then *test* the application - ALL aspects to ensure it is functioning - all menus, workflow and as the different users of the system to ensure their permissions and functionality is the same as the existing production system. A test plan is a good idea so you know how it functions in the existing environment and to ensure it functions the same in the new environment. Option 4: Hire Remedy Consulting to help with the upgrade/migration of your server. NOTE: The ARCLEAN utility is an unsupported utility. Hope this KB article helps you.. Regards, Roney Samuel Varghese On 2/7/07, Sean Harrodine <[EMAIL PROTECTED]> wrote:
Hi all, We have a V5 Remedy installation running on Oracle 8.1.7 on HPUX11 that we are planning on moving across to a Linux server, running Remedy 6.3 with Oracle 9.1.2 I'm interested to hear from anyone as to your experiences in upgrading, and as to what they believe the best order is to upgrade Remedy / Oracle is or any pitfalls (of which i dont doubt there are many !) Thanks in advance. Sean _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
