Management Pack for Oracle® GoldenGate

• Oracle GoldenGate Director only supports UTF-8 format. Oracle GoldenGate Director does not support other character sets so some characters could display incorrectly.

• DB2 z/OS support is introduced in Oracle GoldenGate release 11g (11.2.1.0.3). Refer to Bug 13861016.

• Before the Oracle GoldenGate 11g (11.2.1.0.2) release, list tables is not supported for tables not owned by the current user. Refer to Bug 13885563.

• If SSL Mode Login is enabled, an exception is generated instead of a clear message that explains the condition.

• An exception occurs when accessing the database to create a DEFGEN file or to display a list of tables (SHOW TABLES) if the database contains a table that has a special character that is not supported. The expected result is to generate a clear message that explains the condition.

• Oracle GoldenGate Director requires the installation of Oracle GoldenGate release 11g (11.2.1.0.3) and higher.

• The Param check button in the Param File Editor is not available by design.

Only processes that are typically defined in GGSCI can be configured, monitored and controlled with Oracle GoldenGate Director. Standalone processes and programs such as DDLGEN, MEASFLS, MEASRPT, and TRIGGEN that are run from the operating system's command line cannot be created or monitored with Oracle GoldenGate Director.

On Windows, UNIX, and NonStop, only the following can be configured, monitored, and controlled with Oracle GoldenGate Director:

• Extract

• Replicat

• Manager

• trails (local and remote)

• files (local and remote)

• Extract and Replicat tasks

On Nonstop, Logger processes can be monitored and controlled, but they must be configured or changed by using GGSCI and the LOGPARM file, not through the Oracle GoldenGate Director Client.

If you have changed the default properties in the boot.properties file, when you start the server domain it may cause an Oracle WebLogic Server security error similar to the following:

<Sep 11, 2017 2:06:08 AM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm ggRealm.>
<Sep 11, 2017 2:06:08 AM PDT> <Critical> <Security> <BEA-090402> 
<Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Sep 11, 2017 2:06:08 AM PDT> <Critical> <WebLogicServer> <BEA-000386>

This depends on the WLS_USER and WLS_PW that is set. If this error occurs, you can delete the Director_server_install_dir\domain\servers\localhost\security\boot.properties file, and then enter the username and password manually on start of the Oracle GoldenGate Director Server domain. 

Oracle GoldenGate Director does not support macros that are defined within a parameter file. Oracle GoldenGate Director does support macros that are referenced externally with the INCLUDE parameter. Oracle GoldenGate Director cannot process the parameter file if the macro defines the following parameters:

• EXTRACT

• REPLICAT

• RMTHOST

• RMTTRAIL

• RMTFILE

• RMTBATCH

• EXTFILE

• EXTTRAIL

• SOURCEDB

• USERID

• TABLE

• MAP

• COLMAP

The built-in DEFGEN utility in Oracle GoldenGate Director creates definitions files with all-default settings. To customize definitions output, the command-line version of DEFGEN must be used.

The built-in GGSCI window in Oracle GoldenGate Director does not support the following Oracle GoldenGate commands. These commands must be issued from GGSCI on the Oracle GoldenGate host.

• All database commands, including DBLOGIN

• VERSION

• FC

• HISTORY

• !

• SHELL

• EDIT PARAMS

• EXIT

• RESTART

• ADD TRACETABLE

Oracle GoldenGate Director has no interface for adding an Oracle GoldenGate TRACETABLE to the Oracle database, nor can one be created from the built-in GGSCI interface in Oracle GoldenGate Director. The ADD TRACETABLE command (and all other database commands) require database login with DBLOGIN, so a local GGSCI session on the Oracle GoldenGate host must be used.

Oracle GoldenGate Director does not support a single Capture object writing to multiple files in different formats using FORMATASCII, FORMATSQL, and FORMATXML. The format parameters can only be applied globally by inserting them into the Capture object. To obtain the same data in different formats, a Capture object must be defined for each format.

In addition, Oracle GoldenGate Director cannot process existing Capture objects that are configured with multiple format parameters. This can cause unexpected behavior if the existing objects are saved using Oracle GoldenGate Director.

A Delivery process from one Oracle GoldenGate instance on a host cannot be configured through Oracle GoldenGate Director to read a trail written by a Capture process from a different Oracle GoldenGate instance on the same machine. This configuration can be created through GGSCI, but it will not be displayed correctly in Oracle GoldenGate Director. No line will be shown connecting the processes.

If you are using a version of Oracle GoldenGate core prior to 11.1.1.0.6 there have been intermittent problems displaying logs on the Oracle GoldenGate Director Desktop and Activity Console. A change was made to the core in Oracle GoldenGate 11.1.1.0.6 to fix this issue.

Oracle GoldenGate Director cannot generate absolute paths for RMTTRAIL on Windows platforms because SQL Server Extract is unable to fetch and write the data in trail file.

You can workaround this issue by using the ggsci ALTER EXTRACT command to modify RMTTRAIL in your Extract parameter file with the absolute path. 

To view the Oracle GoldenGate Knowledge Base, follow these steps:

If you need help with My Oracle Support, click Help at the top of the application window.

If you cannot find an answer to your question or problem in the Knowledge Base, you can open a support case with Oracle Support by following these steps: