. Connect to RMAN using target and catalog
. Execute upgrade catalog
IT Blog
In my previous post (How To Connect To The Oracle Cloud Instance) we reviewed the steps to connect using SQL Developer. Now we will see what DBA tasks we can perform using SQL Developer.
First click on the View menu, then click on the DBA sub menu. This is going to open the DBA pane in the lower left corner.
Click on Connections and add the connection we already setup to the Oracle Cloud Instance.
Here you can expand the tree to verify what is available from SQL Developer.
Let’s click on Tuning and then Real Time SQL Monitoring. The right pane is going to display the SQL Monitoring output. I’m really familiar to this feature in OEM 13c and honestly, looks very similar in SQL Developer.
Now let’s click on Instance Viewer under Database Status menu.
This is going to show you the overall container status and statistics on where our PDB is running on.
The storage menu can help you verify the size of your tablespaces and under RMAN Backup/Recovery you can verify that there are actually backups happening every night.
Thanks,
Alfredo
In my previous post (How To Create An Oracle Cloud Instance) I showed you create your first Oracle Cloud DB instance. Now that the instance is there the question is, how to connect to it?
Let’s say you want to connect using SQL Developer to start creating objects and inserting data. First you need to enable the Client Access feature. Yes, it is disabled by default.
Navigate to the Cloud DB instance dashboard. Click on Manage menu on the left side.
Click on Admin Password and provide a password for the PDB_ADMIN account.
Then click on Client Access and check the enabled flag, then save.
It will show like this.
Once this is enabled you need to download the Access Credentials in order to connect to your instance.
Click on the Client Credentials button located on the right side of the Client Access one. This is going to prompt for a password (type one that you can remember) and it will download a .zip file containing these credentials and connect descriptors.
Note: You don’t have to unzip this file.
Open your SQL Developer software and click on New Connection.
Type a name for your connection. In the username & password you can either type the PDB_ADMIN username and password or the credentials for the newly created schema.
In Connection Type select Cloud PDB and provide the downloaded .zip file along with the password provided (the one that you should remember).
It should look like this.
Click Save and then Connect.
Now let’s test our connection by executing a simple SQL statement.
Using the Cloud DB instance dashboard you can create different schemas as needed.
You just provide the username and password.
At the end you just need to follow the same steps as we did before, just provide the username and password of the new schema.
More information can be found at:
https://docs.oracle.com/en/cloud/paas/exadata-express-cloud/csdbp/connecting-sql-developer.html#GUID-238A40BD-10E9-4478-AAA3-43FC98519D3F
Thanks,
Alfredo
Oracle’s documentation recommends to execute actualize_all in
order to purge old editions in the DB accumulated during previous patching
cycles.
There’s a problem with EBS version 12.2.4 that when running adop
phase=actualize_all you get an ORA-04045 errors during
recompilation/revalidation of .
You can try to manually recompile objects but all of them fail
with the same error. This is documented under bug 24489846.
Follow the instructions on the MOS note id 2187877.1.
I also recommend to open an SR as this bug is still open as of
May 2018.
Thanks,
Alfredo