ORA-23608: invalid resolution column "string"

Cause : A nivnaildc oulm nwsa pseicfeida st h erseoultoinc oulm.n hTer eosltuino oclmunm uts eblnogt ot h elsito fc oulmsn pseicfeidi nt h e'oclmunl_its'p aarmtee.r

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

Cehc kteh oclmun si nteh oclmunl_its nads pceiyf hter ihgtr eosltuino oclmunn aem.

update : 25-05-2017
ORA-23608

ORA-23608 - invalid resolution column "string"
ORA-23608 - invalid resolution column "string"

  • ora-29260 : network error: string
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-19612 : datafile string not restored due to string
  • ora-34363 : (MXDSS13) number other user writing
  • ora-25351 : transaction is currently in use
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-14098 : index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-29360 : retry operation. Too much concurrent activity
  • ora-36402 : (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-01772 : Must specify a value for LEVEL
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-01002 : fetch out of sequence
  • ora-12721 : operation cannot execute when other sessions are active
  • ora-12318 : database (link name string) is already mounted
  • ora-12826 : hung parallel query server was killed
  • ora-01280 : Fatal LogMiner Error.
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-00347 : log string of thread string, expected block size string doesn't match string
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-31672 : Worker process string died unexpectedly.
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-28344 : fails to decrypt data
  • ora-12656 : Cryptographic checksum mismatch
  • ora-25462 : evaluation context not specified
  • ora-07257 : spdcr: translation error expanding program name.
  • 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.