Stay at Home!! Be Safe!! Take Care!!

For Any queries, please mail us at support@funoracleapps.com

Download Oracle EBS Software|R12.2.0|Oracle E-Business Suite

Download Oracle EBS Software|R12.2.0|Oracle E-Business Suite

CentOS Installation on Virtual Box|CentOS 7|Oracle Virtual Box

APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM

 APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM


Error:


APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM, because the environment variable &BASEPATH is not set for the application to which the concurrent program executable &EXECUTABLE belongs.


Shut down the concurrent managers. Set the basepath environment variable for the application. Restart the concurrent managers. (VARIABLE=)

Routine AFPEOT cannot construct the name of an executable file for your concurrent request 122917706.


Check that the file name components are correct and valid on your system. Check that the environment for the person who started the concurrent manager


Cause:

Custom Top is registered and not set in the ENV while starting the concurrent services.


Query to Check whether the Env is set for the Particular Concurrent Request :


select variable_name,value from fnd_env_context e ,fnd_concurrent_processes p ,fnd_concurrent_requests r where p.concurrent_process_id =
e.concurrent_process_id and p.concurrent_process_id = r.controlling_manager and e.variable_name like '%CUSTOM_TOP%' and r.request_id = &request_id;

Solution :


Add the respective Top in env file

$APPL_TOP/admin/adovars.env

or 

Setup custom  environment file.

Restart concurrent managers.

Oracle Virtual Box Installation on Windows

 

ORA-20011: Approximate NDV failed: ORA-00600: internal error code, arguments:

 ORA-20011: Approximate NDV failed: ORA-00600: internal error code, arguments


Error :

After DB upgrade , as part of R12 dbtier post-installation procedure, required to run adstats.sql and getting the following error

declare
*
ERROR at line 1:
ORA-20011: Approximate NDV failed: ORA-00600: internal error code, arguments:
[1350], [1], [23], [], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.DBMS_STATS", line 25335
ORA-06512: at "SYS.DBMS_STATS", line 25877
ORA-06512: at line 3
ORA-06512: at line 33

Cause:

ORA_NLS10 variable not set.

Solution :

1. Make sure that $ORACLE_HOME/nls/data/old/cr9idata.pl executed to create $ORACLE_HOME/nls/data/9idata as per Database upgrading notes.

2. Make sure that the ORA_NLS10 environment variable is set to the full path of the nls/data/9idata directory:

echo $ORA_NLS10
export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

3- If the instance was not started with ORA_NLS10 set correctly restart it.

4- Retest the issue by running adstats.sql again as it should run successfully now.

How to setup UDEV instead of ASM libraries for ASM on Linux

How to setup UDEV instead of ASM libraries for ASM on Linux


In this post I am going to share how to use UDEV on Linux server for ASM disk in place for ASMlib.
It will help to directly allot the raw disk to your asm disk group.It can be used in Red Hat, Oracle, Centos Linux variants using UDEV.

Udev is the mechanism used to create and name /dev device nodes corresponding to the devices that are present in the system. Udev uses matching information provided by sysfs with rules provided by the user to dynamically add the required device nodes.

Steps to use udev for ASM

1. Attach a raw disk to the server.

2. Use lsblk or fdiks -l command to find the new added disk names.

example:

/dev/sdg
/dev/sde
/dev/sdf
/dev/sdc
/dev/sdd

3. Find the ID_Serial for each associated disk, if we directly use the disk name it might get chnaged after the server reboot.

udevadm info --query=property /dev/sdg
udevadm info --query=property /dev/sde
udevadm info --query=property /dev/sdf
udevadm info --query=property /dev/sdc
udevadm info --query=property /dev/sdd

4. Go to cd /etc/udev/rules.d directory and add the new disk details in file 99-oracle-asmdevices.rules as below. Make sure to update ID_SERIAL with your correct value and disk owner and group should be correct based on the env. Also I will give a virtual name/symbolink for eash disk as oraasm01/02/03 etc.


ACTION==""add|change"", SUBSYSTEM==""block"", ENV{ID_SERIAL}==""36000c297a90d6a9681b1d2a5a1b88568"", GROUP=""dba"", SYMLINK+=""oraasm01"" OWNER=""oraasm"", MODE=""0660""
ACTION==""add|change"", SUBSYSTEM==""block"", ENV{ID_SERIAL}==""36000c29906aa418e9822a0947ce9ad22"", GROUP=""dba"", SYMLINK+=""oraasm02"" OWNER=""oraasm"", MODE=""0660""
ACTION==""add|change"", SUBSYSTEM==""block"", ENV{ID_SERIAL}==""36000c291823fef46b990dbc1fe7bebdf"", GROUP=""dba"", SYMLINK+=""oraasm03"" OWNER=""oraasm"", MODE=""0660""
ACTION==""add|change"", SUBSYSTEM==""block"", ENV{ID_SERIAL}==""36000c2944397980b1b7f91a3d0c99e56"", GROUP=""dba"", SYMLINK+=""oraasm04"" OWNER=""oraasm"", MODE=""0660""
ACTION==""add|change"", SUBSYSTEM==""block"", ENV{ID_SERIAL}==""36000c2954d200a2927a1e815945e603d"", GROUP=""dba"", SYMLINK+=""oraasm05"" OWNER=""oraasm"", MODE=""0660"""


5. Reload the udev rules to identify the new disks.

udevadm control --reload-rules
udevadm trigger --type=devices --action=change


Note:
# #OL5
# /sbin/udevcontrol reload_rules

# #OL6 and OL7
# udevadm control --reload-rules

# #OL5 and OL6 : Not needed for OL7
# /sbin/start_udev

6. Verify the disk permissions and permissions

ls -l /dev/oraasm05
ls -l /dev/oraasm03
ls -l /dev/oraasm04
ls -l /dev/oraasm01
ls -l /dev/oraasm02

7. Make sure the ASM disk string should be set as  asm_diskstring='/dev/ora*' to identify the disks.

8. Attach the new disks to the diskgroup in asm now.



Example:

SQL> set pages 40000 lines 120
col PATH for a30
select DISK_NUMBER,MOUNT_STATUS,HEADER_STATUS,MODE_STATUS,STATE,PATH FROM V$ASM_DISK;
SQL> 
DISK_NUMBER MOUNT_S HEADER_STATU MODE_ST STATE    PATH
----------- ------- ------------ ------- -------- ------------------------------
          4 CACHED  MEMBER       ONLINE  NORMAL   /dev/oraasm05
          2 CACHED  MEMBER       ONLINE  NORMAL   /dev/oraasm03
          3 CACHED  MEMBER       ONLINE  NORMAL   /dev/oraasm04
          0 CACHED  MEMBER       ONLINE  NORMAL   /dev/oraasm01
          1 CACHED  MEMBER       ONLINE  NORMAL   /dev/oraasm02

How to change the Timezone for any specific OEM Agent

How to change the Timezone for any specific OEM Agent





In this post I am going to share how to change the timezone of an OEM Agent.


Steps:


1) Check Current Timezone of the agent from the OEM repository database


select target_name, timezone_region

from sysman.mgmt_targets

where target_name='funoracleapps.lab'

order by 1,2;


2) Stop the Agent having wrong timezone


emctl stop agent


3) Reset Timezone for agent

emctl resetTZ agent


It will give command to run on OEM repository like below


Oracle Enterprise Manager Cloud Control 12c Release 5

Copyright (c) 1996, 2015 Oracle Corporation.  All rights reserved.

Updating /oem/oracle/agent12c/agent_inst/sysman/config/emd.properties...

Successfully updated /oem/oracle/agent12c/agent_inst/sysman/config/emd.properties.

Login as the em repository user and run the  script:

exec mgmt_target.set_agent_tzrgn('funoracleapps.lab:3872','Asia/Singapore')

and commit the changes

This can be done for example by logging into sqlplus and doing

SQL> exec mgmt_target.set_agent_tzrgn('funoracleapps.lab:3872','Asia/Singapore')

SQL> commit



4) Execute command on the OEM respository database


SQL> exec mgmt_target.set_agent_tzrgn('funoracleapps.lab:3872','Asia/Singapore')

SQL> commit


Commit complete.


5) Check the OEM Repository again


select target_name, timezone_region

from sysman.mgmt_targets

where target_name='funoracleapps.lab'

order by 1,2;


6) Start agent again


emctl start agent