From: Karl & Betty SchendelSubject: Re: DMT_SHOW Error At 8:42 AM +0000 11/9/99, Trevor East wrote: >Could someone please explain to what the DMT_SHOW error is. The site from >which I receive my data is having problems with their database with the >following error message. > >E_RD0060 Cannot access table information due to non-recoverable DMT_SHOW >E_DM010B An error occurred while showing information about a table >E_SC0206 An internal error prevents further processing of this query. DMT_SHOW would seem to be the internal name for the function(s) that fetch relational schema information from the system catalogs. A DMT_SHOW error usually implies some sort of problem with the core catalogs, such as iiattribute or iirelation. Deadlock on the system catalogs will also result in some form of DMT_SHOW error. I'd start by examining the error log more closely. Are there any other related error messages? Can you select * from iirelation and iiattribute? The next step would probably be a verifydb -mreport -sdbname -odbms which does a number of cross-checks on the catalogs. (Do NOT run this verifydb flavor in -mrun mode, as it sometimes recommends imappropriate actions, especially on databases upgraded from 6.4.) Karl R. Schendel, Jr. K/B Computer Associates schendel@kbcomputer.com Ingres and Unix Expertise Past President, North American Ingres Users Association past_president@naiua.org From: Andre Laframboise Subject: Re: DMT_SHOW Error I always got these when the underlying datafile for a table was for some reason or other unavailable. i.e. Data location file system unmounted, disk errors, etc. Andre From: Jim Agnew Subject: Re: DMT_SHOW Error one other cause is that sometimes we'd do the unloaddb script, and if the name of a table was a sql reserved word (work), that would do it every time... Jim From: Tushar Agarwal Subject: Re: DMT_SHOW Error There may be one of the following problem 1. The database location on which your table/tables stored is drooped 2. The Slice on which the location exists is not mounted at boot time Thanks Tushar > How do I repair a database with the error E_RD0060 ? Cannot access table > information due to a non-recoverable DMT_SHOW error Hi Herv, I've seen this before when recovering unjournalled heap tables. Its caused by an interaction of sysmod and dropping the tables and how this information is all stored in the catalogs! In short you recover the description of the table but not the underlying UNIX file. You can verify this for yourself. If memory serves correctly the non-recoverable DMT_SHOW error is normally preceeded with an error message telling you which filename (UNIX) could not be found. Use the information in iifile_info to convert this into a tablename. If as I say it was a table you wanted to delete anyway then the solution is to touch the filename in tha appropriate data area. Then you may simply drop the table and now Ingres is happy to comply. I've raised this issue with CA a long time ago, and I suspect they've forgotten all about it. Martin Bowes
© William Yuan 2000
Email William