Home › Discussions › Questions & Answers › Resolving ORA-01017 During EBS-ECC Integration: JNDI Connection and DBC File Hostname Issues

Resolving ORA-01017 During EBS-ECC Integration: JNDI Connection and DBC File Hostname Issues

Avatar photoCustomer Questions & Answers 6 replies

We are stuck while performing the EBS-ECC integration and setting up the EBS JNDI connection to the database. The setup is failing with an error message indicating: ‘Could not create connection for datasource ‘ebsDB’. The returned message is: ORA-01017: invalid username/password; logon denied’. We’ve confirmed the password is correct, but we suspect an issue with host resolution in the DBC file or required user privileges. Can you advise on the necessary validation checks?

6 replies

  • Support Enginatics

    An ORA-01017 during JNDI setup often indicates that while the database credentials might seem correct, the database user lacks a critical role, specifically the UMX|APPS_SCHEMA_CONNECT role, required for ECC access. You must ensure this role is added to the EBS_ECC_USER as detailed in Oracle documentation.

  • What about connectivity issues? We also occasionally see errors related to unreachable hosts or connection refusals during the integration script execution.

  • Support Enginatics

    If you encounter connection refusals, verify two things: First, ensure the HOST specified in the `connection.dbc` file is correctly resolvable and pingable from the ECC server. Second, confirm that the database port (typically 1521) is open for connections from the ECC server using `telnet`.

  • Support Enginatics

    Additionally, confirm that you copied the DBC file generated by `AdminDesktop` from the EBS server to the ECC server, as this file contains the necessary database details and node registration.

  • If we resolve these underlying issues but still face general ECC dashboard problems, are there diagnostics to check data loads?

  • Support Enginatics

    If dashboards are empty, you should run the ECC Data Load requests (e.g., Payables Command Center Data Load) for the specific products. You can monitor the status and execution details of these load programs using the specialized Blitz Report ‘ECC Admin – Data Load Tracking’ report, simplifying your overall ECC administration.

  • You must be logged in to reply to this post.