Oracle listener no longer working after migrated to different pool

Common Oracle Listener issues when deploying in vCloud especially when the Vapp moved to another location or gone through IP and Host changes.

Scenario

Vapp - Cloud2 resides in another cloud farm. It was shutdown and migrated to another cloud farm. The IP and Vapp name was forced to change. Obviously, this will impact the /etc/hosts, listener.ora and tnsnames.ora as well. 

After migrated, starting up the lsnrctl will fail. Using netca or changing the listener.ora and /etc/hosts will likely not going to help.

One of the reason is, the listener is still going to be looking a the host_id.

in the listener.xml file 

/home/oracle/app/oracle/diag/tnslsnr/Cloud2-001/listener/alert/log.xml

<msg time='2015-07-06T13:26:52.010-06:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='Cloud2-001'
host_addr='UNKNOWN'>
<txt>TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
  TNS-00515: Connect failed because target host or object does not exist
   Linux Error: 99: Cannot assign requested address
</txt>
</msg>

Resolution

Changing the Computer Name to whatever the new /etc/hosts and listener.ora host name is .. will fix the issue. Once the Computer Name is changed, boot up the Vapp and start up the lsnrctl.

In short, the Computer Name is going to impact the Oracle listener.