Oracle Secure Backups to S3 on 10g

By | In Blog, Oracle | November 02nd, 2011

If you are trying to install the Oracle Secure Backup Cloud Module for Amazon S3 on your Oracle 10g database, one thing you’ll notice right away is that you need version 1.5 or higher of the JDK. Oracle 10g ships with java 1.4, so here is what we did to get this installed

Running the installer with JDK version 1.4

If you didn’t read the requirements from Oracle and just tried to download and run the installer, you’ll notice fairly quickly that this isn’t going to work. The actual values for the -AWSID and -AWSKEY options can be found from the Amazon S3 Security Credentials page, and you’ll want to supply your OTN/Metalink login and password.

A quick check and we see that the version of java that ships with Oracle 10g is insufficient.

Downloading JDK version 1.5

You’ll want to grab a version 1.5 of java in order to install the Oracle Secure Backup Cloud Module for Amazon S3. What I did was I went to Metalink and downloaded patch 9477224, although there are probably other ways to download a stand-alone version of java 1.5. You don’t actually need to install java 1.5 into your 10g ORACLE_HOME. In fact, Oracle says in the patch notes that you should stick with the same major version of java in your 10g ORACLE_HOME (version 1.4). What I did was just unzip the patch into a temporary directory and run the self-extracting executables.

Running the installer with JDK version 1.5

Now that we have java 1.5 extracted, we can run the installer from this temporary directory. The installer will create a couple files based on the environment you’ve sources (your ORACLE_HOME and ORACLE_SID environment variables). This stand-alone version of java is not needed after the installer runs and you can blow it away if you want to.

Backing up to S3

You’ll notice it creates a directory for the wallet, an initialization file and a shared object. You’ll use the path to the initialization file it created, as well as the path to the shared object it extracted, to configure RMAN backups to S3 for this particular database. There’s no difference at this point between a 10g and 11g database in terms of configuring RMAN to backup to the cloud.

That’s all there is to it. At this point you can run a test backup.

Additional Configuration

If you poke around, you’ll notice the contents of the initialization file will look something like this.

There are a few other parameters you can set in this initialization file, although they don’t seem to be well documented (a google search for “OSB_WS_BUCKET” at the time of writing this blog returns zero results). You can see those parameters by strings-ing the shared object. I’ve listed the non-underscore parameters here. We’ve used the OSB_WS_BUCKET parameter in particular to change the default location of where backups are sent to, but that’s a topic for another time.

This process was tested on both the Standard Edition and Enterprise Edition of Oracle 10g. Dallas Willett Blue Gecko – Remote DBA Services

Contact Us

Leave a Reply

Your email address will not be published.
Required fields are marked (*).