Sunday, November 2, 2014

Tools->Copy File function failed with FNDFS_ Error in R12


Problem

When using Tools->Copy File function then it fails with following Error

'An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_. There may be a network configuration problem, or the TNS listener on node FNDFS_ may not be running. Please contact your system administrator.'





Solution

Make sure following profile options are set accordingly

1. "RRA: Enabled" (/FS_ENABLED) should be set to  "Yes"
2. "RRA: Service Prefix" (/FS_SVC_PREFIX)  should be  null-ed out (blank) , no spaces allowed




After making the changes, Log-out and Login back and retest the issue.


Reference

R12: Tools -> Copy Function fails with FNDFS Error after a fresh installation (Doc ID 419142.1)

Saturday, November 1, 2014

DBMS_SCHEDULER Package in Oracle Database


  Dbms_scheduler is a more sophisticated job scheduler introduced from Oracle 10g and this package provides a collection of scheduling functions and procedures that are callable from any PL/SQL program.  Here are some examples.

Creating Job 

BEGIN
Dbms_Scheduler.create_job(
job_name => 'XX_DAILY_HEALTH_MONITOR_JOB',         --Job Name
job_type => 'STORED_PROCEDURE',                              --Type
job_action => 'SYS.XX_DAILY_HEALTH_MONITOR',         --Object Name
start_date => SYSTIMESTAMP,                                      --Job Start Date
repeat_interval => 'freq=daily; byhour=8',                    --Frequency
enabled => TRUE,                                                        --Status
comments => 'Daily DB Health Satus');                          --Comment
END;
/


Creating a Job That Calls an Executable

begin
dbms_scheduler.create_job (
   job_name           =>  'XX_DAILY_HEALTH_MONITOR_JOB',
   job_type           =>  'executable',
   job_action         =>  '/home/oracle/bin/health.sh',
   start_date         =>  '01-sep-2014 06:00:00 am',
   repeat_interval    =>  'freq=daily',
   enabled            =>  true);
end;
/


Run Job Manually

begin
dbms_scheduler.run_job (job_name => 'XX_DAILY_HEALTH_MONITOR_JOB');
end;
/


Modified Attribute

You can change anything about a scheduled job, except its name, using set_attribute Procedure

begin
dbms_scheduler.set_attribute (
name               =>  'XX_DAILY_HEALTH_MONITOR_JOB',
attribute          =>  'repeat_interval',
value              =>  'freq=daily; byhour=3');
end;
/


Stop Running Job

begin
dbms_scheduler.stop_job (job_name => 'XX_DAILY_HEALTH_MONITOR_JOB');
end;
/


Disable Job

begin
dbms_scheduler.disable (job_name => 'XX_DAILY_HEALTH_MONITOR_JOB');
end;
/


Enable Job

begin
dbms_scheduler.enable (job_name => 'XX_DAILY_HEALTH_MONITOR_JOB');
end;
/


Stop Job Permanantly

begin
dbms_scheduler.drop_job ('XX_DAILY_HEALTH_MONITOR_JOB');
end;
/




Detail of some expression defined by repeat_interval attribute

repeat_interval
Description
freq=hourly
Run every hour
freq=daily; byhour=3
Run at 3 am every day
freq=daily; byhour=8,20
Run at 8 am and 8 pm every day
freq=monthly; bymonthday=1
Run on the first day of every month
freq=monthly; bymonthday=-1
Run on the last day of every month
freq=yearly; bymonth=sep; bymonthday=20;
Run yearly on September 20th



Some useful scheduler views

DBA_SCHEDULER_JOBS
DBA_SCHEDULER_PROGRAMS
DBA_SCHEDULER_RUNNING_JOBS

Monday, October 27, 2014

'Function not available to this responsibility...' Error when navigate to Help->Diagnostic->Examine


Problem

When navigate to Help->Diagnostic->Examine then below error occur







Solution

Enable Diagnostic for Application User

Set 'Yes' for User level of profile option  'Utilities:Diagnostics' and logout from application and login again with respective user. Now you enable diagnostic and you can able to view now.











Sunday, October 26, 2014

ORA-06508 PL/SQL Could Not Find Program When Open Sales Order Form


Problem

The issue can be reproduced following

1. Login to R12 Application with respective user

2. Responsibility- Order Management Super User

3. Navigate to  Orders->Returns ->Order Organizer

4. Open Sales Order form and see error:
ORA-06508: PL/SQL: could not find program unit being called In Package ONT_HEADER_Def_Hdlr Procedure Default_Record: REQUEST_DATE 1

Solution

Shared pool memory is too low or high causing a resource utilization

Please update following parameter with given minimum value
sqlplus / as sysdba 
sql> alter system set shared_pool_size=600M scope=spfile; 
sql> alter system reset shared_pool_reserved_size scope=spfile; 
sql> alter system set db_cache_size=400M scope=spfile; 
sql> shutdown immediate 
sql> startup

Reference : Open Sales Order Screen Generates Error ORA-06508 PL/SQL Could Not Find Program Unit Being Called (Doc ID 841870.1)

Wednesday, October 15, 2014

ORA-00845: MEMORY_TARGET not supported on this system

Problem
SQL> show parameter memory

NAME                                 TYPE        VALUE
------------------------------------ ----------- --------
hi_shared_memory_address             integer     0
memory_max_target                    big integer 3152M
memory_target                        big integer 3152M
shared_memory_address                integer     0
SQL> alter system set memory_max_target=8G scope=spfile;

System altered.
SQL> alter system set memory_target=8G scope=spfile;

System altered.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORA-00845: MEMORY_TARGET not supported on this system

Solution
[root@prod ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             754G   42G  674G   6% /
tmpfs                 3.9G   88K  3.9G   1% /dev/shm
/dev/shm mount point size must be greater than or equal to value of MEMORY_TARGET parameter

So Increase the size of /dev/shm mount point
[root@prod ~]# umount -l /dev/shm/
[root@prod ~]# mount -t tmpfs shmfs -o size=8g /dev/shm
[root@prod ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             754G   42G  674G   6% /
shmfs                 8.0G     0  8.0G   0% /dev/shm
SQL> startup
ORACLE instance started.

Total System Global Area 8551575552 bytes
Fixed Size                  2215064 bytes
Variable Size            4093641576 bytes
Database Buffers         4429185024 bytes
Redo Buffers               26533888 bytes
Database mounted.
Database opened.
SQL> show parameter memory

NAME                                 TYPE        VALUE
------------------------------------ ----------- ---------
hi_shared_memory_address             integer     0
memory_max_target                    big integer 8G
memory_target                        big integer 8G

shared_memory_address                integer     0                

Tuesday, October 14, 2014

'An unexpected error has been detected by HotSpot Virtual Machine:' While launching Oracle Universal Installer


Problem
[oracle@prod database]$ ./runInstaller 
dirname: invalid option -- 'b'
Try `dirname --help' for more information.
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 712409 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 24575 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 16777216    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-10-13_03-28-11PM. Please wait ...[oracle@prod database]$ #
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x0000003315e14d70, pid=3286, tid=139755847370512
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_17-b03 mixed mode)
# Problematic frame:
# C  [ld-linux-x86-64.so.2+0x14d70]
#
# An error report file with more information is saved as hs_err_pid3286.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp             integer     0                

Solution

Set 'LD_BIND_NOW' environment variable to value '1' and launch again.
[oracle@prod database]$ export LD_BIND_NOW=1
[oracle@prod database]$ ./runInstaller 
dirname: invalid option -- 'b'
Try `dirname --help' for more information.
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 712019 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 24575 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 16777216    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2014-10-13_03
-33-18PM. Please wait ...[oracle@prod database]$ You can find the log of this install session at:

 /u01/app/oraInventory/logs/installActions2014-10-13_03-33-18PM.log

Sunday, October 12, 2014

Upgrade EBS 12.1.1 to 12.1.3


To apply Oracle E-Business Suite Release 12.1.3, follow these steps

Apply below patches
  1. Patch 9239089
  2. Patch 9239090 
  3. Patch 9239095 
  4. Patch 9817770 
  5. Patch 9966055 

Post Update Steps

Update all database tier nodes with the code level, provided by Oracle E-Business Suite Release 12.1.3 (Create Appsutil Directory using admkappsutil.pl)


Reference

Oracle E-Business Suite Release 12.1.3 Readme (Doc ID 1080973.1)