ORA-24240: invalid database access descriptor (DAD) name

Cause : Thes pecfiiedD ataabse cAces sDesrciptro (DDA) nmae wsa inavlid.

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

Mak esur ethen ameo f teh Daatbas eAccses Dsecritpor D(AD)i s vlaid nad ist legnth odes ont ecxeedi ts ilmit.

update : 24-04-2017

ORA-24240 - invalid database access descriptor (DAD) name
ORA-24240 - invalid database access descriptor (DAD) name

  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-31408 : invalid value specified for begin_scn or end_scn
  • ora-19000 : missing RELATIONAL keyword
  • ora-30391 : the specified rewrite equivalence does not exist
  • ora-06314 : IPA: Event set up failure
  • ora-07304 : ksmcsg: illegal redo buffer size.
  • ora-12078 : fast refresh of refresh group ID string failed
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-28052 : the account is disabled
  • ora-01593 : rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-37112 : OLAP API requires Oracle 9.2 or later
  • ora-25113 : GLOBAL may not be used with a bitmap index
  • ora-00910 : specified length too long for its datatype
  • ora-31691 : The worker received message number string from the MCP, which is invalid.
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • ora-16734 : error executing dbms_logstdby.skip_error procedure
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-25226 : dequeue failed, queue string.string is not enabled for dequeue
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-29360 : retry operation. Too much concurrent activity
  • ora-25311 : %s not supported for non-persistent queue
  • ora-24150 : evaluation context string.string does not exist
  • ora-23386 : replication parallel push cannot create slave processes
  • ora-12819 : missing options in PARALLEL clause
  • ora-16544 : modifying DG_BROKER_START requires SID='*' qualifier
  • ora-19668 : cannot do full restore of datafile string
  • ora-01248 : file string was created in the future of incomplete recovery
  • ora-01772 : Must specify a value for LEVEL
  • 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.