Drop table got Error[4254]: Object has invalid state and can't be accessed
Bug #1443617 reported by
Jieping Zhang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Trafodion |
New
|
Medium
|
Unassigned | ||
Bug Description
I have run into this error for several times, so I am filing a bug to trace this issue.
Sometimes drop table will fail with ERROR[4254], object has invalid state and cannot be accessed.
>>set schema odbctest;
--- SQL operation complete.
>>drop table GTN2BSG5FQ cascade;
*** ERROR[4254] Object TRAFODION.
--- SQL operation failed with errors.
The table above is on onyx13(
Revision history for this message
| Anoop Sharma (anoop-sharma) wrote | #1 |
To post a comment you must log in.
The problem here is that the table is already in an invalid state before the drop command
was issued. It could be the case that the hbase physical object is missing when this
drop command was issued or somehow metadata information about this table
is inconsistent. Earlier we used to ignore it but our error checks now detect this
inconsistent state. To clean up that state, one must issue 'cleanup table t' so
that any inconsistency related to this table could be corrected.