ashoka ajjampura

==> Environmental Details : O/S :Windows Server 2008 64 bits Oracle Version : 11.2.0.1 ==> Error Details : While Taking full database export using “EXPDP” i was getting below mentioned error : ############################################### C:\> expdp directory=pump_dir=expdp_test.dmp logfile=expdp_test.log full=y Export: Release 11.2.0.1.0 – Production on Thu Feb 27 10:48:09 2014 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. Username : system/oracle123 as sysdba Password: Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options ORA-39006: internal error ORA-39213: Metadata processing is not available ############################################### Soultion login  to sys C:\sqlplus sys as sysdba SQL> execute dbms_metadata_util.load_stylesheets ...

select a.tablespace_name as tablespace_name ,a.total_mb,b.used_mb ,a.total_mb-b.used_mb  as free_space from (select d.tablespace_name, sum(d.bytes/1024/1024) as total_mb from dba_data_files d group by d.tablespace_name) a, ( select s.tablespace_name,sum(s.bytes/1024/1024) as used_mb from dba_segments s group by tablespace_name)  b  where a.tablespace_name=b.tablespace_name order by tablespace_name select a.tablespace_name as tablespace_name ,a.total_mb,b.used_mb ,a.total_mb-b.used_mb as  free ,free_space  as free_space from (select tablespace_name, sum(bytes/1024/1024) as total_mb from dba_data_files group by tablespace_name) a, ( select tablespace_name,sum(bytes/1024/1024) as used_mb from dba_segments group by tablespace_name)  b, (select tablespace_name,sum(bytes/1024/1024) as free_space from dba_free_space group by tablespace_name)  c where a.tablespace_name=b.tablespace_name and b.tablespace_name=c.tablespace_name order by tablesp...

In 11gR2, addition to OCR, we have another component called OLR installed on each node in the cluster. It is a local registry for node specific purposes. The OLR is not shared by other nodes in the cluster. It is installed and configured when clusterware is installed. Why OLR is used and why was it introduced. In 10g, we cannot store OCR’s in ASM and hence to startup the clusterware, oracle uses OCR but what happens when OCR is stored is ASM in 11g. OCR should be accessible to find out the resources that need to be started or not. But, if OCR is on ASM, it can’t read until ASM (which itself is the resource of the node and this information is stored in OCR) is up.  To answer this, Oracle introduced a component called OLR. Ø     It is the first fi le used to startup the clusterware when OCR is stored on ASM. Ø     Information about the resources that needs to be started on a node is stored in an OS file called ORACLE LOCAL REGISTRY (OLR). Ø ...