Error: F_JG20D5: Attempt To Start Execute Command ‘Curl’ Failed

Issue

While refreshing tables from Oracle to Amazon Redshift in an Amazon EC2 Windows server, the following errors appear:

F_JG20D5: Attempt to start execute command 'curl' failed, because this file could not be located in any directory in path '.;C:Windowssystem32;C:Windowssystem32SYSTEM; C:Windows;C:hvrhvr_configagents;C:hvrhvr_homebin;C:appclienttestuserproduct 12.2.0client_64_12cbin;C:apptestuserproduct11.2.0client_32BIN;C:Program Files (x86)Common FilesOracleJavajavapath;C:Perl64sitebin;C:Perl64bin;C:Oracle_64 product11.2.0client_64BIN;C:Informatica9.1.0clientsPowerCenterClientclientbin; C:Informatica9.1.0clientstoolsdatadirect;C:Informatica9.1.0clientsjavajrebin server;C:Informatica9.1.0clientsDeveloperClientbin;C:Oracle\_64product11.2.0 client_64BIN;C:Oracle_64product11.2.0client_64bin;C:apptestuserproduct11.2.0 client_32BINBIN;C:apptestuserproduct11.2.0client_32BINbin;C:Informatica10.0.0 clientstoolsdatadirect;C:Informatica10.0.0clientstoolsodbcdrv;C:Program Files (x86)ExamDiff;C:Program FilesEmEditor;C:Informatica10.0.0clientsPowerCenterClient clientbin;C:Program FilesJavajdk1.7.0_80bin;C:Program FilesMicrosoft SQL Server 120DTSBinn;C:Program FilesMicrosoft SQL ServerClient SDKODBC110ToolsBinn; C:Program Files (x86)Microsoft SQL Server120ToolsBinn;C:Program FilesMicrosoft SQL Server120ToolsBinn;C:Program Files (x86)Microsoft SQL Server120ToolsBinn ManagementStudio;C:Program Files (x86)Microsoft SQL Server120DTSBinn;C:Program FilesMicroStrategyMicroStrategy DesktopDataServices180_7764-bitbinserver'.

F_JG2912: The previous error occurred while getting EC2 instance role from 'http://250.199.199.99/2018-11-05/meta-data/iam/security-credentials/'.

F_JG350D: The previous error occurred while creating a mountpoint for url 's3://miscbucket/hvrhub/ebs_shift/shift'.

F_JT04C2: The previous error occurred on line 124 of script 'C:hvrhvr_configjob hvrhubebs_shiftebs_shift-refr-ebs-shift'.

Environment

• HVR 5

Resolution

AWS depends on the external tool curl to handle credentials when using IAM/EC2 instance roles.

To resolve this issue, do one of the following options:

Option 1

Ensure that curl.exe is in your path or is in one of the paths shown in the error messages.

Option 2

Instead of using instance roles, use the AWS key/secret. Even if you didn't specify a role in HVR, without providing other credentials, HVR may try to fetch a default role of EC2 instance.