DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Wednesday, September 27, 2017

Encountering Error 20372 While Running adcfgclone appsTier

ERROR - CLONE-20372 Server port validation failed
 
This error is reported in logs when adcfgclone.pl  run for a R12.2.5 appsTier where many instances are running on same server.

SEVERE : Aug 7, 2017 16:36:36 - ERROR - CLONE-20372   Server port validation failed.
SEVERE : Aug 7, 2017 16:36:36 - CAUSE - CLONE-20372   Possible causes were :Ports of following servers - oacore_server3(7214) - were not available.
SEVERE : Aug 7, 2017 16:36:36 - ACTION - CLONE-20372   Provide valid free ports or if those servers are targeted to non admin host, then use temporary port range mechanism.
java.lang.Exception: Error in validating "SERVER_CONFIG" parameters in "moveplan".
        at oracle.as.clone.cloner.component.j2ee.util.J2EEGenericValidationUtil.validateServerConfig(J2EEGenericValidationUtil.java:218)
        at oracle.as.clone.cloner.component.j2ee.config.GenericPasteConfigSteps.getServerConfig(GenericPasteConfigSteps.java:922)
        at oracle.as.clone.cloner.component.j2ee.config.GenericPasteConfigSteps.executeGenericPasteConfig(GenericPasteConfigSteps.java:385)
        at oracle.as.clone.cloner.component.J2EEComponentApplyCloner.doClone(J2EEComponentApplyCloner.java:259)
        at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:63)
        at oracle.as.clone.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:198)
        at oracle.as.clone.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:77)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:131)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:114)
        at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)
        at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct.
        at oracle.as.clone.cloner.component.J2EEComponentApplyCloner.doClone(J2EEComponentApplyCloner.java:314)
        at oracle.as.clone.cloner.Cloner.doFinalClone(Cloner.java:63)
        at oracle.as.clone.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:198)
        at oracle.as.clone.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:77)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:131)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:114)
        at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)
        at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)
SEVERE : Aug 7, 2017 16:36:36 - SEVERE - CLONE-20937  "pasteConfig" operation of J2EE domain failed. Check clone log and error files for more details.
SEVERE : Aug 7, 2017 16:36:36 - ERROR - CLONE-20237   Restoring the sourceid "J2EECOMPONENT@EBS_domain_FLRPRD" has failed.
SEVERE : Aug 7, 2017 16:36:36 - CAUSE - CLONE-20237   An internal operation failed.
SEVERE : Aug 7, 2017 16:36:36 - ACTION - CLONE-20237   Check the clone log for more details.
SEVERE : Aug 7, 2017 16:36:36 - ERROR - CLONE-20218   Cloning is not successful.
SEVERE : Aug 7, 2017 16:36:36 - CAUSE - CLONE-20218   An internal operation failed.
SEVERE : Aug 7, 2017 16:36:36 - ACTION - CLONE-20218   Provide the clone log and error file for investigation.

It seems the ports reported are using by some other instance in the same server.  Searching on support.oracle.com  I found three articles:

EBS 12.2.2.4 RAPID CLONE FAILS WITH ERROR - CLONE-20372 SERVER PORT VALIDATION(Bug ID 20147454)

12.2: N->1 CLONING TO SAME APPS TIER FAILING DUE TO PORT CONFLICT(Bug ID 20389864)

FS_CLONE IS NOT ABLE TO COMPLETE FOR MULTI-NODE SETUP(Bug ID 18460148)

The situation described in the first two bugs is same.  The articles reference each other but don't provide any solution.

Logically thinking, adcfgclone.pl is picking this up from source configuration that is in $COMMON_TOP/clone directory.  So we did grep on subdirectories of $COMMON_TOP/clone:

cd $COMMON_TOP/clone
find . -type f -print | xargs grep 7214

7214 is  the port that failed validation as per logfile.

It is present in

CTXORIG.xml and
FMW/ohs/moveplan.xml
FMW/wls/moveplan.xml

We tried changing the port numbers in CTXORIG.xml and re-tried adcfgclone.pl and it failed again.

So we changed the port numbers of the ports that failed validation in

$COMMON_TOP/clone/FMW/ohs/moveplan.xml and
$COMMON_TOP/clone/FMW/wls/moveplan.xml

cd $FMW_HOME
find . -name detachHome.sh |grep -v Template

The above command returns the detachHome.sh scripts for all the ORACLE_HOMEs inside FMW_HOME.  Executed this to detach all of them.

Removed the FMW_HOME directory

Re-executed
adcfgclone.pl appsTier

It succeeded this time.  Till we get a patch for this bug, we will continue to use this workaround to complete clones.
 
Happy EBS Learning !!

Encountered Error While Running appsTier Preclone in R12.2

I was encountered error while running preclone on appsTier on Production(Source Instance) of Oracle Applications R12.2. The errors message was:
 START: Creating FMW archive.  
Running /u01/app/TEST/R12apps/fs1/FMW_Home/oracle_common/bin/copyBinary.sh -javaHome /u01/app/TEST/R12apps/fs1/EBSapps/comn/clone/FMW/t2pjdk -al /u01/app/TEST/R12apps/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -smw /u01/app/TEST/R12apps/fs1/FMW_Home -ldl /u01/app/TEST/R12apps/fs1/inst/apps/OCM_orasol06/admin/log/clone/fmwT2PStage -invPtrLoc /var/opt/oracle/oraInst.loc -silent true -debug true  
Script Executed in 3047 milliseconds, returning status 255  
ERROR: Script failed, exit code 255
I check the directory $INST_TOP/admin/log/clone and found the file CLONE2016-12-26_02-56-36_1139966449.error with following error:
WARNING : Dec 26, 2016 02:56:37 - WARNING - CLONE-20316    Oracle Home(s) under the Middleware Home have not been included.
WARNING : Dec 26, 2016 02:56:37 - CAUSE - CLONE-20316   Oracle Home(s) registered with the Oracle Inventory were not present inside the Middle
ware Home.
WARNING : Dec 26, 2016 02:56:37 - ACTION - CLONE-20316   Ensure that the Oracle Home(s) present inside the Middleware Home are registered with
 the Oracle Inventory or provide the correct custom inventory.
SEVERE : Dec 26, 2016 02:56:37 - ERROR - CLONE-20435   Some of the Oracle Homes are excluded during copy operation.
SEVERE : Dec 26, 2016 02:56:37 - CAUSE - CLONE-20435   The following Oracle Homes were excluded during copy operation.
 [/u01/app/TEST/R12apps/fs1/FMW_Home/Oracle_EBS-app1, /u01/app/TEST/R12apps/fs1/FMW_Home/oracle_common, /u01/app/TEST/R12apps/fs1/FMW_Home/webtier]  , and
 possible causes were:
1. All the Oracle Homes were not registered with one OraInventory.
2. If all Oracle Homes were registered with a single custom OraInventory, then corresponding inventory pointer file was not provided to T2P op
eration.
3. Canonical path of Oracle Home registered with OraInventory was not child of Middleware Home.
SEVERE : Dec 26, 2016 02:56:37 - ACTION - CLONE-20435   Make sure that all possible causes mentioned in above CAUSE section are taken care.
SEVERE : Dec 26, 2016 02:56:37 - ERROR - CLONE-20218   Cloning is not successful.
SEVERE : Dec 26, 2016 02:56:37 - CAUSE - CLONE-20218   An internal operation failed.
SEVERE : Dec 26, 2016 02:56:37 - ACTION - CLONE-20218   Provide the clone log and error file for investigation.
java.lang.Exception:  Some of the Oracle Homes are excluded during copy operation.
        at oracle.as.clone.cloner.builder.CreateClonerBuilder.showMessageIfAnyOHIgnored(CreateClonerBuilder.java:1356)
        at oracle.as.clone.cloner.builder.CreateClonerBuilder.getMWAndOHCreateClonerObjects(CreateClonerBuilder.java:226)
        at oracle.as.clone.cloner.builder.CreateClonerBuilder.getCreateClonerObjects(CreateClonerBuilder.java:147)
        at oracle.as.clone.cloner.builder.CreateClonerBuilder.getClonerObjects(CreateClonerBuilder.java:133)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:91)
        at oracle.as.clone.client.CloningClient.executeT2PCommand(CloningClient.java:236)
        at oracle.as.clone.client.CloningClient.main(CloningClient.java:124)
~
The error clearly points to a problem with the oracle inventory, and when I checked there was no data about the related Oracle homes. So I had to register them manually as pointed in note "R12.2 How To Re-attach Oracle Homes To The Central Inventory (Doc ID 1586607.1)".
We need to re-attach Oracle Homes:
/u01/app/TEST/R12apps/fs1/FMW_Home/oracle_common/oui/bin/runInstaller -silent -attachHome -invPtrLoc /var/opt/oracle/oraInst.loc ORACLE_HOME="/u01/app/TEST/R12apps/fs1/FMW_Home/oracle_common" ORACLE_HOME_NAME="VIS_TOOLS__u01_common_fs1_EBSapps_10_1_2" CLUSTER_NODES="{}"

/u01/app/TEST/R12apps/fs1/FMW_Home/webtier/oui/bin/runInstaller -silent -attachHome -invPtrLoc /var/opt/oracle/oraInst.loc ORACLE_HOME="/u01/app/TEST/R12apps/fs1/FMW_Home/webtier" ORACLE_HOME_NAME="VIS_TOOLS__u01_webtier_fs1_EBSapps_10_1_2" CLUSTER_NODES="{}"

/u01/app/TEST/R12apps/fs1/FMW_Home/Oracle_EBS-app1/oui/bin/runInstaller -silent -attachHome -invPtrLoc /var/opt/oracle/oraInst.loc ORACLE_HOME="/u01/app/TEST/R12apps/fs1/FMW_Home/Oracle_EBS-app1" ORACLE_HOME_NAME="VIS_TOOLS__u01_ebsapp1_fs1_EBSapps_10_1_2" CLUSTER_NODES="{}"

/u01/app/TEST/R12apps/fs1/EBSapps/10.1.2/oui/bin/runInstaller -silent -attachHome -invPtrLoc /var/opt/oracle/oraInst.loc ORACLE_HOME="/u01/app/TEST/R12apps/fs1/EBSapps/10.1.2" ORACLE_HOME_NAME="VIS_TOOLS__u01_VIS_fs1_EBSapps_10_1_2"
After that I could run the adpreclone appsTier without any problem.

Happy EBS Troubleshooting !

Weblogic BSU Command

About the bsu Command

When using the bsu command, either interactively or through a script, note that this command:
  • Runs the bsu script (bsu.cmd on Windows systems, bsu.sh on UNIX systems) that is located in the MW_HOME\utils\bsu directory. When running the bsu command, first change to this directory on the system from which you are running it.
  • Can be executed from a command file (on Windows) or shell script (on UNIX).
  • Contains the subset of Smart Update functionality that enables you to:
    • Apply and remove patches that are located in an accessible patch download directory
    • View patches that are in the download directory, applied to a product installation on the current system, or applied to a specific patch profile for the current system
    • Generate reports listing the patches applied to a product installation
    The bsu command can also invoke the Smart Update graphical interface and send messages to a log file.
  • Can apply patches to, or view patches on, only those products installed from the system on which this command is run, as follows:
    • If the current system contains a product that was installed by a different system, you cannot apply patches to that installation or view them.
    • If the current system was used to install a product located on a remote-mounted disk drive, you can use the bsu command with that installation.
    Therefore, the restrictions regarding the specific product installations that can be maintained through the bsu command is the same as for Smart Update's graphical interface.
  • Cannot be used for the following:
    • Creating custom patch profiles
    • Locating start scripts to modify
    These capabilities are available only from Smart Update's graphical interface.

    Example:

    bsu -view -status=downloaded -prod_dir=C:\Oracle\Middleware\wlserver_10.3
    
    
    Parameters
    
    
    -help
    -install
    -gui
    -log
    -remove
    -report
    -version
    -view

    Reference:

    https://docs.oracle.com/cd/E14759_01/doc.32/e14143/commands.htm

     

MDB application XXXX is NOT connected to messaging system


This can be avoided by using the parameter below
 
<start-mdbs-with-application>false</start-mdbs-with-application>

In the weblogic-application.xml, Setting start-mdbs-with-application to false forces MDBs to defer starting until after the server instance opens its listen port, near the end of the server boot up process.

If you want to perform startup tasks after JMS and JDBC services are available, but before applications and modules have been activated, you can select the Run Before Application Deployments option in the Administration Console (or set the StartupClassMBean’s LoadBeforeAppActivation attribute to “true”).

If you want to perform startup tasks before JMS and JDBC services are available, you can select the Run Before Application Activations option in the Administration Console (or set the StartupClassMBean’s LoadBeforeAppDeployments attribute to “true”).

Error:

####<Sep 22, 2017 5:08:02 PM EDT> <Info> <WebService> <PROD> <MedServer>  <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1506114482574> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
 

The error itself will suggest you to put this argument in servers > server name > server start

 arguments.


Other way is you can check the under services > Persistent Store > YourServer > Target is pointed to the corret Managed/Admin server where the application is deployed.

This May need server restart in which the changes are made.

Tuesday, September 19, 2017

OGG-01091 Unable to open file "/u01/ggh/dirdat/ab000000006" (error 2, No such file or directory).

Replicat process abends with OGG-01091 Unable to open file... (Error 2, no such file or directory)

After abnormal crash of server , all databases has been restarted and existing goldengate replicat processes abended with below error,

GGSCI (ggsource.doyensys.com) 14> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING                                           
REPLICAT    ABENDED     REP1        00:00:00      11:56:05    


 ERROR   OGG-01091  Oracle GoldenGate Delivery for Oracle, REP1.prm:  Unable to open file <trail_file> (error 2, No such file or directory)

Whenever start of replicat process everytime same error occured. Although trail file exists in related directory, process could not start. To fix this error , related replicat process has been altered to begin with specific trail file which seems absent.

GGSCI (ggsource.doyensys.com) 15> alter REPLICAT REP1,extseqno 7 extrba 0

2017-09-19 22:29:41  INFO    OGG-06594  Replicat REP1 has been altered through GGSCI. Even the start up position might be updated, duplicate suppression remains active in next startup. To override duplicate suppression, start REP1 with NOFILTERDUPTRANSACTIONS option.

REPLICAT altered.


GGSCI (ggsource.doyensys.com) 17> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING                                           
REPLICAT    RUNNING     REP1        00:00:00      00:00:01    

trail file seq no is absent file no

Thursday, September 14, 2017

                                           Unable to find PD KSH version 


Error:-
[oracle@our12-test bin]$ perl adcfgclone.pl dbTier

                     Copyright (c) 2002 Oracle Corporation
                        Redwood Shores, California, USA

                        Oracle Applications Rapid Clone

                                 Version 12.0.0

                      adcfgclone Version 120.31.12010000.1

Enter the APPS password :

Checking for make...    found - /usr/bin/make
 Checking for ld...     found - /usr/bin/ld
 Checking for gcc...    found - /usr/bin/gcc
 Checking for g++...    found - /usr/bin/g++
 Checking for ar...     found - /usr/bin/ar
 Checking for ksh...
 Unable to find PD KSH version.
 Unable to locate all utilities with system path.
 PATH = /testdb/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/etc/opt/emcpower/bin:/home/oracle/bin


WARNING: Could not find all the required OS utilities in the $PATH. Please review the checks above

[oracle@our12-test bin]$

Solution:-

$ export KSH_VERSION='@(#)PD KSH v5.2.14 99/07/13.2'


then problem is resolved and re-run the adcfgclone.

Tuesday, September 12, 2017

ORACLE GOLDEN-GATE REPLICAT PROCESS STATUS IS ABENDED

REPLICAT PROCESS STATUS IS ABENDED

You can ignore your error by just passing the error code in replicat Process.
#if status is abending then go through this.

GGSCI (bld-qa-ts24) 4> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
REPLICAT     ABENDED     REP1        00:00:00      00:00:03

########################################

GGSCI > view report rep1

2016-12-14 11:06:18  ERROR   OGG-00519  Fatal error executing DDL replication: error [Error code [904],
ORA-00904: "NEW_COL": invalid identifier SQL  ALTER TABLE testt1."BB" drop column new_col  /*


GGSCI > edit params rep1

REPLICAT rep1
ASSUMETARGETDEFS
USERID ggate, PASSWORD ggate
gettruncates
DDL INCLUDE ALL
MAP test.*, TARGET test.*;


############add this line ########

ddlerror 904 ignore  ( DDLERROR ((Your error code) "ora-00904" in this case) ignore )

or Add

DDLERROR DEFAULT IGNORE RETRYOP

#Now your params should be like

REPLICAT rep1
ASSUMETARGETDEFS
USERID ggate, PASSWORD ggate
gettruncates
ddlerror 904 ignore
DDL INCLUDE ALL
DDLERROR DEFAULT IGNORE RETRYOP
MAP test1.*, TARGET testt1.*;

##### now Exit from editor #####

### Restart your replicat process ###

GGSCI > start rep1

Sending START request to MANAGER ...
REPLICAT REP1 starting


GGSCI  > info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
REPLICAT    RUNNING     REP1        00:00:00      00:00:03

Monday, September 11, 2017

ORA-20783 *** Please move GGS_ADMIN to its own tablespace

ORA-20783  *** Please move GGS_ADMIN to its own tablespace

I’d been working on a newly refresh database and i need to enable ddl replication on our GG.

but i’m getting *** Please move GGS_ADMIN to its own tablespace

SQL> @ddl_setup.sql

Oracle GoldenGate DDL Replication setup script

Verifying that current user has privileges to install DDL Replication...

You will be prompted for the name of a schema for the Oracle GoldenGate database objects.
NOTE: For an Oracle 10g source, the system recycle bin must be disabled. For Oracle 11g and later, it can be enabled.
NOTE: The schema must be created prior to running this script.
NOTE: Stop all DDL replication before starting this installation.

Enter Oracle GoldenGate schema name:ggs_admin

Working, please wait ...
Spooling to file ddl_setup_spool.txt

Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ...

Check complete.








declare
*
ERROR at line 1:
ORA-20783:
ORA-20783:
Oracle GoldenGate DDL Replication setup:
*** Please move GGS_ADMIN to its own tablespace
ORA-06512: at line 34


Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

SQL>
I check the default table of ggs_admin


SQL> select username, default_tablespace from dba_users where username='GGS_ADMIN';
USERNAME                       DEFAULT_TABLESPACE          
------------------------------ ------------------------------
GGS_ADMIN                      GGS_DATA      

Then i have to check if other user is using GGS_DATA.


SQL> select USERNAME from dba_users where default_tablespace='GGS_DATA';

USERNAME                    
------------------------------
GGS_ADMIN
AQ_USER

SQL>

So i change the AQ_USER default tablespace to other DATA_GBL.


SQL> alter user aq_user default tablespace DATA_GBL;

User altered.

SQL>
so now no other user is using GGS_DATA


SQL> select USERNAME from dba_users where default_tablespace='GGS_DATA';

USERNAME
------------------------------
GGS_ADMIN

SQL>

now, executed again the @ddl_setup.sql and it worked.


SQL> @ddl_setup.sql

Oracle GoldenGate DDL Replication setup script

Verifying that current user has privileges to install DDL Replication...

You will be prompted for the name of a schema for the Oracle GoldenGate database objects.
NOTE: For an Oracle 10g source, the system recycle bin must be disabled. For Oracle 11g and later, it can be enabled.
NOTE: The schema must be created prior to running this script.
NOTE: Stop all DDL replication before starting this installation.

Enter Oracle GoldenGate schema name:ggs_admin

Working, please wait ...
Spooling to file ddl_setup_spool.txt

Checking for sessions that are holding locks on Oracle Golden Gate metadata tables ...

Check complete.











Using GGS_ADMIN as a Oracle GoldenGate schema name.

Working, please wait ...

DDL replication setup script complete, running verification script...
Please enter the name of a schema for the GoldenGate database objects:
Setting schema name to GGS_ADMIN

CLEAR_TRACE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

CREATE_TRACE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

TRACE_PUT_LINE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

INITIAL_SETUP STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDLVERSIONSPECIFIC PACKAGE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDLREPLICATION PACKAGE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDLREPLICATION PACKAGE BODY STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDL IGNORE TABLE
-----------------------------------
OK

DDL IGNORE LOG TABLE
-----------------------------------
OK

DDLAUX  PACKAGE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDLAUX PACKAGE BODY STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

SYS.DDLCTXINFO  PACKAGE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

SYS.DDLCTXINFO  PACKAGE BODY STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDL HISTORY TABLE
-----------------------------------
OK

DDL HISTORY TABLE(1)
-----------------------------------
OK

DDL DUMP TABLES
-----------------------------------
OK

DDL DUMP COLUMNS
-----------------------------------
OK

DDL DUMP LOG GROUPS
-----------------------------------
OK

DDL DUMP PARTITIONS
-----------------------------------
OK

DDL DUMP PRIMARY KEYS
-----------------------------------
OK

DDL SEQUENCE
-----------------------------------
OK

GGS_TEMP_COLS
-----------------------------------
OK

GGS_TEMP_UK
-----------------------------------
OK

DDL TRIGGER CODE STATUS:

Line/pos                                 Error
---------------------------------------- -----------------------------------------------------------------
No errors                                No errors

DDL TRIGGER INSTALL STATUS
-----------------------------------
OK

DDL TRIGGER RUNNING STATUS
------------------------------------------------------------------------------------------------------------------------
ENABLED

STAYMETADATA IN TRIGGER
------------------------------------------------------------------------------------------------------------------------
OFF

DDL TRIGGER SQL TRACING
------------------------------------------------------------------------------------------------------------------------
0

DDL TRIGGER TRACE LEVEL
------------------------------------------------------------------------------------------------------------------------
0

LOCATION OF DDL TRACE FILE
------------------------------------------------------------------------------------------------------------------------
/optware/oracle/diag/rdbms/cxxxnm2s/CXXXNM2S/trace/ggs_ddl_trace.log

Analyzing installation status...


STATUS OF DDL REPLICATION
------------------------------------------------------------------------------------------------------------------------
SUCCESSFUL installation of DDL Replication software components

Script complete.
SQL>

OGG-00717 : Found unsupported in-memory undo record + Minimum supplemental logging must be enabled to prevent data loss

OGG-00717 : Found unsupported in-memory undo record + Minimum supplemental logging must be enabled to prevent data loss


Possible Cause:
Supplemental logging is not enabled on the database level or the extract is positioned to a point where the supplemental logging has not been enabled i.e an attempt was made to start the extract when the supplemental logging was not enabled on the database.

Solution:

Check if Supplemental logging is enabled

SQL> SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;

SUPPLEME
--------
NO

Enable Supplemental Logging

SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;

Database altered.

Switch Logfile

SQL> ALTER SYSTEM SWITCH LOGFILE;

System altered.

And attempt to start the extract with begin now option

GGSCI (sev274) 2> alter extract EXTRACT3, begin now
EXTRACT altered.


GGSCI (sev274) 3> start EXTRACT3

Sending START request to MANAGER ...
EXTRACT EXTRACT3 starting


GGSCI (sev274) 4> info EXTRACT3

EXTRACT    EXTRACT3  Last Started 2015-11-09 16:29   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:05 ago)
Log Read Checkpoint  Oracle Redo Logs
                     2015-11-09 16:29:20  Seqno 0, RBA 0
                     SCN 0.0 (0)


GGSCI (sev274) 5> !
info EXTRACT3

EXTRACT    EXTRACT3  Last Started 2015-11-09 16:29   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:09 ago)
Log Read Checkpoint  Oracle Redo Logs
                     2015-11-09 16:29:20  Seqno 0, RBA 0
                     SCN 0.0 (0)


GGSCI (sev274) 6> !
info EXTRACT3

EXTRACT    EXTRACT3  Last Started 2015-11-09 16:29   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:03 ago)
Log Read Checkpoint  Oracle Redo Logs
                     2015-11-09 16:55:07  Seqno 11567, RBA 281600
                     SCN 3330.2812657068 (14305053752748)