I have a JMS queue that I want to capture into a GoldenGate trail (which will later be pumped into an Oracle DB), but I'm getting the following error when I try to start it up:
EXTRACT JMSVAM started.
Recovery initialization completed for target file /u01/trails/va000007, at RBA 774.
Output file /u01/trails/va is using format RELEASE 10.4/11.1.
Rolling over remote file /u01/trails/va000007.
Recovery completed for target file /u01/trails/va000008, at RBA 774.
Recovery completed for all targets.
VAM API running in single-threaded mode.
Positionin to start.
VAM Client Report < ***** Oracle GoldenGate Adapter for Java Version 126.96.36.199.0 Build: 007 SunOS_5-9 [sparcv9 (64-bit); Java 5]; GG Java API: 11_1_1_0_0_006 (20100729_085631) ***** >.
VAM Client Report <Error occured in parser.c: The type of parser must be specified in property parser.type >.
VAM Client Report <Error occured in javavamimpl.c: Could not initialize parser >.
VAM function VAMInitialize returned unexpected result: error 600 - VAM Client Report <Could not initialize Generic Vam>.
I *do* have "parser.type=xml" defined in my VAM message capture properties file, but I'm sure some of my dyntxrule.*, dynoprule.*, and dyncolrule.* rules are not all there, or at least may not all be properly defined yet.
My question is, will I continue to see the "parser must be specified in property parser.type" error until I have all of these other properties correct?? ... or is there some other problem going on? I'm guessing the latter, since I've gone so far as to delete all of my dyn*.* rules ... so that I'm left with something like this, and I'm still getting the "parser must be specified in property parser.type" error ... eg:
Thanks for any assistance/clarification on this VAM capture error.