Installing 12c R1 database on oracle linuxDocument Transcript
First, log in to Oracle Software Delivery Cloud, and search for the 12cR1 database software. Since I
am running a 64-bit OS, I chose Linux x86-64 as the platform for the search.
Click on the link titled "Oracle Database 12c Release 1 (188.8.131.52.0) Media Pack for Linux x86-64"
and download the two zip files titled "Oracle Database 12c Release 1 (184.108.40.206.0) for Linux x86-64
(Part 1 of 2)" and "Oracle Database 12c Release 1 (220.127.116.11.0) for Linux x86-64 (Part 2 of 2)" depending on your download speed, this may take a few hours.
Copy the two zip files from the host Windows machine into the guest Linux VM using the shared
folders defined in this previous post. As the oracle unix user, unzip the two zip files using the unzip
command, and a folder named "database" will be created. (If the unzip command reports errors, this
typically implies that the downloaded zip files are corrupt - you may have to download the zip files
again). On my machine, after unzipping the two files, I renamed the "database" folder to
"database_12c" for clarity.
Review the 12cR1 Linux Install Guide before proceeding with the installation. If you have a
previous/older Oracle install on the VM server, ensure that you backup the oraInventory directory
before proceeding. The location of this directory is documented in file /etc/oraInst.loc.
Start the install by executing the "runInstaller" script.
On the first install screen, provide your My Oracle Support credentials if you have them. For the
purposes of this install, I chose not to use this feature. Click Next button.
Click Yes to confirm
Again, for the purposes of this blog post, I chose to skip software updates.
Choose the default option to create and configure a database, then click Next. (Alternatively, you
can choose to install the software only, then create a database later using the DBCA utility)
Choose Desktop Class, then click Next. (Desktop Class is defined in the Install Guide)
Enter the paths for "Oracle base", "Software location" and "Database file location" as appropriate.
Choose "Enterprise Edition" for the edition and AL32UTF8 for the characterset. Choose and
appropriate "Global database name" and strong passwords. Check the box to create container and
pluggable database. Understand the multitenant conceptbefore proceeding. Click Next.
Ensure that you provide a strong admin password. For this blog post, I chose a simple password click Yes to continue.
Review the Summary screen, and if everything is as expected, click the Install button.
The Installer will then proceed with the installation process.
You will be prompted to execute the root.sh script as root.
Run the root.sh script in a separate terminal window as instructed - use the default prompt for the
"local bin directory" variable, then choose to overwrite the 3 environment files (this will happen only if
these files are present from a previous install).
Close the root terminal window, then click OK on the Installer screen. The database configuration
process will start. This process may take a while depending on your VM configuration.
When the 12cR1 database creation process is complete, you will see
Note that all seeded database accounts except for SYS and SYSTEM are locked. You can choose
to unlock them at this point (click on Password Management button), or accounts can be unlcoked
later manually. Click OK, then click Close to exit the installer.
Set these environment variables
and then connect to the container database by issuing command
# sqlplus / as sysdba
and query the database name
select database_name from v$database;
We have successfully connected to the container database (CDB). Next, we need to open the
pluggable database (PDB) "pdborcl" created as part of this install. Note that PDBs are not opened
automatically after a CDB is started.
Issue command "alter pluggable database pdborcl open read write" to open the PDB database.
Edit the tnsnames.ora file (found in $TNS_ADMIN directory) and add a TNS entry for the PDB
pdborcl. The service name in the entry should point to the PDB (pdborcl.localdomain in this case).
Exit out of the CDB connection and connect to the PDB using the syntax
Verify that you have connected to the PDB by issuing command