Lors du redémarrage d'Ubuntu, j'ai rencontré un problème avec OEM ( Oracle Entreprise Manager ), la console d'administration. L'erreur était la suivante: OC4J Configuration issue. /u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee/OC4J_DBConsole_$HOSTNAME_orcl not found.
Pour corriger ce problème, j'ai effectué les opérations suivantes:
- Suppression du repository d'OEM: emca -deconfig dbcontrol db -repos drop;
- export ORACLE_HOSTNAME=$HOSTNAME;
- Recréation du repository: emca -config dbcontrol db -repos create.
Pour démarrer OEM, on utilise la commande suivante: emctl start dbconsole ( arrêt: emctl stop dbconsole ). Sous Ubuntu, on obtient alors le message suivant: ulimit: 25: bad number. Il peut être ignoré.
En plus de l'outil d'administration, on dispose du client de développement habituel, sqldeveloper ( commande: sh sqldeveloper.sh ). Il peut fonctionner avec OpenJDK ( commande: java -version ).
Pour éviter une fenêtre blanche ( gnome ), il faut désactiver les effets visuels dans la personnalisation de l'apparence du bureau.
Inscription à :
Publier les commentaires (Atom)
The fix seems unbelievable but here goes:
RépondreSupprimerWhile installing oracle 11gr, i removed the pre-populated entry for the global database name (which is the fully qualified host name of your machine) and replaced it with just "oradb".
This caused my em instance to be configured under "C:\oracle11gR2\product\11.2.0\dbhome_1\oc4j\j2ee\OC4J_DBConsole_localhost_oradb"
However the emctl startup scripts always expect the folder to be in the hostname format, i.e. it expected the properly configured em app to be in "C:\oracle11gR2\product\11.2.0\dbhome_1\oc4j\j2ee\OC4J_DBConsole__oradb"
So i debugged the perl scripts and found something useful, if you set the env var "ORACLE_HOSTNAME" then you can override the incorrect value that the scripts generate for the path to EM application.
so defined a environment var: "ORACLE_HOSTNAME" and set its value to "localhost".
This fixed this startup error. But wait, there was another one that came up after this:
#######
The agentTZRegion value in C:\oracle11gR2\product\11.2.0\dbhome_1\localhost_oradb/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.
######
This error was logged in C:\oracle11gR2\product\11.2.0\dbhome_1\localhost_oradb\sysman\log\agabend.log
I fixed it be changing the file "C:\oracle11gR2\product\11.2.0\dbhome_1\localhost_oradb\sysman\config\emd.properties" as follows:
Replace the line (the property value may be different in your case):
agentTZRegion=-4:00
With:
agentTZRegion=Asia/Karachi
Ofcourse you would write your machine's timezone. To determine the exact name you can search oracle webpages, you'll find a link where all these zones are listed.
After these two fixes, EM starts to work.