Oracle Startup failed with ORA-00119 and ORA-00130 in Linux

-

Reasons for ORA-00119 and ORA-00130 during Oracle database startup

Oracle startup can be failed on Linux system with below error message.
ORA-00119: invalid specification for system parameter LOCAL_LISTENER and ORA-00130 .

Common reasons for ORA-00119 and ORA-00130 includes,
  • Incorrectly defined local_listener parameter
  • Issues with server hostname configuration
In the given instance no value was set for the LOCAL_LISTENER parameter. And the hostname for the system was correct.

But "hostname –i" was failing, with host name lookup failure as below.

Check the '/etc/hosts' and '/etc/sysconfig/network' for difference on hostname definition. Set the same hostname in both files and reboot the server.





Comments

  1. UnknownJanuary 2, 2015 at 11:56 PM

    Thanks a lot. and Happy New Year 2015. :-)

    ReplyDelete
  2. ESGFebruary 6, 2016 at 1:46 PM

    Thanks a lot. I just added host name definition from '/etc/sysconfig/network' to '/etc/hosts' and worked!

    ReplyDelete
  3. UnknownMay 17, 2016 at 9:04 AM

    Thank Stefan :)

    ReplyDelete
  4. Devanad ShankerMarch 12, 2017 at 1:55 PM

    thanks a lot... my problem is solved

    ReplyDelete
  5. UnknownMay 23, 2017 at 5:28 AM

    very helpful. thanks a lot.

    ReplyDelete
  6. Saurabh TandonDecember 6, 2017 at 9:13 PM

    It helped me too.. Appreciate it.

    ReplyDelete
  7. anilechJanuary 9, 2018 at 12:32 AM

    Thanks a lot. and Happy New Year 2018. :-)

    ReplyDelete

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> Create
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more