ANIL VEJENDLA

How to create user without C## in oracle 12c Even after using hidden parameter in init file, i am unable to create user without c##. But when we  setup  session level then  i am able to create user without c## . Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL> sho parameter _oracle NAME                                 TYPE        VALUE ------------------------------------ ----------- ------------------------------ _oracle_script                       boolean     TRUE SQL>  create user anil identified by anil; create user anil identified by anil             * ERROR at line 1: ORA-65096: invalid common user or role name After setting hidden parameter at session level .. SQL> alter session set "_oracle_script"=true; Session altered. SQL> sho pdbs     CON_ID CON_NAME      OPEN MODE  RESTRICTED ---------- ------------------------------ ---------- ----------

Issue: PDB is in Restricted mode. Today we have upgraded 11g datbase to 12c and plugged in container. After running noncdb_to_pdb.sql we tried to open PDB, PDB status Restricted is  YES.. CDB$ROOT@ AGIIPRDC > sho pdbs     CON_ID CON_NAME                       OPEN MODE  RESTRICTED ---------- ------------------------------ ---------- ----------          3  RQBIPRDPDB1                             READ WRITE YES Reason : Rows with type ERROR and status PENDING from pdb_plug_in_violations select name, cause, type, message, status from pdb_plug_in_violations where type = 'ERROR' and status != 'RESOLVED'  order by name, time; CDB$ROOT@AGIIPRDC> set linesize 150 col name for a15 col cause for a15 col message for a50 select name, cause, type, message, status from pdb_plug_in_violations where type = 'ERROR' and status != 'RESOLVED'  order by name, time;CDB$ROOT@AGIIPRDC> CDB$ROOT@AGIIPRDC> CDB$ROOT@AGI

Error:  ORA-00600 : internal error code, arguments: [qksvcGetGuardCol:2], [100313], [0], [], [], [], [], [], [], [], [], []   We have upgraded Database from 11.2.0.2 to 12.2.0.1 from Exadata ASM to Normal File system. and plugged into container. Everything went fine .. but we encountered ORA-600 error with Few ETL Tables . select  count(*) from table  is working fine..but select * from table is failing. CDB$ROOT@EBTUPRDC> select count(*) from "EBAOREP"."F_POLICY_CT_TRANS";   COUNT(*) ----------    9208566 select * from is failing with ORA-600 Error. CDB$ROOT@EBTUPRDC> select * from EBTUS_GS.T_AS_MAILING_ADDRESS;   select * from EBTUS_GS.T_AS_MAILING_ADDRESS   *   ERROR at line 1:   ORA-00600: internal error code, arguments: [qksvcGetGuardCol:2], [228717], [0],   [], [], [], [], [], [], [], [], []   Solution :  We Exported Failed Tables from source database and imported into Upgraded 12c database. Solution Provided by Oracle support :

Error: CDB$ROOT@EBTUPRDC> CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse; CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse * ERROR at line 1: ORA-65139: Mismatch between XML metadata file and data file /u05/odb/ORADATA_1/EBTUSPRDC/datafile/system.1531.807800993 for value of fcpsb (2230502002 in the plug XML file, 2230505492 in the data file) Fix: Don't open Non-CDB database until we complete pdb creation other wise we will get above error. Shutdown immediate; startup mount; alter database open read only; create xml file. shutdown immediate; Connect to CDB and Create Pluggable database .

12c NON-CDB to Container PDB   Steps for Non-CDB : EBTUSPRD@EBTUSPRD> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. EBTUSPRD@EBTUSPRD> startup mount ORACLE instance started. Total System Global Area 3355443200 bytes Fixed Size                  8626240 bytes Variable Size            1040191424 bytes Database Buffers         2164260864 bytes Redo Buffers              142364672 bytes Database mounted. EBTUSPRD@EBTUSPRD> alter database open read only; Database altered. Create XML file: BEGIN   DBMS_PDB.DESCRIBE(     pdb_descr_file => '/home/oracle/EBTUSPRDC.xml'); END; / PL/SQL procedure successfully completed. Shutdown NON-CDB: EBTUSPRD@EBTUSPRD> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. Steps for Container Database: SET SERVEROUTPUT ON DECLARE   compatible CONSTANT VARCHAR2(3) :=       CASE DBMS_PDB.CH

We have created new database in shared environment using dbca, we Suddenly started seeing " E RR OR: Unable to get logical block size for spfile" errors in few databases.  E RR OR : Unable to get logical block size for spfile '+DATA/aedvam01/spfileaedvam01.ora'. Wed Jul 19 02:21:07 2017 Work around: sho parameter spfile  +DATA/AEDVAM01/PARAMETERFILE/spfile.1401.919658705  Create alias using correct name spfileaedvam01.ora Set environment to ASM Instance. . oraenv +ASM1 asmcmd mkalias +DATA/AEDVAM01/PARAMETERFILE/spfile.1401.919658705 +DATA/aedvam01/spfileaedvam01.ora

Issue: We are getting weblogic stuck thread alerts “ Incident (BEA-000337 [WebLogicServer]) detected in /u01/app/oracle/oem12c/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS2/adr/diag/ofm/GCDomain/EMGC_O ” from our OMS Servers.. Logfile : /u01/app/oracle/oem12c/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS2/adr/diag/ofm/GCDomain/EMGC_OMS2/alert/log.xml Errors in directory: /u01/app/oracle/oem12c/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS2/adr/diag/ofm/GCDomain/EMGC_OMS2/incident/incdir_622  (incident=622): stuck thread detected: [STUCK] ExecuteThread: '70' for queue: 'weblogic.kernel.Default (self-tuning)' Fix: EM 12c: Enterprise Manager 12c Cloud Control Crashes Regularly with Logged Error: BEA-000337 ExecuteThread for OMS [ID 2229322.1]   To increase the Stuck Thread Max Time to a higher value (i.e 1800 seconds) :   1. Log onto the WLS Administration server.   2. Click on Environment

Error: ERROR at line 1: ORA-28086: The data redaction policy expression has an error. ORA-06512: at "SYS.DBMS_REDACT_INT", line 3 ORA-06512: at "SYS.DBMS_REDACT", line 42 ORA-06512: at line 1 When we try to run same as sys user it is working perfectly fine, but as a normal user it is failing with below errors. No Privileges issue because AVO user had DBA Privilege .. Versions  confirmed  as being affected 12.1.0.2 (Server Patch Set) 11.2.0.4 Fixed: The fix for 20693579 is first included in 12.2.0.1 (Base Release) Cause : Bug 20693579 - DBMS_REDACT.ADD_POLICY fails with ORA-28086 when CURSOR_SHARING is force (Doc ID 20693579.8) To Bottom Bug 20693579  DBMS_REDACT.ADD_POLICY fails with ORA-28086 when CURSOR_SHARING is force  This note gives a brief overview of bug 20693579.  The content was last updated on: 17-FEB-2017   Click  here  for details of each of the sections below. Affects: Product ( Compo

We have multiple Databases running on same server and using EM Console to monitor backups information .. We are getting Error "Register Database in Recovery Catalog" which is already registered in catalog . We got this error only for Container Database . in EM console, navigate to Targets -> Databases -> Availability -> Backup and Recovery -> Manage Current Backups  and you get the following error on the screen: Error Only databases with a version of 10.1 or above, or databases that use a recovery catalog of schema version 10.1 or above are supported. You can click the following link to register the database in a recovery catalog. Register Database In Recovery Catalog CAUSE Known bugs in 12.1.0.6.0 EM DB Plugin Bug 21825439 Bug 19346373 Bug 19152759   SOLUTION  Upgrade the DB Plugin from 12.1.0.6.0 to 12.1.0.7 and apply the latest EM DB Plugin Bundle Patch on top of 12.1.0.7.x

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 parameters used for automatic instanc