18 Troubleshooting the Java Adapters
This chapter includes the following sections:
Checking for Errors
- The Replicat or Extract process running the Java Adapter user-exit abends
-
The Extract process running VAM abends.
-
The process runs successfully, but the data is incorrect or nonexistent
If the Extract process does not start or abends, check the error messages in order from the beginning of processing through to the end:
If the process runs successfully, but the data is incorrect or nonexistent, check for errors in any custom filter, formatter or handler you have written for the user exit.
To restart the user exit Extract from the beginning of a trail, see Restarting the Application at the Beginning of a Trail.
Recovering after an Abend
The Extract parameter RECOVERYOPTIONS
defaults to APPENDMODE
for release 10 and later trails. In append mode, Extract writes a recovery marker to the trail when it abends. When the Extract restarts and encounters the recovery
marker, it requests a rollback of the incomplete transaction if local transactions are enabled. If local transactions are not enabled, a warning message is issued. Local transactions are enabled unless the property gg.handler.{name}.localTX
is explicitly set to false
.
Reporting Issues
If you have a support account for Oracle GoldenGate, submit a support ticket. Please include:
-
Operating system and Java versions
The version of the Java Runtime Environment can be displayed by:
$ java -version
-
Configuration files:
-
Parameter file for the Extract running the user exit
-
All properties files used, including any JMS or JNDI properties files
-
Velocity templates for the user exit
-
-
Log files:
In the Oracle GoldenGate install directory, all
.log
files: the Java log4j log files and the user exit or VAM log file.