Thursday, December 26, 2013

sqlplus: error while loading shared libraries: /u01/app/oracle/product/11.1.0/db_1/lib/libnnz11.so: cannot restore segment prot after reloc: Permission denied

Immediately after a successful RDBMS installation (perhaps even including a sample DB instance creation), sqlplus will not start:
[oracle@test ~]$ sqlplus ‘/as sysdba’
sqlplus: error while loading shared libraries: /u01/app/oracle/product/11.1.0/db_1/lib/libnnz11.so: cannot restore segment prot after reloc: Permission denied
The reason is that SELinux is running in “enforcing” mode.
You can check it on file /etc/pam.d/login
Oracle development has recommended the following workaround while they correct the problem:
Switch SELinux from the default “Enforcing” mode that it is running in, to the “Permissive” mode.
Commands, as root:
======================
getenforce       (returns “Enforcing”)
setenforce 0
getenforce       (returns “Permissive”)
This allows SELinux to continue running, and logging denial messages, but SELinux will not actually deny any operations. Once Development has resolved this issue, you can (and should) return SELinux to the default “Enforcing” mode as follows:
Commands, as root:
======================
setenforce 1
getenforce       (returns “Enforcing”)



SOLUTION

This problem will help on RHEL 5
I simpally run
at root
getenforce
setenforce 0
getenforce

and the problem will solve…..
 

Sunday, December 22, 2013

How do I download and install 32-bit Java for Linux Platforms?

How do I download and install 32-bit Java for Linux Platforms?


This article applies to:
  • Platform(s): Red Hat Linux, SUSE Linux, Oracle Linux, Oracle Enterprise Linux, SLES
  • Java version(s): 6.0, 7.0

Linux System Requirements
See supported System Configurations for information about supported platforms, operating systems, desktop managers, and browsers.
You will also need a Pentium 166MHz or faster processor with a minimum of 75MB free disk space and a minimum of 64MB of RAM.

Note: For downloading Java other flavors of Linux see Java for Ubuntu, Java for Fedora


Follow these steps to download and install 32- bit Java for Linux.
  1. Download
  2. Install
  3. Enable and Configure
Download
  1. Go to http://java.com and click on the Download button
  2. There are two types of installation packages.
    • Java on Linux Platforms
      This is an archive binary file that can be installed by anyone (not only the root users), in any location that you can write to. However, only the root user can install Java into the system location.
    • Java on RPM-based Linux Platforms
      32-bit RPM-based Linux platforms, such as Red Hat and SuSE, use a RPM binary file (.rpm) in the system location. You must be root to perform this installation.

    Download the package that best suits your needs. You can download the file to any of the directories on your system.
  3. Download and check the download file size to ensure that you have downloaded the full, uncorrupted software bundle. Before you download the file, notice its byte size provided on the download page on the web site. Once the download has completed, compare that file size to the size of the downloaded file to make sure they are equal.



Install
Java for Linux Platforms
The instructions below are for installing version Java 7 Update 7 (7u7). If you are installing another version, make sure you change the version number appropriately when you type the commands at the terminal. Example: For Java 6u35 replace 7u7 with 6u35. Note that, as in the preceding example, the version number is sometimes preceded with the letter u, and sometimes it is preceded with an underbar, for example, jre1.7.0_07.

  1. Change to the directory in which you want to install. Type:
    cd <directory path name>
    For example, to install the software in the /usr/java/ directory, Type:
    cd /usr/java/

    Note about root access: To install Java in a system-wide location such as /usr/local, you must login as the root user to gain the necessary permissions. If you do not have root access, install the Java in your home directory or a sub directory for which you have write permissions
  2. Move the .tar.gz archive binary to the current directory.
  3. Unpack the tarball and install Java
    tar zxvf jre-7u7-linux-i586.tar.gz

    The Java files are installed in a directory called jre1.7.0_07 in the current directory.
    In this example, it is installed in the /usr/java/jre1.7.0_07 directory.
  4. Delete the .tar.gz file if you want to save disk space.

Java for RPM based Linux Platforms
The instructions below are for installing version Java 7 Update 7 (7u7). If you are installing another version, make sure you change the version number appropriately when you type the commands at the terminal. Example: For Java 6u35 replace 7u7 with 6u35. Note that, as in the preceding example, the version number is sometimes preceded with the letter u, and sometimes it is preceded with an underbar, for example, jre1.7.0_07.

  1. Become root by running su and entering the super-user password.
  2. Uninstall any earlier installations of the Java packages.
    rpm -e <package_name>
  3. Change to the directory in which you want to install. Type:
    cd <directory path name>
    For example, to install the software in the /usr/java/ directory, Type:
    cd /usr/java

  4. Install the package.
    rpm -ivh jre-7u7-linux-i586.rpm

    To upgrade a package,
    rpm -Uvh jre-7u7-linux-i586.rpm

  5. Delete the .rpm file if you want to save disk space.
  6. Exit the root shell. No need to reboot.
The installation is now complete. Go to the Enable and Configure section.


Enable and Configure
Firefox or Mozilla
To configure the Java Plugin follow these steps:
  1. Exit Firefox browser if it is already running.
  2. Uninstall any previous installations of Java Plugin.
    Only one Java Plugin can be used at a time. When you want to use a different plugin, or version of a plugin, remove the symbolic links to any other versions and create a fresh symbolic link to the new one.
  3. Create a symbolic link to the libnpjp2.so file in the browser plugins directory
    • Go to the plugins sub-directory under the Firefox installation directory
      cd <Firefox installation directory>/plugins
      Create plugins directory if it does not exist.
    • Create the symbolic link
      ln -s <Java installation directory>/lib/i386/libnpjp2.so

    Note: If you are upgrading your Java version then before creating new symbolic link you should remove old symbolic link to enable latest downloaded Java.

    To remove old symbolic link:
    type cd <Firefox installation directory>/plugins
    rm libjavaplugin_oji.so

    Example
    • If Firefox is installed at this directory:
      /usr/lib/<Firefox installation directory>
    • And if the Java is installed at this directory:
      /usr/java/<Java installation directory>
    • Then type in the terminal window to go to the browser plug-in directory:
      /usr/lib/<Firefox installation directory>/plugins
    • Enter the following command to create a symbolic link to the Java Plug-in for the Mozilla browser.
      ln -s /usr/java/<Java installation directory>/lib/i386/libnpjp2.so


  4. Start the Firefox browser, or restart it if it is already up.

    In Firefox, type about:plugins in the Location bar to confirm that the Java Plugin is loaded. You can also click the Tools menu to confirm that Java Console is there.

Test Installation
To test that Java is installed and working properly on your computer, run this test applet.

Monday, November 18, 2013

CLONING 11I APPS

Well, today my post is that another important and useful utility which apps dba perform quite often i.e. Cloning Oracle Application 11i Instance. Cloning is the act of creating an identical copy of an already existing Oracle Applications system for Test/Development instances.
Simply copying all of the components from source to target system does not provide us a working Oracle Applications system, there are various configuration files that must be changed & for this purpose we do Cloning. Do keep in mind that the new system & the existing system must have same component versions & operating system type (You can’t clone from windows to linux or Solaris).
Performing Cloning prerequisites steps:
We need to perform certain prerequisites steps before cloning the source system:
STEP 1. Login as Applications file user & run the environment file.
STEP 2. We need to check certain software component versions:
(i) Check the version of perl, it should be atleast 5.005 or above.
To check perl version, Type the following command-
$ perl -v
Make sure that perl is included in the PATH (environment variable of user; echo $PATH).
(ii) Check the version of JRE & JDK which should be atleast 1.1.8 & 1.3.1 or above respectively. for this type:
$ java -version
(iii) Check the version of zip which should be atleast 2.3 or above.for this type :
$ zip
If you don’t have following versions, upgrade these software components as per the operating system.
STEP 3: It is recommendedto apply the latest AD Minipack & the latest AutoConfig Template patch as mentioned in the metalink note 230672.1 but not necessary.
STEP 4: Then we check whether latest Rapid Clone patch is there or not, for this we query the database whether latest Rapid Clone patch and other prerequisite patches as mentioned in the metalink document 230672.1 as follows:
$ select * from AD_BUGS where bug_number='number';
If it shows ” no rows selected ” that means you need to apply the patch. Do ensure that you apply all the patches as per the requirement.
STEP 5: If your system is autoconfig enable configure the application tier by running the adautocfg.sh script as follows:
$ cd $COMMON_TOP/admin/scripts/CONTEXT_NAME/
$adautocfg.sh
If your system is not autoconfig enable then set up the autoconfig on application tier with the help of metalink document 165195.1 ( Migrating to AutoConfig on the Applications Tier).
NOTE:

  • To check whether your system is AutoConfig enable or not , open any configuration file, if you see the text “This file is automatically generated by AutoConfig….”at the top,this mean your system is autoconfig enabled.
  • Also all the applications after 11.5.7 are autoconfig enabled.
STEP 6:Now we set up AutoConfig on the database tier. For this we need to copy AutoConfig to the RDBMS ORACLE_HOME as follows:
• login as Applmgr . Set up the environment file & create appsutil.zip file in AD_TOP by typing the following command:
$ perl $AD_TOP/bin/admkappsutil.pl
This creates appsutil.zip in the $APPL_TOP/admin/out directory.
• Now login as Oracle on the database tier & copy the appsutil.zip file to the and unzip it:
$ cd
$ cp $APPL_TOP/admin/out/appsutil.zip
$ unzip -o appsutil.zip (Option -o will overwrite any existing appsutil directory in database ORACLE_HOME)
Now run AutoConfig on the database tier:
$ cd /appsutil/scripts//adautocfg.sh

difference between Rollup patch and family pack

Rollup patches are usually cumulative collections of one-off patches for an individual product.
Family pack patches are collections of patches for a set of related products (a product family).

Rollup patches are usually smaller than family pack patches, and therefore take less time to apply.
Family pack can patches often contain or supersede related rollup patches. However, because they have broader impact, family pack patches are usually released less frequently than rollup patches.


 Rollup Patch (RUP): An aggregation of patches that may be at the functional level, or at a specific product/family release level. For example, a Flexfields rollup patch contains all the latest patches related to Flexfields at the time the patch was created. A Marketing Family 11.5.10 rollup patch contains all the latest Marketing patches released since, and applicable to 11.5.10

Family Pack: An aggregation of patches at the product family level. Family product codes always end in "_PF" and family packs are given alphabetical sequence such as 11i.HR_PF.B, 11i.HR_PF.C, and 11i.HR_PF.D. Family packs are cumulative. In other words, Discrete Manufacturing Family Pack G (11i.DMF_PF.G) contains everything in 11i.DMF_PF.F, which contains everything in 11i.DMF_PF.E, and so on.

If you search the rollup patch thru Metalink, it would tell you whether it is included in any other patchset (i.e. Family Pack) or not.


anything that encompasses more a group of applications/products is a family pack. For example, a Financials Family Pack could have files/updates/bug fixes for GL, AP, AR, etc. but a AP rollup patch will have it for AP only.

In addition to this if you run patchsets.sh, you will get a very good idea of how Oracle separates these ou

How to find log files locations in 11i and R12

How to find log files locations in 11i and R12




The following log files location could help you to find-out issues and errors from your application 11i instance.

Database Tier Logs are

Alert Log File location:
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

Trace file location:
$ORACLE_HOME/admin/SID_Hostname/udump

Application Tier Logs

Start/Stop script log files location:
$COMMON_TOP/admin/log/CONTEXT_NAME/ 

OPMN log file location
$ORACLE_HOME/opmn/logs/ipm.log

Apache, Jserv, JVM log files locations:
$IAS_ORACLE_HOME/Apache/Apache/logs/ssl_engine_log
$IAS_ORACLE_HOME/Apache/Apache/logs/ssl_request_log
$IAS_ORACLE_HOME/Apache/Apache/logs/access_log
$IAS_ORACLE_HOME/Apache/Apache/logs/error_log
$IAS_ORACLE_HOME/Apache/JServ/logs

Concurrent log file location:
$APPL_TOP/admin/PROD/log or $APPLLOG/$APPLCSF

Patch log file location:
$APPL_TOP/admin/PROD/log

Worker Log file location:
$APPL_TOP/admin/PROD/log

AutoConfig log files location:
Application Tier:
$APPL_TOP/admin/SID_Hostname/log//DDMMTime/adconfig.log

Database Tier:
$ORACLE_HOME/appsutil/log/SID_Hostname/DDMMTime/adconfig.log

Error log file location:
Application Tier:
$APPL_TOP/admin/PROD/log

Database Tier :
$ORACLE_HOME/appsutil/log/SID_Hostname



In Oracle Applications R12, the log files are located in $LOG_HOME (which translates to $INST_TOP/logs)
Below list of log file locations could be helpful for you:

Concurrent Reqeust related logs
$LOG_HOME/appl/conc - > location for concurrent requests log and out files
$LOG_HOME/appl/admin - > location for mid tier startup scripts log files

Apache Logs (10.1.3 Oracle Home which is equivalent to iAS Oracle Home - Apache, OC4J and OPMN)
$LOG_HOME/ora/10.1.3/Apache - > Location for Apache Error and Access log files
$LOG_HOME/ora/10.1.3/j2ee - > location for j2ee related log files
$LOG_HOME/ora/10.1.3/opmn - > location for opmn related log files

Forms & Reports related logs (10.1.2 Oracle home which is equivalent to 806 Oracle Home)
$LOG_HOME/ora/10.1.2/forms
$LOG_HOME/ora/10.1.2/reports

Startup/Shutdown Log files location:
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log

Patch log files location:
$APPL_TOP/admin/$SID/log/ 

Clone and AutoConfig log files location in Oracle E-Business Suite Release 12 

Logs for the adpreclone.pl are located: 
On the database tier: 
RDBMS $ORACLE_HOME/appsutil/log/< context >/StageDBTier_< timestamp >.log 

On the application tier: 
$INST_TOP/admin/log/StageAppsTier_< timestamp >.log 

Where the logs for the admkappsutil.pl are located? 
On the application tier: 
$INST_TOP/admin/log/MakeAppsUtil_< timestamp >.log 

Logs for the adcfgclone.pl are located:

On the database tier: 
RDBMS $ORACLE_HOME/appsutil/log/< context >/ApplyDBTier_< timestamp >.log 

On the application tier: 
$INST_TOP/admin/log/ApplyAppsTier_< timestamp >.log 
Logs for the adconfig are located: 

On the database tier: 
RDBMS $ORACLE_HOME/appsutil/log/< context >/< timestamp >/adconfig.log 
RDBMS $ORACLE_HOME/appsutil/log/< context >/< timestamp >/NetServiceHandler.log 

On the application tier: 
$INST_TOP/admin/log/< timestamp >/adconfig.log 
$INST_TOP/admin/log/< timestamp >/NetServiceHandler.log

Cheers!

Cloning Oracle Application 11.5.9 system

Cloning Oracle Application 11.5.9 system

These are the basic cloning steps for any version.
The output will be a little different with a new version, for examle: java versions will be different and the location of the logs and adclone scripts will be diffrent, but it's all basically the same. You clone the database then the Apps tier.

Cloning
DB Tier

 

Make sure you run exec FND_CONC_CLONE.SETUP_CLEAN; on the new database after it's created
  1. The term source system refers to the production system and the term target system refers to the development or test system that is to be refreshed/cloned.
  2. Copy the Source System to the Target System
    Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed.  Ensure the application tier files copied to the target system are owned by the target APPLMGR user, and that the database tier files are owned by the ORACLE user.
    1. Copy the application tier file system
      Log on to the source system application tier nodes as the APPLMGR user.
      • Shut down the application tier server processes
      • Copy the following application tier directories from the source node to the target application tier node:
        • <APPL_TOP>
        • <COMMON_TOP>/html
        • <COMMON_TOP>/java
        • <COMMON_TOP>/util
        • <COMMON_TOP>/clone
        • <806 ORACLE_HOME>
        • <iAS ORACLE_HOME>
    2. Copy the database tier file system
      Log on to the source system database node as the ORACLE user.
      • Copy the database (DBF) files from the source to the target system
      • Copy the source database ORACLE_HOME to the target system
  1. Configure the Target System
    Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, etc)

    1. Configure the target system database server
      Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
         cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
         perl ./adcfgclone.pl dbTier
    2. Please note choose the pool set to be <database port > -1 eg:IF you need 1522 for your database tns port then choose port pool set 1.
Typical output
Enter the APPS password [APPS]:
APPS
First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
Provide the values required for creation of the new Database Context file. Hit enter to use the default value in brackets [].
Do you want to use a virtual hostname for the target node (y/n) [n] ?:
Target system database SID [PROD]:TEST
Target system domain name [advisor.com]:
Target system RDBMS ORACLE_HOME directory [/u02/oracle/proddb/9.2.0]:/u02/oracle/testdb/9.2.0
Target system utl_file accessible directories list [/usr/tmp/PROD]:/usr/tmp/TEST
Number of DATA_TOP's on the target system [4]:
Target system DATA_TOP 1 [/u03/oracle/proddata]:/u03/oracle/testdata
Target system DATA_TOP 2 [/u04/oracle/proddata]:/u04/oracle/testdata
Target system DATA_TOP 3 [/u05/oracle/proddata]:/u05/oracle/testdata
Target system DATA_TOP 4 [/u06/oracle/proddata]:/u06/oracle/testdata
Do you want to preserve the Display set to seouldb1:0.0 (y/n) [y] ?:
Clone Context uses the same port pool mechanism as the Rapid Install
Once you choose a port pool, Clone Context will validate the port availability.
Enter the port pool number [0-99]:
1
Checking the port pool 1
done: Port Pool 1 is free
Database port is 1522
Backing up /u02/oracle/testdb/9.2.0/appsutil/TEST_seouldb1.xml to /u02/oracle/testdb/9.2.0/appsutil/TEST_seouldb1.xml0.bak
Creating the new Database Context file from :
/u02/oracle/testdb/9.2.0/appsutil/template/adxdbctx.tmp
The new database context file has been created :
/u02/oracle/testdb/9.2.0/appsutil/TEST_seouldb1.xml
Log file located at /u02/oracle/testdb/9.2.0/appsutil/clone/bin/CloneContext_11020154.log
Running Rapid Clone with command:
perl ./adclone.pl java=./../jre/1.3.1 mode=apply stage=/u02/oracle/testdb/9.2.0/appsutil/clone/bin/.. component=dbTier metho
d=CUSTOM dbctxtg=/u02/oracle/testdb/9.2.0/appsutil/TEST_seouldb1.xml  showProgress contextValidated=true
Beginning database tier Apply - Tue Nov  2 01:55:12 2004
Log file located at /u02/oracle/testdb/9.2.0/appsutil/log/TEST_seouldb1/ApplyDBTier_11020155.log

Completed Apply...
Tue Nov  2 01:59:08 2004
Beginning APPSDB_TEST registration to central inventory...
ORACLE_HOME NAME   : APPSDB_TEST
ORACLE_HOME PATH   : /u02/oracle/testdb/9.2.0
INVENTORY LOCATION : /var/opt/oracle/oraInst.loc
Log file located at /u02/oracle/testdb/9.2.0/logs/OracleHomeCloner_11020159.log
Starting database listener for TEST:
Running:
/u02/oracle/testdb/9.2.0/appsutil/scripts/TEST_seouldb1/addlnctl.sh start TEST
You are running addlnctl.sh version 115.3
Starting listener process TEST ...
Listener TEST has already been started.
addlnctl.sh: exiting with status 0


Cloning Apps Tier
Apps Tier
    1. Finishing Tasks
      • Update profile options
        • Site name
        • Default printer if applicable
      • Update printer settings
      • Update workflow configuration settings – if applicable
Verify the APPLCSF variable setting
    1. Configure the target system application tier server nodes
      Log on to the target systems as the APPLMGR user and type the following commands:
               cd <COMMON_TOP>/clone/bin
          perl ./adcfgclone.pl appsTier
Typical output
Enter the APPS password [APPS]:
apps
First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:

Provide the values required for creation of the new APPL_TOP Context file.
Do you want to use a virtual hostname for the target node (y/n) [n] ?:
Target system database SID [PROD]:TEST
Target system domain name [advisors.hal]:
Target system database server node [seouldb1]:
Does the target system have more than one application tier server node (y/n) [n] ?:
Is the target system APPL_TOP divided into multiple mount points (y/n) [n] ?:
Target system APPL_TOP mount point [/u01/oracle/prodappl]:/u01/oracle/testappl
Target system COMMON_TOP directory [/u03/oracle/prodcomn]:/u03/oracle/testcomn
Target system 8.0.6 ORACLE_HOME directory [/u01/oracle/prodora/8.0.6]:/u01/oracle/testora/8.0.6
Target system iAS ORACLE_HOME directory [/u01/oracle/prodora/iAS]:/u01/oracle/testora/iAS
Do you want to preserve the Display set to seouldb1:0.0 (y/n) [y] ?:
Location of JDK 1.3.1 on the target system [/usr/j2se]:
Clone Context uses the same port pool mechanism as the Rapid Install
Once you choose a port pool, Clone Context will validate the port availability.
Enter the port pool number [0-99]:
1
Checking the port pool 1
done: Port Pool 1 is free
Web Listener port is 8001
Complete port information available at /u01/oracle/testappl/admin/out/TEST_seouldb1/portpool.lst
Backing up /u01/oracle/testappl/admin/TEST_seouldb1.xml to /u01/oracle/testappl/admin/TEST_seouldb1.xml.bak
Creating the new APPL_TOP Context file from :
/u01/oracle/prodappl/ad/11.5.0/admin/template/adxmlctx.tmp
The new APPL_TOP context file has been created :
/u01/oracle/testappl/admin/TEST_seouldb1.xml
Log file located at /u03/oracle/testcomn/clone/bin/CloneContext_11020246.log
Running Rapid Clone with command:
perl ./adclone.pl java=./../jre/1.3.1 mode=apply stage=/u03/oracle/testcomn/clone/bin/.. component=appsTier method=CUSTOM ap
pctxtg=/u01/oracle/testappl/admin/TEST_seouldb1.xml  showProgress contextValidated=true
Beginning application tier Apply - Tue Nov  2 02:48:06 2004
Log file located at /u01/oracle/testappl/admin/TEST_seouldb1/log/ApplyAppsTier_11020248.log
/     50% completed       WARNING: AutoConfig completed with errors. Check logfile at /u01/oracle/testappl/admin/TEST_seouldb1/log
/ApplyAppsTier_11020248.log for details.

Completed Apply...
Tue Nov  2 02:57:52 2004
Beginning APPSIAS_TEST registration to central inventory...
ORACLE_HOME NAME   : APPSIAS_TEST
ORACLE_HOME PATH   : /u01/oracle/testora/iAS
INVENTORY LOCATION : /var/opt/oracle/oraInst.loc
Log file located at /var/opt/oracle/oraInventory/logs/OracleHomeCloner_11020258.log
ORACLE_HOME /u01/oracle/testora/iAS was registered successfully.
Starting application Services for TEST:
Running:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adstrtal.sh APPS/<appspwd>
You are running adstrtal.sh version 115.14
Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adapcctl.sh start
script returned:
****************************************************
adapcctl.sh version 115.43
Starting Apache Web Server Listener (dedicated HTTP) ...
Starting Apache Web Server Listener (dedicated PLSQL) ...
adapcctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adalnctl.sh start
script returned:
****************************************************
adalnctl.sh version
Checking for FNDFS executable.
Starting listener process APPS_TEST.
adalnctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adcmctl.sh start
script returned:
****************************************************
You are running adcmctl.sh version 115.19
Starting concurrent manager for TEST ...
Starting TEST_1102@TEST Internal Concurrent Manager
Default printer is noprint
adcmctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adfrmctl.sh start
script returned:
****************************************************
You are running adfrmctl.sh version 115.33
Starting forms server for TEST on port 9001.
adfrmctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adrepctl.sh start
script returned:
****************************************************
You are running adrepctl.sh version 115.20
starting Reports Server for TEST on port 7001.
adrepctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adfmcctl.sh start
script returned:
****************************************************
You are running adfmcctl.sh version 115.16
Starting forms load balancing client for TEST.
adfmcctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/adfmsctl.sh start
script returned:
****************************************************
You are running adfmsctl.sh version 115.12
starting forms  metrics server for TEST.
adfmsctl.sh: exiting with status 0

.end std out.
****************************************************

Executing service control script:
/u03/oracle/testcomn/admin/scripts/TEST_seouldb1/jtffmctl.sh start
script returned:
****************************************************
You are running jtffmctl.sh version 115.7
Starting Fulfillment Server for TEST on port 9301 ...
jtffmctl.sh: exiting with status 0

.end std out.

Check logfile /u03/oracle/testcomn/admin/log/TEST_seouldb1/11020258.log for details
Exiting with status 0
    1. Finishing Tasks
      • Update profile options
        • Site name
        • Default printer if applicable
      • Update printer settings
      • Update workflow configuration settings – if applicable
Verify the APPLCSF variable setting

Saturday, October 19, 2013

error in invoking target 'all_no_orcl ihsodbc' of makefile

error in invoking target 'all_no_orcl ihsodbc' of makefile



I'm installing Oracle 10.2.0 on RHEL 4 ES. The Linux runs on VMWare 1.0.5. The Virtual Machine has 800 Mb of RAM, and 12Gb of hard drive space (/dev/sda).When I was running the Oracle Universal Installer, I got the following error message:
error in invoking target 'all_no_orcl ihsodbc' of makefile '/rman/oracle/product/10.2.0/rdbms/lib/ins_rdbms.mk
I was wounder what happen actually. i investigate the error log.. two library files are missing, so OUI not able to link files..

'/rman/oracle/product/10.2.0/rdbms/lib/ins_rdbms.mk'.See '/u01/app/oracle/oraInventory/logs/installActions2009-11-14_06-41-37PM.log'
solution

Install the following rpm

compat-libstdc++-296-2.96-132.7.2.i386.rpm
compat-libstdc++-33-3.2.3-47.3.i386.rpm

note: check all mandatory rpm before install..

Friday, September 27, 2013

Oracle Apps: Oracle Alerts

Oracle Apps: Oracle Alerts

What are Oracle Alerts?
A: Oracle Alerts monitor your Database information and notify you when the condition that you have specified is found. You can define Alerts in any Oracle application or custom Oracle application. Some applications (Purchasing, for example) supply Alerts that Can simply be activated and used. There are two type of Alerts, Event and Periodic.
Event Based Alerts : These Alerts are fired/triggered based on some change in data in the database.
Ex: If u want to notify your manager when you create an item in the inventory you can use event based alerts. When you create an item in the inventory it will cretae a new record in mtl_system_items_b, here inserting a record in the table is an event so when ever a new record is inserted it will send the alert.In same alert you can also send the information related to that particular item
Periodic Alerts : These Alerts are triggered hourly,daily, weekly, monthly or yearly based on your input.
Ex: If you want to know list of items created on that day at the end of day you can use periodic alerts repeating periodically by single day.This alert is not based on any chages to database.this alert will notify you everyday regardless of data exists or not that means even if no items are created you wil get a blank notification.
Q: What types of actions can be generated when an Alert is triggered?
A: When an alert is triggered or the event is true, the alert can Email a Message, Submit a concurrent program request, Run a SQL statement Script or Run an operating system script.
Q: Can I build an Alert to run with my custom applications or tables?
A: Event or Periodic Alerts can work with any custom application, as long as the application is properly registered within the Oracle Applications package.
Q:  Which Email packages work with Alerts?
A: Oracle Alert is designed to work with Oracle Office, Oracle Interoffice, UNIX Send mail, and VMS Mail.
Q:  Can Alerts be triggered by other Tools? (i.e. other than Oracle Forms and concurrent programs)
A: Oracle Alerts can only be triggered from an application that has been registered in Oracle Applications. Alerts cannot be triggered via SQL updates or deletes to an Alert activated trigger.
Q:  What is Response Processing?
A: Response processing is a component of Alerts which allows the recipients of an alert to reply with a message and have the applications take some action based on the response. Response Processing only works with Oracle Mail Products.
Q:  Do I need Oracle Applications to use Alerts?
Answer——No. The following are the only components required to use Oracle Alerts. The components must be certified versions for your hardware platform and operating system.
-RDBMS
- SQL*PLUS
- FORMS
- ORACLE MAIL product (i.e. Oracle Office or InterOffice
Q: How to create an Alert?
A:
1.Study your Business requirement and decide what type of alert you need either periodic alert or event based alert.
2. If you are going for periodic alert decide the frequency.
3. If you have chosen event based alert then find out on what event(insert,update) you want to fire the alert.
4. Decide what data need to be included in the alert.
5. Based on the data you want in the alert write a SELECT SQL statement to pull the data.
6. Create a distribution list grouping all the people to whom you want to send the alert.
Creating and Testing a Event Alert in Oracle EBS / Apps
In following example I will create an Alert which will send email to  specific email ID when ever any body update or create new employee in Employee Master.
Defining an Alert :
1.  Responsibility  –> Alert Manager.
2.  Naviate to the Alerts Window.
Alert –> Define
3.  Define a Period Alert:
Application = Human Resources
Name =  xxscc_test1
Enable = Selected.
4.    Event
Application  = Human Resources
Table  = PER_ALL_PEOPLE_F
5.   Enter the following SQL statement.
select employee_number
into &emp_numfrom
per_all_people_f where rowid=:rowid



6. Verify, to check whether the syntax written is correct.
7. Save
8. Define Alert Actions:
Action Name :  send_email_notification


8. Define Action Details:
Click on Action Details Button
TO :   Give you email ID here.      Note : You can also put here also bind variable with &email if that taken in select statement.
Subject :  Give Subject of you Email.
Text :  hello this is test email &emp_num

9- Define Action Sets
Click on Action Sets Button.
Action Set Name =  Send Email Test
Go to Action Set Details –> Members.
Action =  send_email_notification  as shown bellow.

10- Define Operating Unit
Click on Alert Details Button from first Alert Window.
Navigate to Installation Tab.
Operating Unit = for me  it is  FS_OU


11- Save.
Now if you Update or Create New Employee you will received notification in given email ID.

Oracle Database Upgrade – 11gR1 (11.1.0.6) to 11gR2 (11.2.0.1)

Oracle Database Upgrade – 11gR1 (11.1.0.6) to 11gR2 (11.2.0.1)

Oracle Database Upgrade - 11gR1 (11.1.0.6) to 11gR2 (11.2.0.1)

11.1.0.1.0

11 - Major database release number
 1 - Database maintenance release number
 0 - Application server release number
 1 - Component specific release number
 0 - Platform specific release number   

http://www.oracle.com/technology/software/products/database/index.html

1. Make sure the source environment is in stable state:
    11.1.0.6 Startup Database
    Alert log location: $ORACLE_BASE/diag/rdbms/aitmr93w/aitmr93w/trace

2. Download the 11gR2 software into the stage from where it needs to be installed.

3. Oracle Database Pre-installation Requirements

Checking the Hardware Requirements:-

The system must meet the following minimum hardware requirements:

1. Memory Requirements
    1. At least 1 GB of RAM
    # grep MemTotal /proc/meminfo

    2. Determine the size of the configured swap space
    # grep SwapTotal /proc/meminfo

    The following table describes the relationship between installed RAM and the configured swap space requirement:
    |-------------------------------------------------------|
    |RAM                                     |   Swap Space                         |
    |-------------------------------------------------------|
    |Between 1 GB and 2 GB    |   1.5 times the size of RAM |
    |Between 2 GB and 16 GB  |   Equal to the size of RAM  |
    |More than 16 GB                |   16 GB                                   |
    |-------------------------------------------------------|

    3. To determine the available RAM and swap space, enter the following command:
    # free

2. System Architecture
    # uname -m

3. Disk Space Requirements
    1. At least 1 GB of disk space in the /tmp directory
    # df -h /tmp

    If the free disk space available in the /tmp directory is less than what is required,
    then complete one of the following steps:

    a) Delete unnecessary files from the /tmp directory to meet the disk space
    requirement.
    b) Set the TMP and TMPDIR environment variables when setting the oracle
    user’s environment.

    2. To determine the amount of free disk space on the system, enter the following command:
    # df -h

    The following tables describe the disk space requirements for software files,
    and data files for each installation type on Linux x86:

    Installation Type     Requirement for Software Files (GB)
    Enterprise Edition     3.95
    Standard Edition     3.88

    Installation Type     Disk Space for Data Files (GB)
    Enterprise Edition     1.7
    Standard Edition     1.5

Checking the Software Requirements:-

1. Operating System & Kernel Requirements
    Oracle Enterprise Linux 4 Update 7
    Oracle Enterprise Linux 5 Update 2

    To determine the distribution and version of Linux installed, enter the following command:
    # cat /proc/version
    Alternatively, you can also enter the following command on some distributions of Linux:
    # lsb_release -id

    Oracle Enterprise Linux 4, and Red Hat Enterprise Linux 4:
    2.6.9 or later
    Oracle Enterprise Linux 5, and Red Hat Enterprise Linux 5:
    2.6.18 or later

    # uname -r

2. Package Requirements
    On Linux x86: Package Requirements
    rpm -q binutils-2.15.92.0.2
    rpm -q compat-libstdc++-33-3.2.3
    rpm -q elfutils-libelf-0.97
    rpm -q elfutils-libelf-devel-0.97
    rpm -q gcc-3.4.6
    rpm -q gcc-c++-3.4.6
    rpm -q glibc-2.3.4-2.41
    rpm -q glibc-common-2.3.4
    rpm -q glibc-devel-2.3.4
    rpm -q glibc-headers-2.3.4
    rpm -q libaio-devel-0.3.105
    rpm -q libaio-0.3.105
    rpm -q libgcc-3.4.6
    rpm -q libstdc++-3.4.6
    rpm -q libstdc++-devel-3.4.6
    rpm -q make-3.80
    rpm -q numactl-0.6.4.i386
    rpm -q pdksh-5.2.14
    rpm -q sysstat-5.0.5
    rpm -q unixODBC-2.2.11
    rpm -q unixODBC-devel-2.2.11

3. Compiler Requirements
    Linux-PAM Library
    Install the latest Linux-PAM (Pluggable Authentication Modules for Linux) library to
    enable the system administrator to choose how applications authenticate users.

    Setting the ORACLE_HOSTNAME Environment Variable
    In Bourne, Bash, or Korn shell:
    $ ORACLE_HOSTNAME=somehost.us.example.com
    $ export ORACLE_HOSTNAME

4. Install 11gR2 (11.2.0.1) Software only

    4.1 Entry into the "oratab" ...
    /etc/oratab -- <ORACLE_SID>:<ORACLE_BASE>/db/11.1:N

    Note: Kindly use local inventory than central as we wont be having access to use central

    4.2 ./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc &
    Where the oraInst.loc should have the below entries
    [ For installation on ems6678 otherwise modify it accordingly]

    inst_group=dba;
    inventory_loc=$ORACLE_BASE/db/oraInventory

    Note: Click on "Ignore All" if there are any swap space failures

    Installation Log: $ORACLE_BASE/db/oraInventory/logs/installActions2010-05-06_11-55-10PM.log

5. Pre-Upgrade steps:

    5.1 Executing Pre-Upgrade Tool:
    Before you start the upgrade process, to identify these checks.
        5.1.1 Copy utlu112i.sql from 11gR2 OH i.e $ORACLE_BASE/db/11.2/rdbms/admin
        to $HOME [ Assuming 11gR2 is Installed $ORACLE_BASE/db/11.2 ]
        5.2.2 Login as SYSDBA
        SQL> SPOOL $HOME/UpgDir/upgrade_info.log
        SQL> @utlu112i.sql
        SQL> SPOOL OFF

    Review the log file and take necesary actions. Then continue with upgrade.

    5.2 Correcting the Warnings [if any] found in above step

        5.2.1 WARNING : Database is using an old time zone file version. After the upgrade,
        patch the database time zone file version using DBMS_DST package to record latest time zone file version.
        Sol: From Webiv Note: 815679.1
        * For 11.1.0.6 and 11.1.0.7, after the upgrade to 11.2.0.1
        use DBSM_DST to update to DSTv11 by following <<Note 977512.1>>
        Updating the RDBMS DST version in 11gR2 (11.2.0.1 and up) using DBMS_DST

        5.2.2 Database contains stale optimizer statistics.
        EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
        [OR]
        EXEC DBMS_STATS.DELETE_SCHEMA_STATS('SYS');

        5.2.3 WARNING: --> SYSTEM schema default tablespace has been altered.
        .... The SYSTEM schema default tablespace is currently set to TOOLS.
        .... Prior to upgrading your database please reset the
        .... SYSTEM schema default tablespace to SYSTEM  using the command:
        .... ALTER USER SYSTEM DEFAULT TABLESPACE SYSTEM;
        5.2.4. WARNING:--> recycle bin in use.
        .... Your recycle bin turned on.
        .... It is REQUIRED
        .... that the recycle bin is empty prior to upgrading
        .... your database.
        .... The command:  PURGE DBA_RECYCLEBIN
        .... must be executed immediately prior to executing your upgrade.

    5.3 Shutdown 11gR1 Database

    5.4 Configuring 11gR2 Instance
        5.4.1 Source 11gR2 instance
        5.4.2 Copy parameter file form pfile location to 11gR2/dbs
            Change Parameters
            ------------------------
            *.compatible='11.2.0'
            shared_pool_size increase to 298MB [as suggested -- 325058560]
            user_dump_dest        -- REMOVE
            background_dump_dest  -- REMOVE
            core_dump_dest        -- REMOVE

6. Upgrading Database

    6.1 Prepare Upgrade
        6.1.1 cd $ORACLE_HOME/rdbms/admin
        6.1.2 Login as SYSDBA
            sqlplus '/ as sysdba'
            startup upgrade
            SPOOL upgrade.log
            @catupgrd.sql

7. Post-Upgrade steps:

    7.1 Post-Upgrade Tool
    Run utlu112s.sql to display the results of the upgrade:
        SQL> SPOOL $HOME/UpgDir/postupgrade_status.log
        SQL> @utlu112s.sql

        Oracle Database 11.2 Post-Upgrade Status Tool           05-07-2010 01:08:37
        Component                                Status         Version  HH:MM:SS
        Oracle Server                            VALID      11.2.0.1.0  00:14:38
        Oracle Text                              VALID      11.2.0.1.0  00:00:36
        Gathering Statistics                                            00:02:59
        Total Upgrade Time: 00:18:15

    PL/SQL procedure successfully completed.

    7.2 Post-Upgrade Actions
    Run catuppst.sql, located in the ORACLE_HOME/rdbms/admin directory, to
    perform upgrade actions that do not require the database to be in UPGRADE mode:
        SQL> SPOOL $HOME/UpgDir/postupgrade_status.log
        SQL> @catuppst.sql

    7.3 Compiling Invalid Objects:
    Compiling Ivalid objects:
        SQL> SPOOL $HOME/UpgDir/Compile_Invalid.log
        SQL> @utlrp.sql
        SQL> SPOOL OFF

    7.4 Updating the RDBMS DST version in 11gR2 (11.2.0.1 and up) -- Webiv Note 977512.1
    Oracle 11.2.0.1 has by default all RDBMS DST updates from DSTv1 to DSTv11 included in the software installation.
    These files are found in $ORACLE_HOME/oracore/zoneinfo and have a prefix indicating the DST version.

        7.4.1 check current RDBMS DST version and "DST UPGRADE STATUS".
            conn / as sysdba
            SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
            FROM DATABASE_PROPERTIES
            WHERE PROPERTY_NAME LIKE 'DST_%'
            ORDER BY PROPERTY_NAME;

            Check that the output gives

            -- PROPERTY_NAME VALUE
            -- ------------------------------ ------------------------------
            -- DST_PRIMARY_TT_VERSION <the old DST version number>
            -- DST_SECONDARY_TT_VERSION 0
            -- DST_UPGRADE_STATE NONE

            -- DST_PRIMARY_TT_VERSION should match the value found when selecting

        7.4.2 SELECT version FROM v$timezone_file;
            VERSION
            ----------
            4

        7.4.3 Do the actual RDBMS DST version update of the database
            7.4.3.1 Change DB into Upgrade Mode
                conn / as sysdba
                shutdown immediate;
                startup upgrade;
                set serveroutput on
                purge dba_recyclebin;

            7.4.3.2 Clean used tables
                TRUNCATE TABLE SYS.DST$TRIGGER_TABLE;
                TRUNCATE TABLE sys.dst$affected_tables;
                TRUNCATE TABLE sys.dst$error_table;

            7.4.3.3 start upgrade window
                EXEC DBMS_DST.BEGIN_UPGRADE(<the new DST version number>);
                SQL> EXEC DBMS_DST.BEGIN_UPGRADE(11);

                SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
                FROM DATABASE_PROPERTIES
                WHERE PROPERTY_NAME LIKE 'DST_%'
                ORDER BY PROPERTY_NAME;

                SELECT OWNER, TABLE_NAME, UPGRADE_IN_PROGRESS FROM ALL_TSTZ_TABLES where UPGRADE_IN_PROGRESS='YES';

            7.4.3.4 Restart the Database
                shutdown immediate
                startup
                set serveroutput on

            7.4.3.5 Upgrade the tables who need action
                VAR numfail number
                BEGIN
                DBMS_DST.UPGRADE_DATABASE(:numfail,
                parallel => TRUE,
                log_errors => TRUE,
                log_errors_table => 'SYS.DST$ERROR_TABLE',
                log_triggers_table => 'SYS.DST$TRIGGER_TABLE',
                error_on_overlap_time => FALSE,
                error_on_nonexisting_time => FALSE);
                DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail);
                END;
                /

                VAR fail number
                BEGIN
                DBMS_DST.END_UPGRADE(:fail);
                DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail);
                END;
                /

            7.4.3.6 Verify the Timezone Upgrade
                SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
                FROM DATABASE_PROPERTIES
                WHERE PROPERTY_NAME LIKE 'DST_%'
                ORDER BY PROPERTY_NAME;

                SELECT * FROM v$timezone_file;

8. Miscellaneous Database Checkups
    8.1 Database, Datafile and Backup

        select name,open_mode,log_mode,database_role,force_logging,flashback_on from v$database;
        select * from v$recover_file;
        select distinct status,count(*) from v$datafile group by status;
        select name, RECOVER from v$datafile_header where RECOVER != 'NO';
        select name, ERROR from v$datafile_header where ERROR is NOT NULL;
        select name, ts# from v$datafile where upper(name) like '%MISSING%';
        select NAME, FILE# from v$datafile where status='RECOVER';
        select status,count(*) from v$backup group by status;

    8.2 DBA Registry

        set lines 150 pages 500
        column COMP_NAME format a45
        column version format a15
        column status format a12
        select comp_name,version,status from dba_registry;

    8.3 DBA Registry History

        set lines 150 pages 500
        column action format a15
        column namespace format a15
        column comments format a20  wrap
        column ACTION_TIME format a30
        col BUNDLE_SERIES format a12
        column version format a15
        select * from dba_registry_history;