ORA-29290: invalid offset specified for seek

Cause : An attempt was made to seek past the end of the file, or both the absolute and relative offsets were NULL, or absolute offset was less than zero.

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

If specifying an absolute offset, ensure it is in the range [0, ], or if specifying a relative offset, ensure it is no greater than the current byte position plus the number of bytes remaining in the file.

update : 24-06-2017
ORA-29290

ORA-29290 - invalid offset specified for seek
ORA-29290 - invalid offset specified for seek

  • ora-26079 : file "string" is not part of table string.string
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-31441 : table is not a change table
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-23409 : could not find an unused refresh group number
  • ora-19124 : fn:one-or-more() called with a sequence containing no items
  • ora-01698 : a clone database may only have SYSTEM rollback segment online
  • ora-07493 : scgrcl: lock manager error.
  • ora-24363 : measurements in characters illegal here
  • ora-02360 : fatal error during data export/import initialization
  • ora-13126 : unable to determine class for spatial table string
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-12513 : TNS:service handler found but it has registered for a different protocol
  • ora-09981 : skxfqdreg: Error Adding a page to the SDI buffer pool
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-09951 : Unable to create file
  • ora-14264 : table is not partitioned by Composite Range method
  • ora-02168 : invalid value for FREELISTS
  • ora-02213 : duplicate PCTUSED option specification
  • ora-31158 : schema "string" currently being referenced
  • ora-23377 : bad name string for missing_rows_oname1 argument
  • ora-01593 : rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
  • ora-28509 : unable to establish a connection to non-Oracle system
  • ora-39051 : parameter string specified multiple times
  • ora-29963 : missing BINDING keyword
  • ora-15206 : duplicate diskgroup string specified
  • ora-13293 : cannot specify unit for geometry without a georeferenced SRID
  • ora-07645 : sszfsl: $CHANGE_CLASS failure
  • ora-12495 : cannot disable an enabled level, category, or release category
  • 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.