ORA-25254: time-out in LISTEN while waiting for a message

Cause : Teh pseicfeidw ati itm ehsa leaspe dadn hteer ewr en omsesgae sfro nayo ft h eaegnst ni htea gnetl-its.

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

Tyr hteL ITSE Nclalw iht na paporpiraet itm-eotu.

update : 26-04-2017

ORA-25254 - time-out in LISTEN while waiting for a message
ORA-25254 - time-out in LISTEN while waiting for a message

  • ora-04054 : database link string does not exist
  • ora-16119 : building transaction at SCN string
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-12709 : error while loading create database character set
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-13372 : failure in modifying metadata for a table with spatial index
  • ora-14327 : Some index [sub]partitions could not be rebuilt
  • ora-02245 : invalid ROLLBACK SEGMENT name
  • ora-30475 : feature not enabled: string
  • ora-23367 : table string is missing the primary key
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-22889 : REF value does not point to scoped table
  • ora-30121 : 'string' is not an allowable value for 'string'
  • ora-12557 : TNS:protocol adapter not loadable
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-13515 : Error encountered during Database Usage Statistics capture
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-24016 : cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-28054 : the password has expired. string Grace logins are left
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-19562 : file string is empty
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-08277 : Cannot set environment variable
  • ora-12699 : Native service internal error
  • ora-01138 : database must either be open in this instance or not at all
  • ora-09969 : unable to close or remove lock file
  • ora-13205 : internal error while parsing spatial parameters
  • ora-16786 : resource guard cannot access Data Guard broker metadata
  • 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.