Kbase P37512: Should ProtoOra be run on the client site or should the newl
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/08/2003 |
|
Status: Unverified
GOAL:
Should ProtoOra be run on the client site or should the newly created schema holder be deployed to client site?
GOAL:
What is the best way to deploy a Progress schema holder to client site?
GOAL:
What things need to be done on the ORACLE side if the Progress schema holder is being deployed?
FACT(s) (Environment):
Oracle DataServer
FIX:
The guidelines and techniques that apply to deploying a Progress database apply to deploying a schema holder for an ORACLE database. There is, however, an additional consideration. Make sure that you make changes to both the supporting ORACLE database and the schema holder. For example, when you provide an SQL script to modify an ORACLE database, you must also provide a new data definitions file or 4GL code to update the schema holder. Keep in mind that the SQL script that you send to a customer's site must consider how the ORACLE database is configured on their system, including table space and security issues.
There are two techniques for updating a deployed schema holder:
1. Allow your users to use the DataServer Update and Add Table Definitions utility.
2. Send a new data definitions file for the schema holder. Your users can load the .df file into an empty Progress database. Consider any CRC issues.
If the client site is willing and able to run the schema migration at the site, then do so. You can load the .sql and data when running the Progress to Oracle Migration. However, data load may take longer than loading the definitions into ORACLE, you you may want to load the data seperately.
If you choose to not run the schema migration, then have the client create a user in ORACLE. Make sure that this user has all the correct privilleges that are required by the DataServer. And load the .sql and .d files into ORACLE at the client site.