PROGRESS 9.1D on Unix.
I moved a table from one area to another using
proutil dbname -C tablemove pub.tablename "accounting data area" "accounting data area"
This command ran successfully.
I logged in to the DB and went to data dictionary => Schema => Modify table => picked same table i just moved It showed me the new "accounting data area" to which it belongs, which is just fine asit shud be this way.
Now when i see internally thru _file VST _ianum is not updated to 14. It still reads 10 as i moved table from 10 to 14 area number.
isn't that Odd!!! What can i do to fix it??? I don't see any data corruption in that table or any other table.
These are the messages in log file when i did the tablemove:-
13:47:46 Usr 6: Table pub.opi [71] has been moved to area accounting data area [14]. (8613)
13:47:46 Usr 6: All indexes associated with table pub.opi [71] have been moved to area accounting data area [14]. (8614)
I moved a table from one area to another using
proutil dbname -C tablemove pub.tablename "accounting data area" "accounting data area"
This command ran successfully.
I logged in to the DB and went to data dictionary => Schema => Modify table => picked same table i just moved It showed me the new "accounting data area" to which it belongs, which is just fine asit shud be this way.
Now when i see internally thru _file VST _ianum is not updated to 14. It still reads 10 as i moved table from 10 to 14 area number.
isn't that Odd!!! What can i do to fix it??? I don't see any data corruption in that table or any other table.
These are the messages in log file when i did the tablemove:-
13:47:46 Usr 6: Table pub.opi [71] has been moved to area accounting data area [14]. (8613)
13:47:46 Usr 6: All indexes associated with table pub.opi [71] have been moved to area accounting data area [14]. (8614)
