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 : 29-04-2017

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

  • ora-31617 : unable to open dump file "string" for write
  • ora-25447 : encountered errors during evaluation of rule string.string
  • ora-13402 : the rasterType is null or not supported
  • ora-22304 : input type is not an object type
  • ora-19587 : error occurred reading string bytes at block number string
  • ora-13221 : unknown geometry type in the geometry object
  • ora-25193 : cannot use COMPRESS option for a single column key
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-38952 : Source database not compatible
  • ora-22295 : cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
  • ora-38722 : ON or OFF expected.
  • ora-02287 : sequence number not allowed here
  • ora-23374 : object group "string"."string" already exists
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-38412 : Expression set column string does not exist.
  • ora-24143 : invalid evaluation context name
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • ora-27025 : skgfqsbi: invalid media manager context area size
  • ora-24788 : cannot switch to specified transaction (server type)
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-06025 : NETASY: Configuration error
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-39142 : incompatible version number string in dump file "string"
  • ora-02152 : Invalid ALTER TABLESPACE ... RENAME option
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-40286 : remote operations not permitted on mining models
  • ora-09790 : sllfcf: unable to close file.
  • ora-29304 : tablespace 'string' does not exist
  • ora-32824 : schedule exists for source string and destination 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.