ORA-29818: column name not properly specified

Cause : Nam eof hte cloumns houdl cotnaint he atblea nd hte cloumnn ame.

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

Speicfy avaldi coulmn anme.

update : 16-08-2017

ORA-29818 - column name not properly specified
ORA-29818 - column name not properly specified

  • ora-22863 : synonym for datatype string.string not allowed
  • ora-06771 : TLI Driver: error reading version
  • ora-24376 : cannot register/get user callback for non-environment handle
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-29868 : cannot issue DDL on a domain index marked as LOADING
  • ora-24384 : Application context size is not initialized
  • ora-25959 : join index must be of the bitmap type
  • ora-01548 : active rollback segment 'string' found, terminate dropping tablespace
  • ora-08106 : cannot create journal table string.string
  • ora-02799 : Unable to arm signal handler
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-24396 : invalid attribute set in server handle
  • ora-31071 : Invalid database username or GUID string
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-29301 : wrong DBMS_PITR package function/procedure order
  • ora-16166 : LGWR network server failed to send remote message
  • ora-23470 : invalid status
  • ora-13526 : baseline (string) does not exist
  • ora-00396 : error string required fallback to single-pass recovery
  • ora-31462 : internal error while accessing metadata
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-19701 : device name exceeds maximum length of string
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-29823 : object being analyzed is not a table
  • ora-25532 : MTTR specified is too large: string
  • ora-27063 : number of bytes read/written is incorrect
  • ora-36634 : (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
  • 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.