"How To Do" in Oracle Apps?
"How To Do" in Oracle Apps?
info
So, relinking Oracle manually is a suggested way. Therefore lets start the step by step procedure to relink manually. Step 1 - Log into database tier as oracle. Step 2 - Verify that $ORACLE_HOME is set correctly by issuing the following command: echo $ORACLE_HOME Step 3 - Verify and Configure the Linux environment for Proper Relinking as follows: Set LD_LIBRARY_PATH to include $ORACLE_HOME/lib Step 4 - For all Oracle Versions and Linux platforms: Verify that we have performed Step 2 correctly: env|pg - make sure that the correct absolute path for $ORACLE_HOME in the variable definitions. Step 5 - For all Oracle Versions and Linux platforms: Verify umask is set correctly by issuing following command: umask This must return 022. If it does not, set umask to 022,as follows: umask 022 Step 6 - Run the OS Commands to Relink Oracle: 1
Before relinking Oracle, shut down both the database and the listener. The following commands will output a lot of text to the session window. To capture this output for upload to support, redirect the output to a file. For all Linux platforms: Oracle 7.3.x For executables: oracle, exp, imp, sqlldr, tkprof cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk install For executables: svrmgrl, svrmgrm cd $ORACLE_HOME/svrmgr/lib make -f ins_svrmgr.mk linstall minstall (linstall is for svrmgrl, minstall is for svrmgrm) For executables: sqlplus cd $ORACLE_HOME/sqlplus/lib make -f ins_sqlplus.mk install For executables: dbsnmp, oemevent, oratclsh cd $ORACLE_HOME/network/lib make -f ins_agent.mk install For executables: names, namesctl cd $ORACLE_HOME/network/lib make -f ins_names.mk install For executables: tnslsnr, lsnrctl, tnsping, csmnl, trceval, trcroute cd $ORACLE_HOME/network/lib make -f ins_network.mk install Oracle 8.0.x For executables: oracle, exp, imp, sqlldr, tkprof, mig, dbv, orapwd, rman, svrmgrl, ogms, ogmsctl 2
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk install For executables: sqlplus cd $ORACLE_HOME/sqlplus/lib make -f ins_sqlplus.mk install For executables: dbsnmp, oemevent, oratclsh, libosm.so cd $ORACLE_HOME/network/lib make -f ins_oemagent.mk install For executables: tnslsnr, lsnrctl, namesctl, names, osslogin, trcasst, trcroute cd $ORACLE_HOME/network/lib make -f ins_network.mk install
Oracle 8.1.X, 9.X.X, 10.X.X or 11.X.X *** NEW IN 8i AND ABOVE ***
A 'relink' script is provided in the $ORACLE_HOME/bin directory. cd $ORACLE_HOME/bin relink This will display all of the command's options. usage: relink accepted values for parameter: all, oracle, network, client, client_sharedlib, interMedia, precomp, utilities, oemagent, ldap relink all
make -f ins_rdbms.mk install PLEASE NOTE: After relinking the oracle executable, make sure that the permissions on the executable are 6751 (-rwsr-s--x). If they are not, run the following command as the Oracle software owner that is oracle: cd $ORACLE_HOME/bin chmod 6751 oracle For executables: sqlplus cd $ORACLE_HOME/sqlplus/lib make -f ins_sqlplus.mk install For executables: isqlplus (Oracle9i and higher versions) cd $ORACLE_HOME/sqlplus/lib make -f ins_sqlplus.mk install_isqlplus For executables: dbsnmp, oemevent, oratclsh cd $ORACLE_HOME/network/lib make -f ins_oemagent.mk install PLEASE NOTE: After relinking the dbsnmp executable, it is necessary to run the following commands as root (so that the ownership/permissions on the executable are correct): # cd $ORACLE_HOME/bin # chown root dbsnmp # chmod 6750 dbsnmp For executables: names, namesctl cd $ORACLE_HOME/network/lib make -f ins_names.mk install For executables: osslogin, trcasst, trcroute, onrsd, tnsping cd $ORACLE_HOME/network/lib make -f ins_net_client.mk install For executables: tnslsnr, lsnrctl 4
cd $ORACLE_HOME/network/lib make -f ins_net_server.mk install For executables related to ldap (for example Oracle Internet Directory): cd $ORACLE_HOME/ldap/lib make -f ins_ldap.mk install
$ADPERLPRG $FND_TOP/patch/115/bin/TXKScript.pl \ -script=$FND_TOP/patch/115/bin/txkInventory.pl -txktop=$APPLTMP \ -contextfile=$CONTEXT_FILE \ -appspass=apps \ -outfile=$APPLTMP/Report_App_Inventory.html We need to execute the following command on database Tier. $ADPERLPRG $ORACLE_HOME/appsutil/bin/TXKScript.pl -script=$ORACLE_HOME/appsutil/bin/txkInventory.pl txktop=$ORACLE_HOME/appsutil/temp -contextfile=$CONTEXT_FILE -appspass=apps -outfile=$ORACLE_HOME/appsutil/temp/Report_DB_Inventory.html If we want to generate the report in text format, the parameter "-reporttype=text" needs to be passed to the above commands. For example: outfile=$ORACLE_HOME/appsutil/temp/Report_DB_Inventory.html -reporttype=text Once the command executes successfully, it should generate the report file in the location specified for "outfile" parameter in above script.
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
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.
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 where
If the above SQL statement does not return any value then please do the following: 9
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%'; 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 FND_CONCURRENT_QUEUES where
10