Skip to main content

SOME 12C NEW FEATURES FOR ORACLE DATABASE ADMINS

12C NEW FEATURES:


1) Like sysdba, sysoper & sysasm, we have new privileges, in Oracle 12.1.0.

    sysbackup for Backup operations

    sysdg for Data Guard operations

    syskm for Key management

 

2) Oracle Database 12c Data Pump will allow turning off redo for the import operation (only).

   $ impdp ... transform=disable_archive_logging:y

 

3) CAN CREATE INVISIBLE COLUMNS AND WE CHANGE IT TO VISIBLE OR INVISIBLE

 

4) Moving and Renaming datafile is now ONLINE, no need to put datafile in offline.

   SQL> alter database move datafile 'path' to 'new_path';

 

5). Restricting PGA size  - Pre Oracle 12c R1, there was no option to limit and control the PGA size. Although, you set a certain size to PGA_AGGREGATE_TARGET initialization parameter, in 12c we can restrict using PGA_AGGREGATE_LIMIT parameter.

 

6) ASM: Introduction of Flex ASM, ASM would run only on 3 instances on a cluster even if more than 3, the instances that not have an ASM would request remote ASM, typically like SCAN. In normal conditions in a node if ASM fails the entire node will be useless, where in 12c the ability to get the extent map from remote ASM instance makes the node useful.

 

7) RMAN: Running SQL commands and executing PLSQL procedures in RMAN without SQL keyword.

   RMAN> select * from v$session;

 

8) Table level restoration i.e. object level using RMAN

 

9) In Oracle 12c, ACTIVE DUPLICATE DATABASE doesn’t not required any pre backup existence to clone the database, RMAN first takes backup of datafiles into backupsets, and transmit to the auxiliary location and will be restored/recovered subsequently.

 

10) New NOOPEN clause in 12c ACTIVE DUPLICATE DATABASE, will prevent opening database immediately after the cloning process completion and the database will remain in MOUNT state and we have to manually open the database.


11)Patching:

Centralised patching. We can retrieve OPatch information using sqlplus query, using DBMS_QOPATCH package

SQL> select dbms_qopatch.get_opatch_lsinventory() from dual;

 

12) New initialization parameters in Oracle 12c Release 1

temp_undo_enabled (=false|true)

DB_FLASH_CACHE_FILE

DB_FLASH_CACHE_SIZE

enable_ddl_logging

 

13) New tables/views in Oracle Database 12c

dba_pdbs

v$pdbs

cdb_data_files

 

14) New Packages in 12c Oracle Release 1

dbms_pdb

dbms_qopatch

UTL_CALLSTACK

dbms_redact

Labels:

Comments

Post a Comment

Popular posts from this blog

Registering The Database to RMAN catalog database:

Registering The Database to RMAN catalog database: Need to start RMAN as follows: RMAN target=sys/password@database_to_backup rcvcat=sys/password@recovery_catalog_database Another variation on the command, if the recovery catalog and the database were on the same server, might be as shown: oraenv ORACLE_SID = [KKUY] ? KKUY RMAN rcvcat=sys/password@recovery_catalog_database RMAN> connect target Recovery Manager: Release 8.0.5.1.0 - Production RMAN-06005: connected to target database: KKUY RMAN-06008: connected to recovery catalog database Use the below command to register the database. RMAN>register database; Want to verify if a database is registered in the recovery catalog. To do this, connect to RMAN and issue the command LIST INCARNATION OF DATABASE. RMAN> list incarnation of database; RMAN-03022: compiling command: list RMAN-06240: List of Database Incarnations RMAN-06241: DB Key Inc Key DB Name DB ID      CUR Reset SCN   Reset Time RMAN
Post a Comment
Read more

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG
Post a Comment
Read more