R12.1.3 EBS Database 11.2.0.2 Upgrade to 12c 12.1.0.2   1 comment

Server Configuration:
——————–
RAM:16GB
CPU’s-4
Operating System: OEL 5.5.
Oracle EBS Version: R12.1.3
Oracle EBS Database Version 11.2.0.2(Before Upgrade)

Ref: Interoperability Notes EBS 12.0 or 12.1 with RDBMS 12cR1 (Doc ID 1524398.1)

Apply Below ApplicationPatches:

If you already on R12.1.3 then non need to apply Patch 9239090 – Oracle E-Business Suite 12.1.3

Apply Patch 12923944
Apply Patch 13473483
Apply Patch 16289505 – 12c Release 1 interoperability patch for Release 12.1
Apply Patch 18843706
Apply Patch 19558309

Step1:Prepare to create the 12.1.0 Oracle home

-Install Oracle Software 12c
mkdir -p /d01/oracle/PROD/db/tech_st/12c
10-3-2014 11-07-52 AM

Download below patchsets for 12c database
p17694377_121020_Linux-x86-64_1of8.zip
p17694377_121020_Linux-x86-64_2of8.zip
p17694377_121020_Linux-x86-64_7of8.zip

Unzip and run the runInstaller

1

2

3

4

5

6

7

new

9

10

11

12

13

14

15

16

17

Step2: Install Examples CD

10-3-2014 11-31-36 AM

10-3-2014 11-31-55 AM

10-3-2014 11-32-10 AM

10-3-2014 11-32-25 AM

10-3-2014 11-32-34 AM

10-3-2014 11-32-50 AM

Step3:
Create nls/data/9idata directory

On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the following command to create the $ORACLE_HOME/nls/data/9idata directory.

$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

export ORACLE_HOME=/d01/oracle/PROD/db/tech_st/12c
export ORACLE_SID=PROD
export PATH=$ORACLE_HOME/bin:$PATH
export ORA_NLS10=/d01/oracle/PROD/db/tech_st/12c/nls/data/9idata
export PATH=$ORACLE_HOME/OPatch:$PATH

Step4:
Apply additional 12.1.0.2 RDBMS patches
Apply the following patches:
For all UNIX/Linux platforms:
Patch 19382851

Step5:Shut down Applications server processes and database listener

On each application tier server node, shut down all server processes or services. On the database tier server node, shut down the Oracle Net or Net8 database listener in the old Oracle home.

Note: The Applications will be unavailable to users until all remaining tasks in this section are completed.
Attention: Make sure that you do not have the LOCAL_LISTENER initialization parameter set to ensure that the database does not inadvertently point to a non-existent listener during upgrade.

Step6:Drop SYS.ENABLED$INDEXES (conditional)

If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it:

SQL> drop table sys.enabled$indexes;

Step6:
Remove the MGDSYS schema (conditional)

If you are upgrading from an RDBMS version prior to 12c, on the old database server node, use SQL*Plus to connect to the database as SYSDBA and run the $ORACLE_HOME/md/admin/catnomgdidcode.sql script. This drops the MGDSYS schema.
$ sqlplus “/ as sysdba” @?/md/admin/catnomgdidcode.sql

Step7:Prepare to upgrade

36C416DE-3E09-4430-9F5A-A5B153EC5135

Step8:
2

Step9:run dbua
3

1

2

3

Run FIX and Check Again…If there are any errors…….
4

5

6

7

8

9

10

11

12

13

Step10:
Compile the Invalids
14

Step11:
Run adgrants.sql

Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the administration server node to the database server node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command:

$ sqlplus “/ as sysdba” @adgrants.sql (or adgrants_nt.sql)
[APPS schema name]

1

2

3

Step12:
4

5

Step13:
6

7

Step14:
8

Step15:De-register Database and Implement Autconfig
9

Step16:
12

13

14

15

Run Autoconfig on the application side as well…..

Start the application tier services…..

16

17

This finishes the R12 EBS Database 11.2.0.2 to 12.1.0.2

Posted October 8, 2014 by balaoracledba.com in OracleAppsR12, Upgrade

How to create CustomTop in R12.2   2 comments

Here in this post i am going to list out the steps to create Custom Top in R12.2

I am using OEL5.5 with R12.2 EBS Database Version 11.2.0.3 and R12.2 Version of EBS.

Step 1: Create Tablespace
create tablespace XXERP datafile ‘xxerp01.dbf’ size 50M;


Step 2: Create USER
create user xxerp identified by xxerp default tablespace xxerp temporary tablespace temp quota unlimited on xxerp;


Step 3: Register your Custom Application
Login to Applications with System Administrator responsibility
Navigate to Application–>Register
Application = XXERP Custom Application
Short Name = XXERP
Basepath = XXERP_TOP
Description = XXERP Custom Application


Step 4: Register Oracle User
Navigate to Security–>Oracle–>Register
Database User Name = xxerp
Password = xxerp
Privilege = Enabled
Install Group = 0
Description = XXERP Custom Application User

In OAM use the following navigation path to add the custom entry : Oracle Applications Manager >> Site Map >> AutoConfig >> Manage Custom Parameters

1

 

 

2

 

 

3

 

 

4

5

6

7

8

9

 

10

 

11

12

 

 

14

 Note: For R12.2.x be sure autoconfig is only executed at the “Run File System”, the “Patch File system” will be configured the next time when a “Patching Cycle” is initiated

Optional: Below Steps are same as what we do in R12, Refer:http://balaoracledba.com/2013/10/30/custom-topapplication-creation-r12/


Step 5: Add Application to a Data Group
Navigate to Security->Oracle–>DataGroup
Data Group = XXERPGroup
Description = XXERP Custom Data Group
Application = XXERP Custom
Oracle ID = APPS
Description = XXERP Custom Application


Step 6: Create custom request group
Navigate to Security–>responsibility–>Request
Group = XXERP Request Group
Application = XXERP Custom
Code = XXERP
Description = XXERP Custom Requests


Step 7: Create custom menu
We will create two menus, one for Core Applications and one for Self Service.
Navigate to Application–>Menu
Menu = XXERP_CUSTOM_MENU
User Menu Name = XXERP Custom Application
Menu Type =
Description = XXERP Custom Application Menu
Seq = 100
Prompt = View Requests
Submenu =
Function = View All Concurrent Requests
Description = View Requests
Seq = 110
Prompt = Run Requests
Submenu =
Function = Requests: Submit
Description = Submit Requests
Menu = XXERP_CUSTOM_MENU_SSWA
User Menu Name = XXERP Custom Application SSWA
Menu Type =
Description = XXERP Custom Application Menu for SSWA

Step 8: Create new responsibility. One for Core Applications and One for Self Service (SSWA)
Navigate to Security–>Responsibility–>Define
Responsibility Name = XXERP Custom
Application = XXERP Custom
Responsibility Key = XXERPCUSTOM
Description = XXERP Custom Responsibility
Available From = Oracle Applications
Data Group Name = XXERPGroup
Data Group Application = XXERP Custom
Menu = XXERP Custom Application
Request Group Name = XXERP Request Group
Responsibility Name = XXERP Custom SSWA
Application = XXERP Custom
Responsibility Key = XXERPCUSTOMSSWA
Description = XXERP Custom Responsibility SSWA
Available From = Oracle Self Service Web Applications
Data Group Name = XXERPGroup
Data Group Application = XXERP Custom
Menu = XXERP Custom Application SSWA
Request Group Name = XXERP Request Group

Step 9: Add responsibility to user
Navigate to Security–>User–>Define
Add XXERP Custom responsibility to users as required.

Posted September 22, 2014 by balaoracledba.com in R12.2

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora   Leave a comment

Autoconfig Log shows below error

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora. [ID 1324667.1]

There is no information in the table FND_NODES for the database node.

This means that autoconfig has not been executed in the database tier or there was a problem
when it was executed in the database tier.
So you need to run autoconfig on the database tier to gather the information.

There is no database node declared in the FND_NODES table

To implement the solution, please execute the following steps:

1. Ensure that you have taken a backup of your system before applying the recommended solution.

2. Clean the Data Topology Model
Sqlplus apps/…
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

3. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers, to repopulate the required system tables

Posted September 4, 2014 by balaoracledba.com in OracleAppsR12

Output Post Processor is Down with Actual Process is 0 And Target Process is 1   Leave a comment

If you see OPP is Down with Actual Process is 0 And Target Process is 1 then do the following

1. Shutdown concurrent server via command adcmctl.sh under $COMMON_TOP/admin/scripts/<context_name>

3. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep applmgr | grep FNDLIBR

4. Run adadmin to relink FNDSVC executable.

a. Invoke adadmin from command prompt
b. Choose option 2 (2. Maintain Applications Files menu)
c. Choose option 1 (1. Relink Applications programs )
d. Then type “FND” When prompted; ( Enter list of products to link (‘all’ for all products) [all] : FND )
e. Ensure adrelink is exiting with status 0

5. Start Concurrent Managers using adcmctl.sh

Posted September 4, 2014 by balaoracledba.com in 11i/R12, OracleAppsR12

AutoConfig: Parallel Run Option on R12.1.1   Leave a comment

The “Parallel Run” feature enables AutoConfig to be executed simultaneously across multiple nodes of an Oracle E-Business Suite instance. Certain AutoConfig configurations of one node depend on the configurations of other nodes. When running in parallel mode, AutoConfig uses dbms_locks so that the configuration of one node does not interfere with the configuration of other nodes. During the instantiation (INST) phase, locking is done at the script level. During the execution (EXEC) phase, locking is done at the product_top level.

AutoConfig can be run in parallel mode on the application tier with the following command:

perl $AD_TOP/bin/adconfig.pl contextfile=<CtxFile> [product=<product_top>] –parallel

Where <CtxFile> is the absolute path of the applicaton tier context file, and <product_top> is the short name of the product to be configured.

AutoConfig can be run in parallel mode on the database tier with the following command:

perl $ORACLE_HOME/appsutil/bin/adconfig.pl contextfile=<CtxFile> -parallel

Where <CtxFile> is the absolute path of the database tier context file.

In parallel mode, AutoConfig must be invoked with the “–parallel” option on all nodes of a multi-node environment.

Posted September 4, 2014 by balaoracledba.com in 11i/R12, OracleAppsR12

Step By Step Upgrade from R12.2.0 to R12.2.4   6 comments

Details:

OS: Oracle Enterprise Linux-x64bit 

CPU’s-4

Memory:16GB

No. Of Nodes:1(Both DBTier and AppsTier on Single Node)

References:

1.Oracle E-Business Suite Release 12.2.4 Readme (Doc ID 1617458.1)

2.Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)

3.Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1)

4. Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

Step1: Apply Required Database Patches:

Review Metalink Note 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes, and apply all required patches for your database version.

As I installed my R12.2 with startCD Version 12.2.0.47, I have all the updates (patches) belongs to 12.2.0.47 for my Database 11.2.0.3 and other Application Technology Software. So I need to apply patches belongs to 12.2.0.48 and also 8-26-2014 12-06-19 PM

 

Footnote 6 – This database patch is no longer available. For a more recent version of this fix that also includes additional fixes, refer to Patch 19078951 and its associated footnote.

Footnote 8 – This database patch is required to support the latest AD and TXK release update packs, as described in My Oracle Support Knowledge Document 1617461.1Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2. If Patch 17502060 was installed, you should roll it back before installing Patch 17693770 from My Oracle Support.

Footnote 11 – If Patch 18259911 or Patch 17461865 was installed, you should roll it back before installing Patch 19078951 from My Oracle Support.

Before applying 17693770 patch on 11.2.0.3 DB Home, rollback 17502060, and apply 17693770.

Before applying 18116376 rollback 17047617

For patch 18259911 FOOTNOTE6  says that it is no longer available and we need to refer Patch 1907895. (We will apply this 19078951 after applying all patches)

Before Applying 17875948 rollback 16587934

Before applying 19078951 rollback 14751895, 1825991117461865

DONT FORGET TO PERFORM POST INSTALL STEPS FROM PATCH README’s

Click on this to get abstract for applying DB Patches on 11.2.0.3 Database Patches Applied on 11203

Step2: Let’s Apply Patches for 10.1.2 Oracle_Home(Forms Home)

21012

Step 3:Web Tier and Utilities (OHS) 11.1.1.6 Patches and Bug Numbers

—Only One Patch needs to be applied.

Click on the this link to get Abstract for applying patches on Webtier Utilities1116Patch_Abstract

Step4:Patches  for Oracle Fusion Middleware 11.1.1.6.0

FUnsion

 

Click on the this link to get Abstract for applying patches on Fusion Middleware OH FusionOH1116

Step4: Oracle Weblogic Server 10.3.6.0 Patch

Download and Unzip both the patches in the /d01/oracle/PROD/fs1/FMW_Home/utils/bsu/cache_dir

weblogic

weblogicdirectory

Open VNC and run bsu.sh 

 

bsu1

bsu2

 

In the Below Sceenshot click on Green Arrows pointing upwards doing so will apply patches on weblogic. Do it one after the other

bsu5

bsu3

bsu4

Step5: Apply below patch

If you haven’t already applied Consolidated Seed Table Upgrade Patch 17204589:12.2.0, then you must first apply Patch 17204589:12.2.0 on the run file system.

Note: If you have upgraded to Release 12.2.0 using Consolidated Upgrade Patch 18007406:12.2.0 (CUP5) or Consolidated Upgrade Patch 17197281:12.2.0 (CUP4), then you can skip this step.
Stop all Application tier services on the run file system.
sh $ADMIN_SCRIPTS_HOME/adstpall.sh
Start up only the Weblogic AdminServer service on the run file system.
$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
Apply the consolidated seed table upgrade Patch 17204589:12.2.0 on the run file system using adop hotpatch mode.
Copy the patch in /d01/oracle/PROD/fs_ne/EBSapps/patch

$ adop phase=apply patches=17204589 hotpatch=yes

firstpatch

 

Step 6:Apply the Latest AD and TXK Delta Release Update Packs

Download and unzip the following patches:

1.Run adgrants.sql first and apply the patch

adgrats

cp adgrants.sql from patch/admin directory to db tier and execute as below, this may take some time depends upon hardware.

adpatch1

adpatch2

 

Before upgrade Version of EBS:

before

Step 7:Apply Patch 19259764:R12.FND.C (conditional).

Note: This step is not applicable for new installation and upgrade customers who are applying the Oracle E-Business Suite Release 12.2.4 Release Update Pack.

$ adop phase=apply patches=19259764 hotpatch=yes

Step 8: Run fs_clone as below

  1. Source the run edition environment file.

    $ . <EBS_ROOT>/EBSapps.env run

  2. Synchronize the file systems (conditional)

    $ adop phase=fs_clone

Step 9:Path A from the metalink note 1617458.1- Upgrade and New Installation Customers upgrading to Oracle E-Business Suite 12.2.4 Release Update Pack

Source the run edition applications environment.

$ . <INSTALL_BASE>/EBSapps.env run

Stop Weblogic AdminServer and Node Manager services.

Applying the patch in downtime mode requires all application tier services to be down. Therefore, Weblogic AdminServer and Node Manager that were started previously when applying the latest Release Update Packs for AD and TXK for Release 12.2 need to be shut down.

Stop Weblogic AdminServer service on the run file system.

$sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

Stop Node Manager service on the run file system.

$sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

Apply Oracle E-Business Suite 12.2.4 Release Update Pack Patch 17919161 on the run edition application environment, using downtime mode.

$adop phase=apply apply_mode=downtime patches=17919161

Start all Application tier services on the run file system.

$sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

Perform adop cleanup action.

$adop phase=cleanup

Synchronize the file systems using the command shown below. This action will copy the new run edition code and configuration to the other file system, to ensure that both file systems are in sync before applying patches using the regular adop cycle on the other file system.

$ adop phase=fs_clone

Post-Update Steps

Note: If you are upgrading from Release 11i, 12.0.x or 12.1.x to Release 12.2.4, then you must continue with 12.2.0 post upgrade steps mentioned in the Upgrade guides before performing the below steps.
Apply Oracle E-Business Suite Release 12.2.4 Online Help

Apply Oracle E-Business Suite Release 12.2.4 Online Help Patch 17919162 merged with Patch 19290141 using adop hotpatch mode on the run file system.

$ adop phase=apply patches=17919162,19290141 hotpatch=yes merge=yes

This Finishes the R12.2.4 Upgrade from R12.2.0.

r124

New Feature

 

Let me know if anyone faces any issues in upgrading

 

Posted August 26, 2014 by balaoracledba.com in R12.2

Latest Updates to AD and TXK Tools for EBS 12.2   Leave a comment

Latest Updates to AD and TXK Tools for EBS 12.2

https://blogs.oracle.com/stevenChan/entry/latest_updates_to_ad_and?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+OracleE-BusinessSuiteTechnology+%28Oracle+E-Business+Suite+Technology%29

Posted July 22, 2014 by balaoracledba.com in R12.2

Follow

Get every new post delivered to your Inbox.

Join 480 other followers