Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.BeamNonJTADataSource'. Resolved 'jdbc'; remaining name 'BeamNonJTADataSource'
After Applying below patches we see that error in BAM Log files and BAM wont come up.
Another issue is in admin console bam status will show starting.
Patch 21885138 (BP4),22524811(BP5)
Patch 22144497 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 21438873 21488819 21883560
Patch 22144471 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 19154446 21466129
Patch 22190179 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 22144523 22127760
Patch 22237005 : MERGE REQUEST ON TOP OF SOA BP 12.1.3.0.4 FOR BUGS 21238852 21418640
Patch 20484519 - BAM 12c Performance / Scalability
Patch 20835861 - EMS : Status shown in the UI is not correct
Patch 20744648 - Collapsed List header alignment not aligning to Left fully.
Patch 22013059 - Add DataObject Metadata Caching to Improve Performance
Please
do the following to start BAM Server.
1. Create a new Generic Data Source called BamNonJTADataSource using the JNDI Name jdbc/BeamNonJTADataSource.
2. Specify Oracle's Driver (Thin) for Instance connections; Version:Any as the Database Driver.
3. Make sure the Supports Global Transactions checkbox is unchecked.
4. Copy the Database Name, Host Name, Port, Database User Name and Password from the existing BamDataSource Data Source.
5. Target the new Data Source to all servers in the BAM cluster or to the single BAM Server if not in a clustered environment.
Refer to this document for detailed instructions:
http://www.oracle.com/technetwork/middleware/bam/community/instruct-patch-20484519-2479103.pdf
