ORA-26673: duplicate column name string

Cause : An attempt was made to specify a duplicate column name in an LCR.

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

Remove the duplicate column and retry the operation.

update : 23-05-2017

ORA-26673 - duplicate column name string
ORA-26673 - duplicate column name string

  • ora-02342 : replacement type has compilation errors
  • ora-24049 : invalid agent name string, names with AQ$_ prefix are not valid
  • ora-24802 : user defined lob read callback error
  • ora-00019 : maximum number of session licenses exceeded
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-22160 : element at index [string] does not exist
  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-31669 : Worker process string violated startup protocol.
  • ora-32109 : invalid column or parameter position
  • ora-06802 : TLI Driver: could not open the /etc/netware/yellowpages file
  • ora-00608 : testing error [string] [string] [string] [string] [string]
  • ora-23489 : duplicate entry "string"
  • ora-00053 : maximum number of enqueues exceeded
  • ora-17507 : I/O request size string is not a multiple of logical block size
  • ora-27012 : skgfrd: read from file failed
  • ora-30181 : integer in argument index is not immediately followed by )
  • ora-22317 : typecode number is not legal as a number type
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-14164 : subpartition "string": INITRANS value must be less than MAXTRANS value
  • ora-13623 : The recommendation string is not valid for task string.
  • ora-31116 : Tablespace not specified correctly
  • ora-14303 : partitions or subpartitions are not in the right order
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-13333 : invalid LRS measure
  • ora-19693 : backup piece string already included
  • ora-09241 : smsalo: error allocating SGA memory
  • ora-09878 : sstascre/sstasat: shmat error, unable to attach tas write page
  • ora-14301 : table-level attributes must be specified before partition-level attributes
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-16167 : LGWR network server could not switch to non-blocking mode
  • 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.