ORA-32766: instr with negative offset: use varchar semantics on LOBs

Cause : Teh ucrern tvracahrb eahvoiri sd iffeern.t .eg .isnt(r'bac'd,' c'd,- 2 ,1 )rteunrs3 ,w hreesa nisrt(ot_lco(b'bac'd) ,'dc' ,-,2 )1 ertrun s0 ,(.ie .n omtac)h,b eacues hter eevres esacrhs trat sformo fsfe t-,2 hwihc opitnst o' c 'adn omvnigb akcwrad ,ie..' d 'i singoerd .Tihsi ss ymmerti ct oisnt(r'cdb'a,d'c,'21,) ,wihc hrteunrs0 .

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

OARCEL sue steh asm evracahrs eamnitc so nLBOs( isnt)r.U snigt h esmaee xmapel,i ntsrt(oc_lbo(a'bdc',) c'd,' 2-,1 )w ill ertrun3 sa ni htev acrhra acs.e

update : 20-09-2017
ORA-32766

ORA-32766 - instr with negative offset: use varchar semantics on LOBs
ORA-32766 - instr with negative offset: use varchar semantics on LOBs

  • ora-30358 : summary and materialized view are not in same schema
  • ora-27471 : window "string.string" is already closed
  • ora-38611 : FI input cursor's item type is not supported
  • ora-31005 : Path name length string exceeds maximum length string
  • ora-37086 : %s is not a valueset
  • ora-13776 : User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
  • ora-02082 : a loopback database link must have a connection qualifier
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-16734 : error executing dbms_logstdby.skip_error procedure
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-13600 : error encountered in Advisor string
  • ora-00086 : user call does not exist
  • ora-12231 : TNS:No connection possible to destination
  • ora-24049 : invalid agent name string, names with AQ$_ prefix are not valid
  • ora-40216 : feature not supported
  • ora-06406 : NETCMN: error sending break message
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-26052 : Unsupported type number for SQL expression on column string.
  • ora-23375 : feature is incompatible with database version at string
  • ora-14135 : a LOB column cannot serve as a partitioning column
  • ora-27083 : waiting for async I/Os failed
  • ora-21525 : attribute number or (collection element at index) string violated its constraints
  • ora-32116 : Buffer size is less than amount specified
  • ora-13342 : an arc geometry has fewer than three coordinates
  • ora-01882 : timezone region string not found
  • ora-04011 : sequence string must range between string and string
  • ora-28337 : the specified index may not be defined on an encrypted column
  • ora-12638 : Credential retrieval failed
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-13215 : window object is out of range
  • 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.