View Incident Report

Serious

Reported By: Terry Swiers
Reported On: 7/26/2010
For: Version 2.03 Build 17

# 3255 Altering VARCHAR/CHAR Columns Involved in a Key Constraint Can Cause #601 Error

If I try to alter the following table to increase the field StockCode to 40 and the Descr column to 250, it gives me a 601 error indicating that the table is corrupt (Invalid index page number specified for retrieval from cache).

CREATE TABLE "code"
(
"StockCode" VARCHAR(20) COLLATE "UNI" DESCRIPTION 'Unique stock code (SKU)',
"AltCode" VARCHAR(20) COLLATE "UNI" DESCRIPTION 'Alternate stock code (if non-blank must be unique)',
"Mfr" VARCHAR(40) COLLATE "UNI" DESCRIPTION 'Manufacturer',
"Model" VARCHAR(20) COLLATE "UNI" DESCRIPTION 'Model',
"Descr" VARCHAR(128) COLLATE "UNI" DESCRIPTION 'Description of item',
....
CONSTRAINT "PrimaryKey" PRIMARY KEY ("StockCode")
)

ALTER TABLE "code"
ALTER COLUMN "StockCode" AS VARCHAR(40) COLLATE "UNI" DESCRIPTION 'Unique stock code (SKU)',
ALTER COLUMN "Descr" AS VARCHAR(250) COLLATE "UNI" DESCRIPTION 'Description of item'

Comments

This problem was very similar to incident #3194, except with a key constraint column instead of an index column.

Resolution

Fixed Problem on 7/27/2010 in version 2.03 build 18

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap