APP-FND-00002: Password must contain at least one letter and at least one number
Workaround to fix while giving weak passwords to application users when changing using FNDCPASS
Error:
FNDCPASS apps/apps123 0 Y system/manager USER SYSADMIN sysadmin
Log filename : L8833563.log
Report filename : O8833563.out
Error:
FNDCPASS apps/apps123 0 Y system/manager USER SYSADMIN sysadmin
Log filename : L8833563.log
Report filename : O8833563.out
cat L8833563.log
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
module:
+---------------------------------------------------------------------------+
Current system time is 18-APR-2013 12:58:23
+---------------------------------------------------------------------------+
APP-FND-00002: Password must contain at least one letter and at least one number.
+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 18-APR-2013 12:58:23
Workaround:
Set the following profile option value to No. and Change password. Revert back profile option value
Signon Password Hard to Guess
Other profile options related to Password are below:
1-Signon password failure limit
2-Signon Password Length
3-Signon Password No Reuse
2-Signon Password Length
3-Signon Password No Reuse
Simple PCP configuration
Simple PCP configuration on Non RAC Environment
1. Assume that you have your Application tier is shared across all internal middle tiers
2. Assume you have two CM nodes
3. Stop the Concurrent Managers on both the CM nodes
4. Apply patch 9074947 on application tier
5. set APPLDCP value ON in the context file of both the CM nodes.
6. Run autoconfig on Both cm nodes
7. Verify tnsnames.ora on both CM nodes has FNDFS entries of both the nodes
8. Ensure Internal Monitors on both CM nodes is defined properly and have workshifts assigned to them
9. Make sure 2 Internal monitor Managers of both the nodes is activated. If not activate from Concurrent -> Manager -> Administrator
10. Use the following query to find out your concurrent managers details.
SELECT distinct C.USER_CONCURRENT_QUEUE_NAME, C.MAX_PROCESSES, C.RUNNING_PROCESSES, C.TARGET_PROCESSES, C.NODE_NAME, C.NODE_NAME2
FROM APPLSYS.FND_CONCURRENT_QUEUE_CONTENT A, APPLSYS.FND_CONCURRENT_PROGRAMS B, APPS.FND_CONCURRENT_QUEUES_VL C
WHERE type_id = b.concurrent_program_id and c.concurrent_queue_id = a.concurrent_queue_id;
10. Now Define Primary and secondary nodes for each concurrent manager from Concurrent -> Manager -> Define as per your configuration.
11. Bring up Concurrent Managers on both the CM nodes.
12. Test the concurrent managers by submitting two uniqe concurrent programs that should be running on managers on both the nodes.
Failover Testing
Test Case #1
1. Bring down Apps Listener on CM node 2 using kill -9
2. Kill all FNDLIBR process on CM node 2 using kill -9
3. Start Apps listener on CM node 2 after 5 mins.
4. Monitor CM2, you should see all the managers on CM2 should come up automatially
Test Case #2
1. Bring down apps listener on CM node2 using kill -9.
2. Start the managers on CM1, you should see managers of CM2 will start on CM node 1.
3. Bring up Apps listenr on CM2.
4. You should see, Managers of CM2 should fall back to CM2 from CM1.
Test Case #3
1. Bring down host of CM node 2. It should be shutdown.
2. You should see all the managers of CM2 should be failed over to CM1
3. Bring up host of CM node2.
4. Bring up apps listener on cm node2.
5. You should see all the managers of CM2 should fall back to CM2 fro CM1.
Oracle Note id : How to Setup and Test Failover of PCP on Non-RAC Environments. [ID 743716.1]
How to Create The Service Manager ‘FNDSM’ on Oracle Applications
Run below command to check if node is registered for FNDSM:-
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like ‘FNDSM%’;
if not then use Note.218893.1 :How to Create The Service Manager ‘FNDSM’ on Oracle Applications
Solution
From the Application tier:
1. Log in as applmgr
2. cd to $FND_TOP/patch/115/sql
3. Run the script: afdcm037.sql
4. This script will create libraries for FNDSM and create Managers for
Preexisting Nodes.
Note: Service Manager “FNDSM” can not be created from form:
Concurrent> Manager> Define under Sysadmin Responsibility.
Reference <bug:6085070 FNDSM TRIGGER CAUSES SERVICE MANAGER NOT TO BE CREATED AFTER CLONING SINGLE NODE>
How to enable Apache and Jserv Debugging in Oracle Apps 11i?
PURPOSE:-If a user
experiences an error, request a screen shot of the error and any further
error details that they can report.If the error is reproducible, enable
the following middle tier debug settings and collect diagnostic
information appropriately and upload to support for troubleshooting.
Looking for Jserv.log at $IAS_ORACLE_HOME/Apache/Jserv/logs then enable…
For Temporary purpose manually editing configuration files.
1) Shut Down Apache Server
2) Backup the existing files in the following files:
$IAS_ORACLE_HOME/Apache/Apache/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs/jvm
3) Enable debug logging for Apache
s_apache_loglevel=debug (In Context File)
Or
loglevel debug (In $IAS_ORACLE_HOME/Apache/Apache/conf/httpd.conf)
4) Enable debug logging for mod_jserv
s_apjservloglevel=debug (In Context File)
Or
ApJServLogLevel debug (In $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.conf)
5) Enable debug logging for Jserv
s_oacorelog=true (In Context File)
Or
log=true log.channel=true log.channel.info=true log.channel.debug=true
(In $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties)
6) Enable debug logging for Forms Listener Servlet JVM. (Optional)
s_oaformslog=true (In Context File)
Or
log=true log.channel=true log.channel.info=true log.channel.debug=true
(In $IAS_ORACLE_HOME/Apache/Jserv/etc/forms.properties)
7) Restart Apache
(If Context File had been edited in above steps then run autoconfig to update the configuration files.) 8) Replicate the Problem.
9) Review the following files from the $IAS_ORACLE_HOME/Apache/Jserv/logs directory
a) mod_jserv.log
b) jserv.log
c) All files from the $IAS_ORACLE_HOME/Apache/Jserv/logs/jvm directory These will
have filenames of the form jvm.jvm.stdoutstderr For example,
OACoreGroup.0.stderr
d) $COMMON_TOP/rgf/instance_hostname/javacache.log
Source: http://leenus2b.wordpress.com
For R12: How To : How to enable Apache, OC4J and OPMN logging in Oracle Applications R12 use Doc id [ID 419839.1]
Looking for Jserv.log at $IAS_ORACLE_HOME/Apache/Jserv/logs then enable…
For Temporary purpose manually editing configuration files.
1) Shut Down Apache Server
2) Backup the existing files in the following files:
$IAS_ORACLE_HOME/Apache/Apache/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs/jvm
3) Enable debug logging for Apache
s_apache_loglevel=debug (In Context File)
Or
loglevel debug (In $IAS_ORACLE_HOME/Apache/Apache/conf/httpd.conf)
4) Enable debug logging for mod_jserv
s_apjservloglevel=debug (In Context File)
Or
ApJServLogLevel debug (In $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.conf)
5) Enable debug logging for Jserv
s_oacorelog=true (In Context File)
Or
log=true log.channel=true log.channel.info=true log.channel.debug=true
(In $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties)
6) Enable debug logging for Forms Listener Servlet JVM. (Optional)
s_oaformslog=true (In Context File)
Or
log=true log.channel=true log.channel.info=true log.channel.debug=true
(In $IAS_ORACLE_HOME/Apache/Jserv/etc/forms.properties)
7) Restart Apache
(If Context File had been edited in above steps then run autoconfig to update the configuration files.) 8) Replicate the Problem.
9) Review the following files from the $IAS_ORACLE_HOME/Apache/Jserv/logs directory
a) mod_jserv.log
b) jserv.log
c) All files from the $IAS_ORACLE_HOME/Apache/Jserv/logs/jvm directory These will
have filenames of the form jvm.jvm.stdoutstderr For example,
OACoreGroup.0.stderr
d) $COMMON_TOP/rgf/instance_hostname/javacache.log
Source: http://leenus2b.wordpress.com
For R12: How To : How to enable Apache, OC4J and OPMN logging in Oracle Applications R12 use Doc id [ID 419839.1]
Forms Servlet mode to Socket mode conversion on Release 12 Apps
How to convert Forms server to Socket mode from Servlet mode in Oracle Apps R12
Run the following command to enable Forms Socket Mode on Forms/web nodes (Place correct context file name and port value)
$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$CONTEXT_FILE -mode=socket -port=9030 -runautoconfig=No
Where port = forms port and contextfile=your environment contextfile
To Start/Stop/check Status of forms servers use following scripts
cd $ADMIN_SCRIPTS_HOME
./adformsrvctl.sh status/stop/start
Run the following command to enable Forms Socket Mode on Forms/web nodes (Place correct context file name and port value)
$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$CONTEXT_FILE -mode=socket -port=9030 -runautoconfig=No
Where port = forms port and contextfile=your environment contextfile
To Start/Stop/check Status of forms servers use following scripts
cd $ADMIN_SCRIPTS_HOME
./adformsrvctl.sh status/stop/start
MSG-00102: Error Message :ORA-20100: File o0000071.tmp creation for FND_FILE failed.
Troubleshooting Details
If a PL/SQL Concurrent Program can't write to an external file, you will receive an error message similar to:
MSG-00102: Error Message :ORA-20100: File o0000071.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
ORA-06512: at "APPS.FND_FILE", line 378
ORA-06512: at "APPS.FND_FILE", line 473
ORA-06512: at "APPS.AP_TRIAL_BALANCE_PKG", line 192
REP-1419: 'beforereport': PL/SQL program aborted.
NOTE: Applications also produces temporary PL/SQL output files used in concurrent processing. These files are written to a location on the database server node specified by the APPLPTMP environment setting. The APPLPTMP directory must be the same directory as specified by the utl_file_dir parameter in your database initialization file.
.
Rapid Install sets both APPLPTMP and the utl_file_dir parameter to the same default directory. As the temporary files placed in this directory may contain context sensitive information, it should be a secure directory on the database server node with read and write access for the database server owner. In a multi-node system, the directory defined by APPLPTMP does not need to exist on the application tier servers. During an upgrade with AutoUpgrade, you must provide the utl_file_dir parameter value for the APPLPTMP environment setting.
To isolate where the problem is, verify the following:
1) Make sure that the name of the file is valid (the file name should not include characters like "^")
2) Make sure that APPLPTMP is set to a valid directory and that BOTH the applmgr user and the database user have read and write permissions on that directory (normally, it can be set to the same directory as APPLTMP)
3) Make sure that the file does not exit on the directory pointed by APPLPTMP
4) Make sure the directory pointed by APPLPTMP is the first entry on the utl_file_dir. Also, verify that all the entries on the utl_file_dir are valid and that the applmgr has read/write permissions.
If using an spfile, verify the proper syntax to set utl_file_dir:
Eg: ALTER SYSTEM SET UTL_FILE_DIR='directory1','directory2' scope=spfile;
5) If still having problems, check if you can write a file directly using FND_FILE, which is the package used by the Application. From sqlplus, connected as the apps user, run:
SQL> exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST');
This should dump a file on APPLPTMP.
If this test works, it would indicate that FND_FILE is ok and the problem is possibly with the Application.
You may want to leave only one entry on utl_file_dir for this test.
6) If still having problems, check if you can write a file using UTL_FILE, which is used by FND_FILE.
Run the PL/SQL below, changing to the first entry on utl_file_dir (you may want to leave just one entry on utl_file_dir for this test).
set serveroutput on
DECLARE
file_location VARCHAR2(256) := '';
file_name VARCHAR2(256) := 'utlfile1.lst';
file_text VARCHAR2(256) := 'THIS IS A TEST';
file_id UTL_FILE.file_type;
BEGIN
file_id := UTL_FILE.fopen(file_Location, file_name, 'W');
UTL_FILE.put_line(file_id, file_text);
UTL_FILE.fclose(file_id);
EXCEPTION
WHEN UTL_FILE.INVALID_PATH
THEN dbms_output.put_line('Invalid path ' || SQLERRM);
WHEN OTHERS
THEN dbms_output.put_line('Others '|| SQLCODE || ' ' || SQLERRM);
END;
/
This program should dump a file on the requested directory. If the test fails, the problem is probably on the Database side.
If it works, the problem is probably on FND_FILE. In this scenario, check the versions of AFCPPIOS.pls and AFCPPIOB.pls.
Source : Troubleshooting ORA-20100 on Concurrent Processing [ID 261693.1] (suppot.oracle.com)
If a PL/SQL Concurrent Program can't write to an external file, you will receive an error message similar to:
MSG-00102: Error Message :ORA-20100: File o0000071.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
ORA-06512: at "APPS.FND_FILE", line 378
ORA-06512: at "APPS.FND_FILE", line 473
ORA-06512: at "APPS.AP_TRIAL_BALANCE_PKG", line 192
REP-1419: 'beforereport': PL/SQL program aborted.
NOTE: Applications also produces temporary PL/SQL output files used in concurrent processing. These files are written to a location on the database server node specified by the APPLPTMP environment setting. The APPLPTMP directory must be the same directory as specified by the utl_file_dir parameter in your database initialization file.
.
Rapid Install sets both APPLPTMP and the utl_file_dir parameter to the same default directory. As the temporary files placed in this directory may contain context sensitive information, it should be a secure directory on the database server node with read and write access for the database server owner. In a multi-node system, the directory defined by APPLPTMP does not need to exist on the application tier servers. During an upgrade with AutoUpgrade, you must provide the utl_file_dir parameter value for the APPLPTMP environment setting.
To isolate where the problem is, verify the following:
1) Make sure that the name of the file is valid (the file name should not include characters like "^")
2) Make sure that APPLPTMP is set to a valid directory and that BOTH the applmgr user and the database user have read and write permissions on that directory (normally, it can be set to the same directory as APPLTMP)
3) Make sure that the file does not exit on the directory pointed by APPLPTMP
4) Make sure the directory pointed by APPLPTMP is the first entry on the utl_file_dir. Also, verify that all the entries on the utl_file_dir are valid and that the applmgr has read/write permissions.
If using an spfile, verify the proper syntax to set utl_file_dir:
Eg: ALTER SYSTEM SET UTL_FILE_DIR='directory1','directory2' scope=spfile;
5) If still having problems, check if you can write a file directly using FND_FILE, which is the package used by the Application. From sqlplus, connected as the apps user, run:
SQL> exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST');
This should dump a file on APPLPTMP.
If this test works, it would indicate that FND_FILE is ok and the problem is possibly with the Application.
You may want to leave only one entry on utl_file_dir for this test.
6) If still having problems, check if you can write a file using UTL_FILE, which is used by FND_FILE.
Run the PL/SQL below, changing to the first entry on utl_file_dir (you may want to leave just one entry on utl_file_dir for this test).
set serveroutput on
DECLARE
file_location VARCHAR2(256) := '';
file_name VARCHAR2(256) := 'utlfile1.lst';
file_text VARCHAR2(256) := 'THIS IS A TEST';
file_id UTL_FILE.file_type;
BEGIN
file_id := UTL_FILE.fopen(file_Location, file_name, 'W');
UTL_FILE.put_line(file_id, file_text);
UTL_FILE.fclose(file_id);
EXCEPTION
WHEN UTL_FILE.INVALID_PATH
THEN dbms_output.put_line('Invalid path ' || SQLERRM);
WHEN OTHERS
THEN dbms_output.put_line('Others '|| SQLCODE || ' ' || SQLERRM);
END;
/
This program should dump a file on the requested directory. If the test fails, the problem is probably on the Database side.
If it works, the problem is probably on FND_FILE. In this scenario, check the versions of AFCPPIOS.pls and AFCPPIOB.pls.
Source : Troubleshooting ORA-20100 on Concurrent Processing [ID 261693.1] (suppot.oracle.com)
"Error Occurred While Attempting to Establish an Applications File Server Connection"
Error:
" An error occurred while attempting to establish an Applications File Server connection. There may be a network configuration problem, or the TNS listener may not be running on "
Solutions to Check
1. Is this a Multinode Install or a Single Node Install.
- If this is a Multinode Install, you will need access to the Middle Tier and the Backend Tier (Concurrent Processor) 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora files
- If this is a Single Node Install, you need access to the Concurrent Processor 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora file
2. Run a report, is there actually a Report Output and Log file being produced at the Operating System level?
- Check the $APPLCSF/out and the $APPLCSF/log directories for the Request_ID out and log file
- If there are no log and output file being produces there Check the permissions on those directories (APPLMGR should have write)
- If $APPLCSF is not set, check the $FND_TOP/log and out for output and logs
3. Confirm that there are 2 listener processes actively running for the Instance that you cannot view reports on -- 1 from 8.0.6 and from 8.1.6 directory structures
- type the following:
ps -ef | grep tnslsnr
- If there is only 1 listener running from the 8.1.6 directory structure
That is the Database Listener
The FNDFS listener needs to be started separately from the Database Listener
- To start the FNDFS Listener:
a. Log the Operating System Level as the APPLMGR account user
b. Set the environment for the $APPL_TOP & 8.0.6 $ORACLE_HOME (APPSORA.env)
c. Go to the $OAD_TOP/admin/scripts (Common_top area)
d. Run the following script:
adalnctl.sh start APPS_SID
(you can confirm the FNDFS Listener name from viewing the 8.0.6 ORACLE_HOME/network/admin/listener.ora file)
4. Check the actual machine name for the Concurrent Processor Server
- type the following:
uname -n
5. Go to the Applications and check the CONCURRENT > MANAGER > ADMINISTER screen in the System Administrator Responsibility The INTERNAL MANAGER NODE NAME; is it the same as what was returned from question 4?
- If it is the same then continue with next step
- If it is not the same,
Shutdown Concurrent Managers and update the FND table:
a. Go to the $OAD_TOP/admin/scripts
b. adcmctl.sh apps/apps stop
c. Connect to SQL*PLUS apps/apps
d. SQL > select target_node from FND_CONCURRENT_QUEUES;
--------------------
This may return the name of an old machine
e. SQL > update FND_CONCURRENT_QUEUES set target_node='' where target_node='';
f. SQL > commit;
g. SQL > exit
h. adcmctl.sh apps/apps start
6. In the 8.0.6 TNSNAMES.ora file, look at the FNDFS_ connection string entry.
Is the hostname value the same as is in questions 4?
- The Rapid Install creates 2 or sometimes 3 FNDFS entries in the TNSNAMES.ora
a. 1 with the FNDFS_
b. 1 with the FNDFS_
c. 1 with the FNDFS_
- The one that is the correct entry is FNDFS_ (hostname being what is returned from a "uname -n")
- If this file does not contain the correct Hostname value
Make a backup of it and edit it to change the FNDFS entry.
7. Check the Network Connection for the FNDFS entry that was defined by the Rapid Install.
- At the Operating System Level
a. tnsping FNDFS_
- This should return the Hostname name and Port information identical to the FNDFS entry in the TNSNAMES.ora file
8. Check the Following PROFILE > SYSTEM Options in The System Administrator Responsibility
CONCURRENT: Report Access Level (this must be set to USER or RESPONSIBILITY)
RRA: Service Prefix (this should be BLANK)
RRA: Enabled (this must be set to YES)
VIEWER: Text (this should be BLANK to view with the default text viewer)
- Viewer: Text can Be set to "browser" to view with Netscape or IE
9. This step should be performed in a case where there might have been patches applied and possibly the FNDFS executable was not Relinked, or it may be missing from the file system or corrupted.
- Shutdown the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh stop APPS_SID
- Rename or Move the Current FNDFS executable before relinking
a. $FND_TOP/bin
mv FNDFS FNDFS.bak
b. As APPLMGR account user
adrelink.sh force=y "fnd FNDFS"
- Start the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh start APPS_SID
Metalink Note : ID 117012.1
" An error occurred while attempting to establish an Applications File Server connection. There may be a network configuration problem, or the TNS listener may not be running on "
Solutions to Check
1. Is this a Multinode Install or a Single Node Install.
- If this is a Multinode Install, you will need access to the Middle Tier and the Backend Tier (Concurrent Processor) 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora files
- If this is a Single Node Install, you need access to the Concurrent Processor 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora file
2. Run a report, is there actually a Report Output and Log file being produced at the Operating System level?
- Check the $APPLCSF/out and the $APPLCSF/log directories for the Request_ID out and log file
- If there are no log and output file being produces there Check the permissions on those directories (APPLMGR should have write)
- If $APPLCSF is not set, check the $FND_TOP/log and out for output and logs
3. Confirm that there are 2 listener processes actively running for the Instance that you cannot view reports on -- 1 from 8.0.6 and from 8.1.6 directory structures
- type the following:
ps -ef | grep tnslsnr
- If there is only 1 listener running from the 8.1.6 directory structure
That is the Database Listener
The FNDFS listener needs to be started separately from the Database Listener
- To start the FNDFS Listener:
a. Log the Operating System Level as the APPLMGR account user
b. Set the environment for the $APPL_TOP & 8.0.6 $ORACLE_HOME (APPSORA.env)
c. Go to the $OAD_TOP/admin/scripts (Common_top area)
d. Run the following script:
adalnctl.sh start APPS_SID
(you can confirm the FNDFS Listener name from viewing the 8.0.6 ORACLE_HOME/network/admin/listener.ora file)
4. Check the actual machine name for the Concurrent Processor Server
- type the following:
uname -n
5. Go to the Applications and check the CONCURRENT > MANAGER > ADMINISTER screen in the System Administrator Responsibility The INTERNAL MANAGER NODE NAME; is it the same as what was returned from question 4?
- If it is the same then continue with next step
- If it is not the same,
Shutdown Concurrent Managers and update the FND table:
a. Go to the $OAD_TOP/admin/scripts
b. adcmctl.sh apps/apps stop
c. Connect to SQL*PLUS apps/apps
d. SQL > select target_node from FND_CONCURRENT_QUEUES;
--------------------
This may return the name of an old machine
e. SQL > update FND_CONCURRENT_QUEUES set target_node='' where target_node='';
f. SQL > commit;
g. SQL > exit
h. adcmctl.sh apps/apps start
6. In the 8.0.6 TNSNAMES.ora file, look at the FNDFS_ connection string entry.
Is the hostname value the same as is in questions 4?
- The Rapid Install creates 2 or sometimes 3 FNDFS entries in the TNSNAMES.ora
a. 1 with the FNDFS_
b. 1 with the FNDFS_
c. 1 with the FNDFS_
- The one that is the correct entry is FNDFS_ (hostname being what is returned from a "uname -n")
- If this file does not contain the correct Hostname value
Make a backup of it and edit it to change the FNDFS entry.
7. Check the Network Connection for the FNDFS entry that was defined by the Rapid Install.
- At the Operating System Level
a. tnsping FNDFS_
- This should return the Hostname name and Port information identical to the FNDFS entry in the TNSNAMES.ora file
8. Check the Following PROFILE > SYSTEM Options in The System Administrator Responsibility
CONCURRENT: Report Access Level (this must be set to USER or RESPONSIBILITY)
RRA: Service Prefix (this should be BLANK)
RRA: Enabled (this must be set to YES)
VIEWER: Text (this should be BLANK to view with the default text viewer)
- Viewer: Text can Be set to "browser" to view with Netscape or IE
9. This step should be performed in a case where there might have been patches applied and possibly the FNDFS executable was not Relinked, or it may be missing from the file system or corrupted.
- Shutdown the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh stop APPS_SID
- Rename or Move the Current FNDFS executable before relinking
a. $FND_TOP/bin
mv FNDFS FNDFS.bak
b. As APPLMGR account user
adrelink.sh force=y "fnd FNDFS"
- Start the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh start APPS_SID
Metalink Note : ID 117012.1
FAQs - How do we know how many users are connected to Oracle Applications.
FAQs - How do we know how many users are connected to Oracle Applications.
1. Enable Profile Option "Sign-On Audit" at "Form" level.
2. Run "Purge Signon Audit" request.
3. Security:Users -> Monitor" option
4 or with the below sql query mentioned below.
select distinct fu.user_name User_Name,fr.RESPONSIBILITY_KEY Responsibility
from fnd_user fu, fnd_responsibility fr, icx_sessions ic
where fu.user_id = ic.user_id AND
fr.responsibility_id = ic.responsibility_id AND
ic.disabled_flag='N' AND
ic.responsibility_id is not null AND
ic.last_connect like sysdate;
5. Can use this SQL statement to count concurrent_users in Oracle apps:
select count(distinct d.user_name) from apps.fnd_logins a,
v$session b, v$process c, apps.fnd_user d
where b.paddr = c.addr
and a.pid=c.pid
and a.spid = b.process
and d.user_id = a.user_id
and (d.user_name = 'USER_NAME' OR 1=1)
MRC Implementaion on Existing Environment???
What is MRC?
MRC allows Oracle Applications to support organizations that are transitioning from their national currency (Functional Currency) to other Currencies Supported by Oracle.
Is the process of converting functional currency into other currency during reporting.
Modules Impacted With MRC
General Ledger
Account Payables
Account Receivables
Fixed Assets etc.
How do I Enable MRC
STEPS TO BE FOLLOWED:
Installing MRC with Invokers Rights On( This is for New Installation).
Set Up Environment and Database.
Compile and Validate APPS Schemas.
Convert to Multiple Reporting Currencies.
Verify the Installation.
Perform Post–Installation Steps.
Maintain MRC Schema Objects
Running adadmin
Login to FE Node (elephant)
Run adadmin
Filename [adadmin.log] : adadmin_dv1_mrc.log
Please enter the batchsize [1000] : 100000
Enter the password for your 'SYSTEM' ORACLE schema:
Enter the ORACLE password of Application Object Library [APPS]
4. Maintain Applications Database Entities menu
1. Validate APPS schema
This will generate APPS.lst @ $APPL_TOP/admin/SID/out/APPS.lst
Sample Summary of Issues and Proposed Fixes Reported by APPS.lst
Objects with the same name as schema
Proposed Fix: Dropping all objects
Invalid Synonyms in APPS
Proposed Fix: Drop & Recreate all ,drop which are still invalid as reported by validate APPS.
missing or incorrect synonyms in "APPS"
Proposed Fix : Repointed the missing and incorrect synonyms
Missing Grants
Proposed Fix: Grant will be given to the reported objects.
Missing Privileges/ synonyms to objects not in "APPS" base schemas - 2586
Proposed Fix: Grants will be given
Invalid Objects
Proposed Fix: If Close to production. The objects will be documented and the results verified post MRC Installation.
Code Objects in the Base Schema - (Recommended but not mandatory)
Proposed Fix: No Action
Tables exist both in APPS & Base Schema
Proposed Fix: Compare in production & dropped.
Checking for packages in "APPS" with lines > 255 characters
Proposed Fix: Breaking the lines having more than 255 chars.
Checking for missing/invalid APPS_DDL or APPS_ARRAY_DDL packages
Proposed Fix: DBA will address this.
some Issue while running adadmin
sqlplus -s SYSTEM/***** @/apps/SID/appl_top/ad/11.5.0/admin/sql/advrfapp.sql APPS APPLSYS
declare
*
ERROR at line 1:
ORA-20000: ORA-01403: no data found : This procedure cannot continue because
the "SELECT ANY DICTIONARY" privilege for the SYSTEM schema is missing.
Please rerun the procedure as the privilege has now been granted.
ORA-06512: at line 26
Re-run adamin or grant select any dictionary to system;
ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_LOCK.
Identify the session holding DBMS_LOCK
Workaround
Set job queue process to 0
sqlplus -s SYSTEM/***** @/apps/sid/appl_top/ad/11.5.0/admin/sql/advrfapp.sql APPS APPLSYS
ERROR at line 1:
ORA-20000: ORA-20000: ORU-10027: buffer overflow, limit of 50000 bytes :
Fix : Changed serveroutput from 50000 to 1000000
Different issues
Incorrect synonym:
APPS.MSD_APP_INSTANCE_ORGS - should point to MRP.MSD_APP_INSTANCE_ORGS. Incorrect
Synonym Pointing to Remote Objects with DB Link
Synomyms Pointing to Objects which is Invalid.
Synomyms pointing to Objects which does not exist.
Application Schema not having standard packages like APPS_ARRAY_DDL and APPS_DDL
Similar table object exists in two different schemas.
Necessary grants are not given from Custom Apps schema to APPS.
Package line length more than 255 chars
Invalid Objects
Enabling MRC through adadmin
Run adadmin
4. Maintain Applications Database Entities menu
5. Convert to Multiple Reporting Currencies
Enter SYSTEM password
Enter the number of workers [64] : 24
Converting to Multiple Reporting Currencies (MRC) will create
one extra schema per APPS schema in your database.
Each MRC schema requires about 600 Megabytes of free space in your
SYSTEM tablespace and takes from 6 to 18 hours to create.
You must not perform any DDL operations on your Oracle Applications
database while converting to MRC, but you may change data.
Issue and Fixes
declare
*
ERROR at line 1:
ORA-20005: ORA-02021: DDL operations are not allowed on a remote database
[create_mc_schema(APPLSYS, TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS,
APPS, APPS_MRC, none, TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,CCA_ACK_HEADER, FALSE,ALL,APPS):
create_grant(APPS,APPS_MRC,CCA_ACK_HEADER,ALL,FALSE,): do_apps_ddl(APPS,GRANT
ALL ON "CCA_ACK_HEADER" TO APPS_MRC): do_apps_ddl(APPS,GRANT ALL ON
"AMV_MATCHING_QUEUE_TBL" TO APPS_MRC): do_apps_ddl(APPS,GRANT ALL ON
"AK_LOADER_TEMP" TO APPS_MRC): Start Time: 2009-03-17;00:19:25 Failure Time:
2009-03-17;00:23:24 Elapsed: 00;00:03:59]
ORA-06512: at line 25
Fix : Drop the object pointing to remote object and re-create after MRC is over
ERROR at line 1:
ORA-20005: ORA-01403: no data found
ORA-01720: grant option does not exist for 'APPLSYS.FND_LOBS'
[create_mc_schema(APPLSYS, TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS,
APPS, APPS_MRC, none, TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,FCOA_ATTACHMENTS_V, FALSE,ALL,APPS):
create_grant(FCOA_ATTACHMENTS_V does not exist in ): do_apps_ddl(APPS,GRANT ALL
ON "FCOA_ATTACHMENTS_V" TO APPS_MRC): Start Time: 2009-03-05;08:56:58 Failure
Time: 2009-03-05;08:58:33 Elapsed: 00;00:01:35]
ORA-06512: at line 25
Fix :select owner,object_type from dba_objects where object_name='FCOA_ATTACHMENTS_V';
CONNECT APPLSYS/xxxx
grant ALL on APPLSYS.FND_LOBS TO XXFAXMGR with grant option;
grant ALL on APPLSYS.FND_ATTACHED_DOCUMENTS TO XXFAXMGR with grant option;
CONNECT APPS/xxxxxx
grant ALL on APPS.FND_ATTACHED_DOCS_FORM_VL TO XXFAXMGR with grant option;
CONNECT XXFAXMGR/xxxxx
grant ALL on XXFAXMGR.FCOA_ATTACHMENTS_V TO APPS with grant option;
ERROR at line 1:
ORA-20005: ORA-00980: synonym translation is no longer valid
[create_mc_schema(APPLSYS, TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS,
APPS, APPS_MRC, none, TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,AVL_LOOKUPS, FALSE,ALL,APPS):
create_grant(APPS,APPS_MRC,AVL_LOOKUPS,ALL,FALSE,): do_apps_ddl(APPS,GRANT ALL
ON "AVL_LOOKUPS" TO APPS_MRC): Start Time: 2009-03-10;03:27:40 Failure Time:
2009-03-10;03:27:43 Elapsed: 00;00:00:03]
ORA-06512: at line 25
conn /as sysdba
col object_name for a40
select owner,object_name, object_type from dba_objects where OBJECT_NAME ='AVL_LOOKUPS';
connect apps/xxxxx
grant all on AVL_LOOKUPS to APPS_MRC;
ERROR at line 1:
ORA-20005: ORA-20000: PACKAGE BODY APPS.CMF_CREATE_ITEMS_PKG: Line 28 longer
than 255 characters. [create_mc_schema(APPLSYS, TRUE, FALSE, none):
do_create_mc_schema(1, APPLSYS, APPS, APPS_MRC, none, TRUE):
invoker_mrc_grants(APPS, APPS_MRC): grant_a_package(APPS, CMF_CREATE_ITEMS_PKG,
PACKAGE, APPS_MRC, Y, D, FALSE):
ad_apps_private.copy_code(CMF_CREATE_ITEMS_PKG,PACKAGE BODY,APPS,APPS_MRC):
Start Time: 2009-03-09;03:50:50 Failure Time: 2009-03-09;03:55:23 Elapsed:
00;00:04:33]
ORA-06512: at line 25
Compile package
===============
ALTER PACKAGE APPS.CMF_CREATE_ITEMS_PKG COMPILE BODY;
ALTER PACKAGE APPS.CMF_CREATE_ITEMS_PKG COMPILE;
Action : Line length fix by Maynak and complied the package
Status : Restarted adadmin and Fixed
ERROR at line 1:
ORA-20005: ORA-04063: has errors
ORA-04063: view "CMS.CMS_R_SO_HEADERS_V" has errors [create_mc_schema(APPLSYS,
TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS, APPS, APPS_MRC, none,
TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,CMS_R_SO_HEADERS_V, FALSE,ALL,APPS):
create_grant(APPS,APPS_MRC,CMS_R_SO_HEADERS_V,ALL,FALSE,):
do_apps_ddl(APPS,GRANT ALL ON "CMS_R_SO_HEADERS_V" TO APPS_MRC): Start Time:
2009-03-17;03:56:51 Failure Time: 2009-03-17;03:56:53 Elapsed: 00;00:00:02]
ORA-06512: at line 25
Fix:
.Take bacup of source of that view using dbms_metadata
Drop that view after consulting appl team.
Maintaining MRC after Patching and addition of objects to APPS/Custom schema impacting MRC
Increase of Patching Window time
Synonym Objects exists in APPS which is pointing to remote DB through DB link
Non Standard APPS Custom schema creation without Standard packages.
New custom Package creation with Line > 255.
Full grant of SYS, APPS , APPLSYS and other Standard APPS schema objects to Custom Apps Schema Owners
Existence of Code objects in base schemas
Reference
Metalink IDS
135756.1
135773.1
Pre Requisites to Enable MRC
1. 1486355 or 1512489 patches to be applied
2. Requirement 2000m in SYSTEM/TEMP and UNDO each.
3. Modify Validation Script to increase buffer size as below:
cd $AD_TOP/admin/sql/
Modify advrfapp.sql
From :
begin
dbms_output.enable(50000);
end;
To :
begin
dbms_output.enable(1000000);
end;
MRC allows Oracle Applications to support organizations that are transitioning from their national currency (Functional Currency) to other Currencies Supported by Oracle.
Is the process of converting functional currency into other currency during reporting.
Modules Impacted With MRC
General Ledger
Account Payables
Account Receivables
Fixed Assets etc.
How do I Enable MRC
STEPS TO BE FOLLOWED:
Installing MRC with Invokers Rights On( This is for New Installation).
Set Up Environment and Database.
Compile and Validate APPS Schemas.
Convert to Multiple Reporting Currencies.
Verify the Installation.
Perform Post–Installation Steps.
Maintain MRC Schema Objects
Running adadmin
Login to FE Node (elephant)
Run adadmin
Filename [adadmin.log] : adadmin_dv1_mrc.log
Please enter the batchsize [1000] : 100000
Enter the password for your 'SYSTEM' ORACLE schema:
Enter the ORACLE password of Application Object Library [APPS]
4. Maintain Applications Database Entities menu
1. Validate APPS schema
This will generate APPS.lst @ $APPL_TOP/admin/SID/out/APPS.lst
Sample Summary of Issues and Proposed Fixes Reported by APPS.lst
Objects with the same name as schema
Proposed Fix: Dropping all objects
Invalid Synonyms in APPS
Proposed Fix: Drop & Recreate all ,drop which are still invalid as reported by validate APPS.
missing or incorrect synonyms in "APPS"
Proposed Fix : Repointed the missing and incorrect synonyms
Missing Grants
Proposed Fix: Grant will be given to the reported objects.
Missing Privileges/ synonyms to objects not in "APPS" base schemas - 2586
Proposed Fix: Grants will be given
Invalid Objects
Proposed Fix: If Close to production. The objects will be documented and the results verified post MRC Installation.
Code Objects in the Base Schema - (Recommended but not mandatory)
Proposed Fix: No Action
Tables exist both in APPS & Base Schema
Proposed Fix: Compare in production & dropped.
Checking for packages in "APPS" with lines > 255 characters
Proposed Fix: Breaking the lines having more than 255 chars.
Checking for missing/invalid APPS_DDL or APPS_ARRAY_DDL packages
Proposed Fix: DBA will address this.
some Issue while running adadmin
sqlplus -s SYSTEM/***** @/apps/SID/appl_top/ad/11.5.0/admin/sql/advrfapp.sql APPS APPLSYS
declare
*
ERROR at line 1:
ORA-20000: ORA-01403: no data found : This procedure cannot continue because
the "SELECT ANY DICTIONARY" privilege for the SYSTEM schema is missing.
Please rerun the procedure as the privilege has now been granted.
ORA-06512: at line 26
Re-run adamin or grant select any dictionary to system;
ORA-04021: timeout occurred while waiting to lock object SYS.DBMS_LOCK.
Identify the session holding DBMS_LOCK
Workaround
Set job queue process to 0
sqlplus -s SYSTEM/***** @/apps/sid/appl_top/ad/11.5.0/admin/sql/advrfapp.sql APPS APPLSYS
ERROR at line 1:
ORA-20000: ORA-20000: ORU-10027: buffer overflow, limit of 50000 bytes :
Fix : Changed serveroutput from 50000 to 1000000
Different issues
Incorrect synonym:
APPS.MSD_APP_INSTANCE_ORGS - should point to MRP.MSD_APP_INSTANCE_ORGS. Incorrect
Synonym Pointing to Remote Objects with DB Link
Synomyms Pointing to Objects which is Invalid.
Synomyms pointing to Objects which does not exist.
Application Schema not having standard packages like APPS_ARRAY_DDL and APPS_DDL
Similar table object exists in two different schemas.
Necessary grants are not given from Custom Apps schema to APPS.
Package line length more than 255 chars
Invalid Objects
Enabling MRC through adadmin
Run adadmin
4. Maintain Applications Database Entities menu
5. Convert to Multiple Reporting Currencies
Enter SYSTEM password
Enter the number of workers [64] : 24
Converting to Multiple Reporting Currencies (MRC) will create
one extra schema per APPS schema in your database.
Each MRC schema requires about 600 Megabytes of free space in your
SYSTEM tablespace and takes from 6 to 18 hours to create.
You must not perform any DDL operations on your Oracle Applications
database while converting to MRC, but you may change data.
Issue and Fixes
declare
*
ERROR at line 1:
ORA-20005: ORA-02021: DDL operations are not allowed on a remote database
[create_mc_schema(APPLSYS, TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS,
APPS, APPS_MRC, none, TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,CCA_ACK_HEADER, FALSE,ALL,APPS):
create_grant(APPS,APPS_MRC,CCA_ACK_HEADER,ALL,FALSE,): do_apps_ddl(APPS,GRANT
ALL ON "CCA_ACK_HEADER" TO APPS_MRC): do_apps_ddl(APPS,GRANT ALL ON
"AMV_MATCHING_QUEUE_TBL" TO APPS_MRC): do_apps_ddl(APPS,GRANT ALL ON
"AK_LOADER_TEMP" TO APPS_MRC): Start Time: 2009-03-17;00:19:25 Failure Time:
2009-03-17;00:23:24 Elapsed: 00;00:03:59]
ORA-06512: at line 25
Fix : Drop the object pointing to remote object and re-create after MRC is over
ERROR at line 1:
ORA-20005: ORA-01403: no data found
ORA-01720: grant option does not exist for 'APPLSYS.FND_LOBS'
[create_mc_schema(APPLSYS, TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS,
APPS, APPS_MRC, none, TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,FCOA_ATTACHMENTS_V, FALSE,ALL,APPS):
create_grant(FCOA_ATTACHMENTS_V does not exist in ): do_apps_ddl(APPS,GRANT ALL
ON "FCOA_ATTACHMENTS_V" TO APPS_MRC): Start Time: 2009-03-05;08:56:58 Failure
Time: 2009-03-05;08:58:33 Elapsed: 00;00:01:35]
ORA-06512: at line 25
Fix :select owner,object_type from dba_objects where object_name='FCOA_ATTACHMENTS_V';
CONNECT APPLSYS/xxxx
grant ALL on APPLSYS.FND_LOBS TO XXFAXMGR with grant option;
grant ALL on APPLSYS.FND_ATTACHED_DOCUMENTS TO XXFAXMGR with grant option;
CONNECT APPS/xxxxxx
grant ALL on APPS.FND_ATTACHED_DOCS_FORM_VL TO XXFAXMGR with grant option;
CONNECT XXFAXMGR/xxxxx
grant ALL on XXFAXMGR.FCOA_ATTACHMENTS_V TO APPS with grant option;
ERROR at line 1:
ORA-20005: ORA-00980: synonym translation is no longer valid
[create_mc_schema(APPLSYS, TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS,
APPS, APPS_MRC, none, TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,AVL_LOOKUPS, FALSE,ALL,APPS):
create_grant(APPS,APPS_MRC,AVL_LOOKUPS,ALL,FALSE,): do_apps_ddl(APPS,GRANT ALL
ON "AVL_LOOKUPS" TO APPS_MRC): Start Time: 2009-03-10;03:27:40 Failure Time:
2009-03-10;03:27:43 Elapsed: 00;00:00:03]
ORA-06512: at line 25
conn /as sysdba
col object_name for a40
select owner,object_name, object_type from dba_objects where OBJECT_NAME ='AVL_LOOKUPS';
connect apps/xxxxx
grant all on AVL_LOOKUPS to APPS_MRC;
ERROR at line 1:
ORA-20005: ORA-20000: PACKAGE BODY APPS.CMF_CREATE_ITEMS_PKG: Line 28 longer
than 255 characters. [create_mc_schema(APPLSYS, TRUE, FALSE, none):
do_create_mc_schema(1, APPLSYS, APPS, APPS_MRC, none, TRUE):
invoker_mrc_grants(APPS, APPS_MRC): grant_a_package(APPS, CMF_CREATE_ITEMS_PKG,
PACKAGE, APPS_MRC, Y, D, FALSE):
ad_apps_private.copy_code(CMF_CREATE_ITEMS_PKG,PACKAGE BODY,APPS,APPS_MRC):
Start Time: 2009-03-09;03:50:50 Failure Time: 2009-03-09;03:55:23 Elapsed:
00;00:04:33]
ORA-06512: at line 25
Compile package
===============
ALTER PACKAGE APPS.CMF_CREATE_ITEMS_PKG COMPILE BODY;
ALTER PACKAGE APPS.CMF_CREATE_ITEMS_PKG COMPILE;
Action : Line length fix by Maynak and complied the package
Status : Restarted adadmin and Fixed
ERROR at line 1:
ORA-20005: ORA-04063: has errors
ORA-04063: view "CMS.CMS_R_SO_HEADERS_V" has errors [create_mc_schema(APPLSYS,
TRUE, FALSE, none): do_create_mc_schema(1, APPLSYS, APPS, APPS_MRC, none,
TRUE): create_synonyms_for_mc(APPS,APPS_MRC,APPS):
ad_apps_private.create_gs(APPS,APPS_MRC,CMS_R_SO_HEADERS_V, FALSE,ALL,APPS):
create_grant(APPS,APPS_MRC,CMS_R_SO_HEADERS_V,ALL,FALSE,):
do_apps_ddl(APPS,GRANT ALL ON "CMS_R_SO_HEADERS_V" TO APPS_MRC): Start Time:
2009-03-17;03:56:51 Failure Time: 2009-03-17;03:56:53 Elapsed: 00;00:00:02]
ORA-06512: at line 25
Fix:
.Take bacup of source of that view using dbms_metadata
Drop that view after consulting appl team.
Maintaining MRC after Patching and addition of objects to APPS/Custom schema impacting MRC
Increase of Patching Window time
Synonym Objects exists in APPS which is pointing to remote DB through DB link
Non Standard APPS Custom schema creation without Standard packages.
New custom Package creation with Line > 255.
Full grant of SYS, APPS , APPLSYS and other Standard APPS schema objects to Custom Apps Schema Owners
Existence of Code objects in base schemas
Reference
Metalink IDS
135756.1
135773.1
Pre Requisites to Enable MRC
1. 1486355 or 1512489 patches to be applied
2. Requirement 2000m in SYSTEM/TEMP and UNDO each.
3. Modify Validation Script to increase buffer size as below:
cd $AD_TOP/admin/sql/
Modify advrfapp.sql
From :
begin
dbms_output.enable(50000);
end;
To :
begin
dbms_output.enable(1000000);
end;
Upgradation of Forms and Reports Oracle Home(10g) in R12
Upgradation of Forms and Reports Oracle Home(10g) in R12
Solution:
Metalink Note :
437878.1 Upgrading Forms and Reports 10g in Oracle Applications Release 12:
Steps:
1) Stop all services and take backup of DB and all code tree's with inventory.
2) Let us Say Form and Report OH is /apps/test_inst/tech_stat/10.1.2
3) make sure that /apps/test_inst/tech_stat/10.1.2/oraInst.loc is pointing to the right inventory location (/var/opt/oracle/oraInst.loc)
4) Apply patch 4960210 through Runinstaller ..
5) export DISPLAY=local_host:0.0
6) cd Disk1 (If you unzip the patch, you will find it)
./runinstaller (or)
./runInstaller -invPtrLoc /apps/test_inst/tech_stat/10.1.2/oraInst.loc
7)check the installed products
click next
enter the full path of the products to be installed
/apps/test_inst/PATCHES/Disk1/stage/products.xml
select destination oracle home
apps_test_inst_apps_apps_tech_st_10_1_2
path
/apps/test_inst/apps/tech_st/10.1.2/
click next
select product to update Oracle Application Server Software Update
choose "Oracle Application Server and Developer Suite 10g R2 Software Update 10.1.2.2.0"
Supply the ias_admin default password 'secret' when it prompts.
8. run root.sh when it prompts.
9. post patch:
Update File Permissions
chmod ug+x $ORACLE_HOME/sso/bin/ssoreg.sh
10. Deploy new forms.ear file as per Note 397174.1
----------------------------------------------
cp $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml_org_10152008
vi $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
oc4jadmin
OC4J Administrator
OC4J Administrator
{903}7pt3cBV4AkL6tlFqYHmHdhHbrTpDcTS8
oc4jadmin
OC4J Administrator
OC4J Administrator
!welcome
$FND_TOP/bin/txkrun.pl -script=CfgOC4JApp
Enter Application name for re-deployment ? forms
Enter Oc4j Instance password for re-deployment ? welcome
Run Autoconfig ? No
NOTE: mention the password as welcome only.
restore back the xml files for previous password
cp $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml_org_10152008 $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
Run autoconfig on all the nodes..
11.Apply patch 5861907
a) Shutdown the iAS instance.
b) Backup the $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml file.
c) Copy the patch oraclehomeproperties.xml to $ORACLE_HOME/inventory/ContentsXML.
12) Apply the below additional patches in same order
5841985
6002686
5985861
6146823
5637184
5466491
5841985
=======
export PATH=$PATH:/apps/test_inst/apps/tech_st/10.1.2/OPatch
export ORACLE_HOME=/apps/test_inst/apps/tech_st/10.1.2
make sure that /apps/tst_inst/apps/tech_st/10.1.2/oraInst.loc is pointing to the right inventory location
(/apps/local/TEST_INST/inst/apps/TEST_INST_coe-dev-17/admin/oraInventory)
If no inventory exists under $INST_TOP/admin then copy the central inventory to this location.
make sure that JRE_LIB_DIR in /apps/test_inst/apps/tech_st/10.1.2/sysman/lib/env_sysman.mk is pointing to the correct location
opatch lsinventory -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
Make sure the output is correct. This should not error out.
cd /apps/test_inst/PATCHES/5841985
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
6002686
=======
cd /apps/test_inst/PATCHES/6002686
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
5985861
=======
cd /apps/test_inst/PATCHES/5985861
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
6146823
=======
pre req
echo $OPATCH_PLATFORM_ID
export OPATCH_PLATFORM_ID=46
chmod +X $ORACLE_HOME/bin/genshlib
unzip p6146823_101220_Linux.zip
cd 6146823
sh apply.sh | tee 6146823_apply.log
Note: This will apply all these patches (5456500,5527100,5650051,5753922,5893392 and 5985840)
unset OPATCH_PLATFORM_ID
5637184
=======
cd /apps/test_inst/PATCHES/5637184
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
5466491
=======
cd /apps/test_inst/PATCHES/5466491
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
13. Apply interoper patch 5411711
using adpatch
14.Regenerate Jar files if the time stamp is not current in $OA_JAVA/oracle/apps/fnd/jar directory
Using adadmin
select Generate Applications Files > Generate Product JAR Files
(Do not force the regeneration of all JAR files)
15. Start services and verify the upgrade.
a) Log on to Applications as any user, launch any form, select About Applications from the Help menu,
and confirm that the Forms version (under Forms Server) is 10.1.2.2.0.
b) Execute following command,to display various component versions.
This command requires DISPLAY environment variable to be set correctly.
$ORACLE_HOME/bin/frmcmp help=y
Solution:
Metalink Note :
437878.1 Upgrading Forms and Reports 10g in Oracle Applications Release 12:
Steps:
1) Stop all services and take backup of DB and all code tree's with inventory.
2) Let us Say Form and Report OH is /apps/test_inst/tech_stat/10.1.2
3) make sure that /apps/test_inst/tech_stat/10.1.2/oraInst.loc is pointing to the right inventory location (/var/opt/oracle/oraInst.loc)
4) Apply patch 4960210 through Runinstaller ..
5) export DISPLAY=local_host:0.0
6) cd Disk1 (If you unzip the patch, you will find it)
./runinstaller (or)
./runInstaller -invPtrLoc /apps/test_inst/tech_stat/10.1.2/oraInst.loc
7)check the installed products
click next
enter the full path of the products to be installed
/apps/test_inst/PATCHES/Disk1/stage/products.xml
select destination oracle home
apps_test_inst_apps_apps_tech_st_10_1_2
path
/apps/test_inst/apps/tech_st/10.1.2/
click next
select product to update Oracle Application Server Software Update
choose "Oracle Application Server and Developer Suite 10g R2 Software Update 10.1.2.2.0"
Supply the ias_admin default password 'secret' when it prompts.
8. run root.sh when it prompts.
9. post patch:
Update File Permissions
chmod ug+x $ORACLE_HOME/sso/bin/ssoreg.sh
10. Deploy new forms.ear file as per Note 397174.1
----------------------------------------------
cp $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml_org_10152008
vi $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
oc4jadmin
OC4J Administrator
OC4J Administrator
{903}7pt3cBV4AkL6tlFqYHmHdhHbrTpDcTS8
oc4jadmin
OC4J Administrator
OC4J Administrator
!welcome
$FND_TOP/bin/txkrun.pl -script=CfgOC4JApp
Enter Application name for re-deployment ? forms
Enter Oc4j Instance password for re-deployment ? welcome
Run Autoconfig ? No
NOTE: mention the password as welcome only.
restore back the xml files for previous password
cp $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml_org_10152008 $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
Run autoconfig on all the nodes..
11.Apply patch 5861907
a) Shutdown the iAS instance.
b) Backup the $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml file.
c) Copy the patch oraclehomeproperties.xml to $ORACLE_HOME/inventory/ContentsXML.
12) Apply the below additional patches in same order
5841985
6002686
5985861
6146823
5637184
5466491
5841985
=======
export PATH=$PATH:/apps/test_inst/apps/tech_st/10.1.2/OPatch
export ORACLE_HOME=/apps/test_inst/apps/tech_st/10.1.2
make sure that /apps/tst_inst/apps/tech_st/10.1.2/oraInst.loc is pointing to the right inventory location
(/apps/local/TEST_INST/inst/apps/TEST_INST_coe-dev-17/admin/oraInventory)
If no inventory exists under $INST_TOP/admin then copy the central inventory to this location.
make sure that JRE_LIB_DIR in /apps/test_inst/apps/tech_st/10.1.2/sysman/lib/env_sysman.mk is pointing to the correct location
opatch lsinventory -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
Make sure the output is correct. This should not error out.
cd /apps/test_inst/PATCHES/5841985
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
6002686
=======
cd /apps/test_inst/PATCHES/6002686
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
5985861
=======
cd /apps/test_inst/PATCHES/5985861
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
6146823
=======
pre req
echo $OPATCH_PLATFORM_ID
export OPATCH_PLATFORM_ID=46
chmod +X $ORACLE_HOME/bin/genshlib
unzip p6146823_101220_Linux.zip
cd 6146823
sh apply.sh | tee 6146823_apply.log
Note: This will apply all these patches (5456500,5527100,5650051,5753922,5893392 and 5985840)
unset OPATCH_PLATFORM_ID
5637184
=======
cd /apps/test_inst/PATCHES/5637184
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
5466491
=======
cd /apps/test_inst/PATCHES/5466491
opatch apply -invPtrLoc /apps/test_inst/apps/tech_st/10.1.2/oraInst.loc
13. Apply interoper patch 5411711
using adpatch
14.Regenerate Jar files if the time stamp is not current in $OA_JAVA/oracle/apps/fnd/jar directory
Using adadmin
select Generate Applications Files > Generate Product JAR Files
(Do not force the regeneration of all JAR files)
15. Start services and verify the upgrade.
a) Log on to Applications as any user, launch any form, select About Applications from the Help menu,
and confirm that the Forms version (under Forms Server) is 10.1.2.2.0.
b) Execute following command,to display various component versions.
This command requires DISPLAY environment variable to be set correctly.
$ORACLE_HOME/bin/frmcmp help=y
Check Concurrent Manager Status from the Back end?
How to check Concurrent Managers Status from the Back End?
select CONCURRENT_QUEUE_NAME,max_processes,running_processes,decode(control_code,
'A','Activating',
'B','Activated',
'D','Deactivating',
'E','Deactivated',
'N','Target node/queue unavailable',
'O','Suspending concurrent manager',
'P','Suspended',
'Q','Resuming concurrent manager',
'R','Restarting',
'T','Terminating',
'U','Updating environment information',
'V','Verifying',
'X','Terminated')
from apps.fnd_concurrent_queues
where
MAX_PROCESSES <> RUNNING_PROCESSES or
(control_code is not null and control_code not in ('B','E'));
select CONCURRENT_QUEUE_NAME,max_processes,running_processes,decode(control_code,
'A','Activating',
'B','Activated',
'D','Deactivating',
'E','Deactivated',
'N','Target node/queue unavailable',
'O','Suspending concurrent manager',
'P','Suspended',
'Q','Resuming concurrent manager',
'R','Restarting',
'T','Terminating',
'U','Updating environment information',
'V','Verifying',
'X','Terminated')
from apps.fnd_concurrent_queues
where
MAX_PROCESSES <> RUNNING_PROCESSES or
(control_code is not null and control_code not in ('B','E'));
Concurrent Program Phases and status List
Concurrent Program Phases and status List
Phase_Code :
'C', 'Completed',
'I', 'Inactive',
'P', 'Pending',
'R', 'Running',
Status_Code :
'A', 'Waiting',
'B', 'Resuming',
'C', 'Normal',
'D', 'Cancelled',
'E', 'Errored',
'F', 'Scheduled',
'G', 'Warning',
'H', 'On Hold',
'I', 'Normal',
'M', 'No Manager',
'Q', 'Standby',
'R', 'Normal',
'S', 'Suspended',
'T', 'Terminating',
'U', 'Disabled',
'W', 'Paused',
'X', 'Terminated',
'Z', 'Waiting',
Table: apps.fnd_concurrent_requests
Phase_Code :
'C', 'Completed',
'I', 'Inactive',
'P', 'Pending',
'R', 'Running',
Status_Code :
'A', 'Waiting',
'B', 'Resuming',
'C', 'Normal',
'D', 'Cancelled',
'E', 'Errored',
'F', 'Scheduled',
'G', 'Warning',
'H', 'On Hold',
'I', 'Normal',
'M', 'No Manager',
'Q', 'Standby',
'R', 'Normal',
'S', 'Suspended',
'T', 'Terminating',
'U', 'Disabled',
'W', 'Paused',
'X', 'Terminated',
'Z', 'Waiting',
Table: apps.fnd_concurrent_requests
JInitiator 1.1.8.7 Crash when launch it from IE
JInitiator 1.1.8.7 Crash when launch it from IE
Fixes
1. Try Uninstall existing JInitiator 1.1.8.7 and install the same
2. If the above dont work.. Try the following
Rename symcjit.dll into somethnig else ex: symcjit_old.dll
path is C:\Program Files\Oracle\JInitiator 1.1.8.16\bin
Fixes
1. Try Uninstall existing JInitiator 1.1.8.7 and install the same
2. If the above dont work.. Try the following
Rename symcjit.dll into somethnig else ex: symcjit_old.dll
path is C:\Program Files\Oracle\JInitiator 1.1.8.16\bin
Get Concurrent Request ID from SID
Get Concurrent Request ID from SID:
select c.request_id, status_code, phase_code, USER_CONCURRENT_PROGRAM_NAME,d.use
r_name requestor, s.sid,p.spid,s.process,s.osuser
,s.username,s.program,s.status,logon_time,last_call_et where sid in ( select sid from gv$access where object like '%XXCCP_OE_ORDER_HEADERS_ALL_QTC%');
from v$session s, v$process p, apps.fnd_concurrent_requests c,apps.fnd_concurren
t_programs_tl ct, apps.fnd_user d
where oracle_process_id=p.spid
and s.paddr=p.addr and
ct.concurrent_program_id=c.concurrent_program_id 11 00:14 show_rid.sql
and c.requested_by = d.user_id
and s.sid = '&enter_sid'
select c.request_id, status_code, phase_code, USER_CONCURRENT_PROGRAM_NAME,d.use
r_name requestor, s.sid,p.spid,s.process,s.osuser
,s.username,s.program,s.status,logon_time,last_call_et where sid in ( select sid from gv$access where object like '%XXCCP_OE_ORDER_HEADERS_ALL_QTC%');
from v$session s, v$process p, apps.fnd_concurrent_requests c,apps.fnd_concurren
t_programs_tl ct, apps.fnd_user d
where oracle_process_id=p.spid
and s.paddr=p.addr and
ct.concurrent_program_id=c.concurrent_program_id 11 00:14 show_rid.sql
and c.requested_by = d.user_id
and s.sid = '&enter_sid'
Important Apps Tables
Important Applications tables?
Users
fnd_user
ak_web_user_sec_attr_values (securing attributes)
fnd_user_resp_groups_direct ( direct responsibilities)
Define Responsibility
fnd_responsibility_vl
Menu Exclusions - fnd_resp_functions ( type, name, desc)
Request Groups
fnd_request_groups (header)
fnd_request_group_units (details)
Oracle Users
fnd_oracle_userid
Data Groups
fnd_data_groups (header)
fnd_data_group_units_v
Requests
fnd_conc_req_summary_v (main)
Request Set
fnd_request_sets_vl (main)
fnd_req_set_stages_form_v (stages)
fnd_request_set_programs (stage_requests)
fnd_descr_flex_col_usage_vl (request parameters)
fnd_req_set_stages_form_v (link stages)
Concurrent Managers
fnd_concurrent_queues_vl (main)
fnd_concurrent_queue_content (specialization rules)
fnd_concurrent_queue_size (work shifts)
work shifts
fnd_concurrent_time_periods
concurrent programs
fnd_concurrent_programs_vl (main)
fnd_descr_flex_col_usage_vl (parameters)
fnd_executables_form_v (executables)
fnd_conflict_domain ( concurrent conflicts domain)
profile
fnd_profile_options_vl
applications
fnd_application_vl
form functions
fnd_form_functions_vl (description)
menus
fnd_menus_vl (header)
fnd_menu_entries_vl (detail)
value sets
fnd_flex_value_sets, fnd_flex_values,
key flexfield segments
fnd_id_flexs
fnd_id_flex_segments_vl
fnd_segment_attribute_values (qualifiers)
Concurrent Managers
FND_CONCURRENT_PROCESSES
FND_CONCURRENT_PROGRAMS
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_QUEUES
FND_CONCURRENT_QUEUE_SIZE
Important FND
fnd_nodes
fnd_responsibility
fnd_databases
fnd_unsuccessful_logins
fnd_languages
fnd_application
fnd_profile_option_values
fnd_logins
fnd_user
fnd_appl_tops
fnd_dm_nodes
fnd_tns_aliases
Important AD
ad_install_processes
ad_sessions
ad_appl_tops
ad_applied_patches
ad_patch_drivers
ad_bugs
Users
fnd_user
ak_web_user_sec_attr_values (securing attributes)
fnd_user_resp_groups_direct ( direct responsibilities)
Define Responsibility
fnd_responsibility_vl
Menu Exclusions - fnd_resp_functions ( type, name, desc)
Request Groups
fnd_request_groups (header)
fnd_request_group_units (details)
Oracle Users
fnd_oracle_userid
Data Groups
fnd_data_groups (header)
fnd_data_group_units_v
Requests
fnd_conc_req_summary_v (main)
Request Set
fnd_request_sets_vl (main)
fnd_req_set_stages_form_v (stages)
fnd_request_set_programs (stage_requests)
fnd_descr_flex_col_usage_vl (request parameters)
fnd_req_set_stages_form_v (link stages)
Concurrent Managers
fnd_concurrent_queues_vl (main)
fnd_concurrent_queue_content (specialization rules)
fnd_concurrent_queue_size (work shifts)
work shifts
fnd_concurrent_time_periods
concurrent programs
fnd_concurrent_programs_vl (main)
fnd_descr_flex_col_usage_vl (parameters)
fnd_executables_form_v (executables)
fnd_conflict_domain ( concurrent conflicts domain)
profile
fnd_profile_options_vl
applications
fnd_application_vl
form functions
fnd_form_functions_vl (description)
menus
fnd_menus_vl (header)
fnd_menu_entries_vl (detail)
value sets
fnd_flex_value_sets, fnd_flex_values,
key flexfield segments
fnd_id_flexs
fnd_id_flex_segments_vl
fnd_segment_attribute_values (qualifiers)
Concurrent Managers
FND_CONCURRENT_PROCESSES
FND_CONCURRENT_PROGRAMS
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_QUEUES
FND_CONCURRENT_QUEUE_SIZE
Important FND
fnd_nodes
fnd_responsibility
fnd_databases
fnd_unsuccessful_logins
fnd_languages
fnd_application
fnd_profile_option_values
fnd_logins
fnd_user
fnd_appl_tops
fnd_dm_nodes
fnd_tns_aliases
Important AD
ad_install_processes
ad_sessions
ad_appl_tops
ad_applied_patches
ad_patch_drivers
ad_bugs
Enable FRD ( Forms Runtime Diagnostic ) Trace??
Solution:
1. Login into SYSADMIN --> System Administrator --> Profile --> System
Search the profile option for "ICX Forms Launcher" and Make sure Site and User leave has been checked.
2. Set the value following values at user level only according to the version
3. For R12, http://url:/OA_HTML/frmservlet?record=collect
4. For 11i, http://url:/dev60cgi/f60cgi?&record=collect&log=<>
5. Get the FRD trace from $FORMS_TRACE_DIR path at OS Level
1. Login into SYSADMIN --> System Administrator --> Profile --> System
Search the profile option for "ICX Forms Launcher" and Make sure Site and User leave has been checked.
2. Set the value following values at user level only according to the version
3. For R12, http://url:/OA_HTML/frmservlet?record=collect
4. For 11i, http://url:/dev60cgi/f60cgi?&record=collect&log=<>
5. Get the FRD trace from $FORMS_TRACE_DIR path at OS Level
Concurrent requests show Inactive No Manager? Then?
Solution:
1. Get the request id from the user,
2. Go to SYSADMIN --> System Administrator --> Others --> View Requests screen, search for the request. Click on Tools --> Manager log to see under which manager this program is being executed. Check the status of the manager in Concurrent --> Manager --> Administer and take necessary action.
3. If the Manager screen doesn't show any entry, this means the program is not attached to any manager. The application team needs to include this program under one of the managers.
1. Get the request id from the user,
2. Go to SYSADMIN --> System Administrator --> Others --> View Requests screen, search for the request. Click on Tools --> Manager log to see under which manager this program is being executed. Check the status of the manager in Concurrent --> Manager --> Administer and take necessary action.
3. If the Manager screen doesn't show any entry, this means the program is not attached to any manager. The application team needs to include this program under one of the managers.
How to register Jar File in Class Path?
Solution:
1. Make an entry in jserv.properties under Classpath section.
2. Add a new liine as "wrapper.classpath=".
3. Bounce the Apache.
1. Make an entry in jserv.properties under Classpath section.
2. Add a new liine as "wrapper.classpath=".
3. Bounce the Apache.
How do you check whether Trace is enabled to particular concurrent program from the back end?
Solution:
1. select CONCURRENT_PROGRAM_ID,USER_CONCURRENT_PROGRAM_NAME from apps.fnd_concurrent_programs_tl where USER_CONCURRENT_PROGRAM_NAME like '%Program Name%'; (You will get Id)
2. select concurrent_program_id,enable_trace from apps.fnd_concurrent_programs where concurrent_program_id ='concurrent program id';
1. select CONCURRENT_PROGRAM_ID,USER_CONCURRENT_PROGRAM_NAME from apps.fnd_concurrent_programs_tl where USER_CONCURRENT_PROGRAM_NAME like '%Program Name%'; (You will get Id)
2. select concurrent_program_id,enable_trace from apps.fnd_concurrent_programs where concurrent_program_id ='concurrent program id';
How do you know which concurrent manager is taking care of your request?
sqlplus apps/appspwd @$FND_TOP/sql/@afcmcreq.sql
(Give Request number when prompts)
No comments:
Post a Comment