Oracle Apps DBA

My Photo
More than 5+ Years of IT Experience in administering Enterprise wide Multi Vendor UNIX Servers, Oracle Databases (8i to 11gR2), Middle-tiers, Applications and Clusters. I am a Sun Certified System Administrator (SCSA) for Solaris 10, oracle 10g database certified associate(OCA), Oracle 10g Database certified professional (OCP) and Oracle E-Business suite R12 certified professionl(OCP)

Oracle Database and Applications

Monday, 27 October 2014

Updating bash shell on Oracle Solaris 11.2 without SRU update

Oracle will release periodic updates for Oracle Solaris Operating System packages as Support Repository Updates (SRU). The latest available SRU is "Oracle Solaris 11.2.3.4.1 Support Repository Update"

Each SRU contains updates for multiple packages. If you want to update a specific package then you need to use locking mechanism on packages.

This method will be helpful if customers are not willing to update full SRU Immediately. They can update individual packages according to their requirements and at later stage they can update the complete SRU.

In this demonstration we will update bash shell independently of SRU cycle.

Steps:

- Check Existing version of bash

root@soltest1:~# pkg list bash
pkg list bash
NAME (PUBLISHER)                                  VERSION                    IFO
shell/bash                                        4.1.11-0.175.2.0.0.42.1    i--


- Check for available updates

root@soltest1:~# pkg list -af shell/bash
pkg list -af shell/bash
NAME (PUBLISHER)                                  VERSION                    IFO
shell/bash                                        4.1.11-0.175.2.3.0.4.0     ---
shell/bash                                        4.1.11-0.175.2.2.0.8.0     ---
shell/bash                                        4.1.11-0.175.2.2.0.7.0     ---
shell/bash                                        4.1.11-0.175.2.0.0.42.1    i--
shell/bash                                        4.1.9-0.175.1.13.0.1.0     ---
shell/bash                                        4.1.9-0.175.1.0.0.24.0     ---
shell/bash                                        4.1.9-0.175.0.0.0.2.537    ---
shell/bash                                        4.0.28-0.151.0.1           ---
root@soltest1:~# 

Installed version - 4.1.11-0.175.2.0.0.42.1

- Check package contents and lock status

root@soltest1:~# pkg contents -m userland-incorporation | grep shell/bash
pkg contents -m userland-incorporation | grep shell/bash
depend facet.version-lock.shell/bash=true fmri=pkg:/shell/bash@4.1.11-0.175.2.0.0.42.1 type=incorporate


root@soltest1:~# pkg facet -a version-lock.shell/bash
pkg facet -a version-lock.shell/bash
FACET                                                            VALUE SRC
facet.version-lock.shell/bash                                    True  system
root@soltest1:~# 


-  Lets try to update bash/shell without changing its facet "lock" status

root@soltest1:~# pkg update shell/bash@4.1.11-0.175.2.3.0.4.0
pkg update shell/bash@4.1.11-0.175.2.3.0.4.0
Creating Plan (Solver setup): /
pkg update: No matching version of shell/bash can be installed:
  Reject:  pkg://solaris/shell/bash@4.1.11,5.11-0.175.2.3.0.4.0:20141002T223817Z
  Reason:  This version is excluded by installed incorporation pkg://solaris/consolidation/userland/userland-incorporation@0.5.11,5.11-0.175.2.0.0.42.1:20140623T010405Z
root@soltest1:~# 


It will not proceed as its not able to find the matching version of other packages.


- Change the facet value for shell/bash

root@soltest1:~# pkg change-facet -r version-lock.shell/bash=false
pkg change-facet -r version-lock.shell/bash=false
            Packages to change:   1
     Variants/Facets to change:   1
       Create boot environment:  No
Create backup boot environment: Yes
PHASE                                          ITEMS
Removing old actions                             1/1
Updating package state database                 Done 
Updating package cache                           0/0 
Updating image state                            Done 
Creating fast lookup database                   Done 
Updating package cache                           1/1 
root@soltest1:~# 




- Update shell/bash package with specific SRU release

root@soltest1:~# pkg update shell/bash@4.1.11-0.175.2.3.0.4.0
pkg update shell/bash@4.1.11-0.175.2.3.0.4.0
            Packages to update:   1
       Create boot environment:  No
Create backup boot environment: Yes
DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                                1/1           5/5      0.5/0.5 38.9k/s

PHASE                                          ITEMS
Removing old actions                             3/3
Installing new actions                           5/5
Updating modified actions                        3/3
Updating package state database                 Done 
Updating package cache                           1/1 
Updating image state                            Done 
Creating fast lookup database                   Done 
Updating package cache                           1/1 
root@soltest1:~# 



- Check the Installed version of shell/bash

root@soltest1:~# pkg list -af shell/bash
pkg list -af shell/bash
NAME (PUBLISHER)                                  VERSION                    IFO
shell/bash                                        4.1.11-0.175.2.3.0.4.0     i--
shell/bash                                        4.1.11-0.175.2.2.0.8.0     ---
shell/bash                                        4.1.11-0.175.2.2.0.7.0     ---
shell/bash                                        4.1.11-0.175.2.0.0.42.1    ---
shell/bash                                        4.1.9-0.175.1.13.0.1.0     ---
shell/bash                                        4.1.9-0.175.1.0.0.24.0     ---
shell/bash                                        4.1.9-0.175.0.0.0.2.537    ---
shell/bash                                        4.0.28-0.151.0.1           ---
root@soltest1:~# 


The shell/bash package has been updated. The facet value of the package cannot be changed until you update the full SRU.

After updating the full SRU and  rebooting system from the updated B.E. the facet value can be changed.


- Change the facet value

root@soltest1:~# pkg facet -a version-lock.shell/bash
FACET                                                            VALUE SRC
facet.version-lock.shell/bash                                    False local
root@soltest1:~# 


root@soltest1:~# pkg change-facet  version-lock.shell/bash=true
            Packages to change:   1
     Variants/Facets to change:   1
       Create boot environment:  No
Create backup boot environment: Yes
PHASE                                          ITEMS
Installing new actions                           1/1
Updating package state database                 Done 
Updating package cache                           0/0 
Updating image state                            Done 
Creating fast lookup database                   Done 
Updating package cache                           1/1 
root@soltest1:~# pkg facet -a version-lock.shell/bash
FACET                                                            VALUE SRC
facet.version-lock.shell/bash                                    True  local
root@soltest1:~# 


Same procedure is applicable for other packages as well. All packages can be updated individually without SRU cycle.

Thanks for reading.

regards,
X A H E E R



Friday, 24 October 2014

using start CD 12.2.0.48 with R12.2 Stage

In this article i will demonstrate how to use latest start CD with and existing Oracle E-Business suite R12.2 stage. Oracle released two versions of start CD since the announcement of Oracle EBS R12.2.

The base release of start CD is 12.2.0.46 then later it released 12.2.0.47 and 12.2.0.48. The start CD 12.2.0.48 is available to download via patch "18086193" .  The download of patch is only available to customers who has a valid and active support contract (CSI) account.

 This version of start CD include all bugs from the previous releases (12.2.0.46 & 12.2.0.47). Oracle Strongly recommends to use the latest version of start CD for fresh EBS Installation.

Steps:

1) Verify the version of existing start CD
2) Rename/delete the existing start CD directory
3) Download and copy the patch into the existing stage area
4) unzip the patch and verify the version of start CD


1) Verify the version of existing start CD:

Each start CD Disk contains executable "RapidWizVersion", it will display the version of existing startCD.


[root@erpnode2 rapidwiz]# pwd
/d01/R12.2_Stage/startCD/Disk1/rapidwiz
[root@erpnode2 rapidwiz]# ls
bin            driver  File    jlib  oui       RapidWiz.cmd  RapidWizVersion      TechInstallers  unzip
ClientWiz.cmd  etc     images  jre   rapidwiz  RapidWiz.ini  RapidWizVersion.cmd  template        Xpatches
[root@erpnode2 rapidwiz]# ./RapidWizVersion



Oracle E-Business Suite Rapid Install Wizard

Version 12.2.0.46

(c) Copyright 2000-2011 Oracle Corporation.  All rights reserved.



[root@erpnode2 rapidwiz]# 

 
2) Rename/delete the existing start CD directory

Rename or delete the existing start CD directory from the staging area. In my setup i just renamed it to startCD_46.

 3) Download and copy the patch into the existing stage area

login to support.oracle.com with a valid CSI account and download patch "18086193"

[root@erpnode2 startCD_122_48]# cp p18086193_R12_GENERIC.zip  /d01/R12.2_Stage 



4) unzip the patch and verify the version of start CD

- unzip the patch in the existing stage directory and patch will create new directory for startCD 

[root@erpnode2 R12.2_Stage]# ls
EBSInstallMedia  p18086193_R12_GENERIC.zip  startCD_46  TechInstallMedia  TechPatches
[root@erpnode2 R12.2_Stage]# unzip -o p18086193_R12_GENERIC.zip 


- Verify the version of startCD

Execute "RapidWizVersion" command from the new stratCD directory


[root@erpnode2 startCD]# cd Disk1/
[root@erpnode2 Disk1]# ls
doc  html  images  rapidwiz
[root@erpnode2 Disk1]# cd rapidwiz/
[root@erpnode2 rapidwiz]# ls
bin            driver  File    jlib  oui       RapidWiz.cmd  RapidWizVersion      TechInstallers  unzip
ClientWiz.cmd  etc     images  jre   rapidwiz  RapidWiz.ini  RapidWizVersion.cmd  template        Xpatches
[root@erpnode2 rapidwiz]# ./RapidWizVersion



Oracle E-Business Suite Rapid Install Wizard

Version 12.2.0.48

(c) Copyright 2000-2011 Oracle Corporation.  All rights reserved.



[root@erpnode2 rapidwiz]# 
[root@erpnode2 rapidwiz]# pwd
/d01/R12.2_Stage/startCD/Disk1/rapidwiz
[root@erpnode2 rapidwiz]# 




Conclusion:

Installation of Oracle E-Business suite with startCD R12.2.0.48 will install all bug fixes included in it. To know the bug fixes please refer patch readme.

startCD  12.2.0.48 contains maximum number of  bug fixes as of current date. If you are upgrading or planning to upgrade from R12.1 to R12.2.4 then it is recommended to use the latest version of startCD . It will make your upgrade process easier as you are not required to install all these patches individually,

Hope it helps :)

thanks,
X A H E E R


Monday, 13 October 2014

UPLOAD_SYSTEM Threshold (UploadMaxNumberXML: 5000) exceeded with 5698 files) EM 12c Agent

I was facing  Issues on Oracle Enterprise Manager cloud control agent with Error "UPLOAD_SYSTEM Threshold (UploadMaxNumberXML: 5000) exceeded with 5698 files)" for command "emctl status agent"

I tried to stop/start agent but failed to communicate with OMS Server.

This Issue occurred because of incorrect configuration of open files. You need to properly configure the value for open files. I encountered this Issue on Oracle Solaris 10 OS. This Issue can also be encountered on other unix/linux flavour .

Output for command "emctl status agent":

[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 12.1.0.2.0
OMS Version       : (unknown)
Protocol Version  : 12.1.0.1.0
Agent Home        : /oem/OEMAGENT/agent/agent_inst
Agent Binaries    : /oem/OEMAGENT/agent/core/12.1.0.2.0
Agent Process ID  : 23697
Parent Process ID : 23413
Agent URL         : https://oradb01:3872/emd/main/
Repository URL    : https://oemserver1.orasol.com:4901/empbs/upload
Started at        : 2014-10-12 08:49:40
Started by user   : oemagent
Last Reload       : (none)
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload           : 5,719
Size of XML files pending upload(MB)         : 5.48
Available disk space on upload filesystem    : 50.79%
Collection Status                            : [COLLECTIONS_HALTED(
  UPLOAD_SYSTEM Threshold (UploadMaxNumberXML: 5000) exceeded with 5698 files)]
Heartbeat Status                             : Agent is blocked
Last attempted heartbeat to OMS              : 2014-10-12 09:40:33
Last successful heartbeat to OMS             : (none)
Next scheduled heartbeat to OMS              : 2014-10-12 09:43:33

---------------------------------------------------------------
Agent is Running and Ready



Solution:

1) Stop agent
2) Increase ulimit value
3) unblock agent
4) start agent
5) upload to OMS
6) check agent status


1) Stop agent

[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ./emctl stop agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Stopping agent .......... stopped.


2) Increase ulimit value

- Current Value of open files:

[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ulimit -a
core file size        (blocks, -c) unlimited
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
open files                    (-n) 256
pipe size          (512 bytes, -p) 10
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) 29995
virtual memory        (kbytes, -v) unlimited 

- Increase Value of open files:


[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ulimit -n 65536
[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ulimit -a
core file size        (blocks, -c) unlimited
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
open files                    (-n) 65536
pipe size          (512 bytes, -p) 10
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) 29995
virtual memory        (kbytes, -v) unlimited
[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]#

3) unblock agent

Navigate to Setup >> Manage clound control >> agent >> 

- Select block agent and unblock target




4) start agent

[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ./emctl start agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Starting agent ........................................................................................................................... started but not ready.


5) upload to OMS

[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ./emctl upload

6) check agent status 

[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]# ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 12.1.0.2.0
OMS Version       : 12.1.0.2.0
Protocol Version  : 12.1.0.1.0
Agent Home        : /oem/OEMAGENT/agent/agent_inst
Agent Binaries    : /oem/OEMAGENT/agent/core/12.1.0.2.0
Agent Process ID  : 12790
Parent Process ID : 12532
Agent URL         : https://oradb01:3872/emd/main/
Repository URL    : https://oemserver1.orasol.com:4901/empbs/upload
Started at        : 2014-10-12 11:24:50
Started by user   : oemagent
Last Reload       : (none)
Last successful upload                       : 2014-10-12 11:35:14
Last attempted upload                        : 2014-10-12 11:35:14
Total Megabytes of XML files uploaded so far : 0.03
Number of XML files pending upload           : 146
Size of XML files pending upload(MB)         : 0.17
Available disk space on upload filesystem    : 50.83%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2014-10-12 11:35:06
Last successful heartbeat to OMS             : 2014-10-12 11:35:06
Next scheduled heartbeat to OMS              : 2014-10-12 11:36:06

---------------------------------------------------------------
Agent is Running and Ready
[oemagent@oradb01][/oem/OEMAGENT/agent/agent_inst/bin]#

Now the agent is successfully able to communicate with OMS and upload XML.

Thanks for reading.

regards,
X A H E E R