# Clarion 6 and Oracle 21c XE

**URL:** <https://clarionhub.com/t/clarion-6-and-oracle-21c-xe/7243>\
**Category:** questions\
**Tags:** drivers, c6\
**Created:** [June 17, 2024, 1:10pm UTC](https://clarionhub.com/t/clarion-6-and-oracle-21c-xe/7243 "2024-06-17T13:10:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinicius\_Souza](https://clarionhub.com/user_avatar/clarionhub.com/vinicius_souza/32/2394_2.png) [@Vinicius\_Souza](https://clarionhub.com/u/Vinicius_Souza)\
**Post date:** [June 17, 2024, 1:10pm UTC](https://clarionhub.com/t/clarion-6-and-oracle-21c-xe/7243/1 "2024-06-17T13:10:06Z")

</div>

Hello, we have Clarion 6 applications running and connecting to Oracle 11g XE with 11g Client.  
I am carrying out tests to use Oracle 21c XE, using Client 21c 32bit, but the applications do not connect to the new database.  
I tested positive using Windows ODBC AD 32bit drives for test connection.

Any tips?

---

<div class="post-metadata">

**Author:** ![PurpleEdge2214](https://clarionhub.com/user_avatar/clarionhub.com/purpleedge2214/32/5109_2.png) [@PurpleEdge2214](https://clarionhub.com/u/PurpleEdge2214)\
**Post date:** [June 18, 2024, 2:04am UTC](https://clarionhub.com/t/clarion-6-and-oracle-21c-xe/7243/2 "2024-06-18T02:04:42Z")

</div>

One trick is to create a dictionary using the ODBC data source you tested with to import one of the files.

Then wizard an app using that file.

If that app connects, then filename{Prop:ConnectString}, somewhere in a procedure that uses the file, will give you the proper connect string without needing to use the ODBC driver.

---

<div class="post-metadata">

**Author:** ![JonW](https://clarionhub.com/user_avatar/clarionhub.com/jonw/32/1344_2.png) [@JonW](https://clarionhub.com/u/JonW)\
**Post date:** [June 18, 2024, 11:38am UTC](https://clarionhub.com/t/clarion-6-and-oracle-21c-xe/7243/3 "2024-06-18T11:38:19Z")

</div>

My database was recently upgraded from 11 to 19. Upgrading the client was essential: the 11 client cannot connect to the 19 database. But sounds like you’ve dealt with that.

I also installed 19 XE on my home computer, and the main thing I noticed there was that XE sets itself up with “pluggable” databases (PDB) by default, and this has an impact on how you log on. A normal user can only log on to the pluggable database on which they are set up. If you want to log into the root you need to be a “common” user (which in this sense means special, allowed to log into the “common” area"), and the user name starts with c##. I haven’t played with it that much, so can’t give you more guidance.

> **[Administrator’s Guide](https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/logging-cdb-or-pdb.html)**
>
> Different variations of the Enterprise Manager Database login page appear automatically based on the feature that you requested while logging in.