ORA-24911: Cannot start listener thread at specified port

Cause : Thread already running at a different port.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Set the correct port in the environment handle or let the system choose the port.

update : 18-08-2017

ORA-24911 - Cannot start listener thread at specified port
ORA-24911 - Cannot start listener thread at specified port

  • ora-00406 : COMPATIBLE parameter needs to be string or greater
  • ora-06974 : X.25 Driver: SID lookup failure
  • ora-16211 : unsupported record found in the archived redo log
  • ora-06024 : NETASY: VTM error
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-07513 : sscgctl: $deq unexpected return on cancel of term. lock
  • ora-02770 : Total number of blocks is invalid
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-09908 : slkmnm: gethostname returned error code.
  • ora-13014 : a topology identifier outside the range of 1 to 8 was specified
  • ora-27056 : could not delete file
  • ora-16746 : resource guard encountered errors during database mount
  • ora-14007 : missing LESS keyword
  • ora-28580 : recursive external procedures are not supported
  • ora-26041 : DATETIME/INTERVAL datatype conversion error
  • ora-31411 : change set string is referenced by a change table
  • ora-10691 : Set background process core file type (Unix only)
  • ora-13621 : The task_or object string is marked as a template and cannot perform the requested operation.
  • ora-06318 : IPA: Local maximum number of connections exceeded
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-02398 : exceeded procedure space usage
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-06913 : CMX: error during redirection of connection
  • ora-06041 : NETDNT: disconnect failed
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-13528 : name (string) is already used by an existing baseline
  • ora-19229 : XP0009 - schema import not supported
  • ora-17612 : Failed to discover Oracle Disk Manager library, return value string
  • ora-32827 : Messaging Gateway agent must be shut down
  • ora-39014 : One or more workers have prematurely exited.
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.