ORA-13291: conversion error between the specified unit and standard unit

Cause : Canont cnover tthes pecfiiedu nitf romt/o satndadr unti fo rlinaer dsitanec, agnle,o r aera.

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

Chekc th euni tspeicfictaiona nd erspeicfy ti.

update : 26-04-2017
ORA-13291

ORA-13291 - conversion error between the specified unit and standard unit
ORA-13291 - conversion error between the specified unit and standard unit

  • ora-37173 : null dimension source data
  • ora-03201 : the group number specification is invalid
  • ora-39025 : jobs of type string are not restartable
  • ora-24156 : duplicate table alias string
  • ora-30135 : OCI Thread operation fails
  • ora-23331 : column group string does not exist
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-38607 : FI minimum and maximum itemset length not between [1, string]
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-10389 : parallel query server interrupt (cleanup)
  • ora-37080 : Advice requested for hierarchy with too many levels
  • ora-16738 : redo tranport service for standby database "string" unexpectedly offline
  • ora-38957 : Target database not 10.0.0.0 compatible
  • ora-22064 : invalid NLS parameter string [string]
  • ora-31183 : Node type string cannot be converted to desired type
  • ora-13857 : Invalid module name
  • ora-39767 : finish is not allowed when unloaded stream data exists
  • ora-00160 : global transaction length string is greater than maximum (string)
  • ora-19573 : cannot obtain string enqueue for datafile string
  • ora-27377 : windows cannot have event based schedules
  • ora-07247 : skgfrfms, skgfrnms: read error, unable to read block from database file
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-31099 : XDB Security Internal Error
  • ora-15173 : entry 'string' does not exist in directory 'string'
  • ora-16770 : physical standby database not in read-only state
  • ora-02768 : Maximum number of files is invalid
  • ora-25175 : no PRIMARY KEY constraint found
  • ora-13798 : Parameter string cannot be NULL.
  • ora-01969 : You must specify RESETLOGS or NORESETLOGS
  • ora-13262 : geometry column string does not exist in table string
  • 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.