Axis RightFax 8.5 Guía de instalación Pagina 43

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 106
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 42
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
Features/Limitations:
Simple and straightforward. There is no need to pre-create an Oracle Database in the
destination machine.
Fast. The total time needed is governed by physically transferring datafiles from source
machine to destination machine.
Whole database copy. If there are data in the source database that the client does not want to
copy to the destination database, then data cleaning process should be carried out in the
destination database after the copy.
Source and destination servers must be the same platform, same operating system and same
Oracle Database version between.
Requires DBA skills.
Requires down time in the source database if there is no hot-backup.
Oracle Database Export/Import Utility
Using the Oracle Database export/import method, the entire Oracle Transportation Management
database structures can be copied from one database to another. To successfully copy an Oracle
Transportation Management database, following guidelines are recommended:
1. Create all tablespaces used by Oracle Transportation Management first in the target database.
2. Check if all of Oracle Transportation Management required init.ora parameters are properly set
in the target database.
3. Oracle Transportation Management database roles and schema users should be created in the
target database before the import. This should be done by running Oracle Transportation
Management supplied SQL scripts as described below.
4. Log in to the target database as user SYS.
@create_glog_users.sql -- Make sure no errors
5. Perform export on the source database. The easiest way is to do a FULL export. But if for any
reason you do not want a FULL export, you can do a schema export. Oracle supplies a schema
export parameter file (exp_GC3.par), where it lists all schemas the Oracle Transportation
Management application needs.
6. Perform import on the target database. You can do a FULL import if the export was a FULL
export. Alternatively you can do a schema import. Oracle supplies a schema import parameter
file (imp_GC3.par), where it lists all schemas the Oracle Transportation Management
application needs.
7. After the import finished successfully, there are post-import SQL scripts to be run in the target
database. The steps to run these scripts are described in the Installation Guide in the
Database Server section. It is important to follow the instructions to run the scripts. Ensure
you log in to the database as the correct users when running the scripts.
Features/Limitations:
Can be used between different platforms and different operating systems.
Oracle Database version in the destination environment must be equal or higher than that of
source environment.
Need to pre-create an Oracle Database in the destination environment.
Whole Oracle Transportation Management database copy. If there are data in the source
database that the client does not want to be copied to the destination database, then data
cleaning process should be carried out in the destination database after the import.
May take a long time to finish depending on the size of the database.
Vista de pagina 42
1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 105 106

Comentarios a estos manuales

Sin comentarios