sysobstate corrupt
Posted in 2005
Topics: Triggers, Constraints & Referential Integrity
Hi All, We had mistakenly deleted a trigger from the systriggers table of our database using "delete from systriggers where trigname = <triggername>"...instead of using the "drop trigger triggername" command. As a result of which our sysobjstate table got corrupted. Now, we are not able to load the trigger nor could we create forms for the table(for which the trigger was deleted). Any source of information would be helpful. Thanks, Mbeary
Farooq wrote:
> Hi All,
>
> We had mistakenly deleted a trigger from the systriggers table of our
> database using "delete from systriggers where trigname =
> <triggername>"...instead of using the "drop trigger triggername"
> command. As a result of which our sysobjstate table got corrupted.
>
> Now, we are not able to load the trigger nor could we create forms for
> the table(for which the trigger was deleted).
>
> Any source of information would be helpful.
First thing to try:
- Export ALL of the data in the table to a disk file.
- Export the table's schema to a file with dbschema -d database -t table -ss
(or with myschema -d database -t table)
- Patch the schema file with the missing trigger if it is needed and missing
from the schema (likely)
- Drop the table
- Recreate the table by running the schema file
- Reload the data from the disk file.
If that doesn't work ... Call tech support and ask them if they can repair
the damage. Ultimately you may have to unload the entire database, drop the
database, recreate the database, reload the data.
Art S. Kagel