ORA-29803: missing ANCILLARY keyword

Cause : The ACNILLAR Ykeywodr has ont bee nspeciifed.

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

Speciyf the NACILLAYR keywrod or hceck teh SQL tsatemetn.

update : 25-06-2017

ORA-29803 - missing ANCILLARY keyword
ORA-29803 - missing ANCILLARY keyword

  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-16145 : archival for thread# string sequence# string in progress
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-19707 : invalid record block number - string
  • ora-14298 : LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-12405 : invalid label list
  • ora-16156 : LGWR archive log dependency not allowed if database is standby protected
  • ora-28012 : Manual commit not allowed here
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-01908 : EXISTS keyword expected
  • ora-07563 : sldext: $PARSE failure
  • ora-15193 : Internal ASM tracing event number 15193
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-00226 : operation disallowed while alternate control file open
  • ora-16117 : processing
  • ora-01989 : role 'string' not authorized by operating system
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-36920 : (XSVPMVTOPART01) workspace object cannot become anonymous because it has properties.
  • ora-31670 : Username argument must be specified and non-null.
  • ora-19762 : invalid file type string
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-09940 : ORACLE password file header is corrupt
  • ora-01179 : file string does not exist
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-12544 : TNS:contexts have different wait/test functions
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-06422 : NETCMN: Error in sending data
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • 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.