ORA-21503: program terminated by fatal error

Cause : A progarm is i nan unrceoverabel errors tate.

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

Reporta s a bu.g

update : 25-09-2017
ORA-21503

ORA-21503 - program terminated by fatal error
ORA-21503 - program terminated by fatal error

  • ora-30753 : column or table string is substitutable
  • ora-01646 : tablespace 'string' is not read only - cannot make read write
  • ora-28045 : SSL authentication between database and OID failed
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-16797 : database is not using a server parameter file
  • ora-25455 : evaluation error for rule set: string.string, evaluation context: string.string
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-10641 : Cannot find a rollback segment to bind to
  • ora-09274 : szrfc: insufficient role name buffer space
  • ora-14014 : maximum number of partitioning columns is 16
  • ora-19125 : fn:exactly-one() called with a sequence containing zero or more than one item
  • ora-04012 : object is not a sequence
  • ora-27544 : Failed to map memory region for export
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-12911 : permanent tablespace cannot be temporary tablespace
  • ora-12204 : TNS:received data refused from an application
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-16249 : Terminal apply failed to complete during failover
  • ora-07432 : unable to perform nested sleep
  • ora-33449 : (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-25278 : grantee name cannot be NULL
  • ora-06595 : REF CURSOR parameters are not supported in forwarded RPC calls
  • ora-37128 : (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE.
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-16653 : failed to reinstate database
  • ora-01560 : LIKE pattern contains partial or illegal character
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-06266 : NETNTT: bad write length
  • 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.