SQL Server - Extract Error - OGG-00868 Supplemental logging is disabled

Question

Hello,
We are trying to replicate from a SQL Server 2008 database to Oracle database, but when trying to start the extract process we are getting the following error message:
OGG-00868 Supplemental logging is disabled for database 'GoldenGate'. To enable logging, perform the following: 1) Set 'trunc. log on chkpt.' to false. 2) Create a full backup of the database. Please refer to the "Oracle GoldenGate For Windows and UNIX Administration Guide" for details.
I have read that for enabling the supplemental logging is enough to "add trandata table_name", and this is done, and the extract process we are using is the following:
EXTRACT cap_or4
SOURCEDB GoldenGate
TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT
EXTTRAIL c:\GoldenGate\V28983-01-GG-111112-SQLServer-Windows-x64\dirdat\C4
TABLE GoldenGate.dbo.DES_T1;
And the 'trunc.log on chkpt' is set to false.
We don’t know what else to do, or to check... does anyone have any idea?!
Thank you very much, best regards,
Araitz.-

Answer 1

Have you followed all the process for installing as per the guide? clearly you missed something
Please follow below steps.
Installation & Configuration of Oracle GoldenGate for MS SQL Server:
Pre-requisites:
1.Change Data Capture (CDC) must be enabled for Oracle GoldenGate and will be enabled by Oracle GoldenGate by means of the ADD TRANDATA command.
2.SQL Server source database must be set to use the full recovery model.
3.Oracle GoldenGate does not support system databases.
4.After the source database is set to full recovery, a full database backup must be taken.
5.SQL Server 2008 ODBC/OLE DB: SQL Server Native Client 10.0 driver
6.Oracle GoldenGate processes can use either Windows Authentication or SQL Server Authentication to connect to a database.
7.Before installing Oracle GoldenGate on a Windows system, install and configure the Microsoft Visual C ++ 2005 SP1 Redistributable Package. Make certain it
is the SP1 version of this package, and make certain to get the correct bit version for your server. This package installs runtime components of Visual C++
Libraries. For more information, and to download this package, go to http://www.microsoft.com.
Privileges:
1.Required SQL Server privileges for Manager when using Windows authentication
Extract(source system)
BUILTIN\Administrators account must be a member of the SQL Server fixed server role System Administrators.
Account must be a member of the SQL Server fixed server role System Administrators
Replicat (target system)
BUILTIN\Administrators account must be at least a member of the db_owner fixed database role of the target database.
Account must be at least a member of the db_owner fixed database role of the target database.
2.Required SQL Server privileges for Extract and Replicat when using SQL Server authentication
Extract - Member of the SQL Server fixed server role System Administrators.
Replicat - At least a member of the db_owner fixed database role of the target database.
Downloading Oracle GoldenGate
Download the appropriate Oracle GoldenGate build to each system that will be part of the Oracle GoldenGate configuration.
1. Navigate to http://edelivery.oracle.com.
2. On the Welcome page:
--Select your language.
--Click Continue.
3. On the Export Validation page:
--Enter your identification information.
--Accept the Trial License Agreement (even if you have a permanent license).
--Accept the Export Restrictions.
--Click Continue.
4. On the Media Pack Search page:
--Select the Oracle Fusion Middleware Product Pack.
--Select the platform on which you will be installing the software.
--Click Go.
5. In the Results List:
--Select the Oracle GoldenGate Media Pack that you want.
--Click Continue.
6. On the Download page:
--Click Download for each component that you want. Follow the automatic download
process to transfer the mediapack.zip file to your system.
Installing the Oracle GoldenGate files
1. Unzip the downloaded file(s) by using WinZip or an equivalent compression product.
2. Move the files in binary mode to a folder on the drive where you want to install Oracle GoldenGate. Do not install Oracle GoldenGate into a folder that contains spaces in its name, even if the path is in quotes. For example:
C:\“Oracle GoldenGate” is not valid.
C:\Oracle_GoldenGate is valid.
3. From the Oracle GoldenGate folder, run the GGSCI program.
4. In GGSCI, issue the following command to create the Oracle GoldenGate working
directories.
CREATE SUBDIRS
a.Create the necessary working directories for GG.
Source DB:
GGSCI>create subdirs
Target DB:
GGSCI>create subdirs
Install the GoldenGate Manager process
1.Create a GLOBALS parameter file
--Execute the following commands from the <install location>.
GGSCI> EDIT PARAMS ./GLOBALS
--In the text editor, type the following:
MGRSERVNAME <mgr service>
Using a GLOBALS file in each GoldenGate instance allows you to run multiple Managers as services on Windows. When the service is installed, the Manager name
is referenced in GLOBALS, and this name will appear in the Windows Services control panel.
Note! Check to ensure that the GLOBALS file has been added in the GoldenGate installation directory and that it does not have an extension.
--Execute the following command to exit GGSCI.
GGSCI> EXIT
2. Install the Manager service
Execute the following command to run GoldenGate’s INSTALL.EXE . This executable installs Manager as a Windows service and adds GoldenGate events to the
Windows Event Viewer.
Shell> INSTALL ADDSERVICE ADDEVENTS
Note: Adding the Manager as a service is an optional step used when there are multiple environments on the same system or when you want to control the name
of the manager for any reason.
Configuring an ODBC connection
A DSN stores information about how to connect to a SQL Server database through ODBC (Open Database Connectivity). Create a DSN on each SQL Server source
and target system.
NOTE: Replicat will always use ODBC to query the target database for metadata.
To create a SQL Server DSN
1. Run one of the following ODBC clients:
--If using a 32-bit version of Oracle GoldenGate on a 64-bit system, create the DSN by running the ODBCAD32.EXE client from the %SystemRoot%\SysWOW64
folder.
--If using a 64-bit version of Oracle GoldenGate on a 64-bit system, create a DSN by running the default ODBCAD32.EXE client in Control Panel>Administrative
Tools>Data Sources (ODBC).
--If using a version of Oracle GoldenGate other than the preceding, use the default ODBC client in Control Panel>Administrative Tools>Data Sources (ODBC).
2. In the ODBC Data Source Administrator dialog box of the ODBC client, select the System DSN tab, and then click Add.
3. Under Create New Data Source, select the correct SQL Server driver as follows:
--SQL Server 2000: SQL Server driver
--SQL Server 2005: SQL Native Client driver
--SQL Server 2008: SQL Server Native Client 10.0 driver
4. Click Finish. The Create a New Data Source to SQL Server wizard is displayed.
5. Supply the following:
--Name: Can be of your choosing. In a Windows cluster, use one name across all nodes in the cluster.
--Server: Select the SQL Server instance name.
6. Click Next.
7. For login authentication, select With Windows NT authentication using the network login ID for Oracle GoldenGate to use Windows authentication, or select
With SQL Server authentication using a login ID and password entered by the user for Oracle GoldenGate to use database credentials. Supply login information
if selecting SQL Server authentication.
8. Click Next.
9. If the default database is not set to the one that Oracle GoldenGate will connect to,
click Change the default database to, and then select the correct name. Set the other
settings to use ANSI.
10. Click Next.
11. Leave the next page set to the defaults.
12. Click Finish.
13. Click Test Data Source to test the connection.
14. Close the confirmation box and the Create a New Data Source box.
15. Repeat this procedure from step 1 on each SQL Server source and target system.
Setting the database to full recovery model
Oracle GoldenGate requires a SQL Server source database to be set to the full recovery model.
To verify or set the recovery model
1. Connect to the SQL Server instance with either Enterprise Manager for SQL Server 2000 or SQL Server Management Studio for SQL Server 2005 and 2008.
2. Expand the Databases folder.
3. Right-click the source database, and then select Properties.
4. Select the Options tab.
5. Under Recovery, set Model to Full if not already.
6. If the database was in Simple recovery or never had a Full database backup, take a Fulldatabase backup before starting Extract.
7. Click OK.
Enabling supplemental logging
These instructions apply to new installations of Oracle GoldenGate for all supported SQL Server versions. You will enable supplemental logging with the ADD
TRANDATA command so that Extract can capture the information that is required to reconstruct SQL operations on the target. This is more information than
what SQL Server logs by default.
--SQL Server 2005 updated to CU6 for SP2 or later: ADD TRANDATA calls the sys.sp_extended_logging stored procedure.
--SQL Server 2005 pre-CU6 for SP2: ADD TRANDATA creates the following:
A replication publication named [<source database name>]: GoldenGate<source database name> Publisher. To view this publication, look under Replication>Local
Publications in SQL Server Management Studio. This procedure adds the specified table to the publication as an article.
A SQL Server Log Reader Agent job for the publication. This job cannot run concurrently with an Extract process in this configuration.
--SQL Server 2008: ADD TRANDATA enables Change Data Capture (CDC) and creates a minimal Change Data Capture on the specified table.
a.Oracle GoldenGate does not use the CDC tables other than as necessary to enablesupplemental logging.
b.As part of enabling CDC, SQL Server creates two jobs per database: <dbname>_capture and <dbname>_cleanup. The <dbname>_capture job adjusts the secondary
truncation point and captures data from the log to store in the CDC
tables. The <dbname>_cleanup job ages and deletes data captured by CDC.
c.Using the TRANLOGOPTIONS parameter with the MANAGESECONDARYTRUNCATIONPOINT option for Extract removes the <dbname_capture> job, preventing the overhead of
the job loading the CDC tables.
d.The alternative (using TRANLOGOPTIONS with NOMANAGESECONDARYTRUNCATIONPOINT) requires the SQL Server Agent to be running and requires the <dbname>_capture and <dbname>_cleanup jobs to be retained. You will probably need to adjust the <dbname>_cleanup data retention period if the default of three days is not acceptable for storage concerns.
To enable supplemental logging
1. On the source system, run GGSCI.
2. Log into the database from GGSCI.
DBLOGIN SOURCEDB <DSN>[, USERID <user>, PASSWORD <password>]
Where:
-- SOURCEDB <DSN> is the name of the SQL Server data source.
-- USERID <user> is the Extract login and PASSWORD <password> is the password that is required if Extract uses SQL Server authentication.
3. In GGSCI, issue the following command for each table that is, or will be, in the Extract configuration. You can use a wildcard to specify multiple table
names, but not owner names.
ADD TRANDATA <owner>.<table>
NOTE:The Log Reader Agent job cannot run concurrently with the GoldenGate Extract process.
4.Configuration
a.Create and start manager on the source and the destination.
Source DB:
shell>ggsci
GGSCI> edit params mgr
PORT 7809
DYNAMICPORTLIST 7900-7950
DYNAMICPORTREASSIGNDELAY 5
AUTOSTART ER *
AUTORESTART ER *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 30
LAGCRITICALMINUTES 60
LAGREPORTMINUTES 30
PURGEOLDEXTRACTS c:\ogg\dirdat\T*, USECHECKPOINTS, MINKEEPFILES 10
GGSCI> start manager
GGSCI>info all
b. Create the extract group on the source side:
GGSCI> edit params EXT1
Add the following lines to the new parameter file
EXTRACT EXT1
SOURCEDB <DSN>, USERID ogg, PASSWORD ogg@321!
TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT
EXTTRAIL c:\ogg\dirdat\T1
DISCARDFILE c:\ogg\dirrpt\EXT1.DSC, PURGE, MEGABYTES 100
TABLE dbo.TCUSTMER;
TABLE dbo.TCUSTORD;
GGSCI>ADD EXTRACT EXT1, TRANLOG, BEGIN NOW
GGSCI>ADD EXTTRAIL c:\ogg\dirdat\T1, EXTRACT EXT1, MEGABYTES 100
GGSCI> edit params PMP1
Add the following lines to the new parameter file
EXTRACT PMP1
SOURCEDB <DSN>, USERID ogg, PASSWORD ogg@321!
PASSTHRU
RMTHOST dr, MGRPORT 7810
RMTTRAIL c:\ogg\dirdat\P1
TABLE dbo.TCUSTMER;
TABLE dbo.TCUSTORD;
GGSCI> ADD EXTRACT PMP1, EXTTRAILSOURCE c:\ogg\dirdat\T1
GGSCI> ADD EXTTRAIL c:\ogg\dirdat\P1, EXTRACT PMP1, MEGABYTES 100
Target DB:
===========
shell>ggsci
GGSCI> edit params mgr
PORT 7810
AUTOSTART ER *
AUTORESTART ER *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 30
LAGCRITICALMINUTES 60
LAGREPORTMINUTES 30
PURGEOLDEXTRACTS c:\ogg\dirdat\P*, USECHECKPOINTS, MINKEEPFILES 10
GGSCI> start manager
GGSCI>info all
Create parameter file for replicat:
GGSCI> edit params REP1
REPLICAT REP1
ASSUMETARGETDEFS
TARGETDB <dsn>, USERID ogg@DR, PASSWORD ogg@321!
DISCARDFILE c:\ogg\dirrpt\REP1.DSC, append, megabytes 100
HANDLECOLLISIONS
ASSUMETARGETDEFS
MAP dbo.TCUSTMER, TARGET dbo.TCUSTMER;
MAP dbo.TCUSTORD, TARGET dbo.TCUSTORD;
GGSCI>ADD REPLICAT REP1, RMTTRAIL c:\ogg\dirdat\P1, nodbcheckpoint
# Start extract and replicat:
Source:
GGSCI> start er *
Destination:
GGSCI> start er *Greetings,
N K