Skip to main content
kihwank16044798
Participant
October 21, 2021
Question

Coldfusion 2016 with Oracle 19c

  • October 21, 2021
  • 2 replies
  • 371 views

We have Coldfusion 2016 and it is running on Oracle 11g. we just updated from Oracle 11g to 19c and have tried to make a connection by creating a new data source with ojdbc8.jar in Data Source on a CF Admin.  The creation was sucessfully and the verfication also showed me "OK"

however, when running our web it showed an error below

Here are the steps what I did. 
1. downloaded a ojdbc8.jar ( I also tried ojdbc10.jar but no luck ) and placed it in C:\ColdFusion2016\cfusion\lib and then restated the service. 

2. create a new data source in a DS page (I added the tnsoraname.ora below)

-----

AAAA=
(description=
(address_list=
(address = (protocol = TCP)(host =xxxxxx)(port = 1521))
)
(connect_data =
(service_name=AAAA)
)
)

-----

so, I put the JDBC URL and Driver class like that:
 JDBC URL:jdbc:Oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxx)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME = AAAA)))

Driver Class: oracle.jdbc.driver.OracleDriver

the creation was successful and the verification also showed me "OK"

 

FYI: we have applied the update 11 so far.
 

I am still not getting a connection in our web. Can you tell me how to solve this problem? Your comments would be greatly appreciated. 

 

Many Thanks!

    This topic has been closed for replies.

    2 replies

    BKBK
    Community Expert
    Community Expert
    October 21, 2021

    ColdFusion 2016 dates from early 2016 and Oracle 19c from early 2019. Hence Oracle 19c is a big jump for ColdFusion 2016.

     

    Going just by instinct, I would say don't do it, even if the connection tested OK. Update instead to a version closer to Oracle 11g.

    Charlie Arehart
    Community Expert
    Community Expert
    October 21, 2021

    Yes. Look in the coldfusion-out.log when the error occurs. The 500 error may have nothing to do with the dsn setup (especially since that verifies ok).

     

    If there is nothing in that Cf log at the time, run the request in a browser on the server, IIS (which is showing the error) may show different details ON the server rather than off.

     

    There's much more that could be considered, depending on what you find. Let us know. 

    /Charlie (troubleshooter, carehart. org)