Endeca Extensions There was an error when trying to access the data source

Issue 1- Datasource Error

There was an error when trying to access the data source. Please confirm with your system administrator that the data source is available.

Below error is observed on Endeca Pages when a clone of EBS Instance is completed.

  Below are the few causes for the issue:

1)      The source EBS may not have Endeca application configured.

2)      Not executed Concurrent program “Populate Endeca Metadata for iProcurement” after any metadata changes performed on Endeca side <-- This is specific to iProcurment page

3)      Endeca data source ebsdb is not listing target managed servers

Launch Console of Endeca Server -> Datasources -> click on datasource ebsdb ->  Monitoring -> Testing. This screen should list the Studio Managed server.

Studio log file reported below errors: (/u01/Oracle/Middleware/user_projects/domains/endeca_domain/servers/StudioManagedServer/logs/StudioManagedServer.log)

####<Jun 8, 2015 10:18:46 PM CDT> <Error> <Deployer> <hpeidrd01.hpinc.com> <StudioManagedServer> <[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KrMKwR45yW^5xVWByW1LT_gK000000> <1433819926781> <BEA-149205> <Failed to initialize the application 'ebsdb' due to error weblogic.application.ModuleException: .

weblogic.application.ModuleException:

        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)

Caused By: weblogic.common.resourcepool.ResourceSystemException:

 Could not connect to 'oracle.apps.fnd.ext.jdbc.datasource.AppsDataSource'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.

 It is also possible that something else is invalid in

 the configuration or that the database is not available.

        at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:301)

        at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.makeConnection(PooledConnectionEnvFactory.java:317)

        at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.createResource(PooledConnectionEnvFactory.java:97)

        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)

Fix:

The password of EBS User ENDECADM in console is incorrect. Update the correct password for user ENDECADM in console to correct value and save it.

Console -> Lock & Edit in change center -> Datasource -> click on ebsdb -> configuration -> Connection Pool.

Update the password to correct value  and click on Save.

Activate Changes on control center

Once the changes are activated we should be able to see the Managed Server.