Tim,
I often ARS from a development server to a "soon to be"
production server:
Solaris 9
Oracle 9i
ARS 6.3
The ARS server names (and machine names) are different so I
don't see where it would be much different from your
situation.
The process involves exporting the database from the
develpment server, importing the database on the second server, and then
performing clean up to make sure the server names in workflow are what I
expect. Here are the steps I've used a couple of times per month for the
past several months to migrate from one server to another:
1. Export all forms and workflow using the Remedy Admin
tool on the “source” Remedy server (this is your clean backup in case things go
bad)
2. Shutdown the “source” Remedy server
3. Export the entire ARSystem database using database native export tools
4. Verify the object count (you'll need this later to verify the import)
5. Shutdown the “target” Remedy Server arsystem processes
6. Import the entrire ARSystem database using database native import tools (see your DBA on this)
7. Compare object counts on target database with those on source database
8. Check for instances of an invalid server name in workflow and form data
2. Shutdown the “source” Remedy server
3. Export the entire ARSystem database using database native export tools
4. Verify the object count (you'll need this later to verify the import)
5. Shutdown the “target” Remedy Server arsystem processes
6. Import the entrire ARSystem database using database native import tools (see your DBA on this)
7. Compare object counts on target database with those on source database
8. Check for instances of an invalid server name in workflow and form data
Run these SQL Commands to verify that there are no "bad"
server name references
select distinct servername from field_enum;
select distinct tfserver from field_table;
select distinct server from char_menu_query;
select distinct server from char_menu_sql;
select distinct server from char_menu_dd;
select distinct servername from filter_call;
select distinct servername from actlink_call;
select distinct servername from actlink_open;
select distinct server from report; (if you have the report server installed)
select distinct servername from field_enum;
select distinct tfserver from field_table;
select distinct server from char_menu_query;
select distinct server from char_menu_sql;
select distinct server from char_menu_dd;
select distinct servername from filter_call;
select distinct servername from actlink_call;
select distinct servername from actlink_open;
select distinct server from report; (if you have the report server installed)
If a search returns values other than those expected, use
values from the results to structure a SQL statement to correct the erroneous
value. The format of the statement is: update <table name> set
<column name> = “@” where <column name> = ‘erroneous
value’;
9. First start the target Remedy server. If the
target Remedy server starts with errors, perform the following:
•Edit the ar.conf file and set Debug-mode: 17
•Start the arsystem
•If the server does not start up, verify that the API logs report RPC id's of 390600 through 390695 and not 000000. RPC id 000000 is used while arserverd is caching the forms and workflow in memory.
•Edit the ar.conf file and set Debug-mode: 17
•Start the arsystem
•If the server does not start up, verify that the API logs report RPC id's of 390600 through 390695 and not 000000. RPC id 000000 is used while arserverd is caching the forms and workflow in memory.
•repeat these steps until all errors are
resolved
10. Once ARSystem starts with no errors
•Stop the arsystem
•Edit the ar.conf file and remove Debug-mode: 17
•Add IP-Name aliases in the ar.conf file for any server names that could still be embedded in the system
•Stop the arsystem
•Edit the ar.conf file and remove Debug-mode: 17
•Add IP-Name aliases in the ar.conf file for any server names that could still be embedded in the system
•Start arsystem.
Of
course you should work with your DBA to make sure these SQL statements work in
your environment.
Hope
this helps,
Marc
Simmons
Remedy Development
(703)456-1559
"Every day above ground is a good day..... the rest is just a choice!"
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tim Button
Sent: Monday, April 24, 2006 3:07 PM
To: [email protected]
Subject: Migration and Name Change
We are currently moving our server set from one location to another while re-naming the server at the same time.
HPUX
Oracle 9
ARS 5.1.2
What is the best process that anyone has used to do this? We are a little leery about some of the solutions we have explored, but we don't want to re-build everything and do manual or migrated data loads either.
Is there a simple way of doing a rename and restore at the same time for a
Remedy production database? Can anyone provide a lessons learned as we attempt
this endeavor?
Timothy Button
Remedy Systems Consultant
Remedy Systems Consultant
Plano, TX
