Posts

Unable to get logical block size for spfile in alert log

We have created new database in shared environment using dbca, we Suddenly started seeing "ERROR: Unable to get logical block size for spfile" errors in few databases. 




ERROR: 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


BEA-000337:Weblogic stuck thread detected: [STUCK] ExecuteThread

Image
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 in the top right side menu and expand Servers. …

ORA-28086: The data redaction policy expression has an error

Image
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 affected12.1.0.2 (Server Patch Set)11.2.0.4
Fixed:The fix for 20693579 is first included in12.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 (Component)Oracle Server (Rdbms)Range of versions believed to be affectedVersions >= 12.1 but BEL…

12c EM Manage Current Backups Returns Error for Container Database

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

Image
Database Patch Set Release Roadmap:


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



12.2.0.1 Release Date 15-Mar-2017

Image
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

Image
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.