DOYENSYS Knowledge Portal

We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal

Friday, February 20, 2015

Unable to determine SMTP server to use: set FND_SMTP_HOST

Outpost Processor has encountered the below error.

This error can be found in OPP logs:
[GC 14000K->8905K(20284K), 0.0074280 secs]
ProcessorException: Unable to determine SMTP server to use: set FND_SMTP_HOST
        at oracle.apps.fnd.cp.opp.EmailDeliveryProcessor.deliver(
        at oracle.apps.fnd.cp.opp.DeliveryProcessor.process(


1. Log into System Administrator responsibility.
2. Navigate to Profile - System.
3. Query up the %smtp% profiles.
4. Set the following profile values to the defined host and port:
FND:smtp Host (Hostname or IP)
FND:smtp Port (Default is 25)

Ref : R12: "PostProcessorException: Unable to determine SMTP server to use: set FND_SMTP_HOST" Error In OPP manager log file When Selecting Delivery Opts in FNDRSRUN to Send Email Notifications (Doc ID 1240768.1)

Wednesday, February 11, 2015

Copy Plan Erroredout with "No Free partitions available. Contact DBA to create partitions"


If you have no other free partitions, then simply run
Create APS Partitions program
with parameters
Plan partition = 1
Instance partition = 0
This will create a new plan partition that can be used to create a new plan.

You can verify using the following:

select * from msc_plans;
-- the purged plan should not exist in this table (plan name in column COMPILE_DESIGNATOR)

select * from msc_designators;
-- the purged plan should not exist in this table (plan name in column DESIGNATOR)

select * from msc_plan_partitions;
-- FREE_FLAG is showing 2 for partition with this plan name

NOTE: For FREE_FLAG = 1 with old PLAN_NAME still showing - this is fine
- the plan name is NOT replaced until you save a new plan AND have created plan options for that new plan name.

You can drop the old partition using
Drop Partition Request and enter the partition number and set parameter Plan = Yes
Note: This step should be done AFTER you verify that MSC_PLANS and MSC_DESIGNATORS DO NOT show the name of the purged plan

Ref ( Doc ID 1333292.1)

"Loader Worker With Direct Load Option" Erroredout with usdsop: exec failed during spawnsqlldr:

"Loader Worker With Direct Load Option"   Erroredout with the below
usdsop: exec failed during spawnsqlldr: Permission denied
Program exited with status 1
APP-FND-01630: Cannot open file /app04/oracle/TEST/inst/apps/TEST_<hostname>/appltmp/OFQY5qaa.t for reading

In $ORACLE_HOME/bin the file called sqlldr is either missing or has the wrong permissions with the APPLMGR (ie APPS) user which is how sqlldr is called from MSCPLD - Loader Worker With Direct Load Option when the concurrent request is run


1.To regenerate the sqlldr file if not exists, login as the APPLMGR (ie APPS) user

      a.  cd $ORACLE_HOME/rdbms/lib
      b.  Run the following command to regenerat sqlldr for APPLMGR:
             $make -f isqlldr
      c. Rerun the ASCP plan

2.To fix the permissions,run the following command as the APPLMGR user in directory $ORACLE_HOME/bin:
        $chmod 755 sqlldr
     a. Check the persmissions of this file with the following command:
       $ls -al sql* 
       -rwxr-xr-x 1 applmgr dba 702577 Nov 28 2008 sqlldr
     b. Then rerun the ASCP plan

Reference (Doc ID 1081447.1)

Wednesday, February 4, 2015

                            ORA-00344 unable to re-create


RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 06/09/2008 10:03:56
ORA-00344: unable to re-create online log 'E:\app\admin\redo01.log'

ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.


Control file could not able to find the redo01.log 


You can either recreate the directory structure as specified in the error.

alter database rename file 'FILE NAME WITH FULL PATH' TO 


           Getting error while running on Apps Tier 


ERROR: RC-50013: Fatal: Failed to instantiate driver /u01/appl/trn/apps/tech_st/10.1.2/appsutil/driver/regclone.drv

$ appsTier 

AutoConfig is exiting with status 1

RC-50013: Fatal: Instantiate driver did not complete successfully.


The executable unable to find the oracle_home files .


export ORACLE_HOME=/u01/app/oracle/oas_home/10.1.3
export PERL5LIB=$ORACLE_HOME/perl/lib/5.8.3:$ORACLE_HOME/perl/lib/site_perl/5.8.3:
export PERL5LIB=$PERL5LIB:$ORACLE_HOME/perl/lib/site_perl/5.8.3/i686-linux-thread-multi:$PERL5LIB
export PATH=$ORACLE_HOME/perl/bin:$PATH
Now again you can execute same above command.

Monday, February 2, 2015

ORA-20001: invalid column name or duplicate columns/column groups/expressions in method_opt***

This Error may occur while running Gather Schema Statistics after 11g Database Upgrade .

The Cause may be:

There are duplicate rows on FND_HISTOGRAM_COLS table for JE_BE_LINE_TYPE_MAP table.
Because of this problem, FND_STATS tries to gather histogram information using wrong command and
it fails with ora-20001 errors.

The following SQL should return one row, not two:

select column_name, nvl(hsize,254) hsize
where table_name = 'JE_BE_LINE_TYPE_MAP'
order by column_name;

------------------------------ ----------

Column does not exist on the table but still listed in FND_HISTOGRAMS_COL table.
You can use following SQL to identify. SQL will prompt for table name, use table name from the errors. In above examples you can use FII_FIN_ITEM_HIERARCHIES.

select hc.table_name, hc.column_name
from FND_HISTOGRAM_COLS hc , dba_tab_columns tc
where hc.table_name ='&TABLE_NAME'
and hc.table_name= tc.table_name (+)
and hc.column_name = tc.column_name (+)
and tc.column_name is null;


Find out all duplicates and/or obsolete rows in FND_HISTOGRAM_COLS and delete one of them logged in as the applsys user.
Remember to take backup of the FND_HISTOGRAM_COLS table before deleting any data.

-- identify duplicate rows

select table_name, column_name, count(*)
group by table_name, column_name
having count(*) > 1;

-- Use above results on the following SQL to delete duplicates

where table_name = '&TABLE_NAME'
and  column_name = '&COLUMN_NAME'
and rownum=1;

Now Run the Gather Schema Statistics, Your Error would've been fixed.