Icon View Incident Report

Serious Serious
Reported By: Ulrich Doewich
Reported On: 4/22/2010
For: Version 2.03 Build 11
# 3192 #601 Error When Altering a Table and Adding a New Primary Key

I'm getting a strange error message with 2.03 build 11:

#601: The table user is corrupt (Error reading index pages into cache)

I get this error when I let my server create the db from scratch, and then use the client app to add a user (i.e. it would write a record to the user table).

CREATE TABLE "user"
(
"id" INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 0, INCREMENT BY 1),
"created" TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
"modified" TIMESTAMP GENERATED ALWAYS AS CURRENT_TIMESTAMP,
"auth_type" INTEGER DEFAULT 0,
"alias" VARCHAR(16) COLLATE "UNI_CI",
"password" VARCHAR(32) COLLATE "UNI",
"dn" VARCHAR(256) COLLATE "UNI",
"fst_name" VARCHAR(32) COLLATE "UNI_CI",
"surname" VARCHAR(32) COLLATE "UNI_CI",
"tel" VARCHAR(24) COLLATE "UNI_CI",
"email" VARCHAR(64) COLLATE "UNI_CI",
"tlan_cal" INTEGER,
"tree_lvl" INTEGER,
"tree_pid" INTEGER,
"acc_code" INTEGER,
"log_seq" INTEGER,
"last_mac" BYTE(8)
)
VERSION 1.0
ENCRYPTED

CREATE INDEX "tlvl_idx" ON "user" ("tree_lvl")
DESCRIPTION '1.0'

ALTER TABLE "user"
ADD CONSTRAINT "id_pk" PRIMARY KEY ("id")
DESCRIPTION '1.0'

ALTER TABLE "user"
ADD CONSTRAINT "alias_con" UNIQUE ("alias")
DESCRIPTION '1.0'



Comments Comments
The problem was caused by a mismatch in the header size for the index file used with the table. REPAIR TABLE will fix this issue after it occurs.


Resolution Resolution
Fixed Problem on 4/23/2010 in version 2.03 build 12


Products Affected 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

Image