<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SSG Limited &#187; MetaLink</title>
	<atom:link href="http://blog.ssglimited.com/tag/metalink/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ssglimited.com</link>
	<description>Bridging the Gap between Business Vision and Technology Implementation</description>
	<lastBuildDate>Fri, 21 Jan 2011 17:02:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Cleaning up Tablespaces after OATM has Completed</title>
		<link>http://blog.ssglimited.com/2008/12/29/cleaning-up-tablespaces-after-oatm-has-completed/</link>
		<comments>http://blog.ssglimited.com/2008/12/29/cleaning-up-tablespaces-after-oatm-has-completed/#comments</comments>
		<pubDate>Mon, 29 Dec 2008 23:28:45 +0000</pubDate>
		<dc:creator>Robert McMillen</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[DBA]]></category>
		<category><![CDATA[E-Business Suite]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[Release 11i]]></category>
		<category><![CDATA[Release 12]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[LOB's]]></category>
		<category><![CDATA[MetaLink]]></category>
		<category><![CDATA[OATM]]></category>
		<category><![CDATA[Oracle Database]]></category>

		<guid isPermaLink="false">http://www.trioragroup.com/ssg/?p=299</guid>
		<description><![CDATA[Often after running Oracle Application Tablespace Migration (OATM) you will find that there are still indexes, tables and objects left in some of the old tablespaces.  You want to clean them up so you can delete the old tablespaces and recover the space used by the datafiles.  In the OATM documentation there&#8217;s no clear instructions [...]]]></description>
		<wfw:commentRss>http://blog.ssglimited.com/2008/12/29/cleaning-up-tablespaces-after-oatm-has-completed/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Release 12 Critical Patch Collection for November Available</title>
		<link>http://blog.ssglimited.com/2008/12/01/r12-critical-patch-collection-for-november-available/</link>
		<comments>http://blog.ssglimited.com/2008/12/01/r12-critical-patch-collection-for-november-available/#comments</comments>
		<pubDate>Mon, 01 Dec 2008 18:36:49 +0000</pubDate>
		<dc:creator>Robert McMillen</dc:creator>
				<category><![CDATA[Critical Patch Collection]]></category>
		<category><![CDATA[DBA]]></category>
		<category><![CDATA[E-Business Suite]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[Patch]]></category>
		<category><![CDATA[Release 12]]></category>
		<category><![CDATA[MetaLink]]></category>

		<guid isPermaLink="false">http://www.trioragroup.com/ssg/?p=250</guid>
		<description><![CDATA[In a previous post we discussed the new patching bundle, the Critical Patch Collection (CPC) that Oracle began issuing in October.  As a recap, this is what Oracle says about CPC&#8217;s. R12 Financials Critical Patch Collections (CPC) are consolidated critical patches that all R12 Financials customers must apply to ensure proper operation of their systems. [...]]]></description>
		<wfw:commentRss>http://blog.ssglimited.com/2008/12/01/r12-critical-patch-collection-for-november-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Applying RUP6 for Release 12.0.6</title>
		<link>http://blog.ssglimited.com/2008/12/01/applying-rup6-for-release-1206/</link>
		<comments>http://blog.ssglimited.com/2008/12/01/applying-rup6-for-release-1206/#comments</comments>
		<pubDate>Mon, 01 Dec 2008 18:20:29 +0000</pubDate>
		<dc:creator>Robert McMillen</dc:creator>
				<category><![CDATA[DBA]]></category>
		<category><![CDATA[E-Business Suite]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[Patch]]></category>
		<category><![CDATA[Release 12]]></category>
		<category><![CDATA[RUP]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[Critical Patch Collection]]></category>
		<category><![CDATA[MetaLink]]></category>
		<category><![CDATA[RUP6]]></category>

		<guid isPermaLink="false">http://www.trioragroup.com/ssg/?p=243</guid>
		<description><![CDATA[I recently applied the latest RUP for Release 12 at a client that is in the midst of a new R12 installation.  I thought I&#8217;d recap my experience. The 12.0.6 patch was released on Friday, November 7th.  We were alerted to it because we ran a fresh version of patchsets.sh during the week and it [...]]]></description>
		<wfw:commentRss>http://blog.ssglimited.com/2008/12/01/applying-rup6-for-release-1206/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>So That&#8217;s What Those Hidden Oracle Parameters Are For!</title>
		<link>http://blog.ssglimited.com/2008/11/05/so-thats-what-those-hidden-oracle-parameters-are-for/</link>
		<comments>http://blog.ssglimited.com/2008/11/05/so-thats-what-those-hidden-oracle-parameters-are-for/#comments</comments>
		<pubDate>Wed, 05 Nov 2008 14:34:21 +0000</pubDate>
		<dc:creator>Robert McMillen</dc:creator>
				<category><![CDATA[Database]]></category>
		<category><![CDATA[DBA]]></category>
		<category><![CDATA[E-Business Suite]]></category>
		<category><![CDATA[RAC]]></category>
		<category><![CDATA[Release 12]]></category>
		<category><![CDATA[cloning]]></category>
		<category><![CDATA[controlfile]]></category>
		<category><![CDATA[MetaLink]]></category>
		<category><![CDATA[RMAN]]></category>

		<guid isPermaLink="false">http://www.trioragroup.com/ssg/?p=231</guid>
		<description><![CDATA[We hit this issue when we were cloning a production RAC environment that had been backed up using RMAN and then restored to a non-RAC test environment. To get past it, we had to add a hidden parameter to the target init.ora file to allow us to open the duplicated database, and then remove it [...]]]></description>
		<wfw:commentRss>http://blog.ssglimited.com/2008/11/05/so-thats-what-those-hidden-oracle-parameters-are-for/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Oracle Critical Patch Updates for this Quarter</title>
		<link>http://blog.ssglimited.com/2008/10/15/oracle-critical-patch-updates-for-this-quarter/</link>
		<comments>http://blog.ssglimited.com/2008/10/15/oracle-critical-patch-updates-for-this-quarter/#comments</comments>
		<pubDate>Wed, 15 Oct 2008 14:41:53 +0000</pubDate>
		<dc:creator>Robert McMillen</dc:creator>
				<category><![CDATA[Critical Patch Update]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[E-Business Suite]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[Patch]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[MetaLink]]></category>

		<guid isPermaLink="false">http://www.trioragroup.com/ssg/?p=202</guid>
		<description><![CDATA[A Critical Patch Update is a collection of patches for multiple security vulnerabilities. It also includes non-security fixes that are required (because of inter-dependencies) by those security patches. Critical Patch Updates are cumulative (with some exceptions) but each advisory describes only the security fixes added since the previous Critical Patch Update. The Critical Patch Update [...]]]></description>
		<wfw:commentRss>http://blog.ssglimited.com/2008/10/15/oracle-critical-patch-updates-for-this-quarter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

