The following commands may be used to convert an 11g or 12c database to use a BIGFILE temporary tablespace datafile instead of the default regular file, which is limited to 32GB. BIGFILEs can grow to 32TB.
This can be useful when loading very large amounts of data into a database, for example for a POC test.
The Dell EMC Unity array is a capable mid-market platform able to support a variety of workloads.
In the all-flash configuration it delivers good performance for Oracle databases, and with the ability to support VVols is a good choice for databases virtualized with VMware ESX 6.
The following blog post walks you through adding VVol based shared storage for an Oracle 12c RAC using ASM and virtualized on VMware ESX 6.
There are many examples of this one, this is again more for my benefit than anyone else’s.
The following shows relocating the OCR and voting disks on a 12c RAC.
No downtime is needed. You only need to execute these commands on one node. Log in as root and source the Grid Infrastructure environment to make these changes:
Oracle currently ships 12cR1 (220.127.116.11) as the preferred install.
Being the R1 release it needs a lot of patching, and now many patches require OPatch 18.104.22.168, although the OPatch shipped with Grid 22.214.171.124 is in fact OPatch 126.96.36.199.3.
So you need to patch OPatch, before you can apply the patches you need to make 12cR1 work. Follow?
On this blog and elsewhere you will find UDEV rules examples for setting device ownership and naming consistency on older versions of Linux.
With RHEL7 some of the syntax has changed slightly.
This example was created using OEL7 with the Red Hat kernel, but should also work on Red Hat and CentOS.
The following shows how to clean up a failed 12cR1 RAC install on Linux, so that you can launch the runInstaller executable again.
Note. This approach assumes you have a single Oracle Home. If you have multiple versions of Oracle installed this approach may need to be adapted.
USE AT YOUR OWN RISK.
This is an issue that keeps tripping me up in the development lab.
I create a quick database, and then after some time I go back to try to log in, and get:
ORA-28002: the password will expire within 7 days
And then I spend a while trying to figure out how to disable the password expiry component of the profile.
Here then, for my benefit as much as anyone else, is my quick guide to checking the user profile, and then disabling security components that cause headaches in the development lab.