Datamover fails with /bin/java does not exist****oadAutomationAE/JRE_WA/ Exiting error

Document ID : KB000005081
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

DataMover fail to execute 'paramfile' and getting below example error :

 

[root@Hostname DataMover]# perl uajmdatamover.pl paramfile

SRCDBTYPE is set to oracle

SRCDBMACHINE is set to source_db_hostname

SRCDBNAME is set to SOURCEDBNAME

SRCDBPORT is set to 1524

SRCDBUSER is set to autosys

TGTDBTYPE is set to oracle

TGTDBMACHINE is set to target_machine_name

TGTDBNAME is set to TargetDBName

TGTDBPORT is set to 1524

TGTDBUSER is set to aedbadmin

TGTAEDBADMINWALLETPATH is set to

NATIVEJDBCJARPATH is set to /opt/CA/oracle/product/11.2.0.4/client_1/jdbc/lib/ojdbc6.jar

ADDITIONALJARSPATH is set to

JREPATH is set to /opt/CA/WorkloadAutomationAE/JRE_WA/

VERIFY is set to yes

 MBMEMORYLIMIT is set to 1024

/bin/java does not exist****oadAutomationAE/JRE_WA/

Exiting...Correct the JREPATH and reissue the command

Environment:
Operating System: Linux/Unix, Aix,Solaris WindowsDatabase: All supported Oracle DB releases.
Cause:

This issue occurs if the provided "paramfile" values are not appropriate.

Resolution:

In this case scenario the symptom could be resolved by following below steps:

  • SRCDBUSER was set to 'autosys' whereas the AE r11.0 database uses the mdbadmin by default as schema owner.
  • SRCDBUSER has to be changed to mdbadmin and execute the paramfile.

 

Additional Information: