Welcome to Datavail’s Blog, where you can read the latest insights, tips and opinions of our experts on all things data and technology.
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
The following is an example of how to move your SPFILE from ASM to your file system or vice versa. In this case, we have our spfile in the +DATA diskgroup and we want to move it to the default location on our file system. The default location will be in our $ORACLE_HOME/dbs directory. In order to accomplish this, we need to create a pfile from our existing spfile and then create the new spfile from this temporary pfile. Afterwords, we bounce the database instance for the change to take effect.
Most of us have had the need to backfill some data at one point or another. Perhaps we needed to create some data to test out a new application we’re building, or we wanted to test a new Oracle feature. Backfilling can be as easy as writing some INSERT and UPDATE commands, or coding up a simple PL/SQL script.
As promised for our upcoming presentation at this year’s Collaborate 2011 Conference, we have our Real Application Testing scripts. At the conference, Datavail and WTS will show how we used Oracle’s Real Application Testing to tune a production workload from a JD Edwards EnterpriseOne database running on Oracle.
Last week when we talked about how to implement a fast refresh materialized view with a MAX aggregate function. This week we will tackle another restriction on fast refresh materialized views. We will work through an example on how to modify a materialized view that includes a COUNT(DISTINCT) in order to get it to fast refresh.
With a very simple materialized view that contains an aggregate function like MAX, Oracle can perform a fast refresh of the materialized view. However, once we start adding some complexity to the materialized view query, Oracle starts to either error out on the fast refresh, or will disallow the creation of the fast refresh materialized view in the first place.