“How To Do” in Oracle Apps? - Oracle Application DBA Flipbook PDF

“How To Do” in Oracle Apps? How to Relink Oracle Database Software ... How To Do in Oracle Apps Author: SAIBABA Created

---

145 Views
66 Downloads
FLIP PDF 318.16KB

DOWNLOAD FLIP

REPORT DMCA

Author – A.Kishore/Sachin http://appsdba.info

“How To Do” in Oracle Apps? 

How to Relink Oracle With : CONTEXT_PARAMS="diag=Y wait=N" Save the file.  Steps for enable the Debug Service Login with System Administrator responsibility Navigate to Concurrent -> Manager->Define Query manager with name "Debug Service" Tick the "Enabled" checkbox if not yet ticked Click Save button. Once completed the above steps, required to bounce the concurrent managers cd $COMMON_TOP/admin/scripts/SID_HOSTNAME adcmctl.sh stop apps/apps_password Wait for all concurrent process to complete, you can monitor using ps -ef|grep -i fndlibr All CM process completed, start your CM adcmctl.sh start apps/password Please Note: Switch it off after the debug information has been generated.



How to synchronize (sync) refreshed database with already applied patches in Test Apps Tiers Normally, we apply patches to test Instance. But if we have a situation like after applying the patches to the Test instance, suddenly need to refresh the database with latest from production db. 7

Author – A.Kishore/Sachin http://appsdba.info

We can perform the database refresh part without having any problems, but how to sync already applied patch to the newly refreshed database. In this case, we have to use the adpatch option "options=nocopyportion,nogenerateportion". By doing this, only the database portion will be applied, and the database will be in sync with the application in terms of those earlier patches.



How to Enable Tracing in Jinitiator This trace file will obtain additional information when the application is running - For e.g. to know the files being loaded when the web form application uses images. There are two ways to enabling tracing in Jinitiator  Method 1 From client machine, Open the Jinitiator Control Panel. On Windows select Start - Settings Control Panel - Jinitiator 1.3.1.x. Enter the following in the "java Run Time parameters" textfield: -Djavaplugin.trace=true -Djavaplugin.trace.option=basic|net|security|ext|liveconnect. Tracing set through the Control Panel will take effect when the Plug-in is launched, but changes made through the Control Panel while a Plug-in is running will have no effect until restart. We can see the trace information in the jinitiator console or in the file C:\Documents and Settings\\jinitiator131x.trace  Method 2 This method assumes you are running a web forms application and the Java Console is active. Press an appropriate number using your alphanumeric keypad (0-5). The trace level options (0-5) are increasingly verbose with the various levels corresponding to the following: 0 - off 1 - basic 2 - network and basic 8

Author – A.Kishore/Sachin http://appsdba.info

3 - security, network and basic 4 - extension, security, network and basic 5 - LiveConnect, extension, security, network and basic



How to start concurrent managers ,if concurrent managers do not start after doing a clone Sometimes after cloning, all the concurrent managers may not start. The symptom of the issue is , after doing a clone when attempt to start the concurrent manager using the below : $COMMON_TOP/admin/scripts/ . adcmctl.sh stop apps/apps We get the following errors: Errors found in ICM logfile as Could not initialize the Service Manager FNDSM__. Verify that has been registered for concurrent processing. The reason for this issue is that, FND_NODES table having incorrect node entries (old node from the Source Instance) and that no Service Manager was found for the existing node. Solution to the issue 1. 2. 3. 4.

Stop all middle tier services including the concurrent managers. Stop the database. Start the database. Connect SQLPLUS as APPS user and run the following : EXEC FND_CONC_CLONE.SETUP_CLEAN; COMMIT; EXIT;

5. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtiers to repopulate the required system tables. 6. Connect to SQLPLUS as APPS user and run the following sql statement : select CONCURRENT_QUEUE_NAME from CONCURRENT_QUEUE_NAME like 'FNDSM%';

FND_CONCURRENT_QUEUES

If the above SQL statement does not return any value then please do the following: 9

where

Author – A.Kishore/Sachin http://appsdba.info

Go to $FND_TOP/patch/115/sql Connect SQLPLUS as APPS user and run the following script : SQL> @afdcm037.sql; Please Note : The same "afdcm037.sql" is used for Release 12 also . This script will create libraries for FNDSM and create managers for preexisting nodes. Check again that FNDSM entries now exist: select CONCURRENT_QUEUE_NAME from CONCURRENT_QUEUE_NAME like 'FNDSM%';

FND_CONCURRENT_QUEUES

where

7. Go to cd $FND_TOP/bin $ adrelink.sh force=y "fnd FNDLIBR" $ adrelink.sh force=y "fnd FNDSM" $ adrelink.sh force=y "fnd FNDFS" $ adrelink.sh force=y "fnd FNDCRM" 8. Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit). 9. Start the middle tier services including your concurrent manager. 10. Retest the issue We can check the following document from Metalink. NOTE:218893.1 - How to Create The Service Manager 'FNDSM' on Oracle Applications NOTE:260887.1 - Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES NOTE:134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables

10