FRM-92020: Failed to connect to the Server: /forms/Iservlet-1

Hi All,

The "FRM-92020: Failed to connect to the Server: /forms/Iservlet-1" very common error message when trying to connect to application from "Internet Explorer 8" we can avoid this error through below mentioned solution.

1. The permanent solution is to be apply patches.

2. If we are not able to get the patches or unable to apply then use the following short workaround.

Workaround:
Open Internet Explorer
---------------->> go to "Tools" menu
------------------------------->> go to "Internet Options"
--------------------------------------->> choose "Security" tab
------------------------------------------->>click on "Custom Level"
------------------------------------------------>>disable "xss filter"
--------------------------------------------------->> click on "ok".

through the above workaround you can able to open "form" without any error message.

Thanks

Changing SYSADMIN default password

Hi All,

This article is about "Reset of SYSADMIN password".

Steps:
1. Keep all the services running.
Do not shutdown appsTier Or dbTier application

2. Login to OS level via applmgr manager user
Login to application server via Operating System User.

3. Run environment scripts
a. cd $APPL_TOP
run APPLORA.env
$ . ./APPLORA.env

b. cd admin (folder)
run adovars.env
$. ./adovars.env

c. cd $FND_TOP/bin (folder)
run FNDCPASS to change the SYSADMIN password
(IMPORTANT: Change ONLY the SYSADMIN password)

eg:
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN {new password}

4. Restart the Apache,Forms,Reports, Listener & Concurrent Manager services
In short: Restart the dbTier Or appsTier services.

5. To test, login into the application as the SYSADMIN user and the new password.

6. Verify that a concurrent program such as Active Users runs.
eg: Login to application user and run the any concurrent reports.

Thanks

Changing APPS Schema Password

Hi All,

Yesterday i changed my Production box APPS (Default Password).

I want to share the step which i used for changing APPS Schema password.

1. Shutdown Application Servcies
$INST_TOP/admin/scripts/adstpall.sh

2. using FNDCPASS utility change the APPS schema password
login to APPLMGR user.
eg:
FNDCPASS [logon] 0 Y [system/password] SYSTEM [username] [new_password]

$FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS NEWPASS

NOTE: here i am changing the APPS Schema Default Password (Default password of apps schema is "apps" & default password of SYSTEM (ORACLE USER) is "manager")

Whenever we change the APPS schema password then APPLSYS password will also change by system. APPS or APPLSYS are same user.

3. run "adautocfg.sh" on dbTier as well as appsTier with NEW PASSWORD
3.1 logon on dbTier
$ORACLE_HOME/appsutil/admin/[SID_HOSTNAME]/adautocfg.sh apps/newpass

3.2 logon on appsTier
$INST_TOP/admin/scripts/adautocfg.sh apps/newpass

4. start APPLICATION services and login to application with new password.

5. In case of any doubt or query feel free to ask or mail @ star_taj @ yahoo. com

Unable to Find 'kshell' in Path When Running adcfgclone.pl

Dear all,

If you face the below error then please follow the below procedure.

Error:
while runing adcfgclone.pl script on linux x86 for r12

Unable to find the PD KSH version
Unable to find in user PATH

Solution:
before running/execute adcfgclone.pl script export the following command

$ export KSH_VERSION='@(#)PD KSH v5.2.14 99/07/13.2'

check metalink note: 451994.1 for more details.

Thanks

Cleaning An Apps Instance Of Redundant Files (EBS)

Reference: ML 274666.1

The following are the locations and files that can be considered for deletion:
1. In the $HOME/patch(es) directory, you can delete any zipped files that have been unzipped or any patches that have been applied.

2. In the bin directory of any $PRODUCT_TOP, you may see executable files that have been replaced by patches or a relink of theprogram. You can delete any of the executables that have a .number. a .bak, or a .sav after them.
For example in $FND_TOP/bin, you may

see:
FNDLIBR
FNDLIBR.bak
FNDLIBR.sav
FNDLIBR.1253
FNDLIBR.41248
FNDLIBR.7978

In this case you can delete the following:
FNDLIBR.bak
FNDLIBR.sav
FNDLIBR.1253
FNDLIBR.41248
FNDLIBR.7978

If you do delete the current program file by mistake, you can regenerate it by using adrelink or adadmin.

3. If you have been applying patches, in the $APPL_TOP/admin/<>/log directory, you will find files that end in .req, html, or .lst. If you are not applying patches or running adadmin, you can delete all of these files. Additionally in that same directory, you will find all of the log files for the patches that have been applied. You can delete those that were from patches that have been applied successfully. You can also truncate any adwork< # >.log or adadmin.log files you find.

These files can get very large and it is not necessary to keep the data in them for very long.

4. In the $APPL_TOP/admin/<>/out directory, you may see many files. They may end in .out, .mk, .log, .lst. If the files are older than 2 weeks old, it wil be safe to delete them. There may also be files in this directory that end in a .number. These can be deleted at the end of two weeks as well.

5. In the $COMMON_TOP/admin/log, $COMMON_TOP/admin/out and the $COMMON_TOP/temp directories there may be files that you can delete. $COMMON_TOP = (/region/oracle/<>/<>comn) You may also find files in any $PROD_TOP/log or $PROD_TOP/out directory.In the $COMMON_TOP/admin/log directory you can delete the files like Apache<>.txt, these files just contains informational messages.

6.In the 8i $ORACLE_HOME/dbs directory check the init<>.ora, this will list the location of three directories: udump, cdump, and bdump. In the udump directory, you will find any database traces that have been generated. If you do not need these trace files, you can delete them. In the cdump directory, you will find any core dumps that have occurred in the database. You candelete these if you do not need them. In the bdump, you may find trace files generated by the database startup and shutdown. You will also find the alert_<>.log. You can delete the trace files and truncate the alert_<>.log if necessary.

7.In your application $ORACLE_HOME directory, (usually), /region/oracle/<>/<>ora/8.0.6), there may be old files from anyOracle Developer upgrades. If you look in the $ORACLE_HOME/lib directory, you may find files that look like this:
libocl60.a
libocl60.a.PRE_P3
libocl60.a.PRE_P5
libocl60.a.PRE_P7

NOTE:
-------
The files that end in .PRE_P* can be deleted. However you have to be very careful to only delete those files that end in .PRE_P*. If youdelete any files without this suffix, you will corrupt your instance and may require a restore to make it work.There are many other locations in the 8.0.6 $ORACLE_HOME that have these .PRE_P*files. If you run this command: find . ?name.PRE_P* , you will fin all of these types of files. You can then delete them all.

8. Depending on when an instance core dumps, you may find core files in places other than the cdump directory. After the reason for the core dump has been addressed, you may delete these as well. If you go to your $ORACLE_BASE directory , (usually /<>/oracle/<>), and use the command find .?name core*, you will find any core files in the instance.

9.In the application, you should run "Purge Concurrent Request and/or Manager Data" concurrent program as sysadmin to cleanup oldconcurrent request and concurrent manager logfiles, output files and associated concurrent request/manager database records.

10.In pre-11i versions, files that are replaced by patches are copied as a backup before they are replaced. The old files (eg.pre-patch files) are named <>.<>O with an uppercase letter "O" at the end of the filename;(eg.POXCOC3B.plsO is the pre-patch version of POXCOC3B.pls). Some timeafter patches have been applied and the instance is stable, these oldversions of the Apps files can be removed.

11. In $AU_TOP/java and $JAVA_TOP, you may find files with the name apps.bak. If these are over 2 weeks old, it will be safe to remove them as well.By maintaining your instance using the above suggestions, your instance will run faster and it will not shutdown due to a lack ofspace.

12)If logs are not required then remove the files from $ORACLE_HOME/network/log

Low Level Logging Enabled

Dear All,
When you received the following Warning message on login page of Oracle Application...



Reason: "FND: Debug Log Enabled" Profile Set to "YES".
Solution: "FND: Debug Log Enabled" Profile Set "NO"

Navigator:
Login ---> system administrator responsibility ---> System Profile Values ---> "FND: Debug Log Enabled" Profile.

How to Retrieve row from TABLE or SYNONYM for an ORG_ID in r12

I hope everyone face this issue when try to retrieve rows from TABLE or SYNONYM for an Org_id.

for example:
select * from AR_CASH_RECEITPS_V;

Result: NO ROWS SELECTED

Actually Security reason we can't retrieve rows from ORG ID tables/synonym. we need to set "ORG ID" first.

For the R12
SQL*Plus
exec mo_global.set_policy_context('S', &org_id);

Toad and SQL Developer
Begin
mo_global.set_policy_context('S', &org_id);
End;

Refer Metalink Note for more details: 416710.1