I know that Oracle Database 18c is available in the Oracle Cloud and on Exadata engineered systems only right now. But actually I’ve had conversations with some customers who downloaded Oracle 18c on-prem software for Exadata and installed it on their systems. Therefore it may be useful to talk about Oracle Database 18c – Some important changes.… [Read More]
This is a strange behavior – but it seems as automatic maintenance jobs are enabled after upgrade. A customer (thanks Naveen!!) sent me an email the other week asking if there’s a flag in DBUA to prevent this enabling as on some of their databases the automatic maintenance jobs are disabled on purpose.… [Read More]
Interesting things happen. And I learned (credits to Arun Gupta and others) that there is a change in Oracle Database 12.2 environments I wasn’t aware: The DBCA 12.2 does not update
/etc/oratab in GI / RAC environments. Let me give you some extra information and hints on this topic as it may cause some strange situations.… [Read More]
All credits here go to Marcel Pils from Logicalis, a German Oracle partner. Thanks Marcel! In Oracle 12.2 there’s an interesting behavior change:
READ privilege for user
SYSTEM in Oracle 12.2.
Some Background Information
In Oracle 12.1 the READ privilege has been introduced. Please find more information in the Oracle 12.1 Security Guide: New READ Object Privilege and READ ANY TABLE System Privilege for SELECT Operations.… [Read More]
At the moment I work with one of our reference customers, Swiss Mobiliar Insurance, on their Multitenant upgrade to Oracle Database 188.8.131.52. And we encountered an “interesting” issue. After upgrade we received an ORA-44787 making it impossible to switch between containers with “
alter session set container=pdb1;” commands.… [Read More]
Timestamp Format Change
There’s an interesting change in the alert.log since Oracle Database 184.108.40.206: The format of the timestamps has changed.
If you compare the timestamps in Oracle 12.1 vs Oracle 12.2 you’ll recognize the change immediately:
|Oracle 12.1||Oracle 12.2|
Wed Feb 08 15:39:29 2017 Database mounted in Exclusive Mode Lost write protection disabled Completed: ALTER DATABASE MOUNT Wed Feb 08 15:39:29 2017 ALTER DATABASE OPEN Wed Feb 08 15:39:29 2017 Ping without log force is disabled.
The init.ora/spfile parameter
PGA_AGGREGATE_LIMIT got introduced in Oracle Database 220.127.116.11.
As per documentation in Oracle Database 12.1 it got defined as:
PGA_AGGREGATE_LIMIT specifies a limit on the aggregate PGA memory consumed by the instance.“.
Furthermore the algorithm for its setting got described as:
PGA_AGGREGATE_LIMIT is set to the greater of 2 GB, 200% of
PGA_AGGREGATE_TARGET, and 3 MB times the
PROCESSES parameter.… [Read More]