Upgrading discoverer 4i to 10g for 11i

Upgrading oracle discoverer 4i to Oracle Application server middle-tier 10g discoverer Component for oracle applications 11i

As you all know oracle has de-supported oracle discoverer 4i on applications 11i, therefore all DBA's will have at some point to upgrade their discoverer from 4i to 10g.

Refer to note 313418.1 in order to do that upgrade, my post will just give you a direct hint on what to do.

Steps are as follow based on note 313418.1:
-Install Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2). This installation type does not require installation and association to Oracle Application Server 10g Release 2 (10.1.2.0.2) Infrastructure. (You can choose this option if you are not planning to use features Discoverer Connection Management, Discoverer Portlet Provider, and Oracle SSO).

- Create secure directory under $Disco_ORACLE_HOME/discoverer
cd /u07/discoverer_home/discoverer
(mkdir secure)

-cp the $FND_SECURE/.dbc , $FND_SECURE/_.dbc TO your $Disco_ORACLE_HOME/discoverer/secure directory.

-Update tnsnames.ora file in $Disco_ORACLE_HOME to include connect to your Oracle E-Business database Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business application tier server node.

-Migrate your existing Discoverer End User Layers to Discoverer 10.1.2.
$Disco_ORACLE_HOME/bin/eulapi -CONNECT /@ -AUTO_UPGRADE

-Set Applications Profile Options for Discoverer using AutoConfig
-open your xml file and specify variables as listed in the table below:
s_disco_standalone=true
s_disco_machine=for example: srpora03.us.oracle.com
s_disco_port=for example: 7778
s_disco_protocol=http https
s_disco_ver_comma=10,1,2
s_disco_eul_prefix=EUL

After that you have to run autoconfig

-Verify Applications profile options in Oracle Applications
Log into Release 11i with the System Administrator responsibility
Navigate to the Profile > System form
Query the %Discoverer% profile options.
Verify the following ICX profile options in Oracle Applications

ICX_DISCOVERER_LAUNCHER=http://:/discoverer/plus?Connect=[APPS_SECURE]
ICX_DISCOVERER_VIEWER_LAUNCHER=http://:/discoverer/viewer?Connect=[APPS_SECURE]
ICX_DISCOVERER_RELEASE=10
ICX_DISCOVERER_USE_VIEWR=Y N
ICX_DEFAULT_EUL=EUL
ICX_DISCOVERER_EUL_LANGUAGE=US
ICX_DISCOVERER_PARAMETERS=exitURL=http://:/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE

Note:
When you open the discoverer EUL using the Discoverer 10g Desktop/Admin it will ask you if you want to upgrade your EUL and you have to choose yes.

To start/stop the new discoverer do the following:
$Disco_ORACLE_HOME/opmn/bin/opmnctl stopall (to stop).
$Disco_ORACLE_HOME/opmn/bin/opmnctl startall (to start).

Empty emoms.properties file - Solution

When Oracle Management Service (OMS) filesystem is 100% full, you may loose /sysman/config/emoms.properties
Actually the file will remain empty with size of zero bytes.
A small file that can cause Grid Control not to function.

emctl start oms
.
.
.
Could not find Console Server Port in /software/oracle/OEM10gR2/oms10g/sysman/config/emoms.properties

Oracle claims that you have to install a new OMS instead of the old one. (Notes: 418453.1, 418159.1)

After some struggles looking for the undocumented syntax of the file,
I managed to make OMS working again.

The lesson
1. Always BACKUP
2. Monitor the filesystem of OMS itself
3. Create some jobs for deleting old logs and not needed archives.

Anyway, This is the file to be created with the following content,

emoms.properties
#Sun Apr 26 7:00:00 2009
oracle.sysman.emSDK.svlt.ConsoleServerName=oragridctl
oracle.sysman.eml.mntr.emdRepPwd= write here an unencrypted password
emdrep.ping.pingCommand=/bin/ping
oracle.sysman.eml.mntr.emdRepPort=1521
oracle.sysman.eml.mntr.emdRepDBName=oem
oracle.sysman.eml.mntr.emdRepPwdSeed= write here an unencrypted password
oracle.sysman.emRep.dbConn.statementCacheSize=30
(ADDRESS\=(PROTOCOL\=TCP)(HOST\=jigles)(PORT=1521)))(CONNECT_DATA\=(SERVICE_NAME\=oem)))
oracle.sysman.db.isqlplusUrl=http\://oragridctl\:4889/isqlplus/dynamic
oracle.sysman.emSDK.svlt.ConsoleServerPort=4889
oracle.sysman.eml.mntr.emdRepRAC=FALSE
oracle.sysman.emSDK.emd.rt.useMonitoringCred=true
oracle.sysman.eml.mntr.emdRepPwdEncrypted=FALSE
oracle.sysman.db.isqlplusWebDBAUrl=http\://oragridctl\:4889/isqlplus/dba/dynamic
oracle.sysman.emSDK.svlt.ConsoleServerHost=oragridctl
oracle.sysman.emSDK.svlt.ConsoleServerHTTPSPort=1156
oracle.sysman.eml.mntr.emdRepSID=oem
oracle.sysman.eml.mntr.emdRepServer=oragridctl
oracle.sysman.emSDK.sec.ReuseLogonPassword=true
oracle.sysman.eml.mntr.emdRepConnectDescriptor=
oracle.sysman.emkeyfile=/software/oracle/OEM10gR2/oms10g/sysman/config/emkey.ora
oracle.sysman.eml.mntr.emdRepUser=SYSMAN
oracle.sysman.db.adm.conn.statementCacheSize=2
oracle.sysman.db.perf.conn.statementCacheSize=30