Hazrat Ali To His Son
May 18th, 2018, posted in Islamic Teachings, MESSAGEs, Saying Of Hazrat Ali ( A.S )
Oracle EBS Find Where Debug Is On
May 15th, 2018, posted in Oracle QueriesOracle EBS Find Where Debug Is On
If you have Debug is on at Site level then it will Impact the performance of the Instance, here is the script which will help you to quickly check your EBS Instance if ‘Debug’ is on (all level) of the EBS.
set linesize 160 col USER_PROFILE_OPTION_NAME for a30 col CONTEXT for a30 col VALUE for a30 col NAME for a30 SELECT po.profile_option_name "NAME", po.USER_PROFILE_OPTION_NAME, decode(to_char(pov.level_id), '10001', 'SITE', '10002', 'APP', '10003', 'RESP', '10005', 'SERVER', '10006', 'ORG', '10004', 'USER', '???') "LEV", decode(to_char(pov.level_id), '10001', '', '10002', app.application_short_name, '10003', rsp.responsibility_key, '10005', svr.node_name, '10006', org.name, '10004', usr.user_name, '???') "CONTEXT", pov.profile_option_value "VALUE" FROM FND_PROFILE_OPTIONS_VL po, FND_PROFILE_OPTION_VALUES pov, fnd_user usr, fnd_application app, fnd_responsibility rsp, fnd_nodes svr, hr_operating_units org WHERE po.user_profile_option_name like '%Debug%' AND pov.profile_option_value='Y' AND pov.application_id = po.application_id AND pov.profile_option_id = po.profile_option_id AND usr.user_id (+) = pov.level_value AND rsp.application_id (+) = pov.level_value_application_id AND rsp.responsibility_id (+) = pov.level_value AND app.application_id (+) = pov.level_value AND svr.node_id (+) = pov.level_value AND org.organization_id (+) = pov.level_value;
Sample ouptut:
NAME USER_PROFILE_OPTION_NAME LEV CONTEXT VALUE
--------------------------- ---------------------------- ------ --------------------------- ---------------
AFLOG_ENABLED FND: Debug Log Enabled USER SA-USER1 Y
FND_CONC_ALLOW_DEBUG Concurrent: Allow Debugging RESP XXXX_CE_SUP_MY-MYR-GE Y
PRINT_DEBUG FA: Print Debug USER SA-USER2 Y
PO_SET_DEBUG_WORKFLOW_ON PO: Set Debug Workflow ON USER SA-USER3 Y
PA_DEBUG_MODE PA: Debug Mode USER SA-USER4 Y
SO_DEBUG OE: Debug SITE Y
MSC_JAVA_DEBUG MSC: Enable Java Debug SITE Y
7 rows selected.
ORA-01450: maximum key length (6398) exceeded
May 13th, 2018, posted in Oracle Queries
Cause
the errors seen above are encountered because the NLS_LENGTH_SEMANTICS initialisation parameter has been set to CHAR. This is not a supported setting for this parameter in an Oracle Fusion Middle ware installation. This is documented in the Release Notes for each platform.
Solution
To remove the ORA-01450 errors when creating the MDS and SOAINFRA components ensure that the requirement for NLS_LENGTH_SEMANTICS=BYTE is met.
To check the current setting of NLS_LENGTH_SEMANTICS, login to the target database as SYSDBA and issue the following command:
SQL> show parameter NLS_LENGTH_SEMANTICS
NAME TYPE VALUE
———————— ———– ——-
nls_length_semantics string CHAR
SQL> alter system set nls_length_semantics=BYTE;
System altered.
SQL> show parameter NLS_LENGTH_SEMANTICS
NAME TYPE VALUE
———————— ———– ——-
nls_length_semantics string BYTE
After resetting the parameter you should restart your database for the change to take effect.
