ORA-38448: Indexing predicates with "string" operator is not supported.

Cause : An nusupoprte dopeartorw as sued ni th eexfi$ndeoxpera rra.y

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

Chosoe teh opreatosr frmo thsi lits : ,= <,> , <,= >= ,!=,i s nlul, si no tnul,l nv,l an dbetewen.

update : 26-06-2017

ORA-38448 - Indexing predicates with "string" operator is not supported.
ORA-38448 - Indexing predicates with "string" operator is not supported.

  • ora-13857 : Invalid module name
  • ora-12429 : label list range exceeded
  • ora-31199 : Warning in processing file string
  • ora-25179 : invalid PCTTHRESHOLD storage option value
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-38790 : BEFORE must be specified with RESETLOGS
  • ora-09350 : Windows 32-bit Two-Task driver unable to allocate context area
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-12513 : TNS:service handler found but it has registered for a different protocol
  • ora-02152 : Invalid ALTER TABLESPACE ... RENAME option
  • ora-26062 : Can not continue from previous errors.
  • ora-32007 : internal
  • ora-00092 : LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
  • ora-28511 : lost RPC connection to heterogeneous remote agent using SID=string
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-35180 : (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}
  • ora-12521 : TNS:listener does not currently know of instance requested in connect descriptor
  • ora-09877 : sstascre: shmget error, unable to get a shared memory segment.
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-16252 : Rebuild operation not permitted
  • ora-24362 : improper use of the character count flag
  • ora-24399 : invalid number of connections specified
  • ora-09884 : Two Task interface: SID doens't match current PU
  • ora-12533 : TNS:illegal ADDRESS parameters
  • ora-12422 : max policies exceeded
  • ora-15153 : cluster not in rolling upgrade
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-02784 : Invalid shared memory ID specified
  • 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.