<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Jay Z DBA</title>
	<atom:link href="http://jzdba.dotplane.com/blogs/feed/" rel="self" type="application/rss+xml" />
	<link>http://jzdba.dotplane.com/blogs</link>
	<description>At the Center of Technologies</description>
	<pubDate>Wed, 06 Jan 2010 16:26:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Deadlocked by Self</title>
		<link>http://jzdba.dotplane.com/blogs/2010/01/06/deadlocked-by-self/</link>
		<comments>http://jzdba.dotplane.com/blogs/2010/01/06/deadlocked-by-self/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 16:18:01 +0000</pubDate>
		<dc:creator>Jay</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[ORA-04020]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=26</guid>
		<description><![CDATA[A common answer to database deadlocks is that they are caused by two or more sessions waiting on locks held by each other and eventually deadlock themselves. A recent experience revealed to me it could be more concealed than having multiple application sessions running concurrently.
I was trying to re-install the XDB schema in one of [...]]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2010/01/06/deadlocked-by-self/feed/</wfw:commentRss>
		</item>
		<item>
		<title>DBA_TABLESPACE_USAGE_METRICS</title>
		<link>http://jzdba.dotplane.com/blogs/2009/09/11/dba_tablespace_usage_metrics/</link>
		<comments>http://jzdba.dotplane.com/blogs/2009/09/11/dba_tablespace_usage_metrics/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 14:28:39 +0000</pubDate>
		<dc:creator>Jay</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[Oracle 11g tablespace usage]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=25</guid>
		<description><![CDATA[Oracle has a handy view to show the tablespace usage, which has a rather verbose name: DBA_TABLESPACE_USAGE_METRICS
Oracle&#8217;s document describes this view column as 

TABLESPACE_NAME 		VARCHAR2(30) 	Tablespace name
USED_SPACE 			NUMBER 				Total space consumed by the tablespace
TABLESPACE_SIZE 		NUMBER 				Total size of the tablespace
USED_PERCENT 			NUMBER 				Percentage of used space, as a function of the maximum possible tablespace size



  [...]]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2009/09/11/dba_tablespace_usage_metrics/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Encountered ORA-6502 when trying to attach to a data pump export job</title>
		<link>http://jzdba.dotplane.com/blogs/2009/05/28/encountered-ora-6502-when-trying-to-attach-to-a-data-pump-export-job/</link>
		<comments>http://jzdba.dotplane.com/blogs/2009/05/28/encountered-ora-6502-when-trying-to-attach-to-a-data-pump-export-job/#comments</comments>
		<pubDate>Thu, 28 May 2009 13:37:34 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle Dump]]></category>

		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[expdp attach]]></category>

		<category><![CDATA[ORA-6502]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=24</guid>
		<description><![CDATA[I encountered this error since early days of 10gR2 when trying to re-attach to a stopped job with a job name of 30 characters:

ORA-06502: PL/SQL: numeric or value error: character string buffer too small]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2009/05/28/encountered-ora-6502-when-trying-to-attach-to-a-data-pump-export-job/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Check the space used by flashback data archive</title>
		<link>http://jzdba.dotplane.com/blogs/2009/02/12/check-the-space-used-by-flashback-data-archive/</link>
		<comments>http://jzdba.dotplane.com/blogs/2009/02/12/check-the-space-used-by-flashback-data-archive/#comments</comments>
		<pubDate>Thu, 12 Feb 2009 20:05:36 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[flashback data archive]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=23</guid>
		<description><![CDATA[As a DBA, one will inevitably encounter this question: how much space does my allocated flashback archives use?]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2009/02/12/check-the-space-used-by-flashback-data-archive/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Shrink Oracle Undo Space</title>
		<link>http://jzdba.dotplane.com/blogs/2009/01/13/shrink-oracle-undo-space/</link>
		<comments>http://jzdba.dotplane.com/blogs/2009/01/13/shrink-oracle-undo-space/#comments</comments>
		<pubDate>Tue, 13 Jan 2009 18:32:24 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[undo tablespace]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=22</guid>
		<description><![CDATA[To shrink the UNDO space back to a reasonable size, you will have to use a workaround as demonstrated below.]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2009/01/13/shrink-oracle-undo-space/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Shrink SQL Server Database Log</title>
		<link>http://jzdba.dotplane.com/blogs/2008/11/10/shrink-sql-server-database-log/</link>
		<comments>http://jzdba.dotplane.com/blogs/2008/11/10/shrink-sql-server-database-log/#comments</comments>
		<pubDate>Mon, 10 Nov 2008 20:23:56 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[SQL Server]]></category>

		<category><![CDATA[DB Log Shrink]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=21</guid>
		<description><![CDATA[When I first started to use SQL Server, I was caught by surprise one day when I noticed the log file size reached an astonishing 40GB, leaving only a few giga in my disk partition. After that I put regular log shrinking operations on my databases running in FULL recovery mode.]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2008/11/10/shrink-sql-server-database-log/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Bug 7452749: ORA-1732 generated with update on joined view</title>
		<link>http://jzdba.dotplane.com/blogs/2008/11/10/bug-7452749-ora-1732-generated-with-update-on-joined-view/</link>
		<comments>http://jzdba.dotplane.com/blogs/2008/11/10/bug-7452749-ora-1732-generated-with-update-on-joined-view/#comments</comments>
		<pubDate>Mon, 10 Nov 2008 19:42:35 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[Bug 7452749]]></category>

		<category><![CDATA[ORA-1732]]></category>

		<category><![CDATA[update joined view]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=20</guid>
		<description><![CDATA[After I upgraded a database from Oracle 10.2.0.2 to 10.2.0.4, we encountered ORA-1732 when running an update on a joined view: ORA-1732 generated with update on joined view]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2008/11/10/bug-7452749-ora-1732-generated-with-update-on-joined-view/feed/</wfw:commentRss>
		</item>
		<item>
		<title>ORA-32313: REFRESH FAST unsupported after PMOPs</title>
		<link>http://jzdba.dotplane.com/blogs/2008/10/30/ora-32313-refresh-fast-unsupported-after-pmops/</link>
		<comments>http://jzdba.dotplane.com/blogs/2008/10/30/ora-32313-refresh-fast-unsupported-after-pmops/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 02:53:56 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[ORA-32313]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=19</guid>
		<description><![CDATA[Recently I added new partitions to many of my tables and materialized views. Then when I fas refresh some materialized views I got ORA-32313:  REFRESH FAST unsupported after PMOPs]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2008/10/30/ora-32313-refresh-fast-unsupported-after-pmops/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Show Oracle Recyclebin Size</title>
		<link>http://jzdba.dotplane.com/blogs/2008/10/16/show-oracle-recyclebin-size/</link>
		<comments>http://jzdba.dotplane.com/blogs/2008/10/16/show-oracle-recyclebin-size/#comments</comments>
		<pubDate>Fri, 17 Oct 2008 01:52:28 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[Oracle recyclebin]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=18</guid>
		<description><![CDATA[Oracle 10g introduced recycle bin. A dropped table will end up in recyclebin unless it&#8217;s explicitly dropped with purge. Such tables still have their segments in the tablespaces where they were created. Sometimes you want to know how large the junks are so you can purge them in time.
The following script displays recyclebin objects by [...]]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2008/10/16/show-oracle-recyclebin-size/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Kill Orphaned OS Processes</title>
		<link>http://jzdba.dotplane.com/blogs/2008/10/16/kill-orphaned-os-processes/</link>
		<comments>http://jzdba.dotplane.com/blogs/2008/10/16/kill-orphaned-os-processes/#comments</comments>
		<pubDate>Fri, 17 Oct 2008 01:43:57 +0000</pubDate>
		<dc:creator>jzdba</dc:creator>
		
		<category><![CDATA[Oracle database]]></category>

		<category><![CDATA[orphaned process]]></category>

		<guid isPermaLink="false">http://jzdba.dotplane.com/blogs/?p=17</guid>
		<description><![CDATA[Sometimes after killing Oracle sessions, the session&#8217;s paddr and process addr
are disassociated and leave the process orphaned.
To clean up these orphaned processes, generate the  Unix  kill commands with this SQL script:
set pages 0
select 'kill '&#124;&#124;spid from v$process
where addr not in (select paddr from v$session);
Then you can run the generated commands on command line.


 [...]]]></description>
		<wfw:commentRss>http://jzdba.dotplane.com/blogs/2008/10/16/kill-orphaned-os-processes/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
