An application fails. The exception Indicates that the JDEM data source cannot be found. Identify two possible steps that you can perform to verify the data source’s availability.

A "JNDI data source cannot be found" exception indicates that the application's JNDI lookup for the data source failed. This typically occurs for two main reasons. First, the data source and the application may be targeted to different servers or clusters. For an application to access a resource, both must be available on the same target. Second, the data source may have failed to deploy or bind to the JNDI tree for other reasons. Viewing the JNDI tree on the target server is the most direct way to confirm if the data source is actually available for lookup under the expected name.

A. Launch the JDBC Diagnostics utility. This utility tests the database connection from an existing data source. It is used after a JNDI lookup is successful, not to diagnose why the lookup itself is failing.
B. Verify the Dependencies attribute of the data source. While a failed dependency can prevent a data source from starting, it is not a direct verification of its JNDI availability. The primary checks are targeting and the JNDI tree itself.

1. Oracle Fusion Middleware

Administering JDBC Data Sources for Oracle WebLogic Server

12c (12.2.1.4.0)

E90452-05

Chapter 2

"Configuring JDBC Data Sources". The section "Targeting a JDBC Data Source" states: "You must target a data source to the same server or cluster to which you deploy the applications or components that use the data source." This supports option D.

2. Oracle Fusion Middleware

Administering Oracle WebLogic Server with Oracle WebLogic Server Administration Console

12c (12.2.1.4.0)

E90451-05

Chapter 5

"Servers". The section "View the JNDI tree for a server" explains that you can use the console to "view the JNDI tree for a server instance" to "verify that objects are bound to the tree as you expect." This directly supports option C.

3. Oracle Fusion Middleware

Administering JDBC Data Sources for Oracle WebLogic Server

12c (12.2.1.4.0)

E90452-05

Chapter 15

"Diagnosing Problems with JDBC Data Sources". The section "Testing a Data Source" describes how to test a database connection in a data source from the Administration Console. This confirms that diagnostic tests are for connection validity

not JNDI lookup availability

making option A incorrect for this scenario.