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 : 20-08-2017

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

  • ora-13485 : error occurred during compression or decompression: string
  • ora-02315 : incorrect number of arguments for default constructor
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-07606 : szprv: $CHKPRO failure
  • ora-14152 : invalid number of partitions specified in PARTITIONS clause
  • ora-02214 : duplicate BACKUP option specification
  • ora-00287 : specified change number string not found in thread string
  • ora-27476 : "string.string" does not exist
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-30957 : cannot downgrade because there are XML indexes
  • ora-36988 : (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER.
  • ora-10936 : trace name context forever
  • ora-16593 : XML conversion failed
  • ora-22852 : invalid PCTVERSION LOB storage option value
  • ora-37182 : you may only specify one dimension to partition
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-14172 : invalid ALTER TABLE EXCHANGE SUBPARTITION option
  • ora-01654 : unable to extend index string.string by string in tablespace string
  • ora-14513 : partitioning column may not be of object datatype
  • ora-24380 : invalid mode specification
  • ora-36952 : (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
  • ora-28291 : No Kerberos Principal Value found.
  • ora-36680 : (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
  • ora-38309 : object not purgable
  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-12043 : invalid CREATE MATERIALIZED VIEW option
  • ora-32741 : Hang analysis already going on
  • 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.