My Oracle Support Banner

ECC Import Application Using patchEccFiles.pl Scripts Fails With "ERROR: Failed with status 500" and "ORA-12505 TNS:listener does not currently know of SID given in connect descriptor" Error (Doc ID 3023541.1)

Last updated on JUNE 13, 2024

Applies to:

Oracle Enterprise Command Center Framework - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

When attempting to import applications from E-Business Suite (EBS) to Enterprise Command Center (ECC) using patchEccFiles.pl script, the import of applications fail and the following error occurs in the patchEccFiles output logs:

Importing application /xxx/xxx/xxx/ap/12.0.0/patch/115/ecc/applications/ap_emp_exp_ecc.zip
ECC WEB ENTRY URL:https://xx.xx.com:port/ecc
ECC Application File:/xxx/xxx/xxx/ap/12.0.0/patch/115/ecc/applications/ap_emp_exp_ecc.zip
ERROR: Failed with status 500 for url https://xxx.xxx.xxx:port/ecc/user/import/applications?gfmString=hkq3bwzvYHfQvKmFISYm9w..
Please check the log: Unable to resolve 'srcdb'. Resolved '' in ECC instance for error details
java.lang.Exception: https://xxx.xxx.com:port/ecc/user/import/applications?gfmString=hkq3bwzvYHfQvKmFISYm9w.. failed with HTTP status: 500
  at oracle.ecc.client.util.FileUploader.finish(FileUploader.java:100)
  at oracle.ecc.client.util.ApplicationImporter.importApplication(ApplicationImporter.java:114)
  at oracle.ecc.client.ECCClient.main(ECCClient.java:110)

Import of applications failed

ecc-web*.log under $ECC_HOME/quickInstall/logs/ecc shows below:

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.sql.DataSource]: Factory method 'dataSource' threw exception; nested exception is javax.naming.NameNotFoundException: Unable to resolve 'eccdb'. Resolved ''; remaining name 'eccdb'

setup.log under $ECC_HOME/quickInstall/logs shows below:

weblogic.application.ModuleException: weblogic.common.ResourceException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

cannot create EBS Jndi...
JNDI creation failed for EBS database

The issue can be reproduced with the following steps:

1. Setup ECC V12 on EBS 12.2.13 using steps from Doc ID: 2495053.1
2. Make sure that ECC installation and integration is complete
3. Import applications using patchEccFiles.pl script from $FND_TOP/bin directory to see if import is successful


Changes

New Installation of ECC and trying to import applications.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.