Problem:
How do I move Oracle Alerts between R12 instances?
Solution:
Use the FNDLOAD command.
Problem:
How do I move Oracle Alerts between R12 instances?
Solution:
Use the FNDLOAD command.
Problem:
On Windows 2008, the R12.1 instance has become flaky, not allowing connections and responding slowly.
Solution:
Tweak the IRPStackSize registry parameter, or change the memory allocated to user processes using the BCDEDIT Windows command.
Problem:
When an Oracle Alert is run in R12.1.3 on a Windows 2008 platform, the alert completes with status 255 or status -1073741819.
Solution:
Apply patch 13728376.
Problem:
How do I relink executables in AD_TOP?
Solution:
Run adrelink.sh from command line to relink all AD executables by performing the following steps:
Open new MS DOS prompt.
Change directory to APPL_TOP.
Run relink[CONTEXT_NAME].cmd where CONTEXT_NAME is set to the customer specific context name. For example, ‘$ relinkVIS_host1.cmd’ where CONTEXT_NAME IS ‘VIS_host1’.
Run the APPS.SH script, as in $ . ./APPS.SH
Run adrelink.sh to relink executables. For example: $ sh adrelink.sh force=y “ad all”
Problem:
After installing R12.1.1 Vision instance on Windows 2008, all concurrent processes remain on phase ‘Inactive’ and status ‘No Manager’.
Checked concurrent manager log file, located in:
C:oracleVISinstappsVIS2_hostnamelogsapplconclog
At first, CM_VIS2_hostname.log was blank, but then eventually filled with log information. The following message was seen:
setClassPath: Unable to get PATH from environment or registry!: The operation completed successfully.
Solution:
The PATH environment variable exceeds 1024 characters.
Shorten the system path (e.g. remove duplicate entries), so that it does not exceed 1024 characters and ensure that the Windows directories are accessible.
Reference:
376946.1 – Some Managers Fail to Start With ‘setClassPath: Unable to get PATH from environment or registry’
199417.1 – Length of CLASSPATH Environment Variable May Cause Errors In Oracle Applications
761687.1 – Concurrent Manager Fails To Start After 11.5.10.2 and 9iAS Upgrade
Problem:
While cloning E-Business Suite R12 on Windows 2008 to a new machine, the following error appears:
C:oracleTEST2dbtech_st11.1.0appsutilclonebin>perl adcfgclone.pl dbTier Perl lib version (v5.6.1) doesn't match executable version (v5.8.3) at C:oracle UAT1appstech_st10.1.2perl5.6.1libMSWin32-x86/Config.pm line 21. Compilation failed in require at adcfgclone.pl line 28. BEGIN failed--compilation aborted at adcfgclone.pl line 28.
Solution:
Unset PERl5LIB environment variable.
Problem:
Checked alert log file and saw the following errors:
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_3395507964_562 by 128 in tablespace SYSAUX MMON Flush encountered SYSAUX out of space error(1688). MMON (emergency) purge of WR snapshots (546) and older ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_3395507964_562 by 128 in tablespace SYSAUX MMON Flush encountered SYSAUX out of space error(1688). MMON (emergency) purge - nothing to purge, pgsid=0.
Solution:
Add a new datafile to the SYSAUX tablespace.
Problem:
While backing up DEV1 instance on Windows 2008, the following error appears:
C:oracleDEV1instappsDEV1_ittl-hrmstestappltmpOFF446.tmp
Sharing violation
Solution:
Ensure that the Oracle processes are stopped in Windows Services.
It appears that there are still (orphan) database processes running. Right click the Taskbar and open Task Manager. Select the Processes tab. From the View menu, click Select columns. In Select Process Page Columns, scroll down the list and check Command Line. Delete any processes that start with C:oracleDEV1.
Problem:
On the page:
Applications System:DEV1 > Workflow > Service Components > Component Details: Workflow Notification Mailer: DEV1
after clicking the Help link, the following error appears:
404 NOT FOUND An error occurred while retrieving Oracle Applications Help information. Help target US/FND/@OAM_WF_GSC_MLR_DETAILS could not be found.
Solution:
Bug in EBS help files. Instead, manually navigate to help file:
Help Contents > Applied Technology > Oracle Workflow > Administrator’s Guide > Oracle Workflow Manager
Reference:
Help Files in OAM Error Help Target US/FND/@OAM_WF_GSC_MLR_DETAILS Could Not Be Found [ID 1074282.1]
Problem:
When running RDA from Application Diagnostics, the following error appears in the output report:
ERROR - RDA execution failed (9009) ACTION - Review the output of the RDA command (shown below) to determine the cause of this error
Solution:
In APPL_TOP, create APPSORA.cmd from APPSSID_hostname.cmd.
Recent Comments