ORA-23340: incorrect resolution method string

Cause : Use rfuntcioni s sepcifeid wehn cnoflitc reoslutoin mtehodw as ont "SUER UFNCTOIN" ro spceifide reoslutoin mtehodi s nto on eof hte perdefnied emthosd.

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

If suer ufnctoin i sspeicfie dwhe nconlfictr esoultio nmetohd wsa no t"USRE FUCNTIO"N, etiherr ereigste rfuntcionw ithm ethdo as" USE RFUNTCION "or pseciyf a UNLL suer ufnctoin. tOheriwse pSeciyf on eof hte dcoumetned usppotred ocnflcit rseoluiton emthosd.

update : 27-04-2017

ORA-23340 - incorrect resolution method string
ORA-23340 - incorrect resolution method string

  • ora-26736 : Data Pump error
  • ora-19684 : block media recovery failed because database is suspended
  • ora-19672 : media management software returned invalid file status
  • ora-16625 : cannot reach the database
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-06437 : ssaio: the asynchronous write was unable to write to the database file.
  • ora-40109 : inconsistent logical data record
  • ora-02756 : osnfsmnam: name translation failure
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-02167 : LOGFILE clause specified more than once
  • ora-30964 : The XML Index was not usable.
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-31073 : Resource not retrieved using path name
  • ora-08308 : sllfop: Cannot open file
  • ora-12658 : ANO service required but TNS version is incompatible
  • ora-30752 : column or table string is not substitutable
  • ora-38603 : FI including & excluding cursor can only return one column
  • ora-02359 : internal error setting attribute string
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-01569 : data file too small for system dictionary tables
  • ora-32731 : Another Parallel Oradebug session is in progress
  • ora-09759 : osnsbt: bad message received.
  • ora-00274 : illegal recovery option string
  • ora-06035 : NETDNT: connect failed, insufficient resources
  • ora-14455 : attempt to create referential integrity constraint on temporary table
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-07454 : queue timeout, string second(s), exceeded
  • ora-32845 : Messaging Gateway agent is already running
  • 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.