EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB419732: ’ORA-01466 unable to read data -- object definition has changed’ error message appears when running a report in MicroStrategy Developer 10.x against Oracle


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This Technical Note describes an issue that occur where ’ORA-01466 unable to read data -- object definition has changed’ error message appears when running a report in MicroStrategy Developer 10.x against Oracle database. This issue occurs because of a time-based read consistency error for a database object, such as a table or index. A resolution is provided in the action section of this Technical Note

SYMPTOM:
In Strategy Developer 10.x, when users run a report against Oracle they see the following error message:
'ORA-01466 unable to read data -- object definition has changed. Error code -214721544.'
 
CAUSE:
This issue occurs because of a time-based read consistency error for a database object, such as a table or index.
 
Either of the following may have happened:

  • The query was parsed and executed with a snapshot older than the time in which the object was changed.
  • The creation time-stamp of the object is greater than the current system time. This happens, for example, when the system time is set to a time earlier than the creation time of the object.

 
ACTION:
To resolve this issue, the action depends on the cause of the issue.

  • If the cause is an old snapshot, then commit or rollback the transaction and resume work.
  • If the cause is the creation time-stamp in the future, ensure the system time is set correctly.

 
If the object creation time-stamp is still greater than the system time, then export the object's data, drop the object, recreate the object so it has a new creation time-stamp, import the object's data and resume work. 
KB419732


Comment

0 comments

Details

Knowledge Article

Published:

April 17, 2017

Last Updated:

December 31, 2018