ANIL VEJENDLA

Database Patch Set Release Roadmap: To Bottom refer Release Schedule of Current Database Releases (Doc ID 742060.1) for more details.

reference: Release Schedule of Current Database Releases (Doc ID 742060.1) On-Premise Server Releases (includes client) 12.2.0.1 On-Premise Server release date for Linux x86-64 is 15-Mar-2017.

Jan 2017 PSU Patches not available for Database Version 11.2.0.4. MOS Note: 854428.1 Oracle Recommended Patches -- Oracle Database (Doc ID 756671.1) Quick Reference to Patch Numbers for Database/GI PSU, SPU(CPU), Bundle Patches and Patchsets (Doc ID 1454618.1)     As there are no Security Fixes for Oracle Database 11.2.0.4 this quarter there are no SPUs or PSU released.

When the character set of the root is AL32UTF8, PDBs that are plugged into the CDB or cloned can have a different character set than the root. PDBs that are created from the CDB seed inherit the AL32UTF8 from it, but you can migrate the PDB to a different character set. http://docs.oracle.com/database/122/ADMIN/creating-and-configuring-a-cdb.htm#ADMIN13517 ​

RMAN> RECOVER TABLE 'TEST1'.'TEST1'   UNTIL SCN 3785709   AUXILIARY DESTINATION '/u06/aux';  Starting recover at 30-DEC-16 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=130 device type=DISK RMAN-05026: WARNING: presuming following set of tablespaces applies to specified Point-in-Time List of tablespaces expected to have UNDO segments Tablespace SYSTEM Tablespace UNDOTBS1 Creating automatic instance, with SID='flAE' initialization parameters used for automatic instance: db_name=TEST db_unique_name=flAE_pitr_TEST compatible=12.1.0.2.0 db_block_size=8192 db_files=200 diagnostic_dest=/u01/app/oracle _system_trig_enabled=FALSE sga_target=2560M processes=200 db_create_file_dest=/u06/aux log_archive_dest_1='location=/u06/aux' #No auxiliary parameter file used starting up automatic instance TEST Oracle instance started Total System Global Area...

Table Recovery in Standard Edition: Tablespace Point in Time Recovery/Table Recovery  is not Possible in Standard Edition . I am not convinced with this statement and trying  to perform Table Recovery in Standard edition using RMAN. Created Tablespace Called "test1"  and Table called "test1". Taken Backup of Database and Archivelogs: RUN {   ALLOCATE CHANNEL ch11 TYPE DISK MAXPIECESIZE 10G;   BACKUP   FORMAT '/u06/odb/backup/%d_D_%T_%u_s%s_p%p'   DATABASE   PLUS ARCHIVELOG   FORMAT '/u06/odb/backup/%d_A_%T_%u_s%s_p%p';   RELEASE CHANNEL ch11; } Taken Current_scn from v$database: SQL>  select current_scn from v$database; CURRENT_SCN -----------     1655232 Dropped table test1.test1; Now Started working Restore/Recover Dropped Table test1.test1: Created Pfile for auxiliary Instance with following parameters: *************************************************** initialization para...