Platinum Migration to New Server??....

[keithlages]

Where can I find a walkthrough to help me move my Platinum and Clientele server to a new, faster server. I thought I had it licked after 4 days of fumbling but I cant seem to be able to open some windows in Platinum ... like Sales Order Shipment Entry and others like it. No errors, the window just starts to load and then vanishes. Has anyone here moved this package before? ....
Any help is greatly appreciated..

Thanks

Keith

 

[mannington]

Are you moving from a Pervasive server to another Pervasive server? Different versions? Have the workstations changed in terms of configuration?

Respond here or e-mail relictele@hotmail.com if you prefer.

Thanks...

 

[keithlages]

Hi Mannington! Thanks for the reply, I'm keeping everything the same and just moving the existing Platinum software for a single company and the Pervasive SQL engine to a new Dell Poweredge server. I would just like to do it right the first time. Nothing will change version or workstation -wise.
Thanks!!
Keith

 

[SelinaH]

Page: 605PSC
Summary: Housekeeping Steps When Copying Platinum DBs Across Servers
AnswerBook: ERA Solutions

Housekeeping Steps When Copying Platinum Databases Across Servers

When copying databases from one server to another, you may need to do some or all of the following if the Platinum SQL or ERA server objects haven't previously been installed on the target server:
Platinum License (all modules)

The Platinum license info is stored in tables in the server's master database. There are ~ nine such tables, but you really only need to worry about two - s2psrvrs and s2passwd to get the app licensed so that users can access (you won't be able to view the license info via System Manger with this approach though).

· You can create the tables (they won't exist if you copied just the control and company databases to the new server) by running the s2psrvrs.ppc and s2passwd.ppc create table scripts located in the ins\cre directory of the Platinum server code.

· After creating the tables, you can populate them with needed values by selecting them off of the production or source server and inserting into the target server. The Platinum license allows for this if it is a test server in a licensed customer's site.

At this point, the server is licensed for all apps specified in the source server license.

ADM (Advanced Distribution and Manufacturing modules)

The ADM modules use an alias to the login and user 'psqladm' (this alias is required), so there are some additional steps to get this synched up :

1. Run the following statement in the control and company databases:
EXEC sp_dropuser 'psqladm'

2.Run the following statement in the master database:
EXEC sp_droplogin 'psqladm'

3. In the control database and in the company databases where Manufacturing
and Distribution is installed, run the stored procedure z_install in a SQL
query tool, as follows:

exec z_install

The z_install stored procedure will create the login for 'psqladm', add the
'psqladm' user to the databases, and call the z_install_permissions stored
procedure, which grants rights in the databases. After z_install is run, the
Database Error should go away.

At this point, users should be able to access the ADM modules

Control Database Listing (all modules - ERA 7.0)

The Platinum ERA 7.0 install puts a table in the server's master database that points the app to the control databases - masterlst (there is also a copy of this table in the control database). Prior versions don't put this table in the server's master database, just in the control database - so you shouldn't have to add this table for versions prior to ERA 7.0.

· You first need to create the table by running the masterlst.ppc create table script in the ins\cre directory of the Platinum server code.

· You add the Platinum control databases in this table via an insert:

insert masterlst
values (NULL, 'control_db_name', 'control_db_name')

· The group_name column in this table isn't really ever used, so you can insert the control_db_name for this column.