ORA-31644: unable to position to block number string in dump file "string"

Cause : Export or Import was unable to position its file pointer to a specific block within the dump file. This message is usually followed by device messages from the operating system.

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

Take appropriate action based on the device messages.

update : 24-04-2017
ORA-31644

ORA-31644 - unable to position to block number string in dump file "string"
ORA-31644 - unable to position to block number string in dump file "string"

  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-30957 : cannot downgrade because there are XML indexes
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-04070 : invalid trigger name
  • ora-31193 : This versioning feature isn't supported for resource string
  • ora-22810 : cannot modify object attributes with REF dereferencing
  • ora-13353 : ELEM_INFO_ARRAY not grouped in threes
  • ora-00018 : maximum number of sessions exceeded
  • ora-39142 : incompatible version number string in dump file "string"
  • ora-02322 : failure in accessing storage table of the nested table column
  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-04051 : user string cannot use database link string.string
  • ora-24164 : invalid rule engine system privilege: string
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-30155 : An I/O Error occured during an OCIFile function call
  • ora-15057 : specified size of string MB is larger than actual size of string MB
  • ora-16773 : error starting Redo Apply
  • ora-16748 : resource guard encountered errors during database open
  • ora-30158 : The OCIFileWrite causes the file to exceed the maximum allowed size
  • ora-01325 : archive log mode must be enabled to build into the logstream
  • ora-14073 : bootstrap table or cluster may not be truncated
  • ora-28650 : Primary index on an IOT cannot be rebuilt
  • ora-31664 : unable to construct unique job name when defaulted
  • ora-22918 : specified column or attribute is not a VARRAY type
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-26701 : STREAMS process string does not exist
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-19300 : Error occurred in uri processingstring
  • 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.