Corrupt Table (OpenInsight 32-bit Specific)
At 01 JUL 2009 10:05:18AM Sean Bartram wrote:
Very strange problem:
I have a corrupt table that I am attempting to fix in my live database. I have a working, accurate version of the table in a copy of the database before I imported a bunch of data. Attempts to remove the corrupt table seem to have failed, I even deleted the table, but the live database still seems to see the corrupt table. I've created a new version of the table in the SYSPROG account and the live system is properly attached to the dictionary that was created in the SYSPROG account, but the data portion seems to be looking at the old corrupt data in the CRM (main application) account. Is there a way to manually check and/or change the OS file that the system is using for a data table??? Help!
At 02 JUL 2009 10:34AM Jared Bratu wrote:
The LIST_VOLUME command (see Programmers Reference help file) shows the table name/application/operating system file name for all tables in volume application (either attached or unattached). This will show you what OS file OI is using to when it opens a table.
When you deleted the table but it still appears to be present what steps/commands did you do?
Why did you create the new table in SYSPROG instead of your application CRM?