# yum install oracle-rdbms-server-12cR1-preinstall Loaded plugins: security public_ol6_UEKR3_latest | 1.2 kB 00:00 public_ol6_latest | 1.4 kB 00:00 Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package oracle-rdbms-server-12cR1-preinstall.x86_64 0:1.0-11.el6 will be installed --> Processing Dependency: xorg-x11-utils for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: gcc-c++ for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: compat-libcap1 for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: ksh for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: libaio-devel for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: xorg-x11-xauth for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: compat-libstdc++-33 for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Processing Dependency: libstdc++-devel for package: oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 --> Running transaction check ---> Package compat-libcap1.x86_64 0:1.10-1 will be installed ---> Package compat-libstdc++-33.x86_64 0:3.2.3-69.el6 will be installed ---> Package gcc-c++.x86_64 0:4.4.7-4.el6 will be installed ---> Package ksh.x86_64 0:20120801-10.el6_5.9 will be installed ---> Package libaio-devel.x86_64 0:0.3.107-10.el6 will be installed ---> Package libstdc++-devel.x86_64 0:4.4.7-4.el6 will be installed ---> Package xorg-x11-utils.x86_64 0:7.5-6.el6 will be installed --> Processing Dependency: libXxf86misc.so.1()(64bit) for package: xorg-x11-utils-7.5-6.el6.x86_64 --> Processing Dependency: libdmx.so.1()(64bit) for package: xorg-x11-utils-7.5-6.el6.x86_64 --> Processing Dependency: libXxf86dga.so.1()(64bit) for package: xorg-x11-utils-7.5-6.el6.x86_64 ---> Package xorg-x11-xauth.x86_64 1:1.0.2-7.1.el6 will be installed --> Processing Dependency: libXmuu.so.1()(64bit) for package: 1:xorg-x11-xauth-1.0.2-7.1.el6.x86_64 --> Running transaction check ---> Package libXmu.x86_64 0:1.1.1-2.el6 will be installed ---> Package libXxf86dga.x86_64 0:1.1.3-2.el6 will be installed ---> Package libXxf86misc.x86_64 0:1.0.3-4.el6 will be installed ---> Package libdmx.x86_64 0:1.1.2-2.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ======================================================================================================================================== Package Arch Version Repository Size ======================================================================================================================================== Installing: oracle-rdbms-server-12cR1-preinstall x86_64 1.0-11.el6 public_ol6_latest 15 k Installing for dependencies: compat-libcap1 x86_64 1.10-1 public_ol6_latest 17 k compat-libstdc++-33 x86_64 3.2.3-69.el6 public_ol6_latest 183 k gcc-c++ x86_64 4.4.7-4.el6 public_ol6_latest 4.7 M ksh x86_64 20120801-10.el6_5.9 public_ol6_latest 757 k libXmu x86_64 1.1.1-2.el6 public_ol6_latest 65 k libXxf86dga x86_64 1.1.3-2.el6 public_ol6_latest 24 k libXxf86misc x86_64 1.0.3-4.el6 public_ol6_latest 17 k libaio-devel x86_64 0.3.107-10.el6 public_ol6_latest 13 k libdmx x86_64 1.1.2-2.el6 public_ol6_latest 20 k libstdc++-devel x86_64 4.4.7-4.el6 public_ol6_latest 1.6 M xorg-x11-utils x86_64 7.5-6.el6 public_ol6_latest 94 k xorg-x11-xauth x86_64 1:1.0.2-7.1.el6 public_ol6_latest 34 k Transaction Summary ======================================================================================================================================== Install 13 Package(s) Total download size: 7.5 M Installed size: 23 M Is this ok [y/N]: y Downloading Packages: (1/13): compat-libcap1-1.10-1.x86_64.rpm | 17 kB 00:00 (2/13): compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm | 183 kB 00:00 (3/13): gcc-c++-4.4.7-4.el6.x86_64.rpm | 4.7 MB 00:00 (4/13): ksh-20120801-10.el6_5.9.x86_64.rpm | 757 kB 00:00 (5/13): libXmu-1.1.1-2.el6.x86_64.rpm | 65 kB 00:00 (6/13): libXxf86dga-1.1.3-2.el6.x86_64.rpm | 24 kB 00:00 (7/13): libXxf86misc-1.0.3-4.el6.x86_64.rpm | 17 kB 00:00 (8/13): libaio-devel-0.3.107-10.el6.x86_64.rpm | 13 kB 00:00 (9/13): libdmx-1.1.2-2.el6.x86_64.rpm | 20 kB 00:00 (10/13): libstdc++-devel-4.4.7-4.el6.x86_64.rpm | 1.6 MB 00:00 (11/13): oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64.rpm | 15 kB 00:00 (12/13): xorg-x11-utils-7.5-6.el6.x86_64.rpm | 94 kB 00:00 (13/13): xorg-x11-xauth-1.0.2-7.1.el6.x86_64.rpm | 34 kB 00:00 ---------------------------------------------------------------------------------------------------------------------------------------- Total 1.9 MB/s | 7.5 MB 00:03 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : libstdc++-devel-4.4.7-4.el6.x86_64 1/13 Installing : gcc-c++-4.4.7-4.el6.x86_64 2/13 Installing : libXmu-1.1.1-2.el6.x86_64 3/13 Installing : 1:xorg-x11-xauth-1.0.2-7.1.el6.x86_64 4/13 Installing : libdmx-1.1.2-2.el6.x86_64 5/13 Installing : ksh-20120801-10.el6_5.9.x86_64 6/13 Installing : libXxf86dga-1.1.3-2.el6.x86_64 7/13 Installing : compat-libstdc++-33-3.2.3-69.el6.x86_64 8/13 Installing : libXxf86misc-1.0.3-4.el6.x86_64 9/13 Installing : xorg-x11-utils-7.5-6.el6.x86_64 10/13 Installing : libaio-devel-0.3.107-10.el6.x86_64 11/13 Installing : compat-libcap1-1.10-1.x86_64 12/13 Installing : oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 13/13 Verifying : compat-libcap1-1.10-1.x86_64 1/13 Verifying : libstdc++-devel-4.4.7-4.el6.x86_64 2/13 Verifying : xorg-x11-utils-7.5-6.el6.x86_64 3/13 Verifying : oracle-rdbms-server-12cR1-preinstall-1.0-11.el6.x86_64 4/13 Verifying : libaio-devel-0.3.107-10.el6.x86_64 5/13 Verifying : libXxf86misc-1.0.3-4.el6.x86_64 6/13 Verifying : compat-libstdc++-33-3.2.3-69.el6.x86_64 7/13 Verifying : libXxf86dga-1.1.3-2.el6.x86_64 8/13 Verifying : 1:xorg-x11-xauth-1.0.2-7.1.el6.x86_64 9/13 Verifying : ksh-20120801-10.el6_5.9.x86_64 10/13 Verifying : libdmx-1.1.2-2.el6.x86_64 11/13 Verifying : gcc-c++-4.4.7-4.el6.x86_64 12/13 Verifying : libXmu-1.1.1-2.el6.x86_64 13/13 Installed: oracle-rdbms-server-12cR1-preinstall.x86_64 0:1.0-11.el6 Dependency Installed: compat-libcap1.x86_64 0:1.10-1 compat-libstdc++-33.x86_64 0:3.2.3-69.el6 gcc-c++.x86_64 0:4.4.7-4.el6 ksh.x86_64 0:20120801-10.el6_5.9 libXmu.x86_64 0:1.1.1-2.el6 libXxf86dga.x86_64 0:1.1.3-2.el6 libXxf86misc.x86_64 0:1.0.3-4.el6 libaio-devel.x86_64 0:0.3.107-10.el6 libdmx.x86_64 0:1.1.2-2.el6 libstdc++-devel.x86_64 0:4.4.7-4.el6 xorg-x11-utils.x86_64 0:7.5-6.el6 xorg-x11-xauth.x86_64 1:1.0.2-7.1.el6 Complete! #
Oracle PreInstall RPM for Oracle Linux is one the biggest benefits of adopting Oracle Linux. With a single command, you can pre-configure the Oracle Linux environment for OEM 12c Agent, EBS R12, and Oracle Database 11gR2/12c installations. Not only does Oracle configure the Linux environment, but many of the best practices are incorporated in the process.
Oracle provides the PreInstall RPMs for the database on different channels from the EBS R12 or OEM 12c Agent PreInstall RPMs. For EBS and OEM 12c Agent PreInstall RPMs, you can download the PreInstall RPMs from the addons channel from the public-yum repository. Oracle provides a separate RPM for each release of OEM 12c.
For Oracle Database PreInstall RPMs for Oracle Database 11g Release 2 and Oracle Database 12c Release 1, you can download them from the RPM from the latest channel from the public-yum repository. You will have to scroll down quite a bit; the RPMs that start with capital letters are listed above RPMs that have lower case letters.
The location of the source RPM (.src.rpm) can be especially important for Red Hat customers who want to leverage all the hard work that Oracle has put in. Red Hat customers can download the source RPM and build their own RPM package that will work on Red Hat with the rpmbuild command.
First, download the software from OTN and unzip the contents of the zip file. Change your directory to the Disk1 subdirectory and launch the GUI installer by invoking the runInstaller script:
$ unzip 121210_fbo_ggs_Linux_x64_shiphome.zip $ cd fbo_ggs_Linux_x64_shiphome/Disk1 $ ./runInstaller
Choose wether you want to install GoldenGate for Oracle Database 12c or Oracle Database 11g. In our example, we are choosing to install GoldenGate for Oracle Database 12c
Specify the location for the GoldenGate software to be installed. Make sure the Start Manager checkbox is not checked. Click on the Next button to continue.
On the summary screen, review the options and installation details. We can create a response file so that we can perform subsequent GoldenGate installations in a silent mode (from the command line interface).
By default, a response file called oggcore.rsp will be saved in the home directory for Oracle. Once the response file is created, we can proceed with the installation by clicking on the Install button. You can view the progress of the installation. When the installation completes, you will see the Finish screen.
Congratulations. We have successfully installed GoldenGate 12c. Click on the Close button to clear the screen.
Now that we’ve installed GoldenGate on the primary source database server, it is time to install GoldenGate on the target database server.
Oracle Database 12c Release 1 Patchset 1 is the terminal release for Oracle 12.1. As of Oracle OpenWorld 2014, the announcement was made that 220.127.116.11 will be the terminal release for Oracle Database 12c Release 1. Oracle also notified customers that the 12c Release 2 (12.2) will not be available until the first quarter of 2016. With that in mind, customers are encouraged to jump on the terminal release of Oracle Database 12 release 1.
In this blog post, I will focus on installing and configuring Oracle Database 12c Release 1 Patchset 1.
Select the option that you want to install and click on Next. In my example, I am selecting to install and configure Oracle Grid Infrastructure for a standalone server.
Select the languages that you want to install and click on the Next button
In the Create ASM Disk Group screen, we will create a disk group called DATA. We will also:
* Click on the External Redundancy option
* Change the Allocation Unit size from 1MB to 4MB
* Select all the disks that make up the DATA Disk Group. ORCL:DATA1 to ORCL:DATA4
When we customized all the options, we will click on the Next button
Enter the password for the SYS and ASMSNMP accounts. In our example, we will choose to enter the same password for both of the accounts. Click on the Next button to continue.
The password that was entered did not conform to the Oracle recommended standards. We will choose to continue by clicking on the Yes button.
We do not have an OEM 12c Cloud Control environment setup yet so we will continue by clicking on the Next button.
Choose the OS Groups for the ASM administrator, ASM DBA, and ASM Operator. In our example, we chose to stick with one standard group since we do not have a separation of roles and responsibilities between the DBA and Cluster administrator.
Click on Yes to continue
If this is a fresh install, you will want to create the directories for $ORACLE_BASE on the /u01 file system and change the permissions to oracle:dba:
[root@vna01 u01]# mkdir -p /u01/app/oracle [root@vna01 u01]# chown -R oracle:dba /u01/app
Click on Next to continue
Set the path for the oraInventory location. The default location is good for most customers. Click on Next to continue.
The default location for sudo is in /usr/bin directory. For this screen, you will want to change the location of sudo to be /usr/bin/sudo instead of /usr/local/bin/sudo.
If you are new to the world of sudo, you can make a simple change in the /etc/sudoers file and add the following line:
oracle ALL=(ALL) ALL
This example is not encouraged. Most companies with strict sudoers control will list just the commands that the oracle user can execute on behalf of root.
Click on the next button to continue.
We seem to have an issue with a kernel parameter called panic_on_oops. This parameter is not set in the /etc/sysctl.conf parameter file. For now, we will choose to ignore this warning and continue with the installation. Let’s continue by clicking on the Ignore All checkbox on the top right corner of the window; then click on the Next button to continue.
We will see an warning message indicating that we’ve chosen to ignore one or more of the prerequisites. Click on the Yes button to continue.
Finally, we arrive at the Summary screen. Before we click on the Installation button, we will choose the option to save the response file by clicking on the Save Response File button. Carefully review the options that you have chosen and click on the Install button.
We can watch the installation progress. You can click on the Details button if you want to see some of the detailed logs of what is happening.
Once the installation is complete, you will be prompted to auto execute the configuration script. Click on Yes to continue to execute orainstRoot.sh and root.sh as the root user or as the sudo privileged user.
Congrats! We have successfully installed Oracle 12c Release 1 Patchset 1 Grid Infrastructure. Next, we will proceed with installing and configuring the Oracle 12c Release 1 Patchset 1 Database software.
Install Oracle Database Software
[oracle@vna01 database]$ ./runInstaller Starting Oracle Universal Installer... Checking Temp space: must be greater than 500 MB. Actual 29712 MB Passed Checking swap space: must be greater than 150 MB. Actual 31992 MB Passed Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-10-05_03-07-31AM. Please wait ...[oracle@vna01 database]$
Uncheck the option for receiving security updates via Oracle Support
Click on the Next button to continue
Click on the Yes button and confirm that you have chosen to remain uninformed of critical security updates
Click on the Install database software only option and click on the Next button to continue. We will create a database later with the Database Configuration Assistant (dbca).
Click on the Single instance database installation option and click on Next button to continue
Select the languages that you want to install and click on the Next button to continue
At the initial release of Oracle Database 12c Release 1 Patchset 1, only the Enterprise Edition was available. Standard Edition or Standard Edition One is not available as an option yet.
Accept the default location for $ORACLE_BASE and $ORACLE_HOME since we have already installed the Grid Infrastructure and click on the Next button to continue.
Select the OS groups for OSDBA, OSOPER, OSBACKUPDBA, OSDGDBA and OSKMDBA and click on the Next button to continue.
We are at the Summary screen. Before we click on the Install button, we will choose the option to save the response file by clicking on the Save Response File button. Carefully review the options that you have chosen and click on the Install button.
We can watch the installation progress. You can click on the Details button if you want to see some of the detailed logs of what is happening.
As the root account, execute root.sh from the Database Oracle Home.
[oracle@vna01 dbhome_1]$ sudo ./root.sh [sudo] password for oracle: Performing root user operation. The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /u01/app/oracle/product/12.1.0/dbhome_1 Enter the full pathname of the local bin directory: [/usr/local/bin]: The contents of "dbhome" have not changed. No need to overwrite. The contents of "oraenv" have not changed. No need to overwrite. The contents of "coraenv" have not changed. No need to overwrite. Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root script. Now product-specific root actions will be performed.
After root.sh is successfully executed, go back to the Execute Configuration Script window and click on the OK button.
Click on the Close button to complete the database software installation
Create the Fast Recovery Area (FRA)
Launch the ASM Configuration Assistant (asmca). Before we launch asmca, we need to source the oraenv file and setup the Linux environment for ASM.
[oracle@vna01 Desktop]$ . oraenv ORACLE_SID = [oracle] ? +ASM The Oracle base has been set to /u01/app/oracle [oracle@vna01 Desktop]$ asmca
Click on the Create button to create the FRA disk group.
From the Create Disk Group screen, enter FRA for the Disk Group Name and select the option for the External redundancy. Click on the Show Advanced Options and change the Allocation Unit Size (MB) from 1MB to 4MB.
If we know for a fact that only 12.1 databases will ever go on this ASM instance, we can advance the Database Compatibility and ADVM Compatibility to 18.104.22.168.0 also. We will click on the OK button to complete the FRA disk group creation.
While the disk group is being created, you will see the above progress window.
We successfully created the FRA disk group. Click on the Close button to exit the screen and click on the Exit button to cleanly exit asmca.
Create a Database with dbca (using an existing Oracle seeded database template)
We need to launch the Database Configuration Assistant (dbca). Before we launch dbca, we need to source the oraenv file and setup the Oracle environment.
[oracle@vna01 dbhome_1]$ pwd /u01/app/oracle/product/12.1.0/dbhome_1 [oracle@vna01 dbhome_1]$ . oraenv ORACLE_SID = [oracle] ? db ORACLE_HOME = [/home/oracle] ? /u01/app/oracle/product/12.1.0/dbhome_1 The Oracle base has been set to /u01/app/oracle [oracle@vna01 dbhome_1]$ [oracle@vna01 dbhome_1]$ dbca
Select the Create Database option and click on the Next button to continue
Enter the database name and select the disk group location for the database files and fast recovery area. Choose the database character set for the database and enter the administrator password. You can choose the create the database as a Container Database (default). You can enter the name for the pluggable database name. Click on the Next button to continue.
We receive a warning message because the administrative password does not conform to the recommended Oracle standards. Click on the Yes button to continue.
From the Summary screen, review the options that were chosen and click on the Finish button.
We can review the database creation progress. In the meanwhile, we can also view the Activity Log or the Alert Log.
Create a Customized Database with dbca Advanced Mode
Oracle GoldenGate provides a variety of tools and resources that help companies build robust replication solutions. Numerous “best practices” white papers are available for download via My Oracle Support (MOS).
Oracle GoldenGate customers are encouraged to review the available documents for considerations explicit to their operating environments. For example, the following papers are especially useful when deploying Oracle GoldenGate in an Oracle Database environment:
* Database specific bundle patch for Integrated Extract 11.2.x (Doc ID 1411356.1)
* Oracle GoldenGate Best Practices: Instantiation from an Oracle Source Database (Doc ID 1276058.1)
* Oracle GoldenGate Best Practice: NFS Mount options for use with GoldenGate (Doc ID 1232303.1)
* Oracle GoldenGate Best Practices: Oracle GoldenGate high availability using Oracle Clusterware (Doc ID 1313703.1)
* Oracle GoldenGate Best Practice – sample parameter files (Doc ID 1321696.1)
vncserver is a wrapper script for Xvnc, the free X server for VNC (Virtual Network Computing). It provides all capabilities of a standard X server, but does not connect to a display for itself. Instead, Xvnc creates a virtual desktop you can view or control remotely using a VNC viewer.
I was recently asked by a DBA colleague about leveraging VNC Server for installations/upgrades, and if they should incorporate it as part of their infrastructure. Even though VNC Server as a whole is not considered to be secure, DBAs prefer to leverage this technology for Oracle installation and upgrades. DBAs prefer VNC Server technology over the traditional X Windows on the local desktop/laptop, as the Oracle installation/upgrade will proceed significantly faster. DBAs also prefer VNC as network glitches does not cause the install/upgrade to fail. If the network fails during the installation/upgrades, we can simply re-connect to the VNC Server and continue where we left off. If the network fails during the file copies, all we lose is the display and can continue to see the progress. You can install the VNC Server with the yum install command. In the example shown below, we are installing the tightvnc-server RPM on Oracle Linux 6.5:
[oracle@vna01 ~]$ yum install tigervnc-server Loaded plugins: security You need to be root to perform this command. [oracle@vna01 ~]$ su - Password: [root@vna01 ~]# yum install tigervnc-server Loaded plugins: security ol6_UEK_latest | 1.2 kB 00:00 ol6_latest | 1.4 kB 00:00 ol6_latest/primary | 41 MB 00:35 ol6_latest 26208/26208 ol6_u4_base | 1.4 kB 00:00 Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package tigervnc-server.x86_64 0:1.1.0-8.el6_5 will be installed --> Processing Dependency: xorg-x11-xkb-utils for package: tigervnc-server-1.1.0-8.el6_5.x86_64 --> Processing Dependency: xkeyboard-config for package: tigervnc-server-1.1.0-8.el6_5.x86_64 --> Processing Dependency: xorg-x11-fonts-misc for package: tigervnc-server-1.1.0-8.el6_5.x86_64 --> Processing Dependency: libXdmcp.so.6()(64bit) for package: tigervnc-server-1.1.0-8.el6_5.x86_64 --> Running transaction check ---> Package libXdmcp.x86_64 0:1.1.1-3.el6 will be installed ---> Package xkeyboard-config.noarch 0:2.6-6.0.1.el6 will be installed ---> Package xorg-x11-fonts-misc.noarch 0:7.2-9.1.el6 will be installed ---> Package xorg-x11-xkb-utils.x86_64 0:7.7-4.el6 will be installed --> Processing Dependency: libxkbfile.so.1()(64bit) for package: xorg-x11-xkb-utils-7.7-4.el6.x86_64 --> Running transaction check ---> Package libxkbfile.x86_64 0:1.0.6-1.1.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ========================================================================================================================================= Package Arch Version Repository Size ========================================================================================================================================= Installing: tigervnc-server x86_64 1.1.0-8.el6_5 ol6_latest 1.1 M Installing for dependencies: libXdmcp x86_64 1.1.1-3.el6 ol6_latest 30 k libxkbfile x86_64 1.0.6-1.1.el6 ol6_latest 74 k xkeyboard-config noarch 2.6-6.0.1.el6 ol6_latest 710 k xorg-x11-fonts-misc noarch 7.2-9.1.el6 ol6_latest 5.8 M xorg-x11-xkb-utils x86_64 7.7-4.el6 ol6_latest 86 k Transaction Summary ========================================================================================================================================= Install 6 Package(s) Total download size: 7.8 M Installed size: 15 M Is this ok [y/N]: y Downloading Packages: (1/6): libXdmcp-1.1.1-3.el6.x86_64.rpm | 30 kB 00:00 (2/6): libxkbfile-1.0.6-1.1.el6.x86_64.rpm | 74 kB 00:00 (3/6): tigervnc-server-1.1.0-8.el6_5.x86_64.rpm | 1.1 MB 00:00 (4/6): xkeyboard-config-2.6-6.0.1.el6.noarch.rpm | 710 kB 00:00 (5/6): xorg-x11-fonts-misc-7.2-9.1.el6.noarch.rpm | 5.8 MB 00:05 (6/6): xorg-x11-xkb-utils-7.7-4.el6.x86_64.rpm | 86 kB 00:00 ----------------------------------------------------------------------------------------------------------------------------------------- Total 956 kB/s | 7.8 MB 00:08 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : xorg-x11-fonts-misc-7.2-9.1.el6.noarch 1/6 Installing : xkeyboard-config-2.6-6.0.1.el6.noarch 2/6 Installing : libxkbfile-1.0.6-1.1.el6.x86_64 3/6 Installing : xorg-x11-xkb-utils-7.7-4.el6.x86_64 4/6 Installing : libXdmcp-1.1.1-3.el6.x86_64 5/6 Installing : tigervnc-server-1.1.0-8.el6_5.x86_64 6/6 Verifying : libXdmcp-1.1.1-3.el6.x86_64 1/6 Verifying : xorg-x11-xkb-utils-7.7-4.el6.x86_64 2/6 Verifying : libxkbfile-1.0.6-1.1.el6.x86_64 3/6 Verifying : xkeyboard-config-2.6-6.0.1.el6.noarch 4/6 Verifying : xorg-x11-fonts-misc-7.2-9.1.el6.noarch 5/6 Verifying : tigervnc-server-1.1.0-8.el6_5.x86_64 6/6 Installed: tigervnc-server.x86_64 0:1.1.0-8.el6_5 Dependency Installed: libXdmcp.x86_64 0:1.1.1-3.el6 libxkbfile.x86_64 0:1.0.6-1.1.el6 xkeyboard-config.noarch 0:2.6-6.0.1.el6 xorg-x11-fonts-misc.noarch 0:7.2-9.1.el6 xorg-x11-xkb-utils.x86_64 0:7.7-4.el6 Complete!
Now that the VNC Server is installed, let’s configure the VNC Server to auto start a reboot. It is very important for me to note that we do NOT want to do this for the production database servers. We configure the VNC Server to auto-start by modifying the /etc/sysconfig/vncservers file and add the following 2 lines for oracle:
VNCSERVERS="3:oracle" VNCSERVERARGS="-geometry 1280x1024"
To enable the vncserver service to autostart, we have to execute the chkconfig command:
chkconfig vncserver on
Before we start the vncserver, we need to establish a VNC password for the oracle account. Switch user to oracle and execute the vncpasswd command:
# su - oracle $ vncpasswd oracle Password: Verify:
Log back in as the root account and start the vncserver with the “service vncserver start” command.
[root@vna01 ~]# service vncserver start Starting VNC server: 3:oracle xauth: creating new authority file /home/oracle/.Xauthority New 'vna01:3 (oracle)' desktop is vna01:3 Creating default startup script /home/oracle/.vnc/xstartup Starting applications specified in /home/oracle/.vnc/xstartup Log file is /home/oracle/.vnc/vna01:3.log [ OK ]
With any VNC Viewer, you should be able to access the VNC Server. Since I am on a Mac, I am using a freeware/shareware called Chicken of the VNC. Notice that I am leveraging :3 as my display port since I setup the “VNCSERVERS=”3:oracle” in my /etc/sysconfig/vncservers file.
To demonstrate how we can maintain the vncserver as the oracle user, we are going to kill the currently running vncserver process and re-start it. To kill the vncserver, we pass the -kill parameter to the vncserver executable. We also provide the display number to kill parameter as shown in the example below:
[oracle@vna01 ~]$ ps -ef |grep vnc oracle 5954 1 0 11:06 ? 00:00:00 /usr/bin/Xvnc :3 -desktop vna01:3 (oracle) -auth /home/oracle/.Xauthority -geometry 1280x1024 -rfbwait 30000 -rfbauth /home/oracle/.vnc/passwd -rfbport 5903 -fp catalogue:/etc/X11/fontpath.d -pn oracle 5960 1 0 11:06 ? 00:00:00 vncconfig -iconic oracle 5999 5972 0 11:10 pts/0 00:00:00 grep vnc [oracle@vna01 ~]$ vncserver ^C [oracle@vna01 ~]$ man vncserver [oracle@vna01 ~]$ vncserver -kill :3 Killing Xvnc process ID 5954
We can also start a vncserver manually as the oracle user account. To start a vncserver process on display port 3, we pass the :3 parameter:
[oracle@vna01 ~]$ vncserver :3 New 'vna01:3 (oracle)' desktop is vna01:3 Starting applications specified in /home/oracle/.vnc/xstartup Log file is /home/oracle/.vnc/vna01:3.log
When we executed the vncpasswd command, a subdirectory was created under the $HOME directory called .vnc. In this subdirectory, there are several files. The passwd file is the encrypted password for the VNC Server.
[oracle@vna01 .vnc]$ ls -ltr total 16 -rw------- 1 oracle oinstall 8 Oct 4 11:06 passwd -rwxr-xr-x 1 oracle oinstall 654 Oct 4 11:06 xstartup -rw-r--r-- 1 oracle oinstall 5 Oct 4 11:13 vna01:3.pid -rw-r--r-- 1 oracle oinstall 1531 Oct 4 11:13 vna01:3.log
The xstartup file contains all the parameters for the vncserver process.
When to leverage VNC Server
We strongly discourage installing VNC Server on any production servers. Nonetheless, for Oracle installations and upgrades, we often need access to a X Server to set our GUI display to. We can leverage a remote VNC Server on a needed basis. As a temporary solution, we can start a vncserverprocess on another server when we need it and kill the processes when we are done with the install/upgrade. To set the display from the production database server to the remote VNC server, we simply set the DISPLAY parameter to the hostname:DISPLAY port. In our example, the name of our VNC Server was on vna01 and we are listening on DISPLAY port 3 so we will setup our DISPLAY parameter to be:
I had the pleasure of being involved in couple of Exadata implementations where Oracle delivered the wrong ASM redundancy type to a customer. The customer expected single mirroring (normal redundancy) and lot more TBs of useable storage than what was delivered. I have a general rule; if you have to do it more than once, you better script it and automate it. Check out the script the I used to migrate an Exadata customer from high redundancy to normal redundancy.
define DG='&1' set pages 0 set lines 200 trims on feed off echo off echo off ver off spool cr_&DG..sql prompt CREATE DISKGROUP &DG NORMAL REDUNDANCY set serveroutput on size unlimited declare v_failgroup v$asm_disk.failgroup%TYPE; cursor c1 is select chr(39)||path||chr(39) path, name from v$asm_disk where group_number = (select group_number from v$asm_diskgroup where name=upper('&DG')) and failgroup=v_failgroup order by path; cursor c2 is select distinct failgroup from v$asm_disk order by failgroup; cursor c3 is select allocation_unit_size, compatibility, database_compatibility from v$asm_diskgroup; r3 c3%ROWTYPE; begin for r2 in c2 loop v_failgroup := r2.failgroup; dbms_output.put_line('FAILGROUP '||r2.failgroup||' DISK'); for r1 in c1 loop if c1%rowcount = 1 then dbms_output.put_line(r1.path); else dbms_output.put_line(','||r1.path); end if; end loop; end loop; open c3; fetch c3 into r3; dbms_output.put_line('ATTRIBUTE'); dbms_output.put_line(chr(39)||'compatible.asm'||chr(39)||'='||chr(39)||r3.compatibility||chr(39)||','); dbms_output.put_line(chr(39)||'compatible.rdbms'||chr(39)||'='||chr(39)||r3.database_compatibility||chr(39)||','); dbms_output.put_line(chr(39)||'au_size'||chr(39)||'='||chr(39)||r3.allocation_unit_size||chr(39)||','); dbms_output.put_line(chr(39)||'cell.smart_scan_capable'||chr(39)||'='||chr(39)||'TRUE'||chr(39)||';'); close c3; end; / spool off
Here’s a sample of the generated script for the DATA disk group.
CREATE DISKGROUP DATA_EXAD NORMAL REDUNDANCY FAILGROUP EXADCEL01 DISK 'o/10.0.0.3/DATA_EXAD_CD_00_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_01_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_02_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_03_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_04_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_05_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_06_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_07_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_08_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_09_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_10_exadcel01', 'o/10.0.0.3/DATA_EXAD_CD_11_exadcel01' FAILGROUP EXADCEL02 DISK 'o/10.0.0.4/DATA_EXAD_CD_00_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_01_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_02_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_03_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_04_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_05_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_06_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_07_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_08_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_09_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_10_exadcel02', 'o/10.0.0.4/DATA_EXAD_CD_11_exadcel02' FAILGROUP EXADCEL03 DISK 'o/10.0.0.5/DATA_EXAD_CD_00_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_01_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_02_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_03_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_04_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_05_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_06_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_07_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_08_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_09_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_10_exadcel03', 'o/10.0.0.5/DATA_EXAD_CD_11_exadcel03' ATTRIBUTE 'compatible.asm'='22.214.171.124', 'compatible.rdbms'='126.96.36.199', 'au_size'='4M', 'cell.smart_scan_capable'='TRUE';
“Docker is an open platform for developers and sysadmins to build, ship, and run distributed applications. Consisting of Docker Engine, a portable, lightweight runtime and packaging tool, and Docker Hub, a cloud service for sharing applications and automating workflows, Docker enables apps to be quickly assembled from components and eliminates the friction between development, QA, and production environments. As a result, IT can ship faster and run the same app, unchanged, on laptops, data center VMs, and any cloud.” For additional information about Docker, please visit the Docker website.
Oracle has made it clear that the support for Docker in Oracle Linux 6 and 7 is limited at this time. Please refer to the Doc ID – 1921163.1: Limited Support for Docker Running on Oracle Linux Announced: Docker in Addons Channel Now
- Oracle support is limited to the version of Docker built by and downloaded from Oracle. Support is not provided for the upstream binary packages downloaded from the upstream Docker site.
- Oracle support for Docker is limited to customers with either Basic or Premier Oracle Linux Support Subscriptions.
- Oracle only provides Docker server binary packages for Oracle Linux 6 and Oracle Linux 7 (x86_64).
- Oracle support is limited to severity 2 service requests and lower. Severity 1 service requests will not be accepted for Docker.
- Support is limited to assistance with the initial installation of Docker and subsequent configuration of Docker to enable downloading, creation and running of Dockerized applications.
- Use of the btrfs storage engine is only supported on the Unbreakable Enterprise Kernel Release 3 on both Oracle Linux 6 and Oracle Linux 7.
- Oracle Linux support does not include support for any Oracle or 3rd-party applications running within a Docker container on Oracle Linux.
- Oracle will periodically release updates from the upstream project in the addons channel. Interim patching and bug fixing will not be available.
This blog article focuses on configuring VirtualBox to create a new VM for Oracle Linux 7 and installing Oracle Linux 7 from the ISO image as a guest operating system. The Oracle Linux 7 ISO image can be downloaded from edelivery.oracle.com – Oracle Software Delivery Cloud. You must have a valid Oracle Account (free) to download the Linux ISO.
Look in the near future for a VMware Fusion and RedHat 7 version of this post. For some reason when this post went out, the latest version of VMware Fusion did not recognize the virtual disk or the network interface assigned to the VM with RedHat 7 (Oracle Linux 7 worked fine). Stay tuned as that problem will probably be resolved soon.
As far as this blog post is concerned, the follow-up for this post will be on setting up docker for Oracle Linux 6 and Oracle Linux 7.
To create a VM, click on the New button on the top left corner and provide a descriptive name for the VM, location of the VM and select the type of OS. The name that is specified will be used to identify the VM configuration:
On a side note, here’s the list of flavors of Linux supported by VirtualBox. We will choose Oracle (64Bit) for this VM.
Once the required information is provided, click on the Continue button
Next configure the amount of memory allocated for this VM. We will allocate 4GB for this VM and click on the Continue button.
We can modify the virtual disk in another screen later in the configuration process. Take the default and click on the Continue button go to the “Hard drive file type” screen.
Unless you are planning for this virtual disk to be compatible with VMware or other virtualization technology, select the VDI (VirtualBox disk format) and click on the Continue button.
Leave the Dynamically allocated option to choose a thinly provisioned virtual disk. If you want better performance for RAC ASM disks, you can choose the option for Fixed size. For the Fixed size disk, VirtualBox will pre-allocate all the space up front. Click on the Continue button to proceed with the configuration.
For this installation, we will allocate 64GB for the root and /u01 file systems. You may opt to create multiple virtual disks, one for the root file system and another one for the /u01 file system. Click on Create. If you chose earlier for Fixed size, when you click on the Create button, you will be waiting here for a while.
Once the VDI disk is created with the specified size (thin for dynamically allocated or thick for fixed size provisioned), you will be re-directed back to the main screen.
Now, let’s configure our VM, in particular, the CD/DVD Drive. Click on the Settings button on the top left corner next to the New button.
Click on the Storage button on the top (in the middle). On the left side of the screen, choose the IDE controller and Click on the Empty CD icon. Then on the right of the screen, click on the CD image icon for the CD/DVD drive and click on the “Choose a virtual CD/DVD disk file …”. Find your ISO image for Oracle Linux 7 from the file previewer and select the ISO. From the Storage screen, click on the OK button to go back to the main Oracle VM VirtualBox Manager screen.
Installing Oracle Linux 7
From the Oralce VM VirtualBox Manager screen, select your VM that you just created and click on the green Start icon on the top of the screen.
Hit the arrow key up once and choose the option to Install Oracle Linux 7 and hit the Enter key
Keep the default English language for United States and click on Continue
As you can see, the installation process looks significantly different from Oracle Linux 6. Click on the INSTALLATION DESTINATION button.
Select the “I will configure partitioning.” radio button and click on the Done button on the top left hand corner.
In the MANUAL PARTITIONING screen, click on the “Click here to create them automatically” URL.
In our example, we will remove the /home file system and just let the root file system house all the file systems, /home and /u01. To remove the /home file system, click on the /home file system and click on the – sign on the bottom corner of the screen.
CAVEAT: You do NOT want to do this outside your lab. Even in your DEV or non-PROD environment, you will want to carve out a separate file system for the /home file system. You ALWAYS want to carve out a separate /u01 file system for all your Oracle binaries. Click on the Done button on the top left corner.
* Notice that the default file system is XFS (not EXT4 in Oracle or RedHat Linux 6)
You will be presented with a warning screen just to confirm and Accept the Changes that we made to remove the /home file system. Click on the Accept Changes button.
You will be routed back to the main Installation Summary screen. By default, the minimal installation option is the installation method of choice for Oracle and Red Hat Linux. If you want a GUI installation, you will want to select the SOFTWARE SELECTION button and choose the KDE desktop. For security purposes, we only recommend the minimal installation option.
To configure the network and hostname, you should click on the NETWORK & HOSTNAME button. The first thing that you need to do is the specify a new Hostname on the bottom left corner.
Turn on the Network interface by sliding the switch to the on position.
In our case, we will want to assign a static IP address and DNS Servers. Click on the Configure button on the bottom right corner.
Add all the specifics for your IP address, gateway, subnet and DNS servers. Click on the Save button to save the network settings. You will be re-directed to the NETWORK & HOSTNAME screen. Click on the Done button to go back to the INSTALLATION SUMMARY screen.
Optionally, you may want to choose to install a GUI desktop. This is never recommended for a production environment. For ease of maintenance, you can click on the SOFTWARE SELECTION button and choose to install a “Server with GUI” option and choose the KDE desktop. Click on the Done button after you select all the options that you want installed.
Once all the configuration is complete, you can click on the Begin Installation button.
As the installation is progressing, you will see 2 red warnings indicating that the root password is not set and no users are created. At a minimum, click on the Root Password icon to supply a password for the root account to administer the system. Provide the secure password and click on the Done button on the top left corner.
Note: If the root password is insecure, you will be prompted to click on the Done button again to proceed with the insecure password.
From the Configuration screen, click on the Reboot button.
Once the VM reboots, you will be directed to the login prompt. Since we did a bare minimal installation, we will not enter into a GUI mode.
Once we login, we can check /etc/oracle-release file and confirm that we are running an Oracle Linux Server 7 distribution of Linux.
Chose KDE GUI DESKTOP
If you chose the GUI Desktop option earlier, when the system reboots, you will be directed to perform the initial setup.
Click on the LICENSE INFORMATION icon
Click on the checkbox to accept the license agreement and click on the Done button on the top left corner. You will be re-directed to the INITIAL SETUP screen. Click on the FINISH CONFIGURATION button to proceed.
For a production environment, you will always want to enable KDUMP for system crash debugging. Click on the Forward button on the bottom right to continue.
You can configure your system for software updates by providing credentials to Oracle’s Unbreakable Linux Network. We do not want to setup our system for software updates at this time. Click on the Forward button on the bottom right to continue.
Click on the button “No thanks, I’ll connect later.”
Click on the Forward button again
Select English (United States) and Click on Next
Click on English (US) and Click on Next
You will need to create a local account and click on Next
Choose your location from the big list of cities and click on Next
For Oracle installations, we do not care for online accounts. You can skip this step and click on the Next button to proceed.
Click on the “Start using Oracle Linux Server” button and enjoy the GUI desktop.
Posted by Charles Kim, Oracle ACE Director
Lot of our customers seem to be confused about the licensing of Oracle management packs. As we install and configure OEM for our customers, we tell them to be careful to leverage only the features that they are licensed for. To clarify for our customers and others, I decided to detail out when you need to pay for certain licenses and what you are allowed to execute for free if you do not want to pay (or cannot afford to pay) for licenses of Oracle management packs. To start, here’s what you are allowed to monitor without paying for licenses:
• OS statistics
• Optimizer statistics
• SQL Traces
• SQL statistics
• Service statistics
• System statistics
• Time model
• Wait model
Starting in Oracle Database 11g, you can cautiously leverage the CONTROL_MANAGEMENT_PACK_ACCESS initialization parameter to control access or disable the packs. This parameters accepts the following parameters:
In Oracle 12c Release 1 (12.1), the default value for the CONTROL_MANAGEMENT_PACK_ACCESS parameter for Oracle Enterprise Edition is “DIAGNOSTIC+TUNING”. For Standard edition, the default value is set to NONE.
Nowadays, most of Oracle Sales folks are trained to sell the Diagnostic and Tuning pack as part of every database. You should expect this from experienced Oracle Sales folks. You may even get a response for a sales person indicating how can you successfully support or maintain a business critical database without leveraging these features.
Let’s continue our discussion to talk about the Database Diagnostic Pack. Usage of the following feature require licensing the Database Diagnostics Pack:
• Active Session History (ASH)
• Automatic Database Diagnostic Monitor (ADDM)
• Automatic Workload Repository
• Dynamic metric baselines
• Event history and metric history (database and host)
• Event notifications: notification methods, rules, and schedules
• Monitoring templates
• Performance monitoring (database and host)
You will also have to pay for the database diagnostic pack if you leverage any of the following database stored procedures and packages:
If you leverage the following view, you will also end up paying for the diagnostic pack:
• V$ACTIVE_SESSION_HISTORY view
• Views with DBA_ADVISOR_ prefix
• Views with DBA_ADDM_ prefix
• Views with DBA_HIST_ prefix
If you leverage any of the SQL scripts from the $ORACLE_HOME/rdbms/admin directory, you will be liable for the diagnostic pack:
Usage of the following feature require the Database Tuning Pack:
• Automatic Plan Evolution of SQL Plan Management
• Automatic SQL Tuning
• Reorganize objects
• SQL Access Advisor
• SQL Monitoring
• SQL Profiles
• SQL Tuning Advisor
• SQL Tuning Sets
The Tuning Pack has a direct dependency on the Diagnostic Pack. Stated in another way, if you license the Tuning Pack, you will have to also license the Diagnostic Pack.
Similarly, the usage of any of the stored procedures or packages, views or SQL scripts will incur license of the Database Tuning Pack:
• DBMS_ADVISOR package
• DBMS_SQLTUNE package
• V$SQL_MONITOR view
• V$SQL_PLAN_MONITOR view
• sqltrpt.sql report found in the $ORACLE_HOME/rdbms/admin/ directory
Usage of the following feature require the Database Configuration Management Pack:
• Clone Database
• Clone Oracle Home
• Compare configuration
• Database and Host Configuration
• Patch Database and View Patch Cache
• Patch staging
• Search configuration
If you are concerned about a potential Oracle license violation or wandering if you may be using a feature/option that you should not be, you can execute the following SQL code against your database and confirm that you have or have not used licensable features or options:
col name for a45 col description for a40 word wrapped col feature_info for a35 set lines 266 set pages 66 select name, description, version, detected_usages, currently_used, first_usage_date, last_usage_date, feature_info from DBA_FEATURE_USAGE_STATISTICS where detected_usages > 0 /