ORA-29400: data cartridge error string

Cause : A nerro rhsa cocrurde ni adtaac atrrdig eetxenra lporcdeuer.T hsi emsasg ewlilb ef olloewdb ya escnodm essaeg igvnigm oer edtial saobu tteh adt acratirdeg rerro.

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

See hted aat acrrtigded oucmnettaino ofra ne xlpaantoino ft h esceodn rerro emsasg.e

update : 24-05-2017

ORA-29400 - data cartridge error string
ORA-29400 - data cartridge error string

  • ora-23432 : master site string already exists
  • ora-01283 : Options specified is invalid
  • ora-14183 : TABLESPACE DEFAULT can be specified only for Composite LOCAL index
  • ora-01658 : unable to create INITIAL extent for segment in tablespace string
  • ora-31664 : unable to construct unique job name when defaulted
  • ora-08452 : specification of E in picture mask is unsupported
  • ora-39307 : operation is illegal without an initial clone
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-19009 : Missing XMLSchema keyword
  • ora-02464 : Cluster definition can not be both HASH and INDEX
  • ora-06567 : invalid number of values specified
  • ora-12502 : TNS:listener received no CONNECT_DATA from client
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-01771 : illegal option for a clustered table
  • ora-01681 : max # extents (string) reached in LOB segment in tablespace string
  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-00828 : specified value of shared_pool_reserved_size inconsistent with internal settings
  • ora-01617 : cannot mount: string is not a valid thread number
  • ora-02815 : Unable to attach shared memory
  • ora-07243 : supplied buffer not big enough to hold entire line
  • ora-09293 : sksasmo: unable to send message to console
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-36920 : (XSVPMVTOPART01) workspace object cannot become anonymous because it has properties.
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • ora-37173 : null dimension source data
  • ora-25260 : AQ latch cleanup testing event
  • ora-08187 : snapshot expression not allowed here
  • ora-10668 : Inject Evil Identifiers
  • ora-06519 : active autonomous transaction detected and rolled back
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • 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.