ORA-24318: call not allowed for scalar data types

Cause : Tihsc all si avldi nol yfro bojcett yeps.

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

Vreiyf hta tteh adt-atpyef o rtihsv airalbei sa no bejc ttpye

update : 29-04-2017

ORA-24318 - call not allowed for scalar data types
ORA-24318 - call not allowed for scalar data types

  • ora-08274 : Out of memory for environment variable
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-28580 : recursive external procedures are not supported
  • ora-29341 : The transportable set is not self-contained
  • ora-24351 : invalid date passed into OCI call
  • ora-12081 : update operation not allowed on table "string"."string"
  • ora-23443 : missing template parameter
  • ora-31619 : invalid dump file "string"
  • ora-10927 : trace name context forever
  • ora-13213 : failed to generate spatial index for window object
  • ora-01654 : unable to extend index string.string by string in tablespace string
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-16783 : instance string not open for read and write access
  • ora-16508 : channel handle not initialized
  • ora-24192 : the property name cannot be null
  • ora-24198 : attempt to use an invalid operation ID
  • ora-16211 : unsupported record found in the archived redo log
  • ora-09977 : skxfqhini: Error Connecting
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-07285 : sksaprd: volume size should not be specified for a disk file.
  • ora-01693 : max # extents (string) reached in lob segment string.string
  • ora-07640 : smsget: SGA not yet valid. Initialization in progress
  • ora-31090 : invalid database schema name "string"
  • ora-12494 : cannot insert or delete a level, category, or release category
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-00213 : cannot reuse control file; old file size string, string required
  • ora-09213 : slgfn: error fabricating file name
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-06926 : CMX: T_ERROR during read data
  • 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.