XE to E812 Upgrade - Declaring XE Datasources on 8.12

clmates

Reputable Poster
Hi to all.

We are on an upgrade process between two Enterprise Servers

We have the XE Server on Windows NT + SQL 7.0

We have the E812 Server with Windows 2003 + DB2 UDB

We are using the same deployment Server using snapshot

We have successful installed the E812 Deployment and Platform Pack

We have the PS812 Environment Running in both deployment Servers, Web Clients and Development Clients

We want now to declare the DV7333 Datasources in order to make an upgrade plan form DV7333 to DV812

We have tried declaring the Business Data - TEST Datasource similar the one we have in XE, but we are unable to browse data with the UTB in this datasource we get a Table not found in datasource (our ODBC datasource is working)

If we try the reverse, declaring the DV812 Datasource in one XE Workstation, it works!!!!

we need to know how to declare this datasource or if we are missing any step

we also want to know if someone has made a similar upgrade and what is the best procedure:

A. to declare the XE datasources in the 8.12 Installation and then use them in an upgrade plan

B. To declare the DV8.12 Datasources in XE and use the R98403 to copy data, central objects and control tables over the DV812 database

Regarding this point B, we have not yet created the DV812 installation plan, we have installed DV812 pathcodes and databases during the installation process.

How will can copy our custom objects from XE to E812 in this B approach?, is possible?

Many Thanks
 
Hello,

One thing to remember is that business and control table data are updated "in place" what this means is that the upgrade process DOES NOT move XE business data and control table data into a new database, this is NOT the case for the OL, DD, System, Central Objects, which get merged.

The reason you can't pull up the data in those tables from within 8.12 is most likely because the table specs in 8.12 don't match the table definitions in the DB.

If you want have the business data and control tables upgraded in a separate DB than where the XE data resides, my recommendation is to export the data from the XE DB and import it into the 8.12 DB, then point your Business Data and Control Tables data sources to the 8.12 database.

This is what I have done on our 8.9 to 8.12 upgrade, I have effectively created a "sandbox" environment, where we are able to upgrade a copy of DV without actually affecting our "live" DV 8.9 environment. When we have worked through all the issues, we will then upgrade our "live" DV 8.9 environment.

Hope this helps.
Matthew
 
Hi Mattew

[ QUOTE ]
Hello,

One thing to remember is that business and control table data are updated "in place" what this means is that the upgrade process DOES NOT move XE business data and control table data into a new database, this is NOT the case for the OL, DD, System, Central Objects, which get merged.



[/ QUOTE ]

OK, if we have the DV812 database installed. and we have declared the Business Data DV812 Database Datasource in our XE installation. We have copied a single table with R98403 and cheked the contens with the Database Control Panel and the data is copied.

Is possible to copy all business data, control tables, central objects, versions (for this DV environment) form XE to the 8.12 Database, and then create an isntallation or upgrade plan to have objects Merged?

Our main concern is to merge objects, because we now that we can later refresh the DV812 data again from the XE installation.

Is right this procedure?

What we need to do an upgrade plan or an installation plan?

if is an upgrade plan, shoud we use the standar DV812 database or better to create a new one only for the upgrade process?

[ QUOTE ]


If you want have the business data and control tables upgraded in a separate DB than where the XE data resides, my recommendation is to export the data from the XE DB and import it into the 8.12 DB, then point your Business Data and Control Tables data sources to the 8.12 database.



[/ QUOTE ]

How you did this export, with R98403 or with the database tools?

[ QUOTE ]


This is what I have done on our 8.9 to 8.12 upgrade, I have effectively created a "sandbox" environment, where we are able to upgrade a copy of DV without actually affecting our "live" DV 8.9 environment. When we have worked through all the issues, we will then upgrade our "live" DV 8.9 environment.



[/ QUOTE ]

We are using snapshot in the deployment server, and the 8.12 deployment, knows nothing of the XE installation, should we have to declare the XE system datasources in the 8.12 deployment?

Many Thanks

Greetings

Hope this helps.
Matthew

[/ QUOTE ]
 
Yes,

You can use R98403 to copy everything from your XE DV database to your 8.12 database, but it would be much quicker to use the DB tools to do so. As for merged objects being a concern, you can rerun the merges, no problem. I think your procedure is a good one, that is what we are doing, this way we can time everything and work out the issues without affecting the live environment, then when we want to upgrade the live environment, we just move the data from the old DB to the new and rerun the upgrade plan.

As for the 8.12 install not knowing about the xe install, one of the steps is to point the planner - XE (not sure if this is the EXACT namer of the datasource, since we are on 8.9, ours was Planner - B) datasource to the OLD planner DB (in your case it would be to the XE Planner access database).

Reememeber, the first part of the upgrade involves upgrading Pristine. This is not a "true" upgrade as it only involves pulling across some of your system mappings and data from your "old" install. And where does the Pristine upgrade plan get the "old" system mappings and data?? You specify it when creating the plan, but it defaults to the "old" planner data source, in our case it was Planner - B9.

Matthew
 
Hi Mattew.

[ QUOTE ]
Yes,

You can use R98403 to copy everything from your XE DV database to your 8.12 database, but it would be much quicker to use the DB tools to do so. As for merged objects being a concern, you can rerun the merges, no problem. I think your procedure is a good one, that is what we are doing, this way we can time everything and work out the issues without affecting the live environment, then when we want to upgrade the live environment, we just move the data from the old DB to the new and rerun the upgrade plan.


[/ QUOTE ]

you can remerge again form DV7333 to DV812? is possible to remerge only selected objects?

[ QUOTE ]


As for the 8.12 install not knowing about the xe install, one of the steps is to point the planner - XE (not sure if this is the EXACT namer of the datasource, since we are on 8.9, ours was Planner - B) datasource to the OLD planner DB (in your case it would be to the XE Planner access database).

Reememeber, the first part of the upgrade involves upgrading Pristine. This is not a "true" upgrade as it only involves pulling across some of your system mappings and data from your "old" install. And where does the Pristine upgrade plan get the "old" system mappings and data?? You specify it when creating the plan, but it defaults to the "old" planner data source, in our case it was Planner - B9.


[/ QUOTE ]

Well, we have installed pristine (not upgraded), we are going to try to upgrade directly dv7333 mapping our current planner XE database on the 8.12 installation.

One problem is that we never have maintained current the pristine environment, and thus we don't know its status in order to use upgrade it.

Well you have give us some tranquility in order to say that we are in the good way.

Many Thanks

Greetings.
 
Back
Top