<?xml version="1.0" encoding="UTF-8"?><!-- generator="orablog/0.3+" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Modifying Oracle XE&#8217;s backup.sh Script to do Incremental Backups</title>
	<link>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/</link>
	<description>Helping PHP developers migrate from MySQL to Oracle</description>
	<pubDate>Tue, 07 Oct 2008 09:54:56 +0000</pubDate>
	<generator>http://www.orablog.org/?v=0.3+</generator>

	<item>
		<title>by: PHP Conference Update: Oracle is free and easy to use! at lamp2lapo</title>
		<link>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-4</link>
		<pubDate>Tue, 07 Nov 2006 14:29:36 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-4</guid>
					<description>[...] The second issue is ease of use. It is true that Oracle is quite complex and if you build a serious application using it you will require the services of an Oracle DBA at some point in time. I&#8217;ve seen many MySQL installations in my time and I can confidently say that almost every one should have used the services of a MySQL DBA to tune it correctly. DBA issues aside, Oracle XE provides an easy to use, web-based GUI for performing most tasks. It&#8217;s only when you delve outside of your standard CRUD operations, like modifying the default backup strategy, that Oracle-specific knowledge comes in to play. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The second issue is ease of use. It is true that Oracle is quite complex and if you build a serious application using it you will require the services of an Oracle DBA at some point in time. I&#8217;ve seen many MySQL installations in my time and I can confidently say that almost every one should have used the services of a MySQL DBA to tune it correctly. DBA issues aside, Oracle XE provides an easy to use, web-based GUI for performing most tasks. It&#8217;s only when you delve outside of your standard CRUD operations, like modifying the default backup strategy, that Oracle-specific knowledge comes in to play. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bug Fixes and Updated RMAN Configuration at lamp2lapo</title>
		<link>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-3</link>
		<pubDate>Thu, 02 Nov 2006 13:59:40 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-3</guid>
					<description>[...] Register          &#171; Modifying Oracle XE&#8217;s backup.sh Script to do Incremental Backups [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Register          &laquo; Modifying Oracle XE&#8217;s backup.sh Script to do Incremental Backups [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: fifers</title>
		<link>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-2</link>
		<pubDate>Thu, 02 Nov 2006 13:43:50 +0000</pubDate>
		<guid>http://www.lamp2lapo.com/2006/10/04/modifying-oracle-xes-backupsh-script-to-do-incremental-backups/#comment-2</guid>
					<description>The original article wasn't consistent with the tag name.  The database copy was named 'whole_db_cpy' and the incremental backup referred to whole_db_copy.  The quote from Jim Czuprynski used his tag of 'img_cpy_upd' instead of updating it to match our tag of 'whole_db_copy'.  In short, the script didn't quite work and the explanation wasn't easy to follow!  I've updated this article, and my backup script, to fix these problems.  Sorry if I caused any confusion!</description>
		<content:encoded><![CDATA[<p>The original article wasn&#8217;t consistent with the tag name.  The database copy was named &#8216;whole_db_cpy&#8217; and the incremental backup referred to whole_db_copy.  The quote from Jim Czuprynski used his tag of &#8216;img_cpy_upd&#8217; instead of updating it to match our tag of &#8216;whole_db_copy&#8217;.  In short, the script didn&#8217;t quite work and the explanation wasn&#8217;t easy to follow!  I&#8217;ve updated this article, and my backup script, to fix these problems.  Sorry if I caused any confusion!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
