ORATraining Blog » Oracle Database

Configuring Oracle Identity and Access Management components

admin — Mon, 06 Feb 2012 09:30:04 +0000

Oracle Fusion Applications Installation: Configuring Oracle Identity and Access Management components

Previous: Installing Oracle Identity and Access Management Components

Configuring Oracle Identity Management components” can be divided into following tasks.

Configuring the Web Tier
Create Weblogic Domain for Identity Management
Extending the Domain with Oracle Internet Directory
Extending the Domain with Oracle Directory Service Manager (ODSM)
Extending the Domain with Oracle Virtual Directory
Extending the Domain with Oracle Access Manager
Extending the Domain to Configure Oracle Identity Manager and Oracle SOA Suite
Installing and Configuring WebGate

Please note that this post is going to be long so allow time to load all images.

Configuring the Web Tier

Start the configuration from /bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_WT1/bin

[oracle@fusion bin]$ ./config.sh

Click Next

Select “Oracle HTTP Server” and click Next

For Instance location enter “/app/fusion/bea_default/instances” since we will keep all instances in this location. Provide any appropriate Instance name and OHS component name. We will go for the defaults. Click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

Now we will copy staticports.ini default file from /installers/webtier/Disk1/stage/Response to home directory /home/oracle

cp /mnt/fusion/installers/webtier/Disk1/stage/Response/staticports.ini ~/staticports.ini

Now click on “View/Edit File” to edit this file.

Uncomment and set the following values. Click Save

OPMN Local Port = 6700

OHS Port = 7777

Click Next

Deselect email notification and click Next

Save summary if needed and click Configure to start configuration.

Important Note: If SELinux is enabled in your Linux operating System then it will throw an error. Since we already disabled it during installation, we will not see that error here.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

It would have already started HTTP server now. We can verify the same.

[oracle@fusion instances]$ ps -ef | grep http

oracle 3521 3491 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

oracle 3547 3521 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

oracle 3548 3521 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

oracle 3549 3521 0 10:06 ? 00:00:00 /app/fusion/bea_default/Oracle_WT1/ohs/bin/httpd.worker -DSSL

Check /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/httpd.conf to make sure it reflects correct user and group name

User oracle

Group oinstall

We can launch http://fusion:7777 (Homepage of Oracle HTTP server) now. It will look as follows.

Create Weblogic Domain for Identity Management

Start the configuration from /oracle_common/commin/bin

[oracle@fusion bin]$ /app/fusion/bea_default/oracle_common/common/bin/config.sh

Select “Create a new Weblogic domain” and click Next

Select “Oracle Enterprise Manager – 11.1.1.0 [oracle_common]” and “Oracle JRF – 11.1.1.0 [oracle_common]” and click Next

Enter details as above or accept default values and click Next.

Since it accepts minimum 8 characters set password again to
oracle123. Please note that you can also change username from weblogic but in future whenever we refer to weblogic user you must enter the new user which selected. We will go for default “weblogic” username

You would see option of Oracle JRockit here. So select that JDK in this list.

Select “Administration Server” and “Managed Servers, Clusters and Machines”. Click Next

Keep defaults but make a note of the port since this will be widely used during next part of installation. Click Next

Just click Next

Click Next again

Select Second Tab “Unix Machine” and enter the hostname as above. Click Next

Click on AdminServer and Click right arrow. Click Next

It will now look as above. Click Next

On Summary page click Create

Once installation finishes, click Done

Make sure that the encrypted username and password values are already in boot.properties

[oracle@fusion security]$ more /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/AdminServer/security/boot.properties

# Generated by Configuration Wizard on Mon Jan 23 10:59:07 GST 2012

username={AES}zaXc3+4y2KGuxnK6WkI7ehKcliQDeandkjdTdu0vpuY=

password={AES}WZ6Zo+j6aGoCyE2nQmCCdboEkA8TDGRlagdSqFGRedo=

Set StartScriptEnabled=true in nodemanager.properties by running following script

[oracle@fusion bin]$ cd /app/fusion/bea_default/oracle_common/common/bin

[oracle@fusion bin]$ ./setNMProps.sh

Appending required nodemanager.properties

Verify the change.

[oracle@fusion bin]$ tail -f /app/fusion/bea_default/wlserver_10.3/common/nodemanager/nodemanager.properties

#Required NM Property overrides (append to existing nodemanager.properties)

StartScriptEnabled=true

Start Node manager

[oracle@fusion bin]$ cd /app/fusion/bea_default/wlserver_10.3/server/bin

[oracle@fusion bin]$ nohup ./startNodeManager.sh &

…

IDM_domain -> /app/fusion/bea_default/user_projects/domains/IDM_domain

…

INFO: Secure socket listener started on port 5556

Start Weblogic AdminServer

[oracle@fusion bin]$ nohup
/app/fusion/bea_default/user_projects/domains/IDM_domain/bin/startWebLogic.sh &

tail nohup.out file until it shows following message.

Open Weblogic Admin Console

Launch Weblogic Admin console through
http://fusion:7001/console

Note: Go to preferences and change “automatic acquire lock” settings to avoid accidental changes since we are in development mode.

Configuring HTTP server for the Administration Server

Create a new file admin.conf as follows.

[oracle@fusion moduleconf]$ more /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf/admin.conf

ServerName fusion:80

ServerAdmin you@your.address

RewriteEngine On

RewriteOptions inherit

RewriteRule ^/console/jsp/common/logout.jsp /oamsso/logout.html [PT]

RewriteRule ^/em/targetauth/emaslogout.jsp /oamsso/logout.html [PT]

# Admin Server and EM

SetHandler weblogic-handler

WebLogicHost fusion

WeblogicPort 7001

SetHandler weblogic-handler

WebLogicHost fusion

WeblogicPort 7001

SetHandler weblogic-handler

WebLogicHost fusion

WeblogicPort 7001

Restart http server.

ORACLE_HOME=/app/fusion/bea_default/Oracle_WT1

export ORACLE_HOME

ORACLE_INSTANCE=/app/fusion/bea_default/Oracle_WT1/instances/instance1

export ORACLE_INSTANCE

PATH=$ORACLE_HOME/opmn/bin:$PATH

export PATH

opmnctl stopall

opmnctl startall

Now we need to Register HTTP server with Weblogic Server so that Enterprise Manager can monitor the instance.

[oracle@fusion ~]$ opmnctl registerinstance -adminHost fusion -adminport 7001 -adminUsername weblogic

Command requires login to weblogic admin server (fusion):

Username: weblogic

Password:

…

Done

Registering instance

Command succeeded.

Note: We will not enable load-balancer access since we have skipped load-balancing in this single node installation guide.

Enable Weblogic Plugin

Log in the Oracle Weblogic Server Administration and click on Lock and Edit. Click on IDMDomain and Click on Configuration tab and then select the Web Applications tab.

Scroll down and enable “Weblogic Plug-in Enabled”.

Click on Save and Activate the Changes.

Restart the Weblogic Administration Server.

Extending the Domain with Oracle Internet Directory

Start the configuration from

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IDM1/bin

[oracle@fusion bin]$ ./config.sh &

Click Next

Select “Configure Without A Domain” and click Next

Make sure to select any directory inside MW_HOME/instances. You can accept default for Instance Name. Click Next

Deselect email notification and click Next

Select only “Oracle Internet Directory” and click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

In another terminal window copy the staticports.ini file to home directory.

[oracle@fusion bin]$ cp /app/fusion/provisioning/idm/idm/Disk1/stage/Response/staticports.ini ~/

Click on View/Edit file

VERY IMPORTANT:

As per Oracle Manual we should Change it to as follows.

#The Non-SSL port for OID

Oracle Internet Directory Port No = 389

#The SSL port for OID

Oracle Internet Directory (SSL) Port No = 636

But OID fails to configure and start at the end of installation with these values so we will stick to the OID values for 11g in the staticports.ini and just remove the comments.

#The Non-SSL port for OID

Oracle Internet Directory Port No = 3060

#The SSL port for OID

Oracle Internet Directory (SSL) Port No = 3061

Click Save

Once saved, click Next

Enter oracle123 or any suitable password. If you are using different passwords then please make a note of all of them. Click Next

Since we are not using any domains as such but as we have added an entry in our hosts file for fusion.localdomain, we will add “dc=localdomain” for Realm. Enter oracle123 or any suitable password. Click Next

Save summary if needed and click Configure to start configuration.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

Validate the OID installation

[oracle@fusion ~]$ export ORACLE_HOME=/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion ~]$ export ORACLE_INSTANCE=/app/fusion/bea_default/instances/oid_inst1

[oracle@fusion ~]$ export PATH=$ORACLE_HOME/opmn/bin:$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_HOME/ldap/admin:$PATH

[oracle@fusion ~]$ ldapbind -h fusion -p 3060 -D “cn=orcladmin” -q

Please enter bind password:

bind successful

[oracle@fusion ~]$ ldapbind -h fusion -p 3061 -D “cn=orcladmin” -q -U 1

Please enter bind password:

bind successful

[oracle@fusion ~]$ opmnctl status

Processes in Instance: oid_inst1

———————————+——————–+———+———

ias-component | process-type | pid | status

———————————+——————–+———+———

oid1 | oidldapd | 19810 | Alive

oid1 | oidldapd | 19798 | Alive

oid1 | oidmon | 19785 | Alive

EMAGENT | EMAGENT | 19325 | Alive

Registering Oracle Internet Directory with the WebLogic Server Domain

[oracle@fusion ~]$ echo $ORACLE_HOME

/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion ~]$ echo $ORACLE_INSTANCE

/app/fusion/bea_default/instances/oid_inst1

[oracle@fusion ~]$ opmnctl registerinstance -adminHost fusion -adminPort 7001 -adminUsername weblogic

Command requires login to weblogic admin server (fusion):

Username: weblogic

Password:

Registering instance

Command succeeded.

Note: We have skipped next steps related to SSL since we are setting up non-SSL connections here.

Update the Enterprise Manager Repository URL

Next we will update the Enterprise Manager Repository URL using the emctl utility with the switchOMS flag. The emctl utility is located under the ORACLE_INSTANCE/EMAGENT/EMAGENT/bin directory.

[oracle@fusion ~]$ cd /app/fusion/bea_default/instances/oid_inst1/EMAGENT/EMAGENT/bin

[oracle@fusion bin]$ ./emctl switchOMS http://fusion:7001/em/upload

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

SwitchOMS succeeded.

We can now verify whether this instance is registered for monitoring agent.

Login to http://fusion:7001/em

Click on Farm->Agent monitored targets.

You should be able to see the OID instance under this. Make sure that the Agent URL is showing up fine. If the status shows as “Need Configuration” then click on Configure and then in next screen enter weblogic user credentials. It should now show the correct Agent URL.

Extending the Domain with Oracle Directory Service Manager (ODSM)

Start the configuration from /bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IDM1/bin

[oracle@fusion bin]$ ./config.sh &

Click Next

Select “Extend Existing Domain” and enter details of existing weblogic Server and AdminServer port. Click Next

You can ignore this error since we created this domain using the Identity Management installer. Click Yes to ignore.

Verify that the weblogic server directory shown is correct as per previous steps. Specify name and path for Oracle Directory Service instance. Make sure to keep the instance in same parent directory as previous instances. Click Next

Deselect email notification and click Next

Select Oracle “Directory Service Manager” and click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

Meanwhile in another terminal window copy the staticports.ini to home directory.

[oracle@fusion bin]$ cp -p /app/fusion/provisioning/idm/idm/Disk1/stage/Response/staticports.ini ~/

Uncomment the ODS Server Port and keep it default 7006. Click Save.

Once Saved click Next.

Save summary if needed and click Configure to start configuration.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

Password-less startup for ODS

cd /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/wls_ods1/security

cp ../../AdminServer/security/boot.properties .

cd /app/fusion/bea_default/user_projects/domains/IDM_domain/bin

nohup ./startManagedWebLogic.sh wls_ods1

Now you can access ODS homepage at http://fusion:7006/odsm/faces/odsm.jspx (as per the above post-installation summary screen)

Register ODS with OID

Click on Connect to a directory -> Create A New Connection

Enter the details for OID.

Name: fusion-oid

Server: fusion

SSL Enabled: Unchecked

User Name: cn=orcladmin

Password: oracel123

Start Page: Home

Click Connect

Once connection is successful, you should be able to see OID page.

You can randomly check whether you are able to see details of any user, for example cn=orcladmin

Configuring Oracle HTTP Servers to Access the ODSM Console

[oracle@fusion moduleconf]$ cd /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf

[oracle@fusion moduleconf]$ vi admin.conf

# Append following lines in admin.conf

SetHandler weblogic-handler

WebLogicCluster fusion:7006

Restart HTTP server.

Now we can access ODSM through http://fusion:7777/odsm/faces/odsm.jspx

Extending the Domain with Oracle Virtual Directory

Start the configuration from /bin

[oracle@fusion ~]$ cd /app/fusion/bea_default/Oracle_IDM1/bin/

[oracle@fusion bin]$ ./config.sh &

Click Next

Select “Configure Without A Domain“. Click Next

Provide values for Oracle Virtual Directory (OVD) instance. You can accept default values. Click Next

Deselect email notification and click Next

Select “Oracle Virtual Directory” and click Next

Select “Specify Ports using Configuration File” and enter file name as /home/oracle/staticports.ini

Open a separate terminal/putty window and copy staticports.ini file to home directory.

[oracle@fusion ~]$ cp /app/fusion/provisioning/idm/idm/Disk1/stage/Response/staticports.ini ~/

Click on View/Edit.

Edit the staticports.ini file to assign ports 6501 and 7501, as follows.

# The non-SSL port for Oracle Virtual Directory

Oracle Virtual Directory port = 6501

# The SSL port for Oracle Virtual Directory

Oracle Virtual Directory (SSL) port = 7501

Click Save and then Next

Provide OID login details.

Uncheck “Configure Administrative Server in secure mode” since we are not using SSL anywhere in this installation. Click Next

Click Ok

Save summary if needed and click Configure to start configuration.

Once installation finishes, click Next

Save installation summary if needed and click Finish to complete the installation.

Registering OVD with the Oracle WebLogic Server Domain

[oracle@fusion bin]$ cd /app/fusion/bea_default/instances/ovd_inst1/bin

[oracle@fusion bin]$ ./opmnctl registerinstance -adminHost fusion -adminPort 7001 -adminUsername weblogic

Command requires login to weblogic admin server (fusion):

Username: weblogic

Password:

Registering instance

Command succeeded.

Update the Enterprise Manager Repository URL using the emctl utility with the switchOMS flag.

The emctl utility is located under the ORACLE_INSTANCE/EMAGENT/EMAGENT/bin directory.

[oracle@fusion bin]$ cd /app/fusion/bea_default/instances/ovd_inst1/EMAGENT/EMAGENT/bin

[oracle@fusion bin]$ ./emctl switchOMS http://fusion:7001/em/upload

Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.

Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.

SwitchOMS succeeded.

We can now verify whether this instance is registered for monitoring agent.

Login to http://fusion:7001/em

Click on Farm->Agent monitored targets.

You should be able to see the OID and OVD instances under this. Make sure that the Agent URL is showing up fine. If the status shows as “Need Configuration” then click on Configure and then in next screen enter weblogic user credentials. It should now show the correct Agent URL.

Validate the Oracle Virtual Directory Instances

[oracle@fusion ~]$ export ORACLE_HOME=/app/fusion/bea_default/Oracle_IDM1

[oracle@fusion ~]$ export ORACLE_INSTANCE=/app/fusion/bea_default/instances/ovd_inst1

[oracle@fusion ~]$ export PATH=$ORACLE_HOME/opmn/bin:$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_HOME/ldap/admin:$PATH

[oracle@fusion bin]$ ldapbind -h fusion -p 6501 -D “cn=orcladmin” –q

Please enter bind password:

bind successful

[oracle@fusion bin]$ ldapbind -h fusion -p 7501 -D “cn=orcladmin” -q -U 1

Please enter bind password:

SSL handshake failed

This is fine since we did not configure SSL mode.

Creating ODSM connections to Oracle Virtual Directory

Open http://fusion:7777/odsm/faces/odsm.jspx

Click Connect to a directory -> Create a new connection

Enter details of OVD here.

Name: fusion-ovd

Host: fusion

Port: 8899

SSL Enabled: Unchecked

User Name: cn=orcladmin

Password: oracle123

Start Page: Home

Click Connect

It will display OVD home page.

Note: We are skipping the adapter creation for now. We will create them later once needed.

Extending the Domain with Oracle Access Manager

Start the configuration from

[oracle@fusion bin]$ cd /app/fusion/bea_default/oracle_common/common/bin

[oracle@fusion bin]$ ./config.sh

Click “Extend an existing WebLogic domain” and click Next

Scroll down and select user_projects->domains->IDM_domain. Click Next

Select only “Oracle Access Manager with Database Policy Store” and click on Next.

Here you need to provide the database connection details and choose schema owner username. You can keep the name default but make sure to keep a note of it since you will need this later. Choose a password for example oracle123. Click Next

Now it will test the database connectivity through JDBC.

Once successful, click Next

Select “Managed Servers, Clusters and Machines” only and click Next

The first row was from previous configuration of ODS and now there will be another row for OAM. Keep the default port and make a note of it. Enter wls_oam1 for the instance name (or whichever you chose while creating instance) and click Next

Just click Next

On the “Machines” tab make sure that correct hostname is entered. Click Next

Select wls_oam1 and click the right arrow.

Now it should look as above. Click Next

On the summary page Click Extend.

Click OK Since we are aware that these are correct ports being used by AdminServer and wls_ods1 instance.

Once configuration finishes, click Done.

You can start the managed server by using following command.

[oracle@fusion bin]$ cd /app/fusion/bea_default/user_projects/domains/IDM_domain/bin

[oracle@fusion bin]$ ./startManagedWebLogic.sh wls_oam1

This will create the directory /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/wls_oam1

Press CTRL+C to stop the process since we will need to configure startup without password prompt.

[oracle@fusion wls_oam1]$ cd /app/fusion/bea_default/user_projects/domains/IDM_domain/servers/wls_oam1

[oracle@fusion wls_oam1]$ cp ../wls_ods1/security/ boot.properties .

Now we can start the managed server without prompting for password.

[oracle@fusion bin]$ cd /app/fusion/bea_default/user_projects/domains/IDM_domain/bin

[oracle@fusion bin]$ nohup ./startManagedWebLogic.sh wls_oam1 &

Configuring Oracle HTTP Servers to Display Login Page and Oracle Access Manager Console

Append following entries in /app/fusion/bea_default/Oracle_WT1/instances/instance1/config/OHS/ohs1/moduleconf/admin.conf

SetHandler weblogic-handler

WebLogicCluster fusion:14100

SetHandler weblogic-handler

WebLogicHost fusion

WebLogicPort 7001

Restart HTTP Server to bring this to effect.

Note: There are few other steps as well as per Oracle documentation but we will skip them for now.

Extending the Domain to Configure Oracle Identity Manager and Oracle SOA Suite

Start the configuration from

[oracle@fusion bin]$ cd /app/fusion/bea_default/oracle_common/common/bin

[oracle@fusion bin]$ ./config.sh &

Select “Extend an existing WebLogic domain” and click Next

Scroll down and select user_projects->domains->IDM_domain and click Next

Select Oracle Identity Manager. It will automatically select Oracle SOA Suite and Oracle WSM. Click Next

Check all to modify all entries together. Provide database connect details and select a password for all. Accept default value for Schema owner names. Click Next

Now it will test the database connectivity through JDBC.

Once JDBC test is successful, click Next

Select only “Managed Servers, Clusters and Machines” and click Next

Add entries for soa_server1 and oim_server1. As per Oracle documentation you can change them to wls_soa1 and wls_oim1 as well. But here we have kept them as default.

Note the ports and click Next.

Just click Next

Since we are using Linux/Unix machine, delete entry from above screen. And proceed to Unix Machine tab.

Make sure correct hostname is entered here. Click Next

Select oim_server1 and soa_server1 and click right arrow. (if you had renamed them to wls_oim1 and wls_soa1 then you will see those entries instead of this)

The screen will now look like above. Click Next

On Summary screen click Next

Click OK

Once configuration finishes, click Done

Configuring Oracle Identity Manager

Now we will configure the Identity Manager from /bin

[oracle@fusion bin]$ cd /app/fusion/bea_default/Oracle_IAM/bin

[oracle@fusion bin]$ ./config.sh &

Click Next

Select only OIM Server and click Next

Enter database details in shown format “fusion:1521:fusiondb“. Select Schema names (keep default) and enter password (oracle123). Make sure to keep a note of these schema names DEV_OIM and DEV_MDS. We will need these later during provisioning plan. Click Next

Enter AdminServer details in t3://: format. Here t3://fusion:7001

Important Note: Before clicking next make sure that AdminServer is running otherwise it may throw following error on next page. Start or restart AdminServer if you see this error.

INST-6180: Error while retrieving OIM Managed Server URL from the domain.

Click Next

Enter passwords as follows and keep a note of them since we will require them in provisioning wizard.

OIM Admin password: Oracle123

Keystore Password: oracle123

Enter OIM HTTP URL as http://fusion:14000 (based on port value in previous configuration step). Click Next

Deselect both and click Next

Save the summary if required and click Configure.

Once configuration finishes click Next

Save the configuration summary if needed and click Finish to complete the configuration.

Installing and Configuring WebGate

Start Webgate 10g installation from /installers/webgate

[oracle@fusion webgate]$ cd /mnt/fusion/installers/webgate

[oracle@fusion webgate]$ ./Oracle_Access_Manager10_1_4_3_0_linux64_OHS11g_WebGate –gui

Click Next

Enter the OS oracle user details. Click Next

Select a path where you want to install webgate. We have selected /app/fusion/webgate. Click Next

Click Next

Open a new terminal/putty window and execute following commands. Once done enter the location /app/fusion/oam_lib in this screen and click Next to start the installation.

[oracle@fusion oam_lib]$ mkdir /app/fusion/oam_lib

[oracle@fusion oam_lib]$ ln -s /usr/lib64/libstdc++.so.5 /app/fusion/oam_lib/libstdc++.so.5

[oracle@fusion oam_lib]$ ln -s /lib64/libgcc_s.so.1 /app/fusion/oam_lib/libgcc_s.so.1

Now WebGate Configuration will start. Select “Open Mode” and click Next

Since this screen requires WebGate ID from Access Manager. We need to first create a Webgate Agent in Access Manager. So keep this Java window open and open Oracle Access Manager Console in browser by entering http://fusion/oamconsole or http://fusion:7777/oamconsole

Note: We could have done this before starting Webgate installation as well but keeping it here in the guide gives you an idea where we are going to this configuration. Next time when you install, you can do this step before itself.

Login with weblogic admin user.

Once logged under SSO Agents, click on New “OAM 10g Webgate” (since we are installing 10g webgate).

Enter name: Webgate_sso or any name

Base URL: http://fusion:7777

Host Identifier: Webgate_sso

Security: Open

Uncheck all 3 options on right.

Click Apply

Now Edit the same Webgate Agent again. It will show following screen.

We did not put domain since we are using only http://fusion

Change Max Connections to 4

Logout URL: Enter following values.

/oamconsole/logout.html

/console/jsp/common/logout.jsp

/em/targetauth/eamlogout.jsp

Click Apply

Once webgate Agent is created in OAM, go back to the already open configuration window and enter following details and click Next to finish the configuration. In case if the configuration window was closed, you can also launch the configuration from command prompt.

[oracle@fusion webgate]$ /app/fusion/webgate/access/oblix/tools/configureWebGate/start_configureWebGate -i /app/fusion/webgate/access -t WebGate

Please enter the Mode in which you want the Web Gate to run : 1(Open) 2(Simple) 3(Cert) : 1

Please enter the Web Gate ID : Webgate_sso

Please enter the Password for this Web Gate :

Please enter the Access Server ID : wls_oam1

Please enter the Access Server Host Machine Name : fusion

Please enter the Access Server Port : 5575

Preparing to connect to Access Server. Please wait.

Web Gate installed Successfully.

Press enter key to continue …

As per Oracle documentation there are a few steps to use the Webgate and validate but we will skip them for now.

Next step is to prepare Identity and Policy Stores by creating necessary users and groups for provisioning Fusion Applications.

Next: Preparing Identity and Policy Stores

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework

Installing Oracle 11g Database (Applications Transactional Database)

Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Creating another database for Oracle Identity Management Infrastructure (optional)

Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Oracle Identity and Access Management Components

Configuring Oracle Identity and Access Management components

Preparing Identity and Policy Stores

Creating a New Provisioning Plan

Provisioning an Applications Environment

Creating a new Provisioning Plan

admin — Thu, 02 Feb 2012 19:16:05 +0000

Tweet

Oracle Fusion Applications Installation: Creating a new Provisioning Plan

Previous: Preparing Identity and Policy Store

In order to create a new fusion applications provisioning plan we should launch the provisioning wizard again from <framework_location>/provisioning/bin

is same what we mentioned in previous post. i.e. /app/fusion

[oracle@fusion $ cd /app/fusion/provisioning/bin

[oracle@fusion bin]$ ./provisioningWizard.sh

On Welcome screen, click Next

Select “Create a New Applications Environment Provisioning Plan” and click Next

Deselect Security updates notification and click Next

Please note that in Fusion Applications each Applications will include multiple Weblogic Managed Servers, admin servers etc and since our Virtual Machine is not having sufficient capacity to host all these applications, we selected “Oracle Human Capital Management”. You can select any product which you wish to configure first. Click Details to see the topology details for the selected module.

Click Close and then Next on configurations screen.

In this screen provide any name to this provisioning plan. Click Next

Since we entered “weblogic” as Node Manager login earlier, provide its credentials.

Installers Directory Location: The stage or repository location. In our case /mnt/fusion

Oracle Fusion Applications Home: Provide base location for the installation. /app/fusion

Enter /app/fusion/instance for Application Configuration Directory.

As we have noted the location for Webgate Library earlier in Previous post, enter /app/fusion/oam_lib

We had created IDM Properties file /app/fusion/bea_default/Oracle_IAM/idmtools/bin/idmDomainConfig.param in previous post.

RDP Password: oracle123

Click Next

Accept default values. Click Next

Enter database details in this screen. Click Next

Enter same password. Lets’ keep oracle123 again J

This will only accept earlier entered ODI Supervisor password. In our case, nothing to worry since we have all passwords as oracle123

Password: oracle (it validated this password)

We are going to have single host for all domains. Enter our hostname “fusion” and click Next

Deselect DMZ, enter host as fusion, domain as fusion.local. Click Next

Change at least the internal names as above to keep it simple. Click Next

Since we are going to have the simplest installation, deselect Load Balancing. Click Next

Deselect Proxy. Click Next

Entered following values only, remaining were populated from idmDomainConfig.param file

Super User Name: orcladmin

Checked “Create Administrators Group”, “Create Monitors Group”, “Create Operators Group”

Entered oracle123 in both password fields

Unchecked “Identity Store Enabled SSL”, “OIM Endpoint Enabled SSL”

OIM Administrator User Name: xelsysadmin

OIM Administrator Password: oracle123

OIM Managed Server port: 7004

OIM Endpoint Host: fusion (this is because we did not configure load balancing)

OIM Endpoint Port: 7777 (again because we didn’t configure load balancing)

IDM Keystore file: Create a dummy file anywhere on Linux and enter its path here.

[oracle@fusion]$ touch /app/fusion/provisioining/dummy

IDM KeyStore Password: Enter any value

OAM Administrator User Name: oamadmin

OAM Administrator Password: oracle123 (as defined earlier)

OAM AAA Server Host: fusion

OAM AAA Server Port: 5575 (Default and also defined earlier)

Access Server Identifier: wls_oam1

Unchecked OPSS Policy Store SSL Enabled

Deselect Secondary OAM.

OAM Security Mode: Open

Webgate password: oracle123 (as entered earlier in previous post)

Remaining fields already poputed due to idmDomainConfig.param file. Deselect last 2 options. Click Next

Enter Database Details. Also enter DEV_MDS and password (defined earlier during installation in previous post). Click Next

Click Finish to complete creating the plan.

Next: Provisioning an Applications Environment

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework

Installing Oracle 11g Database (Applications Transactional Database)

Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Creating another database for Oracle Identity Management Infrastructure (optional)

Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Oracle Identity and Access Management Components

Configuring Oracle Identity and Access Management components

Preparing Identity and Policy Stores

Creating a New Provisioning Plan

Provisioning an Applications Environment

Running Repository Creation Utility for Oracle Identity Management components

admin — Thu, 02 Feb 2012 11:48:07 +0000

Tweet

Oracle Fusion Applications installation: Running Repository Creation Utility (RCU) for Oracle Identity Management Components

Previous: Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Important Note: We are NOT creating a separate database to host Oracle Identity Management schemas. Instead we will create these schemas in our Fusion Database (fusiondb) itself since the schema names are distinct compared to Fusion Application schemas. We will save a lot of Memory for our Virtual Machine.

In order to run RCU for Identity Management on same database, we must set the open_cursors parameter to 800.

Open a new database session and set following values.

SQL> show parameter open_cursors

NAME TYPE VALUE

———————————— ———– ——————————

open_cursors integer 500

SQL> alter system set open_cursors=800 scope=both sid=’*';

System altered.

Launch Repository Creation Utility for Oracle Identity Management from /fmw_rcu/bin location

[oracle@fusion bin]$ /app/fusion/provisioning/fmw_rcu/bin/rcu &

Click Next

Select Create and click Next

Enter the database information (for same fusiondb database as entered earlier. Click Next

Next it will check for required prerequisites. Upon successful check click OK

Click Idnentity Management. It will select few other required components also automatically. Click Next

Again it will check prerequisites for the selected components. Upon successful check click OK

Enter same password oracle123 for ease of remembering. Click Next

No need to change anything in this screen. Click Next

Click OK

It will create the required tablespaces. Once finished click OK

On this summary screen click Create to create required schemas and load data.

This will be quicker than earlier RCU. Once finished proceed to next screen.

Finally it will display Completion Summary. Clock Close

Next: Installing Oracle Identity and Access Management Components

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework

Installing Oracle 11g Database (Applications Transactional Database)

Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Creating another database for Oracle Identity Management Infrastructure (optional)

Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Oracle Identity and Access Management Components

Configuring Oracle Identity and Access Management components

Preparing Identity and Policy Stores

Creating a New Provisioning Plan

Provisioning an Applications Environment

Running Fusion Applications RCU

admin — Thu, 02 Feb 2012 08:43:35 +0000

Tweet

Oracle Fusion Applications Installation: Running Fusion Applications Repository Creation Utility (Apps RCU)

Previous: Installing Oracle 11g Database (Applications Transactional Database)

Create a directory on physical partition and call it APPS_RCU_HOME

[oracle@fusion linux]$ mkdir /app/fusion/provisioning/apps_rcu

Go to repository_location/installers/apps_rcu and locate the rcuHome_fusionapps_dbinstall.zip file. This file was staged when you created the installer repository.

Extract the contents of rcuHome_fusionapps_dbinstall.zip to a directory (APPS_RCU_HOME) on the database server. All dependent components that Applications RCU needs are included in this zipped file.

[oracle@fusion apps_rcu]$ cd /app/fusion/provisioning/apps_rcu

[oracle@fusion apps_rcu]$ unzip /mnt/fusion/installers/apps_rcu/linux/rcuHome_fusionapps_linux.zip

Create a temporary directory on the database server. Make a note of the location.

You will need to enter this location when you specify a value for FUSIONAPPS_DBINSTALL_DP_DIR

[oracle@fusion apps_rcu]$ mkdir /app/fusion/provisioning/apps_rcu/dp_dir

Locate and copy APPS_RCU_HOME/rcu/integration/fusionapps/export_

fusionapps_dbinstall.zip to the directory you specified for FUSIONAPPS_

DBINSTALL_DP_DIR.

Unzip export_fusionapps_dbinstall.zip to FUSIONAPPS_DBINSTALL_DP_DIR.

[oracle@fusion dp_dir]$ cd /app/fusion/provisioning/apps_rcu/dp_dir

[oracle@fusion dp_dir]$ unzip /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip

Go to APPS_RCU_HOME/rcu/integration/biapps/schema and locate the

otbi.dmp file.

Copy otbi.dmp to FUSIONAPPS_DBINSTALL_DP_DIR (where you unzipped the

contents of export_fusionapps_dbinstall.zip).

[oracle@fusion dp_dir]$ cp -p ../rcu/integration/biapps/schema/otbi.dmp /app/fusion/provisioning/apps_rcu/dp_dir/

Launch Repository Creation Utility (RCU)

[oracle@fusion bin]$ cd /app/fusion/provisioning/apps_rcu/bin

[oracle@fusion bin]$ ./rcu

Click Next

Click Next

Enter same details as entered while creating the database in previous step. Click Next

This screen will check pre-requisites. Click Ok once successful.

Select all components in this Window.

It will look as above when you collapse all parent values. Click Next

Important Note: If you had reduced SGA and PGA size after DB installation then this prerequisites check may fail with following error.

RCU-6083:Failed – Check prerequisites requirement for selected component:FUSIONAPPS

RCU-6107:DB Init Param Prerequisite failure for: pga_aggregate_target

Current Value is 2147483648. It should be greater than or equal to 4294967296.

RCU-6107:DB Init Param Prerequisite failure for: sga_target

Current Value is 2147483648. It should be greater than or equal to 9663676416.

To fix this issue, we need to modify the minimum requirement of SGA and PGA in installer pre-requisite config file located at /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/fusionapps.xml

Change these values as follows.

sga_target

2147483648

…

pga_aggregate_target

2147483648

The prerequisites check should finish successfully. Click Ok

Enter same password for keeping it simplefor now. Click Next

Open another terminal window. Create following directories for custom environment variables.

[oracle@fusion database]$ mkdir /app/fusion/database/applcp

[oracle@fusion database]$ mkdir /app/fusion/database/appllog

[oracle@fusion database]$ mkdir /app/fusion/database/keyflexcombfilter

[oracle@fusion database]$ mkdir /app/fusion/database/obieebkp

Specify these following values in the same screen under Fusion Applications Component (expect first value which is the temporary DP directory created before /app/fusion/provisioning/apps_rcu/dp_dir)

Supervisor Password: You must enter the same password you set up as ODI SUPERVISOR in Applications RCU. Since we kept all passwords as oracle123, nothing much to remember. Enter the same password.

Work Repository Password: Default = None. You must enter the same password set up as ODI SUPERVISOR in Applications RCU.

Oracle Transactional BI

Directory on the database server where Oracle Transactional Business Intelligence import and export files are stored. Enter /app/fusion/provisioning/apps_rcu/dp_dir again.

Change nothing in this page. Click Next

Click OK

Now it will create the required tablespaces. Click OK

Once Tablespaces are created, next Summary screen will appear for creating the required Schemas. Click Create

It may take a couple of hours or even more based on the available memory and CPU for the VM and host machine.

Once finished, a completion summary screen will appear. It will show details for each components and completion states. Click Close

Next: Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework

Installing Oracle 11g Database (Applications Transactional Database)

Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Creating another database for Oracle Identity Management Infrastructure (optional)

Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Oracle Identity and Access Management Components

Configuring Oracle Identity and Access Management components

Preparing Identity and Policy Stores

Creating a New Provisioning Plan

Provisioning an Applications Environment

Installing Transactional Database

admin — Thu, 02 Feb 2012 05:32:41 +0000

Tweet

Oracle Fusion Applications Installation: Installing Transactional Database

Previous: Installing Fusion Applications Provisioning Framework

To install Applications Transactional Database we need to run Oracle Fusion Applications Provisioning Wizard from <framework_location>/provisioning/bin

is same what we mentioned in previous post. i.e. /app/fusion

[oracle@fusion $ cd /app/fusion/provisioning/bin

We need to temporarily set JAVA_HOME to jdk6 directory shipped with the installation media

[oracle@fusion bin]$ export JAVA_HOME=/mnt/fusion/jdk6

[oracle@fusion bin]$ ./provisioningWizard.sh

Click Next

Click Next

Deselect security updates notification. Click Next

Provide database listener port (default is 1521, if you change this port please note to enter the new port in future screens where we have mentioned 1521)

Installer directory location will be the same as you created the stage setup or provisioning repository.

Provide a location for Oracle Base. Press TAB, next values should automatically be populated, if not, go back and click next again.

Enter dba as OSDBA group.

We have specified “fusiondb” as our database name. please note that if you are using any other name then don’t forget to change it in further screens whenever we have mentioned fusiondb.

You can keep simple password like “oracle” also but try to keep something like “oracle123” for all passwords so that it will follow requirements for all further passwords and it will be easier for you to remember all passwords in further installations.

Next it will finish the pre-requisite checks. Click Next

On next page, you can Save the summary. Click Install to start the installation.

Note: This will install the software as well as create a database named “fusiondb” which we provided earlier.

At this point it will prompt for running root.sh as root user.

Do not press Ok until run the following as root user in separate terminal window. Once following is executed, press Ok to continue.

[root@fusion ~]# /app/fusion/database/product/11.2.0/dbhome_1/root.sh

Check /app/fusion/database/product/11.2.0/dbhome_1/install/root_fusion_2012-01-1 5_12-29-28.log for the output of root script

[root@fusion ~]# tail -f /app/fusion/database/product/11.2.0/dbhome_1/install/root_fusion_2012-01-15_12-29-28.log

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /app/fusion/database/product/11.2.0/dbhome_1

Creating /etc/oratab file…

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.

Finished product-specific root actions.

It may take a few hours (at least on a non-high end host machine) and then installation will finish.

Important Note: After installation is finished we reduced the SGA and PGA (from 10GB to 2GB). We are doing this since we are running on a VM and have allocated total 2.5 or 3 GB RAM only. This is not recommended for production installation but since this is only a demo/development installation, you can safely do this. If you wish to keep it 10GB you can do it but this will increase the swap usage exponentially.

Since we are reducing the size of SGA and PGA, next step (RCU) may fail in pre-requisite check. So we will need to change the pre-req check xml file to look for lower value. We will explain this in next post.

Next: Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Installing Oracle Fusion Applications – steps

Installing Fusion Applications Provisioning Framework

Installing Oracle 11g Database (Applications Transactional Database)

Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Creating another database for Oracle Identity Management Infrastructure (optional)

Running Repository Creation Utility (RCU) for Oracle Identity Management components

Installing Oracle Identity and Access Management Components

Configuring Oracle Identity and Access Management components

Preparing Identity and Policy Stores

Creating a New Provisioning Plan

Provisioning an Applications Environment

Operating Systems Endian formats for migrating databases across platforms

admin — Wed, 28 Apr 2010 05:22:05 +0000

Tweet

Nowadays DBAs face requirements for migrating databases across different platforms like from Windows to Linux or Solaris or vice versa. While doing this we would require to use transportable tablespaces or cross-platform transportable tablespaces. In order to decide whether the migration would be simple or will involve file conversion, following command is used to identify platform endian format. If the endian formats are same then the process pretty straightforward.

SQL> select * from v$transportable_platform order by platform_id;

PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT

1 Solaris[tm] OE (32-bit) Big

2 Solaris[tm] OE (64-bit) Big

3 HP-UX (64-bit) Big

4 HP-UX IA (64-bit) Big

5 HP Tru64 UNIX Little

6 AIX-Based Systems (64-bit) Big

7 Microsoft Windows IA (32-bit) Little

8 Microsoft Windows IA (64-bit) Little

9 IBM zSeries Based Linux Big

10 Linux IA (32-bit) Little

11 Linux IA (64-bit) Little

12 Microsoft Windows 64-bit for AMD Little

13 Linux 64-bit for AMD Little

14 HP Open VMS Little

15 Apple Mac OS Big

Fix for “Internet explorer has closed this webpage to help protect your computer”

admin — Tue, 27 Apr 2010 11:01:35 +0000

Tweet

Many users face issue running Oracle forms on Microsoft Internet Explorer 8 (IE8) which causes the page to redirect to following url

res://ieframe.dll/acr_depnx_error.htm#,http://:/forms/frmservlet?config=

It displays following error.

Internet explorer has closed this webpage to help protect your computer

A malfunctioning or malicious add-on has caused Internet Explorer to close this webpage.

Solution:

Goto Internet Explorer -> Tools -> Internet Options -> Advanced -> Scroll down to Security -> Uncheck “Enable memory protection to help mitigate online attacks*”

Close all browser windows and restart the browser. The issue should have been fixed

Edit: Alternatively you can use either of following 2 alternate solutions.

Alternate 2:

Open registry using start->Run->regedit->ok

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main

On the right hand side you will see a DWORD key called DEPOff. IF this is set to value 0, just change it to 1 and close registry editor.

Restart Internet Explorer and check if the problem has been fixed or not.

Alternate 3:

Right click on My Computer->Properties (or start->Run->sysdm.cpl->ok)

Click on “Advanced” Tab. Click on “Settings” button next to Performance.

Click on last tab “Data Execution Prevention”

Select Second option and then select “Internet Explorer” from the bottom pan.

(If “Internet Explorer” is not already present there then just click on “Add” and then select “c:\Program Files\Internet Explorer\iexplore.exe”)

Click OK and restart internet explorer. The problem should have been fixed.

PL/SQL quick reference

admin — Wed, 24 Jun 2009 05:48:04 +0000

Tweet

Oracle PL/SQL Quick Reference

PL/SQL Block Structure
DECLARE --Optional --Variables, Cursors, User-defined exceptions BEGIN --Mandatory --SQL statements --PL/SQL statements EXCEPTION --Optional --Actions to perform when errors occur END; --Mandatory PL/SQL Block Type Anonymous               Procedure               Function [DECLARE]               PROCEDURE name          FUNCTION name                         IS                      RETURN datatype                                                         IS BEGIN                   BEGIN                   BEGIN --statements            --statements            --statements                                                 RETURN value; [EXCEPTION]             [EXCEPTION]             [EXCEPTION] END ;                   END ;                   END ; Declaring PL/SQL Variables identifier [CONSTANT] datatype [NOT NULL]    [:=|DEFAULT expr]; Assigning Values to Variables identifier := expr; Types of Variables PL/SQL variables:

Scalar

Composite

Reference

LOB(Large OBjects)

Non-PL/SQL variables: Bind or host variables

Used to pass run time values out of the PL/SQL block back to the Host environment

Base Scalar Datatypes VARCHAR2(maximum_length)      BOOLEAN           CHAR[(maximum_length)] DATE                         LONG              LONG RAW    BINARY_INTEGER                PLS_INTEGER       NUMBER(precision,scale) TIMESTAMP The %TYPE Attribute Identifier Table_name.column_name%TYPE ; Identifier Variable_name%TYPE ; Composite Datatypes INDEX BY TABLE          RECORD      NESTED TABLE      VARRAY LOB Datatypes CLOB        BLOB        BFILE             NCLOB Creating Bind Variables VARIABLE variable_name dataype Displaying Bind Variables PRINT [variable_name] NOTE: To reference a bind variable in PL/SQL, you must prefix it's name with colon (:) Commenting Code --prefix single-line comments with two dashes /* Place muti-line comment between the symbols */ SELECT Statements in PL/SQL SELECT {column_list|*} INTO {variable_name[,variable_name]...       |record_name} FROM table [WHERE condition]; NOTE: The INTO clause is must and queries must return one and only one row. A CURSOR can be used to retrieve more than one row. Implicit Cursor Attributes for DML statements SQL%ROWCOUNT SQL%FOUND SQL%NOTFOUND SQL%ISOPEN Control Structures IF Statement                              Basic Loop IF condition THEN                         LOOP    statements;                               statements; [ELSIF condition THEN                      ...    statements;]                              EXIT [WHEN condition]; [ELSE                                     END LOOP;    statements;] END IF; FOR Loop                                  WHILE Loop FOR counter IN [REVERSE]                  WHILE condition LOOP    Lower_bound..upper_bound LOOP             statement1;    statement1;                               statement2;    statement2;                               ...    ...                                    END LOOP; END LOOP; CASE CASE selector    WHEN expression1 THEN result1    WHEN expression2 THEN result2    ...    WHEN expressionN THEN resultN [ELSE resultN+1] END; Creating a PL/SQL Record TYPE type_name IS RECORD (field_declaration[,field_declaration]...) ; identifier type_name ; Where field_declaration is: field_name {field_type|variable%TYPE| table.column%TYPE|table%ROWTYPE} [[NOT NULL] {:=|DEFAULT} expr] Referencing Fields in the Record record_name.field_name Declaring Records with the %ROWTYPE Attribute DECLARE record_name       reference%ROWTYPE Creating a PL/SQL Table (INDEX BY Table) TYPE type_name IS TABLE OF {column_type|variable%TYPE|table.column%TYPE |variable%ROWTYPE} [NOT NULL] [INDEX BY BINARY_INTEGER]; identifier type_name ; Referencing a PL/SQL table pl_sql_table_name(primary_key_value) Using PL/SQL Table Method table_name.method_name[(parameters)] PL/SQL Table Methods EXITS(n)    COUNT       FIRST       LAST        PRIOR(n) NEXT(n)     EXTEND(n,i)             TRIM        DELETE PL/SQL Table of Records TYPE table_name_type IS TABLE OF table_name%ROWTYPE INDEX BY BINARY_INTEGER ; table_name table_name_type ; Referencing a Table of Records table_name(index).field Cursor Declaring the Cursor in Declaration Section CURSOR cursor_name IS select_statement ; record_name cursor_name%ROWTYPE ; Opening and Closing the Cursor OPEN cursor_name ; CLOSE cursor_name ; Fetching Data from the Cursor FETCH cursor_name INTO [variable1(,variable2,...)     |record_name] ; Explicit Cusor Attributes cursor_name%ISOPEN cursor_name%NOTFOUND cursor_name%FOUND cursor_name%ROWCOUNT Cursor FOR Loops FOR record_name IN cursor_name LOOP    statement1;    statement2;    ... END LOOP; Cursor FOR Loops Using Subqueries FOR record_name IN (subqueries) LOOP statement1 ... END LOOP ; Cursors with Parameters CURSOR cursor_name [(cursor_parameter_name datatype [,...])] IS select_statement [FOR UPDATE [OF column_reference][NOWAIT]]; Parameter Name cursor_parameter_name [IN] datatype [{:=|DEFAULT}expr] Openning with Parameters OPEN cursor_name(cursor_parameter_name[,...]); Cursor FOR Loops with parameters FOR record_name IN cursor_name(cursor_parameter_name [,...]) LOOP    statement1;    statement2;    ... END LOOP; WHERE CURRENT OF clause UPDATE|DELETE ... WHERE CURRENT OF cursor_name ; Predefined Exceptions NO_DATA_FOUND TOO_MANY_ROWS INVALID_CURSOR ZERO_DIVIDE DUP_VAL_ON_INDEX Exception Trapping Exceptions EXCEPTION    WHEN exception1 [OR exception2 ...] THEN statement1 ; statement2 ; ...    [WHEN exception3 [OR exception4 ...] THEN statement1 ; statement2 ; ...]    [WHEN OTHERS THEN statement1 ; statement2 ; ...] Declaring Non-Predefined Oracle Sever Exception DECLARE    exception EXCEPTION ;    PRAGMA EXCEPTION_INIT(exception, error_number) ; Referencing the declared Non-predefined execption BEGIN    ... EXCEPTION    WHEN exception THEN statement1 ; ... END ; Trapping User-Defined Exceptions DECLARE    exception EXCEPTION ; BEGIN    ...    IF SQL%NOTFOUND THEN RAISE exception ;    END IF ;    ... EXCEPTION    WHEN exception THEN statement1 ; ... END ; Functions for Trapping Exceptions SQLCODE           return error code SQLERRM           return error message RAISE_APPLICATION_ERROR procedure(Executable/Exception Section) RAISE_APPLICATION_ERROR ( error_number, message [, {TRUE|FALSE}]) ; error_number      between -20000 to -20999 message           string up to 2,048 bytes long TRUE              placed on the stack of previous errors. FALSE             replaces all previous errors

Oracle SQL Quick reference

admin — Wed, 24 Jun 2009 05:44:25 +0000

Tweet

Oracle SQL Quick Reference

SELECT Query Statement

SELECT [DISTINCT] {*, column [alias],…}

FROM table

WHERE condition(s)]

ORDER BY {column, exp, alias} [ASC|DESC]]

NOTE:

Avoid using DISTINCT with large table as it first does sorting of all the rows and then eliminates duplicate rows, so need a full table scan and thus it’s very slow.

ORDER BY is the last clause to get executed and thus could see all the column aliases; You can sort by a columns that is not in SELECT list; Default sorting order is Ascending (ASC)

Joins

Oracle proprietary syntax for version 8i and earlier

Cartesian Product

SELECT table1.*, table2.*,[...]

FROM table1,table2[,...]

Equijoin(Simple joins or inner join)

SELECT table1.*,table2.*

FROM table1,table2

WHERE table1.column = table2.column

Non-Equijoin

SELECT table1.*, table2.*

FROM table1, table2

WHERE table1.column

BETWEEN table2.column1 AND table2.column2

Outer join

SELECT table1.*,table2.*

FROM table1,table2

WHERE table1.column(+) = table2.column

SELECT table1.*,table2.*

FROM table1,table2

WHERE table1.column = table2.column(+)

Self join

SELECT alias1.*,alias2.*

FROM table1 alias1,table1 alias2

WHERE alias1.column = alias2.column

SQL: 1999 compliant syntax for version 9i

SELECT table1.column, table2.column

FROM table1

[CROSS JOIN table2] |

[NATURAL JOIN table2] |

[JOIN table2 USING (column_name)] |

[JOIN table2

ON (table1.column_name=table2.column_name)] |

[LEFT|RIGHT|FULL OUTER JOIN table2

ON (table1.column_name=table2.column_name)];

Aggregation Selecting

SELECT [column,] group_function(column),…

FROM table

[WHERE condition]

[GROUP BY group_by_expression]

[HAVING group_condition]

[ORDER BY column];

Group function

AVG([DISTINCT|ALL]n)

COUNT(*|[DISTINCT|ALL]expr)

MAX([DISTINCT|ALL]expr)

MIN([DISTINCT|ALL]expr)

STDDEV([DISTINCT|ALL]n)

SUM([DISTINCT|ALL]n)

VARIANCE([DISTINCT|ALL]n)

NOTE:

All columns in the SELECT list that are not in group functions must be in the GROUP BY clause; but GROUP BY column does not have to be in the SELECT list.

You can not use group functions in the WHERE clause;You use the HAVING clause to restrict groups.

All group functions except count(*) ignores null values. The NVL function forces group functions to include null values.

Subquery

SELECT select_list

FROM table

WHERE expr operator(SELECT    select_list

FROM      table);

NOTE:

The subquery(inner query) executes once before the main query

The result of the subquery is used by the main query(outer query)

The ORDER BY clause in the subquery is not needed unless you are performing TOP-N analysis.

single-row comparison operators: Return only one row

=        >     >=    <     <=    <>

multiple-row comparison operators: Return more than one row

IN         ANY             ALL

Multiple-column Subqueries

SELECT column, column, …

FROM table

WHERE (column, column, …) IN

(SELECT column, column, …

FROM table

WHERE condition);

Data Manipulation Statements (DML)

INSERT Statement(one row)

INSERT INTO table [ (column [,column...])]

VALUES (value [,value...]);

INSERT Statement with Subquery

INSERT INTO table [ column(, column) ]

subquery;

UPDATE Statement

UPDATE table

SET column = value [, column = value,...]

[WHERE condition];

Updating with Multiple-column Subquery

UPDATE table

SET (column, column,…) =

(SELECT column, column,…

FROM table

WHERE condition)

WHERE condition;

Deleting Rows with DELETE Statement

DELETE [FROM] table

[WHERE condition];

Deleting Rows Based on Another Table

DELETE FROM table

WHERE column = (SELECT column

FROM table

WHERE condition);

MERGE statement

MERGE INTO table_name table_aliase

USING (table|view|sub_query) alias

ON (join condition)

WHEN MATCHED THEN

UPDATE SET

col1 = col1_val,

col2 = col2_val

WHEN NOT MATCHED THEN

INSERT (column_list)

VALUES (column_values);

NOTE:

MERGE provides ability to conditionally update or insert data into a database table. It is useful in data warehousing applications. It avoids separate updates; increase performance and ease of use

Transaction Control Statements (TCL)

COMMIT;

SAVEPOINT name;

ROLLBACK [TO SAVEPOINT name];

Displaying table structure

DESC[RIBE] tablename

Data Definition Statemetns (DDL)

CREATE TABLE Statement

CREATE TABLE [schema.]table

(column datatype [DEFAULT expr] [,...]);

CREATE TABLE Statement with Subquery

CREATE TABLE [schema.]table

[(column, column...)]

AS subquery;

NOTE:

When a table is created using existing table except “NOT NULL” constraint, no other constraints are copied. If condition satisfied even rows are copied.

Datatype

VARCHAR2(size)    CHAR(size)        NUMBER(p,s)       DATE

LONG              CLOB              RAW               LONG RAW

BLOB              BFILE             ROWID

ALTER TABLE Statement

Adding columns

ALTER TABLE table_name

ADD (column datatype [DEFAULT expr]

[, column datatype]…);

Changing a column’s type, size and default value of a Table

ALTER TABLE table_name

MODIFY (column datatype [DEFAULT expr]

[, column datatype]…);

RENAMING table column: Supported by 9.2 and higher version only

ALTER TABLE table_name

RENAME column_name to new_column_name;

Dropping a column

ALTER TABLE table_name

DROP (column);

Dropping a Table

DROP TABLE table_name;

Changing the Name of an Object

RENAME old_name TO new_name;

Trancating a Table

TRUNCATE TABLE table_name;

Adding Comments to a Table

COMMENT ON TABLE table_name | COLUMN table.column

IS ‘text’;

Dropping a comment from a table

COMMENT ON TABLE table_name | COLUMN table.column IS ” ;

Data Dictionary

ALL_OBJECTS       USER_OBJECTS

ALL_TABLES        USER_TABLES

ALL_CATALOG       USER_CATALOG or CAT

ALL_COL_COMMENTS USER_COL_COMMENTS

ALL_TAB_COMMENTS USER_TAB_COMMENTS

Defining Constraints

CREATE TABLE [schema.]table

column datatype [DEFAULT expr][NOT NULL]

[column_constraint],…

[table_constraint][,...]);

Column constraint level

column [CONSTRAINT constraint_name] constraint_type,

Constraint_type

PRIMARY KEY REFERENCES table(column) UNIQUE

CHECK (condition)

Table constraint level(except NOT NULL)

column,…,[CONSTRAINT constraint_name]

constraint_type (column,…),

NOT NULL Constraint (Only Column Level)

CONSTRAINT table[_column...]_nn NOT NULL …

UNIQUE Key Constraint

CONSTRAINT table[_column..]_uk UNIQUE (column[,...])

PRIMARY Key Constraint

CONSTRAINT table[_column..]_pk PRIMARY (column[,...])

NOTE:

PRIMARY Key defined on more than column called ‘Composite Primary Key’ and to define composite primary key you need table level constraint as two columns are involved.

FOREIGN Key Constraint

CONSTRAINT table[_column..]_fk

FOREIGN KEY (column[,...])

REFERENCES table (column[,...])[ON DELETE CASCADE]

[ON DELETE SET NULL];

CHECK constraint

CONSTRAINT table[_column..]_ck CHECK (condition)

Adding a Constraint(except NOT NULL)

ALTER TABLE table_name

ADD [CONSTRAINT constraint_name ] type (column);

Adding a NOT NULL constraint

ALTER TABLE table_name

MODIFY (column datatype [DEFAULT expr]

[CONSTRAINT constraint_name_nn] NOT NULL);

Dropping a Constraint

ALTER TABLE table_name

DROP CONSTRAINT constraint_name;

ALTER TABLE table_name

DROP PRIMARY KEY | UNIQUE (column) |

CONSTRAINT constraint_name [CASCADE];

Disabling Constraints

ALTER TABLE table_name

DISABLE CONSTRAINT constraint_name [CASCADE];

Enabling Constraints

ALTER TABLE table_name

ENABLE CONSTRAINT constraint_name;

NOTE:

A UNIQUE or PRIMARY KEY index is automatically created if you enable a UNIQUE key or PRIMARY KEY constraint.

Data Dictionary

ALL_CONSTRAINTS        USER_CONSTRAINTS

ALL_CONS_COLUMNS        USER_CONS_COLUMNS

View

Creating or Modifying a View

CREATE [OR REPLACE] [FORCE|NOFORCE] VIEW view

[(alias[, alias]…)]

AS subquery

[WITH CHECK OPTION [CONSTRAINT constraint_name]]

[WITH READ ONLY [CONSTRAINT constraint_name]];

Top-N Analysis

SELECT [column_list], ROWNUM

FROM (SELECT [column_list]

FROM table_name

ORDER BY Top-N_column)

WHERE ROWNUM <= N;

Removing a View

DROP VIEW view;

SEQUENCE

CREATE SEQUENCE Statement

CREATE SEQUENCE sequence

[INCREMENT BY n]

[START WITH n]

[{MAXVALUE n| NOMAXVALUE}]

[{MINVALUE n| NOMINVALUE}]

[{CYCLE | NOCYCLE}]

[{CACHE [n|20]| NOCACHE}];

Pseudocolumns

sequence.NEXTVAL        sequence.CURRVAL

Modifying a Sequence (No START WITH option)

ALTER SEQUENCE sequence

[INCREMENT BY n]

[{MAXVALUE n| NOMAXVALUE}]

[{MINVALUE n| NOMINVALUE}]

[{CYCLE | NOCYCLE}]

[{CACHE [n|20]| NOCACHE}];

Removing a Sequence

DROP SEQUENCE sequence;

Index

Creating an Index

CREATE INDEX index

ON TABLE (column[,column]…);

Removing an Index

DROP INDEX index;

Synoym

CREATE [PUBLIC] SYNONYM synonym

FOR object;

Removing Synonyms

DROP SYNONYM synonym;

Data Dictionary

ALL_VIEWS                     USER_VIEWS

ALL_SEQUENCES                 USER_SEQUENCES

ALL_INDEXES                   USER_INDEXES

ALL_IND_COLUMNS               USER_IND_COLUMNS

System Privileges (DBA)       User System Privileges

CREATE USER                   CREATE SESION

DROP USER                     CREATE TABLE

DROP ANY TABLE                CREATE SEQUENCE

BACKUP ANY TABLE              CREATE VIEW

CREATE PROCEDURE

Creating Users

CREATE USER user

IDENTIFIED BY password;

Creating Roles

CREATE ROLE role;

Granting System Privileges

GRANT privelges[,...] TO user[,...];

GRANT privelges TO role;

GRANT role TO user[,...];

Changing Password

ALTER USER user IDENTIFIED BY new_password;

Dropping Users

DROP USER user [CASCADE];

Dropping Roles

DROP ROLE role;

Object Privileges

Object      Table       View        Sequence          Procedure

ALTER         X                        X

DELETE        X         X

EXECUTE                                                  X

INDEX         X

INSERT        X         X

REFERENCES   X

SELECT      X         X             X

UPDATE        X       X

Object Privileges

GRAND object_priv [(column)]

ON object

TO {user|role|PUBLIC}

[WITH GRANT OPTION];

Revoking Object Privileges

REVOKE {privilege [,privilege...] | ALL}

ON object

FROM {user[,user...]|role|PUBLIC}

[CASCADE CONSTRAINTS];

Data Dictionary

ROLE_SYS_PRIVS

ROLE_TAB_PRIVS                USER_ROLE_PRIVS

USER_TAB_PRIVS_MADE           USER_TAB_PRIVS_RECD

USER_COL_PRIVS_MADE           USER_COL_PRIVS_RECD

Database Links

CREATE [PUBLIC] DATABASE LINK link_name

[CONNECT TO user_name IDENTIFIED BY password]

USING connection_string;

Single-Row Functions

Character Functions

LOWER(column|expression)

UPPER(column|expression)

INITCAP(column|expression)

INSTR(column|expression,m)

CONCAT(column1|expression1,column2|expression2}

SUBSTR(column|expression,m,[n])

LENGTH(column|expression)

LPAD(column|expression,n,’string’)

RPAD(column|expression,n,’string’)

TRIM(‘character’ FROM column|expression)

REPLACE(‘string1′, ‘string_to_replace’,[replacement_string])

Number Functions

MOD(m,n)

ROUND(column|expression,n)

TRUNC(column|expression,n)

Date Functions

MONTHS_BETWEEN(date1,date2)

ADD_MONTHS(date,n)

NEXT_DAY(date,’char’)

LAST_DAY(date)

ROUND(date[,'fmt'])

TRUNC(date[,'fmt'])

Arithmetic with Dates

Add or subtract a number to or from a date for a resultant date value

Subtract two dates to find the number of days between those dates

Add hours to a date by dividing the number of hours by 24

Conversion Functions

TO_CHAR(number|date[,'fmt'])

TO_NUMBER(char[,'fmt'])

TO_DATE(char[,'fmt'])

NVL(expr1,expr2)

NVL2(expr1,expr2,expr3)

NULLIF(expr1,expr2)

COALESCE(expr1,expr2,…,exprn)

Conditional Expressions: Provide the use of IF-THEN-ELSE logic within a SQL statement.

DECODE(col|expr,search1,result1

[,search2,result2,...,]

[,default])

CASE expr WHEN comparision_expr1 THEN return_expr1

[WHEN comparision_expr2 THEN return_expr2

WHEN comparision_exprn THEN return_exprn

ELSE else_expr]

END

Nesting Functions

Single-row functions can be nested to any level

Nested functions are evaluated from deepest level to the least deep level

In below example, functions F1, F2 and then F3 gets executed

F3(F2(F1(col,arg1),arg2),arg3)

Operators

Arithmetic        *     /     +     -

Comparison        =     >     >=    <     <=    <> or ^= or ~= or !=

BETWEEN…AND…, IN(set), LIKE, IS NULL

Concatenation     ||

Logical           AND OR    NOT

Rules of Precedence

Order Evaluated         Operator

1 Arithmetic operators – multiplication and division(* /)

2 Arithmetic operators – Addition, subtraction and Concatenation operator ( + – || )

3 Comparison conditions

4 IS [NOT] NULL, LIKE, [NOT] IN

5 [NOT] BETWEEN

6 NOT logical condition; ** Exponentiation

7 AND logical condition

8 OR logical condition

Notes

1) Use ESCAPE identifier to search for the actual % and _ symbols (Here, % denotes zero or many characters and _ denotes one character in search condition )

Example: Get employee list having underscore (_) in last_name string

SELECT last_name

FROM EMPLOYEE

WHERE last_name LIKE ‘%\_%’ ESCAPE ‘\’;

2) DUAL is a dummy table you can use to view results from functions and calculations

3) SYSDATE is a function that returns: Date and Time

4) Inline view is a subquery with an alias that you can use within a SQL statement. A named subquery in the FROM clause of the main query is an example of an inline view. It is not a schema object.

Oracle SQL tuning tips

admin — Wed, 24 Jun 2009 05:21:03 +0000

Tweet

Oracle SQL Tuning Tips

consideration when writing an SQL statement is that it returns a correct result. The second is that it be the most efficient for a given situation. You can use many different SQL statements to achieve the same result. It is often the case that only one statement will be the most efficient choice in a given situation.

Remember that processing SQL is a sequence of Parse (syntax check and object resolution), Execution (required reads and writes), and Fetch (row results retrieved, listed, sorted, and returned). SQL “tuning” consists, quite simply, of reducing one or more of them.

Note: generally Parse is the greatest time and resource hog. Parse overhead can be minimized by the use of Procedures, Functions, Packages, Views, etc.

Inadequate performance can have a significant cost impact on your business. A poor performing system and application can result in customer dissatisfaction, reduced productivity, and high costs. It is absolutely critical that the system’s performance is operating at its peak levels.

Following are some general tips that often increase SQL statement efficiency. Being general they may not apply to a particular scenario.

Tuning SQL should only be done after your code is working correctly. Be aware that there is an inevitable tug-of-war between writing efficient SQL and understandable SQL.

Ensure repeated SQL statements are writtenabsolutely identicallyto facilitate efficient reuse: re-parsing can often be avoided for each subsequent use of an identical statement.
Writing best practices: all SQL verbs in upper-case i.e. SELECT; separate all words with a single space; all SQL verbs begin on a new line; SQL verbs aligned right or left within the initial verb; set and maintain a table alias standard; use table aliases and when a query involves more than one table prefix all column names with their aliases. Whatever you do, be consistent.

o Use bind variables: The values of bind variables do not need to be the same for two statements to be considered identical. Bind variables are not substituted until a statement has been successfully parsed.

o Use standard approach to table aliases. If two identical SQL statements vary because an identical table has two different aliases, then the SQL is different and will not be re-use or shared.

o Use table aliases and prefix all column names by their aliases when more than one table is involved in a query. This reduces parse time and prevents future syntax errors if someone adds a column to one of the tables with same name as a column in another table. (ORA-00918: COLUMN AMBIGUOUSLY DEFINED)

Code the query as simply as possible i.e. no unnecessary columns are selected, no unnecessary GROUP BY or ORDER BY.
It is the same or faster to SELECT by actual column name(s). The larger the table the more likely the savings.
Use:
SELECT customer_id, last_name, first_name, street, city FROM customer;
Rather than,
SELECT * FROM customer;

Beware of WHERE clauses which do not use indexes at all. Even if there is an index over a column that is referenced by a WHERE clause included in this section, Oracle will ignore the index. All these WHERE clause can be re-written to use an index while returning the same values. In other words, Do not perform operations on database objects referenced in the WHERE clause:
Use:
SELECT client, date, amount FROM sales WHERE amount > 0;
Rather than:
SELECT client, date, amount FROM sales WHERE amount != 0;
———————————————
Use:
SELECT account_name, trans_date, amount FROM transaction WHERE account_name LIKE ‘CAPITAL%’;
Rather than:
SELECT account_name, trans_date, amount FROM transaction WHERE SUBSTR(account_name,1,7)=‘CAPITAL’;
———————————————
Use:
SELECT account_name, trans_date, amount FROM transaction WHERE amount > 0;
Rather than:
SELECT account_name, trans_date, amount FROM transaction WHERE amount NOT=0;
———————————————
Use:
SELECT account_name, trans_date, amount FROM transaction WHERE amount < 2000;
Rather than:
SELECT account_name, trans_date, amount FROM transaction WHERE amount + 3000 < 5000;
———————————————
Use:
SELECT account_name, trans_date, amount FROM transaction WHERE account_name = ‘AMEX’ AND account_type = ‘A’;
Rather than:
SELECT account_name, trans_date, amount FROM transaction WHERE account_name|| account_type=‘AMEXA’;

Don’t forget to tune views. Views are SELECT statements and can be tuned in just the same way as any other type of SLECT statement can be. All tuning applicable to any SQL statement are equally applicable to views.

Avoid including a HAVING clause in SELECT statements. The HAVING clause filters selected rows only after all rows have been fetched. Using a WHERE clause helps reduce overheads in sorting, summing, etc. HAVING clauses should only be used when columns with summary operations applied to them are restricted by the clause.
Use:
SELECT city FROM country WHERE city!= ‘Vancouver’ AND city!= ‘Toronto’; GROUP BY city;
Rather than:
SELECT city FROM country GROUP BY city HAVING city!= ‘Vancouver’ AND city!= ‘Toronto’;

Minimize the number of table lookups (subquery blocks) in queries, particularly if our statements include subquery SELECTs or multicolumn UPDATEs.
Use:
SELECT emp_name FROM emp WHERE (emp_cat, sal_range) = (SELECT MAX(category), MAX(sal_range) FROM emp_categories) AND emp_dept = 0020;
Rather than:
SELECT emp_name FROM emp WHERE emp_cat=(SELECT MAX(category) FROM emp_categories) AND emp_range = (SELECT MAX(sal_range) FROM emp_categories) AND emp_dept = 0020;

When writing a sub-query (a SELECT statement within the WHERE or HAVING clause of another SQL statement):

o Use a correlated (refers to at least one value from the outer query) sub-query when the return is relatively small and/or other criteria are efficient i.e. if the tables within the sub-query have efficient indexes.

o Use a non-correlated (does not refer to the outer query) sub-query when dealing with large tables from which you expect a large return (many rows) and/or if the tables within the sub-query do not have efficient indexes.

o Ensure that multiple sub-queries are in the most efficient order.

o Remember that rewriting a sub-query as a join can sometimes increase efficiency.

When doing multiple table joins consider the benefits/costs for each of EXISTS, IN, and table joins. Depending on your data one or another may be faster.
Note: IN is usually the slowest.
Note: When most of the filter criteria are in the sub-query IN may be more efficient; when most of the filter criteria are in the parent-query EXISTS may be more efficient.
The following queries return the employee names from each department in department category ‘A’:
SELECT emp_name FROM emp E WHERE EXISTS (SELECT ‘X’ FROM dept WHERE dept_no = E.dept_no AND dept_cat = ‘A’);
———————————————
SELECT emp_name FROM emp E WHERE dept_no IN (SELECT dept_no FROM dept WHERE dept_no = E.dept_no AND dept_Cat = ‘A’);
———————————————
SELECT emp_name FROM dept D, emp E WHERE E.dept_no = D.dept_no AND D.dept_cat = ‘A’;

Where possible use EXISTS rather than DISTINCT, to avoid full table scan as DISTINCT operator causes Oracle to fetch all rows satisfying the table join and then sort and filter out duplicate values. EXISTS is a faster alternative, because the Oracle optimizer realizes when the subquery has been satisfied once, there is no need to proceed further and the next matching row can be fetched.
Use:
SELECT S.id, S.description FROM small_table S WHERE EXISTS (SELECT NULL FROM big_table B WHERE B.id = S.id);
Rather than:
SELECT DISTINCT S.id, S.description FROM small_table S, big_table B
WHERE S.id = B.id;

Where possible use a non-column expression (putting the column on one side of the operator and all the other values on the other). Non-column expressions are often processed earlier thereby speeding the query.
Use:
WHERE SALES < 1000/(1 + n);
Rather than:
WHERE SALES + (n * SALES) < 1000;

Where possible use UNION ALL rather than using UNION. The UNION clause forces all rows retuned by each portion of the UNION to be sorted and merged and duplicates to be filtered out before the first row is returned. A UNION ALL simply returns all rows including duplicates and does not have to perform any sort, merge or filter. If your tables are mutually exclusive(include no duplicate records), or you don’t care if duplicates are returned, the UNION ALL is much more efficient.
USE:
SELECT acct_num, balance_amt FROM debit_transactions WHERE tran_date = ’31-DEC-95′
UNION ALL
SELECT acct_num, balance_amt FROM credit_transactions WHERE tran_date = ’31-DE -95′;
Rather than:
SELECT acct_num, balance_amt FROM debit_transactions WHERE tran_date = ’31-DEC-95′
UNION
SELECT acct_num, balance_amt FROM credit_transactions WHERE tran_date = ’31-DE -95′;

Consider using DECODE to avoid having to scan the same rows repetitively or join the same table repetitively. Note, DECODE is not necessarily faster as it depends on your data and the complexity of the resulting query. Also, using DECODE requires you t change your code when new values are allowed in the field.
USE:
SELECT COUNT(DECODE(status,’Y',’X',NULL)) Y_count,
COUNT(DECODE(status,’N',’X',NULL)) N_count
FROM emp WHERE emp_name LIKE ‘SMITH%’;
Raher than:
SELECT COUNT(*) FROM emp WHERE status = ‘Y’ AND emp_name LIKE ‘SMITH%’;
———————
SELECT COUNT(*) FROM emp WHERE status = ‘N’ AND emp_name LIKE ‘SMITH%’;

Oracle automatically performs simple column type conversions(or casting) when it compares columns of different types. Depending on the type of conversion, indexes may not be used. Make sure you declare your program variables as the same type as your Oracle columns, if the type is supported in the programming language you are using.
Use:
SELECT emp_no, emp_name, sal FROM emp WHERE emp_no = ’123′;
HERE if emp_no indexed numeric, then after implicit conversion query will be:
SELECT emp_no, emp_name, sal FROM emp WHERE emp_no = TO_NUMBER(’123′);
Thus, index is used in this case.
Don’t use:
SELECT emp_no, emp_name, sal FROM emp WHERE emp_type = 123;
HERE if emp_type is indexed varchar2, then after implicit conversion query will be:
SELECT emp_no, emp_name, sal FROM emp WHERE TO_NUMBER(emp_type) = 123;
Thus, index will not be used in this case.

The most efficient method for storing large binary objects, i.e. multimedia objects, is to place them in the file system and place a pointer in the DB.

B-Tree Indexes do not store entries for NULL, so IS NULL is not indexable, but IS NOT NULL is indexable and thus if a huge table contains very few not null values then you should go for B-Tree indexes. On the other hand bitmap indexes support IS NULL condition.
SELECT * FROM big WHERE status IS NOT NULL; (Use B-tree index in this case)

Avoid using functions on indexed columns unless a function-based index is created; as it leads to full table scan even though index exists on the column.

Avoid using the following:

Boolean operators >, <, >=, <=, IS NULL, IS NOT NULL

NOT IN, !=

Like ‘%pattern’, not exists

Calculations on unindexed columns or (use union instead)

Having (use a WHERE clause instead when appropriate)

Do use the following:

Enable aliases to prefix all columns

Place indexed columns higher in the WHERE clause

Use SQL Joins instead of using sub-queries

Make the table with the least number of rows, the driving table, by making it first in the FROM clause

Other important points for SQL Tuning

Establish a tuning environment that reflects your production database

Establish performance expectations before you begin

Always Design and develop with performance in mind

Create Indexes to support selective WHERE clauses and join conditions

Use concatenated indexes where appropriate

Consider indexing more than you think you should, to avoid table lookups

Pick the best join method

Nested loops joins are best for indexed joins of subsets

Hash joins are usually the best choice for “big” joins

Pick the best join order

Pick the best “driving” table

Eliminate rows as early as possible in the join order

Use bind variables. Bind variables are key to application scalability

Use Oracle hints where appropriate

Compare performance between alternative syntax for your SQL statement

Consider utilizing PL/SQL to overcome difficult SQL tuning issues

Consider using third party tools to make the job of SQL tuning easier

Performing these steps is easy and provides a tremendous benefit and performance boost. Follow these simple steps and you can increase your system performance.

PLATFORM_ID	PLATFORM_NAME	ENDIAN_FORMAT
1	Solaris[tm] OE (32-bit)	Big
2	Solaris[tm] OE (64-bit)	Big
3	HP-UX (64-bit)	Big
4	HP-UX IA (64-bit)	Big
5	HP Tru64 UNIX	Little
6	AIX-Based Systems (64-bit)	Big
7	Microsoft Windows IA (32-bit)	Little
8	Microsoft Windows IA (64-bit)	Little
9	IBM zSeries Based Linux	Big
10	Linux IA (32-bit)	Little
11	Linux IA (64-bit)	Little
12	Microsoft Windows 64-bit for AMD	Little
13	Linux 64-bit for AMD	Little
14	HP Open VMS	Little
15	Apple Mac OS	Big