Deploy Enterprise Data Preparation on the AWS Cloud Marketplace (10.5)

Deploy Enterprise Data Preparation on the AWS Cloud Marketplace (10.5)

Frequently asked questions on deployment error messages

Frequently asked questions on deployment error messages

I encountered a CREATE_FAILED error when I launched the deployment.
If AWS CloudFormation fails to create the stack, we recommend that you relaunch the template with
Rollback on failure
set to
No
. (This setting is under
Advanced
in the AWS CloudFormation console,
Options
page.) With this setting, the stack's state will be retained, and the instance will be left running, so you can troubleshoot the issue. (You will want to look at the log files in
/var/log/cfn-init-cmd.log)
When you set
Rollback on failure
to
No
, you will continue to incur AWS charges for this stack. Please make sure to delete the stack when you have finished troubleshooting.
For additional information, see Troubleshooting AWS CloudFormation on the AWS website or contact us on the AWS Discussion Forum.
I encountered errors while installing the Informatica domain and services. Where can I find more information?
View the
/opt/Infa_OneClick_Solution.log
log file to see more information about the errors that you encountered.
I encountered a size limitation error when I deployed the AWS CloudFormation templates.
We recommend that you launch the deployment templates from the location we provided or from another S3 bucket. If you deploy the templates from a local copy on your computer or from a non-S3 location, you might encounter template size limitations when you create the stack. For more information about AWS CloudFormation limits, see the AWS documentation.
What should I do before I relaunch the template with
Rollback on failure
?
Ensure that you disable rollback when you launch the stack in case of a stack failure. If
Enterprise Data Preparation
server stack is created, check the following logs to identify the issues:
  • Node preparation log file:
    /opt/Infa_node_configure.log
  • /opt/Infa_OneClick_Solution.log
  • /var/log/cfn-init.log
  • /opt/Informatica/<Infa_Oracle>/logs/InfaNode/services/InfaHadoopService/Informatica_Cluster_Service/ICS.log
  • /opt/Informatica/<Infa_Oracle>/logs/InfaNode/services/CatalogService/Catalog_Service/LDM.log
If the
Enterprise Data Preparation
server stack is not created, you can check the CloudWatch logs to identify the issues. For more information, see the Verifying AWS CloudWatch Logs for Failures section.
I am facing Model Repository Service connectivity issues with the following error messages:
MRS_50015 "The Repository Service operation failed. ['[PRSVCSHARED_01707] Connection issues with the configured database. Request failed with the error message [[PERSISTENCEAPI_0307] [DBPERSISTER_1005] Failed to process requested operation. This was caused by [informatica][Oracle JDBC Driver]No more data available to read.].']"
MRS_50015 "The Repository Service operation failed. ['[PRSVCSHARED_01707] Connection issues with the configured database. Request failed with the error message [[PERSISTENCEAPI_0307] [PERSISTENCECOMMON_0001] Internal error. The request processing failed. This was caused by [informatica][Oracle JDBC Driver]Exception generated during deferred local transaction handling. See next exception via SQLException.getNextException for details.].']"
Applicable for Oracle. Perform the following steps to resolve the Model repository database connectivity issue:
  1. Launch the AWS RDS page.
  2. Select the RDS instance.
  3. Click the
    Configuration
    tab.
  4. Scroll down the tab page and click the link under the
    Parameter group
    section.
  5. Search for the following parameters in the list of parameters that appear:
    • sqlnetora.sqlnet.send_timeout
    • sqlnetora.sqlnet.recv_timeout
    • sqlnetora.sqlnet.inbound_connect_timeout
    • sqlnetora.sqlnet.outbound_connect_timeout
    • sqlnetora.tcp.connect_timeout
    If the listed parameters are not present in the list, make sure that add the parameters to the list.
  6. Change the value of each of the parameters listed in the previous step to 0 as shown in the following sample image:
    The following image shows the
    sqlnetora.sqlnet.send_timeout
    parameters
  7. Click
    Save changes
    .