Workaround for Oracle service fails to start after changing machine name

When Oracle changes the machine name, it causes the service to not start properly and can be resolved by the following actions: Listener in the Listener.ora file in the 1.oracle\product\10.2.0\db_3\network\admin directory Instead of your new machine name, if you have a domain name, add a domain name, Tnsnames.ora ORCL to your new machine name, if you have a domain name, plus a domain name, 2.oracle\product\10.2.0\db_3\ under your "old machine name _ORCL" folder for the file name, change the old machine name to the new name 3.oracle\product\10.2.0\db_3\oc4j\j2ee has a folder for the oc4j_dbconsole_ old machine name _ORCL, the old machine name to get rid of 4. CMD execution emca-reops recreate rebuild EM database: 5. Execute emca-config Dbcontrol db execution 4,5 will let you fill in: sid:[that is the database name, the default ORCL can] listener port number: [Default fill 1521]sys , Dbsnmp,sysman's password

Workaround for Oracle service fails to start after changing machine name