Blogs

A script to check the query execution time as well as the time to retrieve all records via a FOR cur IN construct:

I run a few websites from a VM on my Synology NAS. The VM has the typical LAMP setup for running Wordpress and Drupal sites. As it is not exposed directly to the internet, Apache serves up all sites on port 80 and I configured the Synology "Application Portal" to forward both port 80/443 requests to it. Application Portal (nginx behind the curtain) also provides handling of SSL Certs on port 443.
So I created 2 Synology Application Portal entries - one to for serving up incoming 80 to ApacheHost:80, and one for serving up incoming 443 to ApacheHost:80.

I opened an SR recently while I was trying to get a feature to work in 19c... was politely directed to this resource... A listing of Oracle features and what version they're available in...
Not sure when this was made available but I hope they keep it up - I much prefer this to trying to find this info in My Oracle Support docs.
Apex App - Features and Licensing Lookup

There are some impressive new features in 20.2. unfortunately my latest upgrades are not going so well.

I see we've got a bundle patch already! Patch 32006852: PSE BUNDLE FOR APEX 20.2 (PSES ON TOP OF 20.2.0.00.20)... But I don't see any of the issues I encountered being addressed.

From most to least severe:

1) ORDS 19.1 munged 3 times over 3 installs

As we move on to 12.2 and 19c we're seeing more instances where simple schema export/import migrations are missing objects on the target database.

If you do object counts after a simple schema migration... Or see something like this pop up in your impdp logs:

Create keystore with a self signed cert

keytool -genkey -keystore /path/keystore.jks -alias selfsigned -keyalg RSA -keysize 4096 -validity 720

Enter details for cert and enter password = password123

Update Tomcat server.xml

Verify

https://192.168.1.10:8443/
Should return this:

If you are getting odd abends on your Golden Gate replicats due to trail file corruption, make sure you visit your filesystem options for the filesystem where the manager process writes the trail files.

Long story short is that we were finding large swaths of Zeroes appearing in our trail files. Using logdump I could see the header of the trail file was OK, but somewhere down the line a valid record would be followed by straight up zeroes. Lots of them. I verified this using logdump and a hex editor.

I find Encryption is blamed for a lot of performance issues so wanted to find out for myself how much of a performance hit we might be taking for common operations. There ain't no free lunch. Adding any extra processing or manipulation to an operation is going to add time to that operation.

If you have clients connecting to a server and the clients don't specify a specific encryption algorithm in SQLNET.ENCRYPTION_TYPES_CLIENT, be aware that the order of the algorithms listed in SQLNET.ORA on the server side matters...

If you don't specify SQLNET.ENCRYPTION_TYPES_CLIENT from a 12.2 client configuration, a SQLNet client side trace shows the following possibilities, the choices are listed from most secure to least secure:

I've been diving into more OEM Automation and collecting information here.

While the Oracle example scripts are a great way to find out how to interact with OEM via the emcli and python/jython interface, there doesn't seem to be much info about how this all gets done. You feed a Python script to emcli and magic happens right?

Adeesh Fulay has a great intro article here.