Oracle Weblogic 12c (12.1.1) Generic Installer x64 on CentOS 6

This post will cover installing Oracle Weblogic 12c (12.1.1) Generic Installer x64 (wls1211_generic.jar) on 64 bit CentOS 6 for evaluation.

Before investing any time in this, despite a fresh download you will need,.... a patch: (p13606167_12110_Generic.zip).ﾂ�

I am installing this remotely, if you are doing the same, you can see my post onﾂ�VNC on CentOS 6

If not, the proceedure is identical.

Create a user 'oracle' and group dba.

Oracle recommends JRockit for Production Mode and JDK 1.7 for Development Mode.

Start by making a home for JAVA.

Ill create mine under /usr/java

Download jdk-7u5-linux-x64.tar.gz to the /usr/java directory

Extract it:

This will create a directory, jdk.17.0_05 under /usr/java:

This will be our JAVA_HOME: /usr/java/jdk1.7.0_05

(You can now remove jdk-7u5-linux-x64.tar.gz using rm -f jdk-7u5-linux-x64.tar.gz).

ﾂ�

Add the following to bash profile for user oracle

Make it available now:

Switch to the user oracle and verify that Java is now in the path of oracle by issuing 'java -version'

Make the user oracle the owner:

Download wls1211_generic.jar from either of these locations:

http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html

http://www.oracle.com/technetwork/middleware/weblogic/downloads/index.htm

ﾂ�

Here is the short version:

1. su - oracle

2. Go to the location where you donwnloaded wls1211_generic.jar (I've downloaded it to /home)

3. Issue:ﾂ�

Important: if you do not set PermSize as well as Xmx, your install will fail with Out of Memory errors.

I had a dozen screen shots for all of this but decided in to just make a mp4 and upload it to YouTube.

My apologies for the quality and (lack of) editing of the video; it's my first video using demo-builder.ﾂ�

If you expand the video to full screen mode you will be able to see the terminal (sort of).ﾂ�

ﾂ�

ﾂ�

ﾂ�

ﾂ�

ﾂ�

As you can see from Part II, once we started the domain, we ran into:

WARNING: Input Action on WSDL operation AbortedOperation and @Action on its associated Web Method abortedOperation did not match and will cause problems in dispatching the requests
Jul 22, 2012 6:10:39 AM com.sun.xml.ws.model.JavaMethodImpl freeze

This required us to install p13606167_12110_Generic.zip as shown in the video

In the video, I installed it on offline mode.

To see how to apply in online mode, see:ﾂ�http://weblogic-wonders.com/weblogic/2010/12/03/methods-to-apply-patches-in-weblogic-server/

As shown above, we start the domain by going to the domain's directory and issuing './startWebLogic.sh'

Start it :

I hope this was helpul.....

http://docs.oracle.com/cd/E24329_01/doc.1211/e24492/prepare.htm#BABFIDAB

ﾂ�

Install Oracle 11g Express (XE) on CentOS

This post will cover basic installation and configuration of Oracle 11g Express Edition (XE) on CentOS.

We will also take a quick look at configuring Application Express (APEX) for 11g XE.

Basic installation is straight forward.

If you just want to get up and running, you can just do steps 1 to 4 below (and 10 and 11 for Apex). The remaining steps (5 to 9) cover basic backup, recovery, and performance configuration.

The full system requirements areﾂ�here

Your CentOS box should have swap equal to 2xRAM.

On every CentOS installation I have done for XE, I just needed to update/install the packages for libaio, bc, and flex.

You can download the Oracle XE rpm, oracle-xe-11.2.0-1.0.x86_64.rpm.zip, from the OTNﾂ�here

Unzip oracle-xe-11.2.0-1.0.x86_64.rpm.zip:

This will create the directory Disk1. Change to the Disk1 directory:

Install the rpm using rpm -ivh oracle-xe-11.2.0-1.0.x86_64.rpm

When installation completes, run '/etc/init.d/oracle-xe configure' to configure and start the database.

Unless you wish to change the ports, except the defaults and set SYS/SYSTEM password.ﾂ�

The installation created the directory /u01 under which Oracle XE is installed.

ﾂ�

To set the required Oracle environment variables, use the oracle_env.sh the script included under cd /u01/app/oracle/product/11.2.0/xe/bin

To set the environment for your current session run '. ./oracle_env.sh':

To set the environment permanently for users, add the following to the .bashrc or .bash_profile of the users you want to access the environment:

You should now be able to access SQL*Plus

ﾂ�

To allow remote access to Oracle 11g XE GUI (as well as Application Express GUI) issue the following from SQL*Plus

You should now be able to access the Oracle 11g XE Home Page GUI at:

http://localhost:8080/apex/f?p=4950:1

Replace localhost above with your IP or domain as required.

Log in as SYSTEM using the password you selected in Step 2 above.

ﾂ�

To protect against disk failure, you should move the Flash Recovery Area to a separate disk.

This is actually now called the Fast Recovery Area, but the existing documentation still refers to it as the Flash Recovery Area

If a separate disk is not in your budget you should, at the very least, move the Flash Recovery Area to a partition other than the Oracle installation directory.

By default, the Fast Recovery Area will be located under /u01/app/oracle/fast_recovery_area

So, to move it elsewhere, first create the new directory

Change the owner to oracle and the group to dbaﾂ�

Now, change the DB_RECOVERY_FILE_DEST to the location you selected above.

To move the files use the movelog.sql script:

Now, set an appropriate size for the Fast Recovery Area. Use df -h to insure that there is ample space.

Verify the new location and size.ﾂ�

You should have at least two Redo Log Groups and each group should have at least two members.

Additionally, the members should be spread across disks (or at least directories)

For whatever reason, only one member is created per group on install.

You can view the redo log files using SQL> SELECT * FROM V$LOGFILE;

Since the default location for the two members is the Flash Recovery Area, the two existing members have been moved to our new FRA.

You should now add an additional member for each group under /u01/app/oracle/oradata/XE

ﾂ�

The default values for parameters and sessions is quite low on the default installation.

You can increase these parameters.

After each change, you will need to restart the database.

Increase sessions and then bounce database.

Verify change to sessions parameter:

Increase processes and restart database

Verify change to processes parameter:

ﾂ�

To enable online or "hot" backups, Archivelog Mode must be enabled.

Additionally, if you do not enable Archivelog Mode and take only offline or "cold" backups, should you need to restore the database you will only be able to restore to the last backup

To enable Archivelog Mode, shutdown the database and then startup mount:

Enable Archivelog Mode

Open the database and verify that Archivelog Mode is enabled

ﾂ�

To create automated backups, you can modify the backup.sh included under /u01/app/oracle/product/11.2.0/xe/config/scripts

Create a directory for your backup script

Change the owner to oracle and the group to dbaﾂ�

Copy the backup.sh script from /u01/app/oracle/product/11.2.0/xe/config/scripts to the directory you created above.

Open the backup.sh script in a text editor or vi. The last section will look like this:

Change it to:ﾂ�

The line we added above, mail -s 'Oracle Backup Completed' ' This email address is being protected from spambots. You need JavaScript enabled to view it. ' < /u01/app/oracle/oxe_backup_current.log, will send us an email notification that the backup has completed as well as cat the backup log to the body of the email.

Note that we have also commented out the last two lines of the script (the prompt).ﾂ�

Create a cron job to run the script as user oracle.

You should run it at least once a day. With Archivelog Mode enabled, it is important that backups be taken regularly to prevent the Flash Recovery Area from filling.ﾂ�

ﾂ�

Oracle 11g Express Edition comes with Application Express 4.0.2 already installed.ﾂ�

If you elect to upgrade to the latest version (4.1 as of this writing), you can do so but will loose access to the XE GUI. Not a huge loss, but something to keep in mind.

Although Apex is already installed, you will need to set the Internal Admin password.

To do so, run the apxchpwd.sql located under /u01/app/oracle/product/11.2.0/xe/apex:

Note: pick something simple like Password123! as you will be prompted to change it on first log in anyways.

You can access the Application Express GUI at:

http://localhost:8080/apex/f?p=4550:1

Replace localhost above with your IP or domain as required.

Workspace: Internal
User Name: admin
Password: (whatever you selected above).

Alternatively, you can access viaﾂ�

http://localhost:8080/apex/f?p=4550:10 or http://localhost:8080/apex/apex_admin

Again, replace localhost above with your IP or domain as required.

ﾂ�

Unless you have a license for Oracle HTTP Server (OHS), your options are the embedded PLSQL Gateway (EPG) or Apex Listener.ﾂ�

The Application Express that comes installed with Oracle 11g XE is configured using the EPG.

While the EPG is simpler than Apex Listener, it can be painfully slow as of Apex 3.2.ﾂ�

Apex Listener, while quite fast, adds an extra layer of complexity.ﾂ�

You will need to install an application server to run Apex Listener.

I have run Apex Listener on both Tomcat (unsupported) as well as Oracle GlassFish 3.x (supported) and was not impressed with either.

A lot of people who know far more than I do about APEX (read: 99.9999% of the population) like the Apex Listener.

Apex Listener and it's installation guide can be foundﾂ�here.

The Apex Listener installation guide is well done and simple to follow.

If you need to install Oracle GlassFish or GlassFish CE (basic installation is the same), you can use my GlassFish 3.1 instructionshere.

If you want to be an outlaw and use Tomcat, you can use my Tomcat 6 installation guideﾂ�here.ﾂ�or my Tomcat 7 installation guideﾂ�here..

ﾂ�

Bash Script for Oracle Data Pump

Red Hat Linux 5.4 or CentOS 5.4 Oracle 11g or 10g SID = orcl This post covers creating a basic bash script to produce a Data Pump export file (.dmp)

file which we can then FTP to a remote server or mail the file using MUTT. We'll also generate a log file of the export and write the output of the log file

into the body of an email notification. In the first scenario, we want to email the export file as an attachment, so we''ll need to do the following:

1. Export the Scott schema on a daily basis using Data Pump.
2. Create a log file of the Data Pump export
3. Add the date and hour of the export to to the file name and log file in the forms of : scott-yyyymmddhh.dmp. and scottLOG-yyyymmddhh.log
4. Use zip or gzip to compress the dump file for easier FTP and/or mailing
5. Write the contents of the log file into the body of an email.
6. FTP the file or attach the file to the email and send it.

To begin, you will need to create an Oracle directory to export the file to and then grant read and write on the directory for the schema. If not already installed, installﾂ�MUTT: Create your bash script. In the first example, we'll zip the export, attach it to an email and place the export log into the body of the

email. I'm creating mine in /usr/lib/myscripts and the file name will be scottscript.sh What is in the script: In the last bit above:

• cat /home/app/oracle/admin/orcl/dpdump/scottLOG-$(date +%Y%m%d%H).log writes the contents of the log file into the body of the email.ﾂ�
• "Scott Backup" is the email subject line.
• -a /home/app/oracle/admin/orcl/dpdump/scott-$(date +%Y%m%d%H).zip attaches our file to the email.
• This email address is being protected from spambots. You need JavaScript enabled to view it. is the recipient address.

From here, you can set a cron job to automate running the script at whatever interval you require.ﾂ�

Now, instead of emailing the zip file, let's FTP the file to a remote server.ﾂ�In this case, we want to FTP the file, so we'll need to do the following:

1. Export the Scott schema on a daily basis using Data Pump.
2. Create a log file of the Data Pump export
3. Add the date and hour of the export to to the file name and log file in the forms of : scott-yyyymmddhh.dmp. and scottLOG-yyyymmddhh.log
4. Use zip or gzip to compress the dump file for easier FTP
5. Write the contents of the log file into the body of an email notification.
6. FTP the file.

What is in the script: