APPSINFODB – Information Technology Group

Finding Solutions for DBA's to smile…….!!!!!!! DBA its just not Administration, its core of customer’s data integrity

  • Blog Stats

    • 38,065 hits
  • Visitors

    free counters
  • Vistors Access

  • Calendar

    November 2017
    M T W T F S S
    « Dec    
     12345
    6789101112
    13141516171819
    20212223242526
    27282930  
  • Archives

  • Authors

Archive for the ‘Troubleshooting’ Category

Not able to cancel concurrent request & Unable to activate CM after cloning

Posted by appsinfo on August 20, 2012

Below are the two issues that I have faced after cloning from production

Q: How to terminate a concurrent request that cannot be cancelled

1.  Identify the request number to terminate.

2.  Shut down the concurrent managers and issue the following sql command as applsys:

            update fnd_concurrent_requests  set status_code = ‘E’, phase_code = ‘C’  where Request_id = <reqnum>; (reqnum = request number)

Q: A Manager is not activating.         

Check the count in sys.dual, system.dual, & apps.fnd_dual. There should only be one (1) row for each. 
If the count is greater, change to one only. This can be done from sqlplus as  follows:

    As user apps:
                   select * from SYS.DUAL;

    Any extra rows should be deleted.

                   delete rownum from SYS.DUAL; (rownum = the row number to delete)

    Any extra rows for apps.fnd_dual must be removed by performing the following SQL command:

                 delete from fnd_dual where rownum < (select max(rownum) from fnd_dual);

**For more on concurrent managers you can refer to FAQ (Concurrent Manager Unix specific Note ID: 105101.1)**

Advertisements

Posted in Cloning, E-Business Suite 11i, E-Business Suite R12, Troubleshooting | Tagged: | Leave a Comment »

ORA-07445: exception encountered: core dump [expepr()+00f4]

Posted by appsinfo on March 20, 2010

Troubleshooting

OS Platform: Linux 5 – 64 Bit

Database: 11.0.7.1

Problem: Incident: ORA-07445: exception encountered: core dump [expepr()+00f4]

You can see this error  in alert<sid>.log file

Reference Note Id: 986731.1

Cause:

This error is occurring due to bug 7327166

Solution:

Apply Patch 7327166

$ opatch apply
Invoking OPatch 11.1.0.6.9

Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation.  All rights reserved.

Oracle Home       : /u02/orauat/uat/db/tech_st/11.1.0
Central Inventory : /u02/orauat/uat/db/tech_st/11.1.0/admin/oui/uat_macaw/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.9
OUI version       : 11.1.0.7.0
OUI location      : /u02/orauat/uat/db/tech_st/11.1.0/oui
Log file location : /u02/orauat/uat/db/tech_st/11.1.0/cfgtoollogs/opatch/opatch2010-03-20_10-19-59AM.log

Patch history file: /u02/orauat/uat/db/tech_st/11.1.0/cfgtoollogs/opatch/opatch_history.txt

ApplySession applying interim patch ‘7327166’ to OH ‘/u02/orauat/uat/db/tech_st/11.1.0’

Running prerequisite checks…

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = ‘/u02/orauat/uat/db/tech_st/11.1.0’)

Is the local system ready for patching? [y|n] y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch ‘7327166’ for restore. This might take a while…
Backing up files affected by the patch ‘7327166’ for rollback. This might take a while…

Patching component oracle.rdbms, 11.1.0.7.0…
Updating archive file “/u02/orauat/uat/db/tech_st/11.1.0/lib/libserver11.a”  with “lib/libserver11.a/qmxtr2.o”
Running make for target ioracle
ApplySession adding interim patch ‘7327166’ to inventory

Verifying the update…
Inventory check OK: Patch ID 7327166 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 7327166 are present in Oracle Home.

The local system has been patched and can be restarted.

OPatch succeeded.

Posted in Troubleshooting | Leave a Comment »

Application Tier adstrtal.sh and adstpall.sh not working

Posted by appsinfo on February 27, 2010

Not able to start Application Tier using  adstrtal.sh and adstpall.sh, however each individual script was working fine

ERROR:

2/24/10-12:41:23 :: adstrtal.sh: Database connection could not be established. Either the database is down or the APPS credentials supplied are wrong.
USAGE:  adstrtal.sh <appsusername/appspassword>

I raised SR still not able to get the solution.

1.  Stop All services one by one  and  run  autoconfig, however this also didnt worked out.

Solution:

Diagnose as last change was with OS patches that there were some Linux OS security updates and fixes that was applied.  However the server was not restarted. I restared the server and then both adstrtal.sh and adstpall.sh were working fine.

Still exact reason havent been figured out.

Posted in Troubleshooting | 2 Comments »

Enable “About this Page” R12

Posted by appsinfo on February 15, 2010

How to Turn On “About This Page” in Oracle R12 Web Forms

Set Following Profile Options as Required at User or Site (System Administrator -> profile)

Personalize Self-Service Defn = YES

FND: Personalization Region Link Enabled = YES

Disable Self-Service Personal = NO (Only at Site)

FND: Diagnostics = Yes

Bounce the Apache Server

Login to Application you can see the About This Page Link on all web pages

By Using About This Page link you can have almost all information of technology Stack

Posted in Troubleshooting | Leave a Comment »

Unable to Create AME Approval Rules

Posted by appsinfo on June 13, 2009

AME Approval defining rules problem

Problem: Users are not able to create the approval rules for all the transactions using Approvals Management Business Analyst.       

Error: Contact system administrator, when enabled debugging the error was standard java error, further  enabled low level debugging using FND: Diagnostics and Jserv.properties file.  The end date was error out with different date format.

 Solution:

 Modified the date parsing logic, which is error out on production, with different date format.

 1. download and apply the Patch # 8593940 in your Test Environment first.

 2. Go through the Readme and Instructions for applying the patch before applying it in the Test Environment.

 3. Make sure that you have HRMS Family Pack K RUP3(6699770) OR Oracle Approvals Management B RUP2 (5708576) 

                Refer to the following links for additional information

                   a) Oracle HRMS Product Family – Release 11i Information

                       http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=135266.1          

                   b) HRMS Patch Install Frequently Asked Questions

                       http://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=130369.1

 4. Ensure you are logged in as applmgr.

 5. Before applying this patch make sure that your Oracle Applications  environment has been set up. Make sure that your $PAY_TOP and   $PER_TOP environment variables have been setup correctly.

 6. After application of these prerequisites you must apply the patch by running adpatch for the driver files in the following order:

       u8593940.drv (This is the unified driver)

 7. Run adadmin to:

       Compile Apps Schemas

 8. POST-INSTALLATION STEPS: 

                 ( Check the adpatch log files for errors (search for the words “error” and “FAILED”) 

                   Type of Log File              Log File Name

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

                   Log file from unified driver  Name entered when running adpatch

                   Log file from worker files    “adworkxx.log” (“xx” = “01””02″ etc.)           

9. To ensure that there are no invalid AME objects, after recompiling the APPS

   schema look for invalid packages with ‘AME_%’, there should not be any.

Posted in Troubleshooting | Leave a Comment »