Welcome to the dBforums forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

If you prefer not to see double-underlined words and corresponding ads, place your cursor
here for ContentLink opt out.

Go Back  dBforums > Database Server Software > Other > Ingres Corruption

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-12-02, 11:31
Gareth Williams Gareth Williams is offline
Registered User
 
Join Date: Feb 2002
Location: Wales in UK
Posts: 1
Unhappy Ingres Corruption

I've recently got BAD_ATTRIBUTE errors using IngresII on Solaris8. This error came out of the blue.

I've search the net and the only explanation I can find is that Ingres put some corrupt info in database fields.

I had to unload-reload these tables using "copydb -c" before I could get around it. That suggests that some odd control charater must have somehow got into one of the index fields that is common to about 10 tables.

The application is written using the Ingres ABF tools. Is there any way of capturing dud characters before they get to the braindead DB Engine?

Has anyone else had this?
__________________
GWilliams
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On