Unknown OracleAS Home Type Error Executing Runstartupconsole.Sh in a Middle Tier Home

When using the command runstartupconsole.sh to start up an Application Server 10g (10.1.2.x.x) Middle Tier on unix/linux, the following error is reported to the screen:

'I have encountered an unknown OracleAS Home type Business' (For a BI and Forms Middle Tier)

or

'I have encountered an unknown OracleAS Home type Portals' (For a Portal and Wireless Middle Tier)

The same command works fine when executed in an AS Infrastructure Oracle Home.

The runstartupasconsole.sh script is just a wrapper for opmnctl/emctl. To workaround the script failure execute the following commands:

To start:
$ORACLE_HOME/opmn/bin/opmnctl startall
$ORACLE_HOME/bin/emctl start iasconsole

To stop:
$ORACLE_HOME/bin/emctl stop iasconsole
$ORACLE_HOME/opmn/bin/opmnctl stopall

Patch # 6678700 (KO NLS) fails with WITH LOADING FADTXD .XLF

While applying Korean NLS patch (6678700) on a 12.1 instance, the patch errors out with the following error in the log:

Target file: FADTXD.xlf[061609_085037223][][EXCEPTION] java.io.UTFDataFormatException: Invalid UTF8 encoding.at oracle.xml.parser.v2.XMLUTF8Reader.checkUTF8Byte(XMLUTF8Reader.java:160)at oracle.xml.parser.v2.XMLUTF8Reader.readUTF8Char(XMLUTF8Reader.java:203)at oracle.xml.parser.v2.XMLUTF8Reader.fillBuffer(XMLUTF8Reader.java:120)at oracle.xml.parser.v2.XMLByteReader.saveBuffer(XMLByteReader.java:450)at oracle.xml.parser.v2.XMLReader.fillBuffer(XMLReader.java:2488)at oracle.xml.parser.v2.XMLReader.tryRead(XMLReader.java:1089)at oracle.xml.parser.v2.XMLReader.scanXMLDecl(XMLReader.java:3047)at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:521)at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:288)at oracle.apps.xdo.oa.util.TemplateTranslator.createMLSTemplates(TemplateTranslator.java:238)at oracle.apps.xdo.oa.util.XLIFFLoader.processUpload(XLIFFLoader.java:738)at oracle.apps.xdo.oa.util.XLIFFLoader.process(XLIFFLoader.java:586)at oracle.apps.xdo.oa.util.XLIFFLoader.processXLIFF(XLIFFLoader.java:1153)at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)at java.lang.reflect.Method.invoke(Method.java:597)at oracle.apps.ad.worker.AdJavaWorker.invokeUtility(AdJavaWorker.java:503)at oracle.apps.ad.worker.AdJavaWorker.main(AdJavaWorker.java:356)

Oracle has an open bug 8357323 for this which is yet to be closed. To work around this issue, please execute the following steps:

run the below commands to load US XML and US RTF manually , after that re-start the patch application by using adadmin and marking the failed worker as success and continue.

Command to reload XML

adjava -ms128m -mx256m -nojit oracle.apps.xdo.oa.util.XDOLoader UPLOAD-DB_USERNAME -DB_PASSWORD -JDBC_CONNECTION"(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=machine.oracle.com)(PORT=1540)))(CONNECT_DATA=(SID=sidname)))"-LOB_TYPE DATA_TEMPLATE -APPS_SHORT_NAME OFA -LOB_CODE FADTXD -LANGUAGE 00-XDO_FILE_TYPE XML-DATA-TEMPLATE -FILE_NAME$FA_TOP/patch/115/publisher/defs/FADTXD.xml

Replace the above with username/pwd and &jdbc_db_addr

Command to reload RTF

adjava -ms128m -mx256m -nojit oracle.apps.xdo.oa.util.XDOLoader UPLOAD-DB_USERNAME -DB_PASSWORD -JDBC_CONNECTION"(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=machine.oracle.com)(PORT=1540)))(CONNECT_DATA=(SID=sidname)))"-LOB_TYPE TEMPLATE_SOURCE -APPS_SHORT_NAME OFA -LOB_CODE FADTXD -LANGUAGE en-TERRITORY US -XDO_FILE_TYPE RTF -TRANSLATE Y -FILE_NAME$FA_TOP/patch/115/publisher/templates/US/FADTXD.rtf

9.2.0.4.Installation Fails with "Do Not Have Sufficient Privileges to Write to the Specified Path"

Trying to install Oracle 9.2.0.4 On Linux Redhat 3 seeing error : -

Error: You do not have sufficient privileges to write to the specified path. in component DatabaseConfiguration Assistant

From the installActions log file:

Please specify a unique SID.
Setting value of s_OPSNodeInfoString to
Setting value of s_oidRegister to *Protected value, not to be logged*
Setting value of s_launchFile to /u01/app/oracle/product/9.2.0.4/bin/dbca
Setting value of s_instLaunchFile to /u01/app/oracle/product/9.2.0.4/assistants/dbca/dbca.sbs
Setting value of s_dbSid to orcl
Calling query generalQueries2.2.0.7.0 getenv

name = ORACLE_BASE
Query returned :
Setting value of s_mountPoint to /oradata

This is because ORACLE_BASE is not set, hence instead of trying to write to $ORACLE_BASE/oradata , the OracleUniversal Installer (OUI)is trying to write to/oradatafor which it does not have the privilege.

To implement the solution, please execute the following steps:
Clean up the failed installation
Set ORACLE_BASE to the appropriate PATH and install again

OC4J configuration assistant fails during application of patch 5983622

While upgrading 10gAS forms and reports in Release 12 using patch 5983622, the OC4J configuration assistant will fail during the runInstaller run. This is expected for EBS customers so you can click NEXT to finish the installation safely. The forms and reports will be upgraded properly now.

11I.PJ_PF.M Family Pack Installation Fails When Processing egot016.odf and egov028.odf

An error occurs when installing11i.PJ_PF.M (Projects Suite) via Patch 3485155 when processing the files egot016.odf and egov028.odf. Errors similar to the following can be seen in the adpatch worker logs:

ATTENTION: All workers either have failed or are waiting:
FAILED: file egot016.odf on worker 2. ...
adwork002.log: ...
Comparing objects in username EGO with ODF file
/u01/app/TEST/testappl/ego/11.5.0/patch/115/odf/egot016.odf
Reading objects from ODF file
AD Worker - adussfrt: INFO: Do not understand token
START_OF_AD_ODF_FILE in ODF file. Line is:
START_OF_BUILDING_BLOCK AD Worker - adussfrh:
ERROR: ODF file does not begin with standard header information
AD Worker - adusrtrf: ERROR: Unable to read header information from the ODF file
AD Worker - aiccep: ERROR: Unable to read ODF file
Time when worker failed: Mon Jul 04 2005 15:35:34
Evaluating symbolic arguments ....
Done evaluating symbolic arguments.
Time when worker started job:
Mon Jul 04 2005 15:35:34
Start time for file is: Mon Jul 04 2005 15:35:34
Comparing objects in username EGO with ODF file /u01/app/TEST/testappl/ego/11.5.0/patch/115/odf/egot016.odf
Reading objects from ODF file AD Worker - adussfrt:
INFO: Do not understand token START_OF_AD_ODF_FILE in ODF file.
Line is: START_OF_BUILDING_BLOCK
AD Worker - adussfrh:
ERROR: ODF file does not begin with standard header information
AD Worker - adusrtrf: ERROR: Unable to read header information from the ODF file
AD Worker - aiccep: ERROR: Unable to read ODF file


To work around the problem perform the following steps:

- Backup your current versions of egot016.odf and egov028.odf.
- Edit the file egot016.odf and make the following change. This change effectively provides the 115.1.50400.2 version of the file.

Replace:

# $Header: egot016.odf 115.1 2004/10/31 23:55:50 svdubey noship $
With:

START_OF_AD_ODF_FILE2.1.3Current system time is 04-FEB-2005 16:56:54# $Header: egot016.odf 115.1.50400.2 2005/02/04 17:09:18 kdenisen noship $

- Edit the file egov028.odf and make the following change. This change effectively provides the 115.2.50400.2 version of the file. -

Replace:

# $Header: egov028.odf 115.2 2004/10/31 23:46:41 svdubey noship $

With:

START_OF_AD_ODF_FILE2.1.3Current system time is 04-FEB-2005 16:56:58# $Header: egov028.odf 115.2.50400.2 2005/02/04 17:10:40 kdenisen noship $

Restart the failed worker and the patch completes successfully.

Pre-requisite checks fails and runInstaller quits

While installing an Oracle software or an oracle patchset runInstaller checks the OS version and may sometimes quit saying that the OS version failed the pre requisite check. to work around the problem, perform the following steps.

- change directory to "install" under the installation disk.- open the oraparam.ini file.
- Search for the following line(s) and comment it using a '#' symbol. some oraparam.ini files may have only some of the lines listed below. Comment them.

[Certified Versions] #You can customise error message shown for failure through CERTIFIED_VERSION_FAILURE_MESSAGE
#Solaris=5.8,5.9
#Windows=4.0,5.0,5.1,5.2
#Linux=redhat-3
#HPUX=B.11.11
#Decunix=V5.1A,V5.1
#AIX=5.1.0.0

- Restart runInstaller.

Now the runInstaller will not perform any OS version checks and proceeds to installation window.