The following workflow pertains only to configuring a Hub and Spoke Global Workshare Configuration for Oracle databases between one Host and one or more Satellites.
GoldenGate is used as the driving software for the replication of data from the Host to all Satellite locations. It connects and captures database changes at the Host location, stages the changes into local files, propagates the changes to the remote servers, and then applies the changes at the Satellite database locations. Model database changes at Satellite locations are similarly propagated back to the Host location.
You cannot use Global Workshare if you are running Oracle on Linux. You must run Oracle on a Windows-based computer to set up Global Workshare.
Verify Databases Have Supplemental Logging Enabled
All Oracle databases that participate as either Host or Satellites must be configured to write supplemental data to the redo log files. This supplemental data enabling is required for successful replication.
Verify Databases are in ARCHIVELOG Mode
When you run a database in ARCHIVELOG mode, you enable the archiving of the redo log. The changes (to data, tables, schemas, and so on) that take place at the Host and Satellite locations are recorded in the database redo log files. Because the GoldenGate Extract process reads information from the redo log files of the database, any database producing changes that are captured must be running in ARCHIVELOG mode.
Verify Databases are enabled for GoldenGate Replication
The ENABLE_GOLDENGATE_REPLICATION parameter of the Oracle instance must be enabled. You must also modify the UNDO_RETENTION value. For more information, see Verify Databases are enabled for GoldenGate Replication.
Allocate streams pool size
Smart 3D uses the Integrated Capture mode for reading data. For Integrated Capture mode, Oracle requires that the streams pool size value be set to handle heavy workloads from the extract processes. To do this, you must set the value to prevent performance and memory issues with the Oracle database. For more information, see Allocate streams pool size.
GoldenGate 126.96.36.199.2 is an installation program that prompts you for the input needed to install the GoldenGate software. For more information, see Install GoldenGate.
GoldenGate replication produces a significant amount of input and output operations on the disk where it is installed. To avoid any performance impacts, install GoldenGate into a folder that is located on a physically independent disk or RAID array from the Oracle database files.
Create the GoldenGate Administrator account
The GoldenGate environment is managed by an administrative database user account. To manage the GoldenGate environment, you must create a GoldenGate administrator user GGADMIN with the appropriate privileges. Do not use the SYS or SYSTEM user as the GoldenGate administrator.
The GoldenGate administrative user can have any valid name. In the case of a multiple Global Workshare configuration, we recommend that each site has its own GoldenGate administrative user with his or her own tablespace.
A script for creating this account is delivered in SharedContent.
Create the Smart 3D GoldenGate User Alias
The Smart 3D GoldenGate user alias is an encrypted GoldenGate representation of an Oracle account. The alias is used to configure and run the GoldenGate processes. This alias is essential to operate the GoldenGate software in a Global Workshare configuration.
Register all Oracle instances on Smart 3D administrative machine
The Smart 3D administrative computer is required to have all the servers registered that are participating in the workshare. The administrative machine executes the command Duplicate model for workshare for all locations, which is essential for the proper generation of replication scripts.
After the Oracle instances are registered on the S3D administrative computer, you can use the New > Location command in the Project Management task to create your Satellite locations. For more information on creating Satellite locations, see Create Locations.
Duplicate Model for Workshare
After the Satellite locations are created, use the Duplicate Model for Workshare command in the Project Management task to replicate the Host databases.
A variety of replication scripts and batch files are generated during execution of the Duplicate Model for Workshare command. These files are created in a subfolder of the user's local temp folder on the administrative computer on which you ran the Duplicate Model for Workshare command. If you are creating a new GWC, the subfolder is named Replication<LocationName>_<ModelName>. If you are adding a single Satellite to an existing GWC, the subfolder is named AddSatellite<LocationName>_<ModelName>.
Copy generated scripts into GoldenGate folders
The contents of the scripts generated in your temp folder must be copied to their corresponding GoldenGate installation directories for each server instance. Copy the files under each location from the Temp folder to their corresponding GoldenGate installation directories.
Execute PreBackup scripts
The administrator account of the database server executes the PreBackup scripts from a command line. The scripts create the initial objects required for replication including the GoldenGate manager service. Execute scripts on the Host and all corresponding Satellite servers.
Make a Smart 3D backup
With Project Management, you can make a backup of the Host databases on the administrative computer. These databases are then transferred and restored on the Satellite servers. Include a copy of the SharedContent folder along with any additional supporting data (Reference 3D files, DGN, DWG referenced files, and so on) on the backup.
Restore Duplicated Databases at Satellite Locations
The duplicated databases are restored on each Satellite location server using the same names as the original databases on the Host server. First, use the Database Wizard to restore the Site and Site schema database. Then, use Tools > Restore in the Project Management task to restore the Catalog, Catalog schema, and Model databases. For more information about restoring databases, see the Project Management User's Guide available from Help > Printable Guides.
Make sure the Site Database Workshare Location box contains the correct location name when restoring the site.
Execute PostRestore scripts
The administrator account of the database server executes the PostRestore scripts from a command line. The scripts create the remaining objects required for replication and starts the GoldenGate processes. Execute scripts on the Host and on all corresponding Satellite servers.
Regenerate Reports Databases
For performance reasons, the Reports and Reports schema databases are not replicated from the Host location and therefore need to be locally generated at each location. At each satellite location, right-click the Model in the Project Management tree view, and then select Regenerate Reports Database. For more information on regenerating the Reports database, see the Project Management User's Guide available from Help > Printable Guides.
Install and configure the Duplication Synchronization Service (DuSS)
You must activate the Duplication Synchronization Service (DuSS) at the end of the Global Workshare setup. This service is run to prevent dangling relationships between objects that are propagated or replicated between the servers. The Duplication Synchronization Service helps prevent certain inconsistencies, particularly those involving to do list entries that arise during the updates that occur in Global Workshare Configuration. The DuSS addresses these issues to keep the model data accurate at all locations. For more information on installing and configuring the Duplication Synchronization Service, see Install and configure the Duplication Synchronization Service (DuSS).
Firewall Exceptions for GoldenGate
There are certain firewall exceptions that needs to be set for GoldenGate software. For more information, see Firewall Exceptions for GoldenGate.
Do not delete the Oracle Archive Log files, unless you are certain they can be safely removed. Deleting these files while GoldenGate still requires them causes the Extract processes to hang. This hang event can be complicated to resolve and sometimes the only solution is to consolidate and reconfigure the Global Workshare.
Oracle GoldenGate should be monitored daily to confirm that the changes are being propagated and that all processes are enabled and healthy. Immediately contact Smart 3D Support for an investigation if problems are noticed, as these issues compound with time. For more information, see Monitoring Replication.
Configuring Global Workshare within an integrated environment is a detailed and complicated process. For more information, contact support at http://www.hexagonppm.com.
What do you want to do?