ORA-29267: illegal call

Cause : The cal lto the LP/SQL AP Iwas illgeal at teh curren tstage o fthe opeartion.

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

Retry teh call a ta diffeernt stag eof the poeration.

update : 22-08-2017

ORA-29267 - illegal call
ORA-29267 - illegal call

  • ora-39307 : operation is illegal without an initial clone
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-06903 : CMX: cannot read transport address of remote application
  • ora-14073 : bootstrap table or cluster may not be truncated
  • ora-16232 : adding Logical Standby skip entry for table string.string
  • ora-28582 : a direct connection to this agent is not allowed
  • ora-02877 : smpini: Unable to initialize memory protection
  • ora-01936 : cannot specify owner when creating users or roles
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-19620 : %s is not of string type
  • ora-28028 : could not authenticate remote server
  • ora-28593 : agent control utility: command terminated with error
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-06309 : IPA: No message queue available
  • ora-00283 : recovery session canceled due to errors
  • ora-12062 : transaction string received out of sequence from site string
  • ora-31157 : Invalid Content-Type charset
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-24021 : queue table definition not imported for string.string
  • ora-26650 : %s background process string might not be started successfully
  • ora-21604 : property [string] is not a property of transient or value instances
  • ora-25262 : agent name cannot be NULL if address is a multi-consumer queue
  • ora-01940 : cannot drop a user that is currently connected
  • ora-14037 : partition bound of partition "string" is too high
  • ora-04074 : invalid REFERENCING name
  • ora-09838 : removeCallback: failure removing the callback port.
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-30447 : internal data for run number string is inconsistent
  • ora-16529 : bad sender id
  • 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.