Hostname Restriction/Limitations For Database Server

All host names should conform to the RFC 952 standard, which permits alphanumeric characters. Host names using underscores ("_") are not allowed. The Internet standards (Request for Comments) for protocols mandate that component hostname labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen (-). The original specification of hostnames in RFC 952, mandated that labels could not start with a digit or with a hyphen, and must not end with a hyphen. This what Oracle recommends for host name for RAC, and it apply also on non-RAC instances. REFERENCES

Error! FRM-92095: Oracle JInitiator version too low. Please install version 1.1.8.2 or higher

Brought a couple new PCs up recently and ran into the subject nasty error when attempting to access EBS. We’ve run into this before and we usually get it worked out one way or another. This time proved to be a bit challenging for some reason… Thought I would post the solution that we used and seems to work consistently. I’ve found other posts out there as well that reference some combination of these steps. For now, this will be my reference moving forward. Uninstall all existing Java installations on machine Uninstall all existing J2SE Runtime Environment installations on machine Restart the machine Install JRE 6u45 Open the Control Panel Search for Java; clicking the link will open the Java Control Panel Select the “Java” tab Click “View…” Double click the field under “Runtime Parameters” Enter this line: -Djava.vendor=”Sun Microsystems Inc.” Click OK Click OK Open IE and go to Oracle EBS and invoke a form to come up It will ask to install J2SE Runtime Environment 5.0 Update 13 Install J2SE Runtime Environment 5.0 Update 13 Restart the machine Open IE and you should now be able to open Oracle EBS This has been tested on x64 flavors of Win7 and Win8 using the x64 installer for JRE. Note: Disable the automatic updater within the Java Control Panel after all the steps listed above

Concurrent Processing - All Concurrent Requests Fail With ORA-03113 and Database Error ORA-07445 (Doc ID 945107.1)

The concurrent managers are up and running, but all concurrent requests are failing with ORA-03113 and ORA-03114. The request log file contains the following error: ORACLE error 3114 in post_cp_metrics_event Cause: post_cp_metrics_event failed due to ORA-03114:not connected to ORACLE. The SQL statement being executed at the time of the error was: &SQLSTMTand was executed from the file &ERRFILE. ORACLE error 3114 in AFPRSR-Resubmit_Time Cause:AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE . The SQL statement being executed at the time of the error was: and was executed from the file. ORA-03114: not connected to ORACLE Routine AFPPRD has encountered a fatal error. ORA-03114: not connected to ORACLE Contact your system administrator or support representative. ORACLE error 3114 in AFPRSR-Resubmit_Time Cause: AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE The following error is reported in the database alert log. ORA-07445: exception encountered: core dump [lfilic()+312] [SIGSEGV] [Address not mapped to object] [0x000000040] [] [] Thu Sep 24 07:59:56 2009 No errors are shown in the Internal Concurrent Manager log file. Cause Changes to symbolic links/paths or other environmental settings can cause ORA-07445 which in turn causes ORA-03114 . The cause of the issue is due to FND binaries/executables. Solution To implement the solution, please execute the below action plan: 1) Stop all the application services. $ cd $ADMIN_SCRIPTS_HOME $ adstpall.sh apps/apps 2) Relink the FND product binaries using adadmin. 3) Start all the application services. $ cd $ADMIN_SCRIPTS_HOME $ adstrall.sh apps/apps 4) Monitor the database alert log for any ORA-07445 errors. 5) Submit a Concurrent Request and check for its successful completion.

getaddrinfo(localhost, NULL, 1) failed (Temporary failure in name resolution): Connection refused

Issue: :: adopmnctl.sh: Starting Oracle Process Manager (OPMN) getaddrinfo(localhost, NULL, 1) failed (Temporary failure in name resolution): Connection refused getaddrinfo(localhost, NULL, 1) failed (Temporary failure in name resolution): Connection refused getaddrinfo(localhost, NULL, 1) failed (Temporary failure in name resolution): Connection refused opmnctl: opmn start failed. : adopmnctl.sh: exiting with status 2 Solution: There is no proper entry in /etc/hosts for local host Entry should be : 127.0.0.1 localhost.localdomain local host try to start again