Daniel
The first step is to add more tracing to the dmconfigurets tool itself. Once way of doing this is as follows:
1. Take a backup of <CDC_Install_dir>\conf\dmts64.vmargs file.
2. Edit "dmts64.vmargs" file, to insert in front of existing text the following
-Dcom.datamirror.trace.on=true -Dcom.datamirror.trace.dir=<Log Directory Path>
Make sure that it is only one line (which will probably wrap of course) and this directory path is NOT the <cdc_install_dir>/instance as in the following example:
-Dcom.datamirror.trace.on=true -Dcom.datamirror.trace.dir=/tmp/testlog -Dorg.apache.commons.logging.Log=com.datamirror.ts.util.trace.TraceSimpleLog -Dcom.datamirror.ts.instance=%TSINSTANCE% com.datamirror.ts.bootstrap.Launcher com.datamirror.ts.commandlinetools.script.Startup3. Recreate the issue: the additional trace files are generated in the <Log Directory Path> directory.
4. After troubleshooting restore the original dmts64.vmargs file
If you don't get anywhere with the additional trace information then you or the customer should open a case.
Regards
Robert
------------------------------
Robert Philo
------------------------------
Original Message:
Sent: Wed August 03, 2022 12:16 PM
From: Daniel Jose Lema Guanziroli
Subject: Oracle Trigger agent fails to create instance
I am trying to install Oracle Trigger agent (built 5643) on Oracle 19c on AIX and it fails with the following error when creating the new instance:
Creating a new instance. Please wait...
Cannot create changes:You must execute the following statement: grant select on SYS.V_$SESSION to USER_NAME
Would you like to abort instance creation (y/n) [n]:
I ran the samples/createuser-ora-nodba.sql that, off course, has a grant select sys.v_$session to the idr user
Notice also that USER_NAME is not the name of the Oracle user I created and configured for IDR.
Is this a bug on the product or is something I am doing wrong?
Thank you so much.
------------------------------
Daniel Jose Lema Guanziroli
------------------------------
#DataReplication
#DataIntegration