In the last post we discussed connecting SQLcl to Oracle Exadata Express, now lets see how we can connect SQL Developer
EDIT: After writing this post, I found there was a detailed help available here – https://docs.oracle.com/en/cloud/paas/exadata-express-cloud/csdbp/connecting-sql-developer.html#GUID-00D45398-2BF3-48D5-B0E9-11979D5EAFFC
Step 1 – Create a new connection in SQL Developer
Note – I’ve obscured my existing connections for obvious reasons.
You’ll need to populate
- Connection Name
- Username (I’m going to use PDB_ADMIN)
- Connection Type – (there is a new connection type of Cloud PDB)
- Configuration File
- Keystore Password
Step 2- Ensure the JCE Policy files are installed
Recall in the post on connecting SQLcl to Exadata Express we needed to install the JCE Policy Files, we need to do the same for SQLDeveloper.
Fortunately SQLDeveloper shows an error message which shows the location it is using to try and find the files.
Hmmm, that’s weird – that is the location I put the files for my SQLcl installation.
Ah! I realised my mistake, SQLDeveloper was already running when I installed the files for SQLcl, so I just needed to restart SQLDeveloper so it picked up the new JCE Policy files.
After a quick restart, everything looks ok
Now we just select the same client_credentials.zip file we used earlier for the SQLcl connection and enter the keystore password that was entered when you downloaded the credentials file.
Clicking the Test button shows we can connect ok!
Now we can save and open the connection and we should be good to go
In this example I connected as PDB_ADMIN, you can use the same technique to connect as your real development SCHEMA user.