|
||||
|
Autoupgrade is compatible with 12.2 and 18.5 and you need to download the kit from 2485457.1 Autoupgrade.jar is available default in 19c How this works Prevent Issues : Analyze and Fixup Modes java -jar autoupgrade.jar -config config.txt -mode analyze java -jar autoupgrade.jar -config config.txt -mode fixups Simplifying Upgrade: Deploy and upgrade java -jar autoupgrade.jar -config config.txt -mode deploy/upgrade In order to duplicate a database one must use rman duplicate command or manual procedure to copy and restore the files From 19c, DBCA facilitates duplication of db with new “CreateDuplicateDB” Requires easy connection string so that it duplicates the target db to wherever running §  From 19c, ability to create PDB from remote PDB using DBCA is possible Use dbca –silent createpluggabledatabase with option “createFromRemotePDB” 
Oracle Open world 2019 - Interesting updates so far.
More will be updated. Oracle Open world #oow19 update , New Announcement, Always free Tier in Oracle cloud to Build, test, and deploy applications on Oracle Cloud—for free Always (Yes always) Whats included ? Databases : Your choice of Autonomous Transaction Processing or Autonomous Data Warehouse. 2 databases total, each with 1 OPCU and 20 GB storage. Compute : Two virtual machines with 1/8 OCPU and 1 GB memory each. Storage: Two Block Volumes instances, 100 GB total. 10 GB Object Storage. 10 GB Archive Storage. Additional Services: Load Balancer, 1 instance, 10 Mbps bandwidth. Monitoring, 500 million ingestion datapoints, 1 billion retrieval datapoints. Notifications, 1 million delivery options per month, 1,000 emails sent per month. Outbound Data Transfer, 10 TB per month. And built my first free services in less than 5 mins. Once logged in, there's a message
Let me show you the video of service offering in always free tier. [embedyt] https://www.youtube.com/watch?v=mSgvB67e040[/embedyt]
Services in the dashboard showing always free.
Previous versions of Oracle database needs to manually manage the flashback area i.e flashback_retention_target to adjust according to growth of flashback logs Or manually backup the logs/backupsets to tape or to delete them But from Oracle 19c onwards, the management of space in the fast recovery area is simplified. Oracle Database monitors flashback logs in the fast recovery area and automatically deletes flashback logs that are beyond the retention period. When the retention target is reduced, flashback logs that are beyond the retention period are deleted immediately. In scenarios where a sudden workload spike causes a large number of flashback logs to be created, the workload is monitored for a few days before deleting flashback logs that are beyond the retention period. This avoids the overhead of recreating the flashback logs, if another peak workload occurs soon after. I will have to check any initialization parameter to control this behavior, but its automatically set if compatible is 19.0.0 or higher In Oracle 19c Grid, Run the Oracle Grid Infrastructure installer in dry-run upgrade mode to determine if the system is ready for upgrade. To perform Oracle Grid Infrastructure dry-run upgrade, create a new Grid home with the necessary user group permissions, extract the Oracle Grid Infrastructure 19c gold image to the new Grid home, and then start the installer with —dryRunForUpgrade flag Start the Oracle Grid Infrastructure installation wizard in dry-run upgrade mode by running the following command: $ /u01/app/19.0.0/grid/gridSetup.sh -dryRunForUpgrade Starting 19c, We can run DML operations on Active Data Guard standby databases. This enables you to run read-mostly applications, which occasionally execute DMLs, on the standby database. Automatic redirection of DML operations to the primary can be configured at the system level or the session level. The session level setting overrides the system level setting.
In Previous versions Oracle, When a service moves to an available instance, Oracle Database does not automatically move the service back to the preferred instance when the preferred instance restarts because:
Starting with Oracle Database release 19.3, if you specify yes for the -failback attribute of a service, then, after failing over to an available instance when the last preferred instance went down, the service transfers back to a preferred instance when one becomes available. For earlier releases, you can automate fail back to the preferred instance by using FAN callouts.
Desupport of Oracle Real Application Clusters for Standard Edition 2 (SE2) Database Edition. Starting with Oracle Database 19c, Oracle Real Application Clusters (Oracle RAC) is not supported in Oracle Database Standard Edition 2 (SE2).
ADDM does not work in a pluggable database (PDB) by default, because automatic AWR snapshots are disabled by default in a PDB. Starting 19c , To use ADDM in a PDB, you must enable automatic AWR snapshots in the PDB by setting the AWR_PDB_AUTOFLUSH_ENABLED initialization parameter to TRUE and AWR snapshot interval greater than 0. To enable ADDM in a PDB:
|
||||
Oracle 23c New Features for DBA's
Follow Me!!!