ORA-02822: Invalid block offset

Cause : A server was unable to seek to the designated block.

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

Check the UNIX error number.

update : 24-05-2017

ORA-02822 - Invalid block offset
ORA-02822 - Invalid block offset

  • ora-26715 : time limit reached
  • ora-19697 : standby control file not found in backup set
  • ora-26735 : operation not allowed on the specified file group version
  • ora-03218 : invalid option for CREATE/ALTER TABLESPACE
  • ora-22057 : bad integer length [string]
  • ora-19379 : invalid time_limit or repeat_interval
  • ora-22893 : constraint can be specified only for REF columns
  • ora-08313 : sllfop: could not allocate buffers
  • ora-25293 : Lob attributes must be null for buffered operations
  • ora-38708 : not enough space for first flashback database log file
  • ora-13061 : topology with the name string does not exist
  • ora-16620 : one or more databases could not be contacted for a delete operation
  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-36995 : (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-00084 : global area must be PGA, SGA, or UGA
  • ora-28505 : cannot get non-Oracle system capabilities from string
  • ora-10560 : block type 'string'
  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-26740 : cannot downgrade because there are file groups
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-00236 : snapshot operation disallowed: mounted control file is a backup
  • ora-07280 : slsget: unable to get process information.
  • ora-06032 : NETDNT: connect failed, access control data rejected
  • ora-09719 : osncui: invalid handle.
  • ora-02426 : privilege grant failed
  • ora-39200 : Link name "string" is invalid.
  • ora-19013 : Cannot create VARRAY columns containing XMLType
  • ora-02253 : constraint specification not allowed here
  • 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.