1. Download the particular patch file
2. Check the file ..\
3. If the following entry is present
(instance_shutdown) true (/instance_shutdown)
then it requires downtime.
How to Check if a Patch requires Downtime
Solution
1. Download the particular patch file
2. Check the file ..\\etc\config\inventory
3. If the following entry is present
(instance_shutdown) true (/instance_shutdown)
then it requires downtime.
1. Download the particular patch file
2. Check the file ..\
3. If the following entry is present
(instance_shutdown) true (/instance_shutdown)
then it requires downtime.
Find Workflow Notification Mailer
SQL> SELECT email_address,name, nvl(WF_PREF.get_pref(name, 'MAILTYPE'),notification_preference)FROM wf_rolesWHERE name like upper('%xxx%');
SQL> select NOTIFICATION_ID,STATUS,MAIL_STATUS from WF_NOTIFICATIONS where TO_USER='UserName';
SQL> SELECT status,mail_status,MESSAGE_TYPE,MESSAGE_NAME,ITEM_KEY from WF_NOTIFICATIONS WHERE notification_id='2732013';
SQL> select mail_status,count(*) from WF_NOTIFICATIONS group by mail_status;
SQL> select NOTIFICATION_ID,STATUS,MAIL_STATUS from WF_NOTIFICATIONS where TO_USER='UserName';
SQL> SELECT status,mail_status,MESSAGE_TYPE,MESSAGE_NAME,ITEM_KEY from WF_NOTIFICATIONS WHERE notification_id='2732013';
SQL> select mail_status,count(*) from WF_NOTIFICATIONS group by mail_status;
COLUMN CORRID FORMAT A55;
COLUMN STATE FORMAT A14;
SELECT CORRID,DECODE(STATE, 0, '0 = READY', 1, '1 = DELAYED', 2, '2 = PROCESSED', 3, '3 = EXCEPTION',TO_CHAR(STATE)) STATE, COUNT(*) COUNT
FROM WF_DEFERRED
GROUP BY CORRID, STATE;
SET LINES 150
COLUMN CORRID FORMAT A55;
COLUMN STATE FORMAT A14;
SELECT CORRID,DECODE(STATE, 0, '0 = READY', 1, '1 = DELAYED', 2, '2 = PROCESSED', 3, '3 =
EXCEPTION',TO_CHAR(STATE)) STATE, COUNT(*) COUNT
FROM WF_NOTIFICATION_OUT
GROUP BY CORRID, STATE;
COL COMPONENT_NAME FORMAT A60
COL COMPONENT_STATUS FORMAT A20
COL STARTUP_MODE FORMAT A20
SET LINES 120
SET PAGES 1000
SELECT COMPONENT_NAME, COMPONENT_STATUS, STARTUP_MODE FROM FND_SVC_COMPONENTS;
SET LINES 160
COL COMPONENT_NAME FORMAT A30
COL PARAMETER_NAME FORMAT A40
COL PARAMETER_VALUE FORMAT A40
SELECT A.COMPONENT_ID, A.COMPONENT_NAME, B.PARAMETER_ID, C.PARAMETER_NAME, B.PARAMETER_VALUE
FROM FND_SVC_COMPONENTS A, FND_SVC_COMP_PARAM_VALS B, FND_SVC_COMP_PARAMS_B C
WHERE A.COMPONENT_ID = B.COMPONENT_ID AND B.PARAMETER_ID = C.PARAMETER_ID
AND UPPER(A.COMPONENT_NAME) LIKE '%MAILER%'
ORDER BY A.COMPONENT_ID, A.COMPONENT_NAME, C.PARAMETER_NAME;
How to change Apps 11i form color change after cloning
To differentiate dev/test from prod, we can change the form color by changing some profile options.
Profile option change to be done:
1. Set the Java Look and Feel profile option value to oracle. If you set it to generic, it will take the default values and you wont be able to set your own color.
2. Then set Java Color Scheme profile option value to any of the LOVs as per your choice.
Remember to set this at site level
NOTE: It won't get effect immediately, you have to log out from
application and again you have to relogin to view color change effect
Profile option change to be done:
1. Set the Java Look and Feel profile option value to oracle. If you set it to generic, it will take the default values and you wont be able to set your own color.
2. Then set Java Color Scheme profile option value to any of the LOVs as per your choice.
Remember to set this at site level
NOTE: It won't get effect immediately, you have to log out from
application and again you have to relogin to view color change effect
Rolling Oracle Clusterware Upgrade 10.2.0.3 to 10.2.0.4
1. Stop both DB nodes
2. Shut down all listeners
3. Log in as the root user Shutdown the CRS crsctl stop crs
Go to following location and check the current CRS version.
cd /CRS/app/10.2.0/bin
./crsctl query crs softwareversion
./crsctl query crs activeversion
Unzip 10.2.0.4 patchset 6810189
Run ./runInstaller
WelcomeScreen
choose the CRS_home and Click Next
selection the CRS_home will automatically select and upgrade the CRS software
Click Next
Click Next
Click Install
10.2.0.4 binaries automatically installed in all nodes. So please run the root102.sh in all the database nodes.
The following instructions are displayed on the Oracle Universal Installer screen:
To complete the installation of this patch set, perform the following tasks on each node:
Log in as the root user and enter the following command to shut down the Oracle Clusterware:
# CRS_home/bin/crsctl stop crs
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
# CRS_home/install/root102.sh
Database Node 1
Please follow the same steps to rest of the all nodes.
The following instructions are displayed on the Oracle Universal Installer screen:
To complete the installation of this patch set, perform the following tasks on each node:
Log in as the root user and enter the following command to shut down the Oracle Clusterware:
# CRS_home/bin/crsctl stop crs
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
# CRS_home/install/root102.sh
Database Node 2
After completing the above steps, please check the CRS version.
./crsctl query crs softwareversion
CRS software version on node [oradbtest1] is [10.2.0.4.0]
./crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.3.0]
2. Shut down all listeners
3. Log in as the root user Shutdown the CRS crsctl stop crs
Go to following location and check the current CRS version.
cd /CRS/app/10.2.0/bin
./crsctl query crs softwareversion
./crsctl query crs activeversion
Unzip 10.2.0.4 patchset 6810189
Run ./runInstaller
WelcomeScreen
choose the CRS_home and Click Next
selection the CRS_home will automatically select and upgrade the CRS software
Click Next
Click Next
Click Install
10.2.0.4 binaries automatically installed in all nodes. So please run the root102.sh in all the database nodes.
The following instructions are displayed on the Oracle Universal Installer screen:
To complete the installation of this patch set, perform the following tasks on each node:
Log in as the root user and enter the following command to shut down the Oracle Clusterware:
# CRS_home/bin/crsctl stop crs
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
# CRS_home/install/root102.sh
Database Node 1
Please follow the same steps to rest of the all nodes.
The following instructions are displayed on the Oracle Universal Installer screen:
To complete the installation of this patch set, perform the following tasks on each node:
Log in as the root user and enter the following command to shut down the Oracle Clusterware:
# CRS_home/bin/crsctl stop crs
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
# CRS_home/install/root102.sh
Database Node 2
After completing the above steps, please check the CRS version.
./crsctl query crs softwareversion
CRS software version on node [oradbtest1] is [10.2.0.4.0]
./crsctl query crs activeversion
CRS active version on the cluster is [10.2.0.3.0]
Notifications Not Being Received After Autoconfig Is Run
SolutionTo implement the solution, please execute the following steps:
1. Log into the Oracle Applications Manager.
2. Click on Site Map.
3. Click on Notification Mailer under Workflow.
4. Click on the Edit button for the active mailer.
5. Click Next to step 3 that lists the Inbound EMail Account and Outbound EMail Account.
6. Confirm that the servers names are correct with the IMAP and SMTP servers and change as needed.
7. Click Next and then Click on Finish.
8. Stop and re-start the workflow mailer services within OAM and test.
9. If the issue is resolved, please migrate the solution as appropriate to other environments.
Permanent solutions:
Autoconfig Overwriting The SMTP Server Name For The Java Mailer
[applmgr@test]$ cat UAT_test.xmlgrep s_smtphost
hostname oa_var= s_smtphost test hostname
[applmgr@test]$ cat UAT_test.xmlgrep s_smtpdomainname
domain oa_var=s_smtpdomainname doyen.com domain
1. Update the following parameters in context file on the Concurrent Manager Application Tier node under oa_smtp_server in OAM to the correct Outbound Server Name assigned to the Workflow Mailer.
Example
SMTP Server Host (s_smtphost)
hostname oa_var= s_smtphost mailtest hostname
Email Server Domain (s_smtpdomainname)
2. The next time autoconfig runs on the node it will contain correct setting.
1. Log into the Oracle Applications Manager.
2. Click on Site Map.
3. Click on Notification Mailer under Workflow.
4. Click on the Edit button for the active mailer.
5. Click Next to step 3 that lists the Inbound EMail Account and Outbound EMail Account.
6. Confirm that the servers names are correct with the IMAP and SMTP servers and change as needed.
7. Click Next and then Click on Finish.
8. Stop and re-start the workflow mailer services within OAM and test.
9. If the issue is resolved, please migrate the solution as appropriate to other environments.
Permanent solutions:
Autoconfig Overwriting The SMTP Server Name For The Java Mailer
[applmgr@test]$ cat UAT_test.xmlgrep s_smtphost
[applmgr@test]$ cat UAT_test.xmlgrep s_smtpdomainname
domain oa_var=s_smtpdomainname doyen.com domain
1. Update the following parameters in context file on the Concurrent Manager Application Tier node under oa_smtp_server in OAM to the correct Outbound Server Name assigned to the Workflow Mailer.
Example
SMTP Server Host (s_smtphost)
Email Server Domain (s_smtpdomainname)
2. The next time autoconfig runs on the node it will contain correct setting.
Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
1. Download the JRE Plug-in interoperability patch - 6863618
2. Download the Sun JRE Plug-in -
1. jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe
or
2. jre-6u12-windows-i586-p.exe
3. Rename the JRE Plug-in and Place it on Webserver
jre-1_5_0_17-windows-i586-p.exe
X means current updated version,
Example
jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe
If you have more then one apps node, need to place all nodes.
4. Shutdown Apps tier
5. Place the JRE 5 Plug-in on the Web Application Tier
Use FTP or WINSCP Tool
Move the jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe file to the web application tier and place it in all apps nodes
$COMMON_TOP/util/jinitiator
6. Enable Maintenance Mode
We have forms 18 patchset, so that i applied following patch for JRE upgrade, If you have less then forms patch 18, first you should upgrade forms 18 or later. If you have forms 19 or later please follow the metalink note id: 290807.1
Developer 6i Patchset 18 Users
Developer 6i Patchset 18 (6.0.8.27.x) users must apply the forms focus fix patches 7362389 and 5884875.
7. Apply Prerequisite Patche 7362389
Note: Just follow the patch readme.
8. Apply Prerequisite Patch 5884875
Note: Just follow the patch readme.
8. Apply JRE Interoperability Patch - 6863618 - Use adpatch
Apply the Patch Driver
If you are upgrading to the JRE native plug-in for the first time, please apply the interop patch using AutoPatch.
Multiple Application-Tier Web Server Nodes
If you have multiple web application tier server nodes, repeat the steps above to apply the patch driver in the JRE Interoperability Patch against all other web application tier server nodes.
9 . Run below script on command prompt
Run the txkSetPlugin.sh script from the//fnd/bin/ directory, against the web node of your middle tier, where is the directory in which you unzipped this patch.
Run the txkSetPlugin.sh Script
$txkSetPlugin.sh 15017
It will ask following input from you, please provide right path.
/u01/oracle/appltestAPPSORA.env
/u01/oracle/appltest/admin/DBA_oraappsdba.xml
Password for the APPS user in the database :apps
Example:
[applmgr@testoraapps bin]$ txkSetPlugin.sh 15017
/u01/oracle/testappl/fnd/11.5.0/bin
Starting interoperability upgrade script...
Sending logfile output to:
/u01/oracle/testappl/admin/log/txkSetPlugin.log
Using the context file:
/u01/oracle/testappl/admin/u01_oraappsu01.xml
Using APPLSYS file:
/u01/oracle/testappl/APPSu01_oraappsu01.env
Enter the password for the Oracle database APPS user [APPS] : apps
Using /u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/bin/java to execute java programs
Getting J2SE parameter values...
Copy oaj2se.exe to html dir...
Copying /u01/oracle/u01comn/util/jinitiator/j2se15017.exe to /u01/oracle/u01comn/html/oaj2se.exe ...
Backing up the Application Context File...
Backing up /u01/oracle/testappl/admin/u01_oraappsu01.xml to /u01/oracle/testappl/admin/u01_oraappsu01.xml.prej2se15017
Using APPSWEB file /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg
Backing up the appsweb file...
Backing up /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg to /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg.prej2se15017
Updating XML context file with new parameters...
Updated Plug-in type to jdk
Updated JInitiator version name to 1.5.0_17
Updated JInitiator mimetype to 1.5.0_17
Updated JInitiator classid to CAFEEFAC-0015-0000-0017-ABCDEFFEDCBA
Updated J2SE mimetype to 1.5.0_17
Updated J2SE Classid to CAFEEFAC-0015-0000-0017-ABCDEFFEDCBA
The log file for this session is located at: /u01/oracle/testappl/admin/u01_oraappsu01/log/04280720/adconfig.log
AutoConfig is configuring the Applications environment...
AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u01/oracle/testappl
Classpath : /u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/jre/lib/rt.jar:/u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/lib/dt.jar:/u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/lib/tools.jar:/u01/oracle/u01comn/java/appsborg2.zip:/u01/oracle/u01comn/java
Using Context file : /u01/oracle/testappl/admin/u01_oraappsu01.xml
Context Value Management will now update the Context file
Updating Context file...COMPLETED
Attempting upload of Context file and templates to database...COMPLETED
Configuring templates from all of the product tops...
Configuring AD_TOP........COMPLETED
Configuring FND_TOP.......COMPLETED
Configuring ICX_TOP.......COMPLETED
Configuring IEO_TOP.......COMPLETED
Configuring ABM_TOP.......COMPLETED
Configuring EAM_TOP.......COMPLETED
Configuring CSD_TOP.......COMPLETED
Configuring IGC_TOP.......COMPLETED
AutoConfig completed successfully.
Upgrading j2se15017 for Oracle Workflow...
Oracle Workflow upgraded successfully...
Done
10. Disable Maintenance Mode
11. Startup your apps nodes
11. Login apps, first it will take time to download for JRE.
Reverting to a Previous JRE Plug-in/JInitiator Version
If you wish to revert back to previously installed version of JRE to be used in your Application, please re-install the required version by re-running the txkSetPlugin script with the appropriate parameters. This will automatically overwrite the JRE parameters in the configuration files.
To revert back to a version of JInitiator, you must also run the txkSetPlugin script with the appropriate parameters and not the old jinit.sh or jinit.cmd scripts that were used for JInitiator upgrades previously. Using JInitiator 1.3.1.28 as an example the command would be;
UNIX Users
$ txkSetPlugin.sh 13121
Reference:
Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
Doc ID: 290807.1
2. Download the Sun JRE Plug-in -
1. jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe
or
2. jre-6u12-windows-i586-p.exe
3. Rename the JRE Plug-in and Place it on Webserver
jre-1_5_0_17-windows-i586-p.exe
X means current updated version,
Example
jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe
If you have more then one apps node, need to place all nodes.
4. Shutdown Apps tier
5. Place the JRE 5 Plug-in on the Web Application Tier
Use FTP or WINSCP Tool
Move the jre-1_5_0_17-windows-i586-p.exe to j2se15017.exe file to the web application tier and place it in all apps nodes
$COMMON_TOP/util/jinitiator
6. Enable Maintenance Mode
We have forms 18 patchset, so that i applied following patch for JRE upgrade, If you have less then forms patch 18, first you should upgrade forms 18 or later. If you have forms 19 or later please follow the metalink note id: 290807.1
Developer 6i Patchset 18 Users
Developer 6i Patchset 18 (6.0.8.27.x) users must apply the forms focus fix patches 7362389 and 5884875.
7. Apply Prerequisite Patche 7362389
Note: Just follow the patch readme.
8. Apply Prerequisite Patch 5884875
Note: Just follow the patch readme.
8. Apply JRE Interoperability Patch - 6863618 - Use adpatch
Apply the Patch Driver
If you are upgrading to the JRE native plug-in for the first time, please apply the interop patch using AutoPatch.
Multiple Application-Tier Web Server Nodes
If you have multiple web application tier server nodes, repeat the steps above to apply the patch driver in the JRE Interoperability Patch against all other web application tier server nodes.
9 . Run below script on command prompt
Run the txkSetPlugin.sh script from the
Run the txkSetPlugin.sh Script
$txkSetPlugin.sh 15017
It will ask following input from you, please provide right path.
/u01/oracle/appltestAPPSORA.env
/u01/oracle/appltest/admin/DBA_oraappsdba.xml
Password for the APPS user in the database :apps
Example:
[applmgr@testoraapps bin]$ txkSetPlugin.sh 15017
/u01/oracle/testappl/fnd/11.5.0/bin
Starting interoperability upgrade script...
Sending logfile output to:
/u01/oracle/testappl/admin/log/txkSetPlugin.log
Using the context file:
/u01/oracle/testappl/admin/u01_oraappsu01.xml
Using APPLSYS file:
/u01/oracle/testappl/APPSu01_oraappsu01.env
Enter the password for the Oracle database APPS user [APPS] : apps
Using /u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/bin/java to execute java programs
Getting J2SE parameter values...
Copy oaj2se.exe to html dir...
Copying /u01/oracle/u01comn/util/jinitiator/j2se15017.exe to /u01/oracle/u01comn/html/oaj2se.exe ...
Backing up the Application Context File...
Backing up /u01/oracle/testappl/admin/u01_oraappsu01.xml to /u01/oracle/testappl/admin/u01_oraappsu01.xml.prej2se15017
Using APPSWEB file /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg
Backing up the appsweb file...
Backing up /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg to /u01/oracle/u01comn/html/bin/appsweb_u01_oraappsu01.cfg.prej2se15017
Updating XML context file with new parameters...
Updated Plug-in type to jdk
Updated JInitiator version name to 1.5.0_17
Updated JInitiator mimetype to 1.5.0_17
Updated JInitiator classid to CAFEEFAC-0015-0000-0017-ABCDEFFEDCBA
Updated J2SE mimetype to 1.5.0_17
Updated J2SE Classid to CAFEEFAC-0015-0000-0017-ABCDEFFEDCBA
The log file for this session is located at: /u01/oracle/testappl/admin/u01_oraappsu01/log/04280720/adconfig.log
AutoConfig is configuring the Applications environment...
AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u01/oracle/testappl
Classpath : /u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/jre/lib/rt.jar:/u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/lib/dt.jar:/u01/oracle/u01comn/util/java/1.5/jdk1.5.0_11/lib/tools.jar:/u01/oracle/u01comn/java/appsborg2.zip:/u01/oracle/u01comn/java
Using Context file : /u01/oracle/testappl/admin/u01_oraappsu01.xml
Context Value Management will now update the Context file
Updating Context file...COMPLETED
Attempting upload of Context file and templates to database...COMPLETED
Configuring templates from all of the product tops...
Configuring AD_TOP........COMPLETED
Configuring FND_TOP.......COMPLETED
Configuring ICX_TOP.......COMPLETED
Configuring IEO_TOP.......COMPLETED
Configuring ABM_TOP.......COMPLETED
Configuring EAM_TOP.......COMPLETED
Configuring CSD_TOP.......COMPLETED
Configuring IGC_TOP.......COMPLETED
AutoConfig completed successfully.
Upgrading j2se15017 for Oracle Workflow...
Oracle Workflow upgraded successfully...
Done
10. Disable Maintenance Mode
11. Startup your apps nodes
11. Login apps, first it will take time to download for JRE.
Reverting to a Previous JRE Plug-in/JInitiator Version
If you wish to revert back to previously installed version of JRE to be used in your Application, please re-install the required version by re-running the txkSetPlugin script with the appropriate parameters. This will automatically overwrite the JRE parameters in the configuration files.
To revert back to a version of JInitiator, you must also run the txkSetPlugin script with the appropriate parameters and not the old jinit.sh or jinit.cmd scripts that were used for JInitiator upgrades previously. Using JInitiator 1.3.1.28 as an example the command would be;
UNIX Users
$ txkSetPlugin.sh 13121
Reference:
Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i
Doc ID: 290807.1
After Cloning DB Tier Service Name Shows PROD Name
After Cloning DB Tier, Service Name shows like this. This wrong, So we need do the folloing steps.
Error Message:
sql > show parameter service
service_names string UAT, SYS$APPLSYS.WF_CONTROL.PROD.DOYENSYS.COM
Solutions:
Step 1: Bounce the Apps Tier.
Then Go to respective Directory.
/UAT/oracle/uatappl/fnd/11.5.0/patch/115/sql
$ ls -lrt wfctqrec.sql
-----wfctqrec.sql
step 2:
SQL> sqlplus apps/passwd
SQL> @wfctqrec.sql applsys passwd
Step 3: Bounce the DB and Listener in Both RAC Nodes
Setp 4: Start Both Nodes and Listener
Step 5: Now check the show parameter service, It shows
After finishing above tasks, its changed.
sql > show parameter service
service_names string UAT, SYS$APPLSYS.WF_CONTROL.UAT.DOYENSYS.COM
OR
sql > show parameter service
service_names string UAT
Error Message:
sql > show parameter service
service_names string UAT, SYS$APPLSYS.WF_CONTROL.PROD.DOYENSYS.COM
Solutions:
Step 1: Bounce the Apps Tier.
Then Go to respective Directory.
/UAT/oracle/uatappl/fnd/11.5.0/patch/115/sql
$ ls -lrt wfctqrec.sql
-----wfctqrec.sql
step 2:
SQL> sqlplus apps/passwd
SQL> @wfctqrec.sql applsys passwd
Step 3: Bounce the DB and Listener in Both RAC Nodes
Setp 4: Start Both Nodes and Listener
Step 5: Now check the show parameter service, It shows
After finishing above tasks, its changed.
sql > show parameter service
service_names string UAT, SYS$APPLSYS.WF_CONTROL.UAT.DOYENSYS.COM
OR
sql > show parameter service
service_names string UAT
The listener failed to spawn the Service Manager process.
Error:
Concurrent Manager Output Post Processor unable to UP
The following error shows the ICM.log
Could not contact Service Manager FNDSM_orauat2_UAT. The TNS alias could not be located, the listener process on orauat2 could not be contacted, or the listener failed to spawn the Service Manager process.
Process monitor session started : 01-APR-2009 05:39:38Could not contact Service Manager FNDSM_orauat2_UAT. The TNS alias could not be located, the listener process on orauat2 could not be contacted, or the listener failed to spawn the Service Manager process.
Cause:
Here my one of the db instance is down(UAT1), so apps listener is try to check the UAT1 instacne. Buit its not able to connect that database. so that it will throug like this error.
UAT=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(POR1521)) (CONNECT_DATA=
(SERVICE_NAME=UAT)
(INSTANCE_NAME=UAT1)
)
)
UAT1=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT1521)) (
CONNECT_DATA=
(SERVICE_NAME=UAT)
(INSTANCE_NAME=UAT1)
)
)
UAT1_FO=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT1) ) )
UAT2= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )
Solutions
If its PCP enable node, please check the TNS entry.
So, Please chenge the instacne name UAT1 to UAT2. Then try to check the Concurrent Manager.
UAT= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )
UAT1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )
UAT1_FO= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT1) ) )
UAT2= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2)
Now, Ping the all the tns names
tnsping UAT
tnsping UAT2
tnsping FNDSM_orauat2.doyensys.com_DEV
tnsping FNDSM_orauat1.doyensys.com_DEV
tnsping FNDSM_orauat1_DEV
Concurrent Manager Output Post Processor unable to UP
The following error shows the ICM.log
Could not contact Service Manager FNDSM_orauat2_UAT. The TNS alias could not be located, the listener process on orauat2 could not be contacted, or the listener failed to spawn the Service Manager process.
Process monitor session started : 01-APR-2009 05:39:38Could not contact Service Manager FNDSM_orauat2_UAT. The TNS alias could not be located, the listener process on orauat2 could not be contacted, or the listener failed to spawn the Service Manager process.
Cause:
Here my one of the db instance is down(UAT1), so apps listener is try to check the UAT1 instacne. Buit its not able to connect that database. so that it will throug like this error.
UAT=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(POR1521)) (CONNECT_DATA=
(SERVICE_NAME=UAT)
(INSTANCE_NAME=UAT1)
)
)
UAT1=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT1521)) (
CONNECT_DATA=
(SERVICE_NAME=UAT)
(INSTANCE_NAME=UAT1)
)
)
UAT1_FO=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT1) ) )
UAT2= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )
Solutions
If its PCP enable node, please check the TNS entry.
So, Please chenge the instacne name UAT1 to UAT2. Then try to check the Concurrent Manager.
UAT= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )
UAT1= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2) ) )
UAT1_FO= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat1.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT1) ) )
UAT2= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=orauat2.doyensys.com)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=UAT) (INSTANCE_NAME=UAT2)
Now, Ping the all the tns names
tnsping UAT
tnsping UAT2
tnsping FNDSM_orauat2.doyensys.com_DEV
tnsping FNDSM_orauat1.doyensys.com_DEV
tnsping FNDSM_orauat1_DEV
Moving Oracle DataBase Control files
Change the Control file Location of current palce to another place.
Existing initTEST.ora file Location.
SQL>select name from v$controlfile;
/oracle/product/10.1.4/oradata/control01.ctl,
/oracle/product/10.1.4/oradata/control02.ctl,
/oracle/product/10.1.4/oradata/control03.ctl
Note:
Change the control file to following order to existing initTEST.ora file.
If you using spfile, just create the init file and change the controlfile patch and shutdown the database.
cd $ORACLE_HOME/dbs/initTEST.ora
/oracle/product/10.1.4/oradata/control01.ctl,
/oracle/product/10.1.4/oradata/controlfile/controlfile
/ctlbkp/oracle/controlfile/control03.ctl
1. Bounce the Database
2. Change the controlfile new path in inittest.ora
3. Now move all the controlfile form respective place to new place, use MV command.
4. Now startup the Database
5. SQL> show parameter control or put below sql query.
6. Again create the spfile from pfile.
SQL> select name from v$controlfile;
/oracle/product/10.1.4/oradata/control01.ctl
/oracle/product/10.1.4/oradata/controlfile/control02.ctl
/ctlbkp/oracle/controlfile/control03.ctl
Existing initTEST.ora file Location.
SQL>select name from v$controlfile;
/oracle/product/10.1.4/oradata/control01.ctl,
/oracle/product/10.1.4/oradata/control02.ctl,
/oracle/product/10.1.4/oradata/control03.ctl
Note:
Change the control file to following order to existing initTEST.ora file.
If you using spfile, just create the init file and change the controlfile patch and shutdown the database.
cd $ORACLE_HOME/dbs/initTEST.ora
/oracle/product/10.1.4/oradata/control01.ctl,
/oracle/product/10.1.4/oradata/controlfile/controlfile
/ctlbkp/oracle/controlfile/control03.ctl
1. Bounce the Database
2. Change the controlfile new path in inittest.ora
3. Now move all the controlfile form respective place to new place, use MV command.
4. Now startup the Database
5. SQL> show parameter control or put below sql query.
6. Again create the spfile from pfile.
SQL> select name from v$controlfile;
/oracle/product/10.1.4/oradata/control01.ctl
/oracle/product/10.1.4/oradata/controlfile/control02.ctl
/ctlbkp/oracle/controlfile/control03.ctl
How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows
Action Plan for Migrate.
1 Take a cold backup and export full db or important schema
2 Take a backup of 10g binaries (Oracle Home)
3 Take a control file backup using command
Alter database backup controlfile to trace;
4 Take a backup of init.ora file
5 Prepare the current oracle directory structure
6 Clone Prod to Prod (32 bit O/S)
7 Install 64 bit Win O/S
8 Create existing oracle directory structure
9 Install 10g (10.2.0.1 Base) oracle binaries(Software Only),Upgrade 10.2.0.4 If you use exp/imp install with database
10 Please follow the Scenario 1 or 2 or 3
Scenario 1:
Oracle 10.2.0.1(32 Bit) to Oracle 10.2.0.1(64 Bit)
1. Install Oracle 10.2.0.1.0 64bit, on Windows 2003 64bit (either AMD64 or EM64T processors).
2. The same directory structure was used for both machines.
NOTE: If a different directory structure will be used, then you will need to recreate the controlfiles, before starting the migration process.
Alter database backup controlfiles to trace;
3. Copy the Database files from the 32bit machine, to the 64bit machine.
(Datafiles, Logfiles, Controlfiles, init.ora, tnsnames.ora, listener.ora, etc...)
4. Create the Oracle service on the 64bit system, using the ORADIM command.
(Eg, oradim –new –sid orcl –startmode auto –pfile
6.Run Sqlplus
sqlplus '/as sysdba'
SQL>startup upgrade
SQL>@$Oracle_Home\rdbms\admin\utlip.sql
SQL>@$Oracle_Home\rdbms\admin\utlrp.sql
SQL> shut immediate
SQL>startup
SQL>select name,platform_name,open_mode from v$database;
Scenario 2:
Oracle 10.2.0.1(32 Bit) to Oracle 10.2.0.4(64 Bit)
1. Install Oracle 10.2.0.1.0 64bit, on Windows 2003 64bit (either AMD64 or EM64T processors).
2. If you wish to apply a patchset, you can do that now. For this test, the 10.2.0.4 patchset was applied to the 64bit installation.
3. The same directory structure was used for both machines.
NOTE: If a different directory structure will be used, then you will need to recreate the controlfiles, before starting the migration process.
Alter database backup controlfile to trace;
4. Copy the Database files from the 32bit machine, to the 64bit machine.
(Datafiles, Logfiles, Controlfiles, init.ora, tnsnames.ora, listener.ora, etc..)
5. Create the Oracle service on the 64bit system, using the ORADIM command.
(Eg, oradim –new –sid orcl –startmode auto –pfile
6.Run Sqlplus
sqlplus '/as sysdba'
SQL>startup upgrade
SQL>@$Oracle_Home\rdbms\admin\utlip.sql
SQL>@$Oracle_Home\rdbms\admin\catupgrd.sql
SQL>@$Oracle_Home\rdbms\admin\utlrp.sql
SQL> shut immediate
SQL>startup
SQL>select name,platform_name,open_mode from v$database;
Note: 403522.1:- How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows
Scenario 3:
Steps to migrate 32 bit oracle 9i database to 64 bit 10g database:
1, Make backups of 32 bit 10g database.
Cold backup, export.
You need to have export file for migration. You can use user system to export entire database.
2, Install 64 bit Oracle 10g.
3, Create required tablespace, users etc.
4, Import 10g export dump file to 10g (from user=user1 to user=user1).
Steps
CONN sys/password@SID_NAME AS SYSDBA
1. Create Schema Name
2. ALTER USER U_NAME IDENTIFIED BY PASSWD ACCOUNT UNLOCK;
GRANT CREATE ANY DIRECTORY TO ;
3. CREATE OR REPLACE DIRECTORY DIR_NAME AS '/u05/oradata/';
4. GRANT READ, WRITE ON DIRECTORY DIR_NAME TO SCHEMA_NAME;
step:2
Schema Exports/Imports
expdp USER_NAME/PASSWD@SID_NAME schemas=SCHEMA_NAME directory=DIR_NAME dumpfile=INV.dmp logfile=EXPINV.log
impdp USER_NAME/PASSWD@SID_NAME schemas=SCHEMA_NAME directory=DIR_NAME dumpfile=INV.dmp logfile=IMPINV.log
Full Database Exports/Imports
expdp sys/password@SID_NAME full=Y directory=DIR_NAME dumpfile=FULLDB.dmp logfile=FULLDB10G.log
impdp sys/password@SID_NAME full=Y directory=DIR_NAME dumpfile=FULLDB.dmp logfile=FULLDB10G.log
1 Take a cold backup and export full db or important schema
2 Take a backup of 10g binaries (Oracle Home)
3 Take a control file backup using command
Alter database backup controlfile to trace;
4 Take a backup of init.ora file
5 Prepare the current oracle directory structure
6 Clone Prod to Prod (32 bit O/S)
7 Install 64 bit Win O/S
8 Create existing oracle directory structure
9 Install 10g (10.2.0.1 Base) oracle binaries(Software Only),Upgrade 10.2.0.4 If you use exp/imp install with database
10 Please follow the Scenario 1 or 2 or 3
Scenario 1:
Oracle 10.2.0.1(32 Bit) to Oracle 10.2.0.1(64 Bit)
1. Install Oracle 10.2.0.1.0 64bit, on Windows 2003 64bit (either AMD64 or EM64T processors).
2. The same directory structure was used for both machines.
NOTE: If a different directory structure will be used, then you will need to recreate the controlfiles, before starting the migration process.
Alter database backup controlfiles to trace;
3. Copy the Database files from the 32bit machine, to the 64bit machine.
(Datafiles, Logfiles, Controlfiles, init.ora, tnsnames.ora, listener.ora, etc...)
4. Create the Oracle service on the 64bit system, using the ORADIM command.
(Eg, oradim –new –sid orcl –startmode auto –pfile
6.Run Sqlplus
sqlplus '/as sysdba'
SQL>
SQL>@$Oracle_Home\rdbms\admin\utlip.sql
SQL>@$Oracle_Home\rdbms\admin\utlrp.sql
SQL> shut immediate
SQL>startup
SQL>select name,platform_name,open_mode from v$database;
Scenario 2:
Oracle 10.2.0.1(32 Bit) to Oracle 10.2.0.4(64 Bit)
1. Install Oracle 10.2.0.1.0 64bit, on Windows 2003 64bit (either AMD64 or EM64T processors).
2. If you wish to apply a patchset, you can do that now. For this test, the 10.2.0.4 patchset was applied to the 64bit installation.
3. The same directory structure was used for both machines.
NOTE: If a different directory structure will be used, then you will need to recreate the controlfiles, before starting the migration process.
Alter database backup controlfile to trace;
4. Copy the Database files from the 32bit machine, to the 64bit machine.
(Datafiles, Logfiles, Controlfiles, init.ora, tnsnames.ora, listener.ora, etc..)
5. Create the Oracle service on the 64bit system, using the ORADIM command.
(Eg, oradim –new –sid orcl –startmode auto –pfile
6.Run Sqlplus
sqlplus '/as sysdba'
SQL>
SQL>@$Oracle_Home\rdbms\admin\utlip.sql
SQL>@$Oracle_Home\rdbms\admin\catupgrd.sql
SQL>@$Oracle_Home\rdbms\admin\utlrp.sql
SQL> shut immediate
SQL>startup
SQL>select name,platform_name,open_mode from v$database;
Note: 403522.1:- How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows
Scenario 3:
Steps to migrate 32 bit oracle 9i database to 64 bit 10g database:
1, Make backups of 32 bit 10g database.
Cold backup, export.
You need to have export file for migration. You can use user system to export entire database.
2, Install 64 bit Oracle 10g.
3, Create required tablespace, users etc.
4, Import 10g export dump file to 10g (from user=user1 to user=user1).
Steps
CONN sys/password@SID_NAME AS SYSDBA
1. Create Schema Name
2. ALTER USER U_NAME IDENTIFIED BY PASSWD ACCOUNT UNLOCK;
GRANT CREATE ANY DIRECTORY TO ;
3. CREATE OR REPLACE DIRECTORY DIR_NAME AS '/u05/oradata/';
4. GRANT READ, WRITE ON DIRECTORY DIR_NAME TO SCHEMA_NAME;
step:2
Schema Exports/Imports
expdp USER_NAME/PASSWD@SID_NAME schemas=SCHEMA_NAME directory=DIR_NAME dumpfile=INV.dmp logfile=EXPINV.log
impdp USER_NAME/PASSWD@SID_NAME schemas=SCHEMA_NAME directory=DIR_NAME dumpfile=INV.dmp logfile=IMPINV.log
Full Database Exports/Imports
expdp sys/password@SID_NAME full=Y directory=DIR_NAME dumpfile=FULLDB.dmp logfile=FULLDB10G.log
impdp sys/password@SID_NAME full=Y directory=DIR_NAME dumpfile=FULLDB.dmp logfile=FULLDB10G.log
Enterprise Manager DST Problem
Purpose
OEM agent suddently not running for daylight saving time changes.
Problem:
$ ./emctl start agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Starting agent ..... failed.
The agentTZRegion value in /oracle/app/em/agent10g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.
Consult the log files in: /oracle/app/em/agent10g/sysman/log
Solutions:
Download the Patch 5632264 for the latest version for your platform, DO NOT APPLY IT with opatch but:
Manually replace the oracore [/zoneinfo/timez*.dat] files in the Central Agent ORACLE_HOME:
Agent ORACLE_HOME
- backup the initial oracore files $ORACLE_HOME/oracore/[/zoneinfo/timez*.dat]
- replace the oracore [/zoneinfo/timez*.dat] files in the Central Agent ORACLE_HOME with the oracore [/zoneinfo/timez*.dat] files extracted from the patch
- ./emctl resetTZ agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Updating /oracle/oracle/agent10g/sysman/config/emd.properties...
Successfully updated /oracle/oracle/agent10g/sysman/config/emd.properties.
Login as the em repository user and run the script:
exec mgmt_target.set_agent_tzrgn('oradiscprod.amestruetemper.com:3872','US/Eastern')
This can be done for example by logging into sqlplus and doing
SQL> exec mgmt_target.set_agent_tzrgn('oradiscprod.amestruetemper.com:3872','US/Eastern')
- start the Central Agent
./emctl start agent
./emctl status agent
Reference:
Enterprise Manager DST Quick Fix Guide: 418792.1
OEM agent suddently not running for daylight saving time changes.
Problem:
$ ./emctl start agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Starting agent ..... failed.
The agentTZRegion value in /oracle/app/em/agent10g/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(
Consult the log files in: /oracle/app/em/agent10g/sysman/log
Solutions:
Download the Patch 5632264 for the latest version for your platform, DO NOT APPLY IT with opatch but:
Manually replace the oracore [/zoneinfo/timez*.dat] files in the Central Agent ORACLE_HOME:
Agent ORACLE_HOME
- backup the initial oracore files $ORACLE_HOME/oracore/[/zoneinfo/timez*.dat]
- replace the oracore [/zoneinfo/timez*.dat] files in the Central Agent ORACLE_HOME with the oracore [/zoneinfo/timez*.dat] files extracted from the patch
- ./emctl resetTZ agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Updating /oracle/oracle/agent10g/sysman/config/emd.properties...
Successfully updated /oracle/oracle/agent10g/sysman/config/emd.properties.
Login as the em repository user and run the script:
exec mgmt_target.set_agent_tzrgn('oradiscprod.amestruetemper.com:3872','US/Eastern')
This can be done for example by logging into sqlplus and doing
SQL> exec mgmt_target.set_agent_tzrgn('oradiscprod.amestruetemper.com:3872','US/Eastern')
- start the Central Agent
./emctl start agent
./emctl status agent
Reference:
Enterprise Manager DST Quick Fix Guide: 418792.1
index is in unusable state
Error Messsage
While compiling the flexfields, the procedure wf_event.raise failed with following
parameters:
event_name = oracle.apps.fnd.flex.dff.compiled
event_key = FND.$SRS$.FNDSCURS
The error raised is:
ORA-00604: error occurred at recursive SQL level 1
ORA-01502: index 'APPLSYS.SYS_C00169351' or partition of such index is in unusable state
Check the Unstale index
select index_name, status from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
WF_JAVA_DEFERRED_N1 UNUSABLE
SYS_C00169351 UNUSABLE
WF_DEFERRED_N1 UNUSABLE
SYS_C00105999 UNUSABLE
Solution:
Rebuild Unstale index.
select 'alter index 'owner'.'index_name' rebuild;' from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
While compiling the flexfields, the procedure wf_event.raise failed with following
parameters:
event_name = oracle.apps.fnd.flex.dff.compiled
event_key = FND.$SRS$.FNDSCURS
The error raised is:
ORA-00604: error occurred at recursive SQL level 1
ORA-01502: index 'APPLSYS.SYS_C00169351' or partition of such index is in unusable state
Check the Unstale index
select index_name, status from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
WF_JAVA_DEFERRED_N1 UNUSABLE
SYS_C00169351 UNUSABLE
WF_DEFERRED_N1 UNUSABLE
SYS_C00105999 UNUSABLE
Solution:
Rebuild Unstale index.
select 'alter index 'owner'.'index_name' rebuild;' from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
SQL*Plus Command Reference
SQL*PLUS - SET Statement
http://www.ss64.com/orasyntax/plus_set.html
SQL*Plus FAQ
http://www.orafaq.com/wiki/SQL*Plus_FAQ
SQL*Plus Command Reference
http://download-west.oracle.com/docs/cd/B10500_01/server.920/a90842/ch13.htm
http://www.ss64.com/orasyntax/plus_set.html
SQL*Plus FAQ
http://www.orafaq.com/wiki/SQL*Plus_FAQ
SQL*Plus Command Reference
http://download-west.oracle.com/docs/cd/B10500_01/server.920/a90842/ch13.htm
How to Restart The Concurrent Manager in Unix.
goal: How to restart the concurrent manager in Unix
goal: How to bounce the concurrent manager in Unix
fact: Oracle Application Object Library
fix:
1. At the command line issue the following shutdown command:
CONCSUB apps/apps sysadmin 'System Administrator' SYSADMIN CONCURRENT FND SHUTDOWN
Note: There are 3 options which can be used for controlling the Internal
Manager from the OS as follows:
SHUTDOWN = Standard, non-invasive shutdown.
DEACTIVATE = Will not allow further Requests to Process once Issued.
ABORT = Terminate Requests and Deactivate the Internal Manager.
2. At the command line, issue the following Start Up command:
startmgr sysmgr="[fnd_usernamd/fnd_password]" mgrname="[mgrname]" printer="[printername]"
mailto="[userid userid2...]" restart="[Nminutes]" logfile="[log_file_name]" sleep="
[new_check]" pmon="[manager_check]" quesiz="[number_check]" diag="[YN]"
ExAMPLE:
startmgr sysmgr="applsys/apps" mgrname="std" printer="localprint"
mailto="Ramesh Mani" restart="N" logfile="mgrlog" sleep="90"
pmon="5" quesiz="10" diag="N"
Note: a space is required between arguments and the "diag" parameter
may be omitted if desired.
Reference: 147449.1
goal: How to bounce the concurrent manager in Unix
fact: Oracle Application Object Library
fix:
1. At the command line issue the following shutdown command:
CONCSUB apps/apps sysadmin 'System Administrator' SYSADMIN CONCURRENT FND SHUTDOWN
Note: There are 3 options which can be used for controlling the Internal
Manager from the OS as follows:
SHUTDOWN = Standard, non-invasive shutdown.
DEACTIVATE = Will not allow further Requests to Process once Issued.
ABORT = Terminate Requests and Deactivate the Internal Manager.
2. At the command line, issue the following Start Up command:
startmgr sysmgr="[fnd_usernamd/fnd_password]" mgrname="[mgrname]" printer="[printername]"
mailto="[userid userid2...]" restart="[Nminutes]" logfile="[log_file_name]" sleep="
[new_check]" pmon="[manager_check]" quesiz="[number_check]" diag="[YN]"
ExAMPLE:
startmgr sysmgr="applsys/apps" mgrname="std" printer="localprint"
mailto="Ramesh Mani" restart="N" logfile="mgrlog" sleep="90"
pmon="5" quesiz="10" diag="N"
Note: a space is required between arguments and the "diag" parameter
may be omitted if desired.
Reference: 147449.1
The field PARAMETER.CONFIG could not be located or read
Symptoms
You are encountering the following error while trying to start/stop the apache
using adapcctl.sh
"The field PARAMETER.CONFIG could not be located or read."
The adapcctl.log carries the following errors:
Cannot read value from field PARAMETER.CONFIG
Cause: The field PARAMETER.CONFIG could not be located or read.
Changes
You upgraded to RDBMS 9.2.0.4 from RDBMS 8.0.6, but the instance was fine for a couple of days after the upgrade. This problem suddenly cropped up.
Cause
Your guest user is end-dated
That is the sole reason you are getting this error.
Fix
Back up your FND_USER TABLE
Run the following command update fnd_user set end_date=null where user_name='GUEST';
Retest with adapcctl.sh
Reference: 298143.1
You are encountering the following error while trying to start/stop the apache
using adapcctl.sh
"The field PARAMETER.CONFIG could not be located or read."
The adapcctl.log carries the following errors:
Cannot read value from field PARAMETER.CONFIG
Cause: The field PARAMETER.CONFIG could not be located or read.
Changes
You upgraded to RDBMS 9.2.0.4 from RDBMS 8.0.6, but the instance was fine for a couple of days after the upgrade. This problem suddenly cropped up.
Cause
Your guest user is end-dated
That is the sole reason you are getting this error.
Fix
Back up your FND_USER TABLE
Run the following command update fnd_user set end_date=null where user_name='GUEST';
Retest with adapcctl.sh
Reference: 298143.1
Diagnostic Script for Concurrent Manager
- - - - - - - - - - - - - - - - Code begins here - - - - - - - - - - - - - - -
spool ccm.lst
prompt Step 1 Checking how many rows in FND_CONCURRENT_REQUEST.
select count(*) from fnd_concurrent_requests;
prompt
-----------------------------------------
prompt Step 2 Checking how many rows in FND_CONCURRENT_PROCESSES table.
select count(*) from fnd_concurrent_processes;
prompt
-----------------------------------------------
prompt Step 3 Checking sys.dual table which should have one and only one row.
select count(*) from sys.dual;
prompt If you have more than one row in sys.dual, please delete it
prompt sql> delete rownum from SYS.DUAL;
Prompt rownum= the row number to delete
prompt
prompt
prompt
---------------------------------------------
prompt Step 4 Checking fnd_dual. There must be at lest one row:
select count(*) from fnd_dual;
prompt If there are no record selected,
prompt Update fnd_dual table to have at lest one record
prompt
----------------------------------------------
prompt Step 5 Checking the Internal Manager queue name "FNDICM" which should be=1
select concurrent_queue_id from fnd_concurrent_queues
where concurrent_queue_name='FNDICM';
prompt
----------------------------------------------
prompt Step 6 Checking for Active processes under the Internal Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDICM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
-----------------------------------------
prompt Step 7 Checking for Active processes under the Standard Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='STANDARD'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
------------------------------------------
prompt Step 8 Checking for Active processes under the Conflict Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDCRM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
---------------------------------------------------
prompt Step 9 Checking Actual and Target Processes for Internal Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDICM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
--------------------------------------------------------
prompt Step 10 Checking Actual and Target Processes for the Standard Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='STANDARD';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
prompt Step 11 Checking Actual and Target Processes for Conflict Resolution Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDCRM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
Prompt Step 12 Checking if the control_code set to 'N':
select control_code from fnd_concurrent_queues
where control_code='N';
prompt
prompt If any rows selected, please update the table fnd_concurrent_queues:
prompt Update fnd_concurrent_queues set control_code = null
prompt where control_code ='N';
PROMPT Update fnd_concurrent_queues set target_node = null;
PROMPT commit;
prompt
prompt
--------------------------------
PROMPT Step 13 Checking terminated processes:
PROMPT
select count (*) from fnd_concurrent_requests
where status_code='T';
prompt
prompt If you have terminated processes run the following sql statement:
prompt
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'T';
prompt
------------------------------------------
prompt Step 14 Checking pending requests:
select count(*) from fnd_concurrent_requests
where status_code='P';
prompt If any rows selected please run the following sql statement:
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'P';
prompt
------------------------------------------------------
prompt Step 15 Checking Running processes:
prompt
select count (*) from fnd_concurrent_requests
where status_code='R';
prompt
prompt If you have Running processes run the following sql statement
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'R';
prompt
------------------------------------------
prompt Step 16 Checking the PMON method, which should be set to LOCK:
prompt
select profile_option_id , profile_option_value
from FND_PROFILE_OPTION_VALUES
where profile_option_id= (select profile_option_id
from FND_PROFILE_OPTIONS
where profile_option_name='CONC_PMON_METHOD');
prompt
prompt If the PROFILE_OPTION_VALUE was't LOCK please
prompt Reset PMON to LOCK by running afimpmon.sql script(The manager should be down)
prompt 1-At UNIX command prompt:
prompt 2-cd $FND_TOP/sql
prompt 3-Log into SQLPLUS as apps/
prompt SQL> @afimpmon.sql
prompt prompt1:dual
prompt prompt2:LOCK (LOCK MUST BE ALL UPPERCASE)
prompt For Oracle Applications Release 11.5, when you check the PMON
prompt Method you may get no rows selected which is normal,
prompt because in apps 11.5 the Pmon Method is hard coded to Lock at
prompt the Operating System level.
prompt
prompt
-------------------------------------------------------
prompt Step-17 Checking how many FNDLIBR processes are running:
prompt -For Unix :From unix command prompt $ ps -ef grep -i fndlibr
prompt If you have any FNDLIBR processes running,please kill them before
prompt starting or shuting down the internal manager
prompt
prompt
prompt -For NT, through Task Manager, check the entries under the Processes tab
for FNDLIBR.exe processes.
prompt If there are any, Highlight and click [End Process] button to kill processes
prompt
----------------------------------------------------------
prompt Step-18 Checking how many "FND_%"invalid objects:
select substr(owner,1, 12) owner, substr(object_type,1,12) type,
substr(status,1,8) status, substr(object_name, 1, 25) name
from dba_objects
where object_name like 'FND_%'
and status='INVALID';
prompt If you have any invalied objects please see note#113947.1 via Metalink
prompt
--------------------------------------------------------------
prompt Step-19-How to find the PID in the O/S for request_id:
prompt If you do not like to check this enter any number then click Enter to Exit
select r.request_id, p.os_process_id
from FND_CONCURRENT_REQUESTS r,FND_CONCURRENT_PROCESSES p
where r.controlling_manager = p.concurrent_process_id
and request_id=&request_id;
prompt
prompt Please upload the "ccm.lst" output to Support, Thanks.
prompt
spool off
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - - - - - -
spool ccm.lst
prompt Step 1 Checking how many rows in FND_CONCURRENT_REQUEST.
select count(*) from fnd_concurrent_requests;
prompt
-----------------------------------------
prompt Step 2 Checking how many rows in FND_CONCURRENT_PROCESSES table.
select count(*) from fnd_concurrent_processes;
prompt
-----------------------------------------------
prompt Step 3 Checking sys.dual table which should have one and only one row.
select count(*) from sys.dual;
prompt If you have more than one row in sys.dual, please delete it
prompt sql> delete rownum from SYS.DUAL;
Prompt rownum= the row number to delete
prompt
prompt
prompt
---------------------------------------------
prompt Step 4 Checking fnd_dual. There must be at lest one row:
select count(*) from fnd_dual;
prompt If there are no record selected,
prompt Update fnd_dual table to have at lest one record
prompt
----------------------------------------------
prompt Step 5 Checking the Internal Manager queue name "FNDICM" which should be=1
select concurrent_queue_id from fnd_concurrent_queues
where concurrent_queue_name='FNDICM';
prompt
----------------------------------------------
prompt Step 6 Checking for Active processes under the Internal Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDICM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
-----------------------------------------
prompt Step 7 Checking for Active processes under the Standard Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='STANDARD'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
------------------------------------------
prompt Step 8 Checking for Active processes under the Conflict Manager queue
prompt in fnd_concurrent_proceses table:
prompt
select a.concurrent_queue_name
, substr(b.os_process_id,0,10) "OS Proc"
, b.oracle_process_id "Oracle ID"
, b.process_status_code
from fnd_concurrent_queues a
, fnd_concurrent_processes b
where a.concurrent_queue_id=b.concurrent_queue_id
and a.concurrent_queue_name='FNDCRM'
and b.process_status_code='A'
order by b.process_status_code;
prompt If any rows found with process_status_code with value = 'A' (= Active)
prompt The internal Manager will not start up ,so to avoide this issue
prompt update these rows to have process_status_code value ='K'(terminated)
prompt
prompt
---------------------------------------------------
prompt Step 9 Checking Actual and Target Processes for Internal Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDICM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
--------------------------------------------------------
prompt Step 10 Checking Actual and Target Processes for the Standard Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='STANDARD';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
prompt Step 11 Checking Actual and Target Processes for Conflict Resolution Manager:
select MAX_PROCESSES,RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME='FNDCRM';
prompt If the MAX_PROCESSES=RUNNING_PROCESSES that means the manager is UP.
prompt
prompt
---------------------------------------------------------
Prompt Step 12 Checking if the control_code set to 'N':
select control_code from fnd_concurrent_queues
where control_code='N';
prompt
prompt If any rows selected, please update the table fnd_concurrent_queues:
prompt Update fnd_concurrent_queues set control_code = null
prompt where control_code ='N';
PROMPT Update fnd_concurrent_queues set target_node = null;
PROMPT commit;
prompt
prompt
--------------------------------
PROMPT Step 13 Checking terminated processes:
PROMPT
select count (*) from fnd_concurrent_requests
where status_code='T';
prompt
prompt If you have terminated processes run the following sql statement:
prompt
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'T';
prompt
------------------------------------------
prompt Step 14 Checking pending requests:
select count(*) from fnd_concurrent_requests
where status_code='P';
prompt If any rows selected please run the following sql statement:
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'P';
prompt
------------------------------------------------------
prompt Step 15 Checking Running processes:
prompt
select count (*) from fnd_concurrent_requests
where status_code='R';
prompt
prompt If you have Running processes run the following sql statement
prompt SQL> Update fnd_concurrent_requests
prompt set status_code = 'E', phase_code = 'C'
prompt where status_code = 'R';
prompt
------------------------------------------
prompt Step 16 Checking the PMON method, which should be set to LOCK:
prompt
select profile_option_id , profile_option_value
from FND_PROFILE_OPTION_VALUES
where profile_option_id= (select profile_option_id
from FND_PROFILE_OPTIONS
where profile_option_name='CONC_PMON_METHOD');
prompt
prompt If the PROFILE_OPTION_VALUE was't LOCK please
prompt Reset PMON to LOCK by running afimpmon.sql script(The manager should be down)
prompt 1-At UNIX command prompt:
prompt 2-cd $FND_TOP/sql
prompt 3-Log into SQLPLUS as apps/
prompt SQL> @afimpmon.sql
prompt prompt1:dual
prompt prompt2:LOCK (LOCK MUST BE ALL UPPERCASE)
prompt For Oracle Applications Release 11.5, when you check the PMON
prompt Method you may get no rows selected which is normal,
prompt because in apps 11.5 the Pmon Method is hard coded to Lock at
prompt the Operating System level.
prompt
prompt
-------------------------------------------------------
prompt Step-17 Checking how many FNDLIBR processes are running:
prompt -For Unix :From unix command prompt $ ps -ef grep -i fndlibr
prompt If you have any FNDLIBR processes running,please kill them before
prompt starting or shuting down the internal manager
prompt
prompt
prompt -For NT, through Task Manager, check the entries under the Processes tab
for FNDLIBR.exe processes.
prompt If there are any, Highlight and click [End Process] button to kill processes
prompt
----------------------------------------------------------
prompt Step-18 Checking how many "FND_%"invalid objects:
select substr(owner,1, 12) owner, substr(object_type,1,12) type,
substr(status,1,8) status, substr(object_name, 1, 25) name
from dba_objects
where object_name like 'FND_%'
and status='INVALID';
prompt If you have any invalied objects please see note#113947.1 via Metalink
prompt
--------------------------------------------------------------
prompt Step-19-How to find the PID in the O/S for request_id:
prompt If you do not like to check this enter any number then click Enter to Exit
select r.request_id, p.os_process_id
from FND_CONCURRENT_REQUESTS r,FND_CONCURRENT_PROCESSES p
where r.controlling_manager = p.concurrent_process_id
and request_id=&request_id;
prompt
prompt Please upload the "ccm.lst" output to Support, Thanks.
prompt
spool off
- - - - - - - - - - - - - - - - Code ends here - - - - - - - - - - - - - - - -
How To Trace a Concurrent Request And Generate TKPROF File
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:9891571609150575875::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,453527.1,1,1,1,helvetica
Reference:
Metalink Note ID: 453527.1
Organization Setup Frequently Asked Questions - FAQ
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6356763575233978369::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,109665.1,1,1,1,helvetica
Doc ID:
109665.1
Reference:
Metalink Note ID: 453527.1
Organization Setup Frequently Asked Questions - FAQ
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6356763575233978369::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,109665.1,1,1,1,helvetica
Doc ID:
109665.1
FNDFS Fails to Relink on Red Hat 4.0 - Undefined Reference to dl_iterate_phdr@GLIBC_2.2.4
Starting link of fnd executable 'FNDFS' on Mon Feb 16 23:26:17 EST 2009
gcc -s -L/U01/oracle/U01ora/8.0.6/lib -L/U01/oracle/U01ora/8.0.6/lib/stubs -ldl -o /U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS
/U01/oracle/U01appl/fnd/11.5.0/lib/afpfss.o \
/U01/oracle/U01appl/fnd/11.5.0/lib/libfnd.a -lsql /U01/oracle/U01ora/8.0.6/lib/nautab.o /U01/oracle/U01ora/8.0.6/lib/naeet.o
/U01/oracle/U01ora/8.0.6/lib/naect.o /U01/oracle/U01ora/8.0.6/lib/naedhs.o `cat /U01/oracle/U01ora/8.0.6/lib/naldflgs` -lnetv2 -lnttcp
-lnetwork -lncr -lclient -lvsn -lcommon -lgeneric -lmm -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lnetv2 -lnttcp -lnetwork -lncr
-lclient -lvsn -lcommon -lgeneric -lepc -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lclient -lvsn -lcommon -lgeneric -lnlsrtl3 -lcore4
-lnlsrtl3 -lcore4 -lnlsrtl3 `cat /U01/oracle/U01ora/8.0.6/lib/sysliblist` -ldl -lpthread -lm /U01/oracle/U01ora/8.0.6/rdbms/lib/defopt.o
/U01/oracle/U01ora/8.0.6/rdbms/lib/ssbbded.o
/usr/lib/gcc/i386-redhat-linux/3.4.6/libgcc_s.so: undefined reference to `dl_iterate_phdr@GLIBC_2.2.4'
collect2: ld returned 1 exit status
make: *** [/U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS] Error 1
Done with link of fnd executable 'FNDFS' on Mon Feb 16 23:26:19 EST 2009
Relink of module "FNDFS" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /U01/oracle/U01appl/fnd/11.5.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.
Done with link of product 'fnd' on Mon Feb 16 23:26:19 EST 2009
adrelink is exiting with status 1
End of adrelink session
Solutions:
For Red Hat 4.0, re-apply Patch 4198954 by doing the following:
1. Verify the package has already been installed by running the following command:
#rpm -qs compat-oracle-rhel4
package compat-oracle-rhel4 is not installed
#rpm -qs compat-libcwait-2
package compat-libcwait-2 is not installed
2. Use the following command to apply the patch 4198954:
# rpm -Uvh compat-oracle-rhel4-1.0-5.i386.rpm
Preparing... ########################################### [100%]1:compat-oracle-rhel4 ########################################### [100%]
# rpm -Uvh compat-libcwait-2.1-1.i386.rpm
Preparing... ########################################### [100%]
1:compat-libcwait ########################################### [100%]
3. Verify the file sizes are now correct by running the following command again:
ls -l /usr/bin/gcc*
The correct file sizes are as follows:
[root@vision]# ls -l /usr/bin/gcc*
-rwxr-xr-x 1 root root 914 Feb 23 2005 /usr/bin/gcc
-rwxr-xr-x 2 root root 84780 Dec 1 2004 /usr/bin/gcc32
-rwxr-xr-x 1 root root 93120 Sep 26 10:28 /usr/bin/gcc.orig
4. Re-link the FNDFS executable using adadmin
Refered ID:
Doc ID: 464519.1
gcc -s -L/U01/oracle/U01ora/8.0.6/lib -L/U01/oracle/U01ora/8.0.6/lib/stubs -ldl -o /U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS
/U01/oracle/U01appl/fnd/11.5.0/lib/afpfss.o \
/U01/oracle/U01appl/fnd/11.5.0/lib/libfnd.a -lsql /U01/oracle/U01ora/8.0.6/lib/nautab.o /U01/oracle/U01ora/8.0.6/lib/naeet.o
/U01/oracle/U01ora/8.0.6/lib/naect.o /U01/oracle/U01ora/8.0.6/lib/naedhs.o `cat /U01/oracle/U01ora/8.0.6/lib/naldflgs` -lnetv2 -lnttcp
-lnetwork -lncr -lclient -lvsn -lcommon -lgeneric -lmm -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lnetv2 -lnttcp -lnetwork -lncr
-lclient -lvsn -lcommon -lgeneric -lepc -lnlsrtl3 -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lclient -lvsn -lcommon -lgeneric -lnlsrtl3 -lcore4
-lnlsrtl3 -lcore4 -lnlsrtl3 `cat /U01/oracle/U01ora/8.0.6/lib/sysliblist` -ldl -lpthread -lm /U01/oracle/U01ora/8.0.6/rdbms/lib/defopt.o
/U01/oracle/U01ora/8.0.6/rdbms/lib/ssbbded.o
/usr/lib/gcc/i386-redhat-linux/3.4.6/libgcc_s.so: undefined reference to `dl_iterate_phdr@GLIBC_2.2.4'
collect2: ld returned 1 exit status
make: *** [/U01/oracle/U01appl/fnd/11.5.0/bin/FNDFS] Error 1
Done with link of fnd executable 'FNDFS' on Mon Feb 16 23:26:19 EST 2009
Relink of module "FNDFS" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /U01/oracle/U01appl/fnd/11.5.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.
Done with link of product 'fnd' on Mon Feb 16 23:26:19 EST 2009
adrelink is exiting with status 1
End of adrelink session
Solutions:
For Red Hat 4.0, re-apply Patch 4198954 by doing the following:
1. Verify the package has already been installed by running the following command:
#rpm -qs compat-oracle-rhel4
package compat-oracle-rhel4 is not installed
#rpm -qs compat-libcwait-2
package compat-libcwait-2 is not installed
2. Use the following command to apply the patch 4198954:
# rpm -Uvh compat-oracle-rhel4-1.0-5.i386.rpm
Preparing... ########################################### [100%]1:compat-oracle-rhel4 ########################################### [100%]
# rpm -Uvh compat-libcwait-2.1-1.i386.rpm
Preparing... ########################################### [100%]
1:compat-libcwait ########################################### [100%]
3. Verify the file sizes are now correct by running the following command again:
ls -l /usr/bin/gcc*
The correct file sizes are as follows:
[root@vision]# ls -l /usr/bin/gcc*
-rwxr-xr-x 1 root root 914 Feb 23 2005 /usr/bin/gcc
-rwxr-xr-x 2 root root 84780 Dec 1 2004 /usr/bin/gcc32
-rwxr-xr-x 1 root root 93120 Sep 26 10:28 /usr/bin/gcc.orig
4. Re-link the FNDFS executable using adadmin
Refered ID:
Doc ID: 464519.1
How To Configure RMAN Backups To Tape via Oracle Enterprise Manager
Solution
+ Log in to Oracle Enterprise Manager Database Control
+ Navigate to: Maintenance -> Backup Settings -> Device
If grid control is used, we need to first select the appropriate database from Targets.
+ Now, under Tape Settings, specify the number of Tape Drives that will be available for this backup schedule/policy. RMAN will allocate that many simultaneous channels as many Tape Drives are specified.
+ On the same screen, specify the MML specific parameters under "Media Management Vendor Library Parameters" which as per our example above are:
ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)
Refer to the example script above and the screen shot below:
+ Log in to Oracle Enterprise Manager Database Control
+ Navigate to: Maintenance -> Backup Settings -> Device
If grid control is used, we need to first select the appropriate database from Targets.
+ Now, under Tape Settings, specify the number of Tape Drives that will be available for this backup schedule/policy. RMAN will allocate that many simultaneous channels as many Tape Drives are specified.
+ On the same screen, specify the MML specific parameters under "Media Management Vendor Library Parameters" which as per our example above are:
ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)
Refer to the example script above and the screen shot below:
+ Specify preferred credentials on the same page if they are not configured already. Additionally, also configure advanced settings such as CONTROLFILE AUTOBACKUP or the backup Retention Policy under the Policy sub-tab of the Backup Settings page. Click OK to save your settings.
+ Now, navigate to: Maintenance -> Schedule Backup.
+ Select Whole Database under Customized Backup and click Schedule Customized Backup. In the screen that follows, accept the defaults though you may like to tinker with some of the settings i.e. to delete obsolete backups etc under Advanced as per your requirement. click Next.
+ In this screen, select Tape to make backups to TAPE. Notice that the MML parameters that we saved earlier are shown here:
+ Click Next.On the new page you can specify Job Name, Job Description and the job schedule. Make appropriate changes and click Next.
+ Click Next
+ This last page now summarizes the configuration we have specified for our backup job and the EM generated script. You might want to edit the EM generated backup script for customized tags or format (backup-piece handle). After you have ensured all settings are appropriate, click Submit Job to complete the setup.
Refference: 735953.1
Create Document in R12 Web ADI Menu Generates HTTP 404 File Not Found Error
Symptoms
When trying to use the function Create Document the following error is displayed:
HTTP 404 File Not Found Error
Steps To Reproduce:
===================
Navigation -
1. Log onto a Release 12 instance with WEB ADI Installed
2. Seleft Responsibility Oracle Web ADI
3. Select Create Document
Solution
1. Go into the responsibility System Administrator.
2. Navigate to System Administrator > Security > Responsibility > Define > Oracle web ADI Responsibility
3. Set the menu to Desktop Integration Menu and save
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
When trying to use the function Create Document the following error is displayed:
HTTP 404 File Not Found Error
Steps To Reproduce:
===================
Navigation -
1. Log onto a Release 12 instance with WEB ADI Installed
2. Seleft Responsibility Oracle Web ADI
3. Select Create Document
Solution
1. Go into the responsibility System Administrator.
2. Navigate to System Administrator > Security > Responsibility > Define > Oracle web ADI Responsibility
3. Set the menu to Desktop Integration Menu and save
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
Oracle Release/Version Number for Apps/ Forms/ Jinitiator/ OID/ SSO/ Portal/ iAS/ OC4J/ Unix/ xxxx ….
OPatch Apply In database Level
OPatch is a Database patch.
Please download latest OPatch Tool and extract the RDBMS Oracle home.
1. Check the OPatch already installed or not
cd $ORACLE_HOME/OPatch
$opatch -lsinventory
This is command will show existing patch
Then Export the following environmet file
$ export ORACLE_HOME=/UAT/app/oracle
$ export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin
$ export OBJECT_MODE=32_64
$ cd patch/
Extract the Following OPatch.
p5246372_10203_LINUX.zip
p5965763_10203_LINUX.zip
5246372
5965763
Then Go to patch Directory and apply the Opatch.
$ cd 5965763/
$ opatch apply
Reference:
OPatch documentation list
Doc ID: 293369.1
Please download latest OPatch Tool and extract the RDBMS Oracle home.
1. Check the OPatch already installed or not
cd $ORACLE_HOME/OPatch
$opatch -lsinventory
This is command will show existing patch
Then Export the following environmet file
$ export ORACLE_HOME=/UAT/app/oracle
$ export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin
$ export OBJECT_MODE=32_64
$ cd patch/
Extract the Following OPatch.
p5246372_10203_LINUX.zip
p5965763_10203_LINUX.zip
5246372
5965763
Then Go to patch Directory and apply the Opatch.
$ cd 5965763/
$ opatch apply
Reference:
OPatch documentation list
Doc ID: 293369.1
Subscribe to:
Posts (Atom)
