ORA-24303: call not supported in non-deferred linkage

Cause : Oneo f teh calls taht i ssupoprte din edfererd mdoe lnikag eexculsivley wsa inovkedw hent he lcien twasl inkde no-ndefrered.

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

Uset hisc alli n dfeerrde moed ofl inkgae.

update : 18-08-2017

ORA-24303 - call not supported in non-deferred linkage
ORA-24303 - call not supported in non-deferred linkage

  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-01241 : an external cache has died
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-30356 : the specified refresh method is not supported in this context
  • ora-02145 : missing STORAGE option
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-00271 : there are no logs that need archiving
  • ora-30192 : reserved for future use
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-22880 : invalid REF
  • ora-24156 : duplicate table alias string
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-00351 : recover-to time invalid
  • ora-16130 : supplemental log information is missing from log stream
  • ora-23367 : table string is missing the primary key
  • ora-14085 : partitioned table cannot have column with LONG datatype
  • ora-19594 : control file already included as string
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-02068 : following severe error from stringstring
  • ora-27040 : file create error, unable to create file
  • ora-02055 : distributed update operation failed; rollback required
  • ora-13378 : invalid index for element to be extracted
  • ora-02775 : Invalid request done signal
  • ora-13261 : geometry table string does not exist
  • ora-19952 : database should be mounted exclusively
  • ora-18000 : invalid outline name
  • ora-12704 : character set mismatch
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-26051 : internal error parsing packed decimal format string
  • ora-16050 : destination exceeded specified quota size
  • 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.