Unable to Upgrade Database from 3.5.12 to 4.0.9

Discuss problems installing or using TrackStudio.

Unable to Upgrade Database from 3.5.12 to 4.0.9

Postby hammj » Wed Jan 05, 2011 12:12 am

Whenever I try to upgrade the DB from version 3.5.12 to 4.0.9 I get an error. Any help would be appreciated, see error below:

------------------FAILED------------------
update gr_udf set udf_script=(select script_longtext from gr_script where script_id=udf_script)
(
------------------------------------------
GDS Exception. 335544569. Dynamic SQL Error
SQL error code = -206
Column unknown
UDF_SCRIPT
At line 1, column 85.
------------------FAILED------------------
update gr_udf set udf_lookupscript=(select script_longtext from gr_script where script_id=udf_lookupscript)
(
------------------------------------------
GDS Exception. 335544569. Dynamic SQL Error
SQL error code = -206
Column unknown
UDF_LOOKUPSCRIPT
At line 1, column 91.
------------------FAILED------------------
update gr_trigger set trigger_after=(select script_longtext from gr_script where script_id=trigger_after)
(
------------------------------------------
GDS Exception. 335544569. Dynamic SQL Error
SQL error code = -206
Column unknown
TRIGGER_AFTER
At line 1, column 92.
------------------FAILED------------------
update gr_trigger set trigger_before=(select script_longtext from gr_script where script_id=trigger_before)
(
------------------------------------------
GDS Exception. 335544569. Dynamic SQL Error
SQL error code = -206
Column unknown
TRIGGER_BEFORE
At line 1, column 93.
------------------FAILED------------------
update gr_trigger set trigger_insteadof=(select script_longtext from gr_script where script_id=trigger_insteadof)
(
------------------------------------------
GDS Exception. 335544569. Dynamic SQL Error
SQL error code = -206
Column unknown
TRIGGER_INSTEADOF
At line 1, column 96.
------------------FAILED------------------
DROP TABLE gr_udfval
(
------------------------------------------
GDS Exception. 335544351. unsuccessful metadata update
cannot delete
COLUMN UDFVAL_UDF
there are 1 dependencies
Reason: unsuccessful metadata update
cannot delete
COLUMN UDFVAL_UDF
there are 1 dependencies
------------------FAILED------------------
CREATE TABLE gr_udfval ( udfval_id VARCHAR(32) NOT NULL, udfval_str VARCHAR(2000) , udfval_num FLOAT , udfval_dat TIMESTAMP , udfval_udflist VARCHAR(32) , udfval_task VARCHAR(32) , udfval_user VARCHAR(32) , udfval_udf VARCHAR(32) NOT NULL, udfval_udfsource VARCHAR(32) NOT NULL, udfval_longtext VARCHAR(32) , CONSTRAINT xpkgr_udfval PRIMARY KEY (udfval_id))
(
------------------------------------------
GDS Exception. 335544351. unsuccessful metadata update
Table GR_UDFVAL already exists
------------------FAILED------------------
INSERT INTO gr_udfval(udfval_id, udfval_str, udfval_num, udfval_dat, udfval_udflist, udfval_task, udfval_user, udfval_udf, udfval_udfsource, udfval_longtext) SELECT udfval_id, udfval_str, udfval_num, udfval_dat, udfval_udflist, udfval_task, udfval_user, udfval_udf, udfval_udfsource, udfval_longtext FROM gr_udfval_tmp
(
------------------------------------------
GDS Exception. 335544569. Dynamic SQL Error
SQL error code = -206
Column unknown
UDFVAL_LONGTEXT
At line 1, column 142.
------------------FAILED------------------
DROP table gr_task
(
------------------------------------------
GDS Exception. 335544351. unsuccessful metadata update
cannot delete
COLUMN TASK_ID
there are 1 dependencies
Reason: unsuccessful metadata update
cannot delete
COLUMN TASK_ID
there are 1 dependencies
------------------FAILED------------------
CREATE TABLE gr_task ( task_id VARCHAR(32) NOT NULL, task_shortname VARCHAR(200) , task_name VARCHAR(200) NOT NULL, task_submitdate TIMESTAMP NOT NULL, task_updatedate TIMESTAMP NOT NULL, task_closedate TIMESTAMP , task_description VARCHAR(2000) , task_abudget BIGINT , task_budget BIGINT , task_deadline TIMESTAMP , task_category VARCHAR(32) NOT NULL, task_status VARCHAR(32) NOT NULL, task_resolution VARCHAR(32) , task_priority VARCHAR(32) , task_submitter VARCHAR(32) NOT NULL, task_handler VARCHAR(32) NOT NULL, task_parent VARCHAR(32) , task_longtext VARCHAR(32) , task_number VARCHAR(32) , CONSTRAINT xpkgr_task PRIMARY KEY (task_id))
(
------------------------------------------
GDS Exception. 335544351. unsuccessful metadata update
Table GR_TASK already exists
------------------FAILED------------------
INSERT INTO gr_task (task_id, task_shortname, task_name, task_submitdate, task_updatedate, task_closedate, task_description, task_abudget, task_budget, task_deadline, task_category, task_status, task_resolution, task_priority, task_submitter, task_handler, task_parent, task_longtext, task_number) SELECT task_id, task_shortname, task_name, task_submitdate, task_updatedate, task_closedate, task_description, task_abudget, task_budget, task_deadline, task_category, task_status, task_resolution, task_priority, task_submitter, task_handler, task_parent, task_longtext, task_number from gr_task_tmp
(
------------------------------------------
GDS Exception. 335544665. violation of PRIMARY or UNIQUE KEY constraint "XPKGR_TASK" on table "GR_TASK"
------------------FAILED------------------
ALTER TABLE gr_udfval ADD CONSTRAINT fudfval_6 FOREIGN KEY (udfval_longtext) REFERENCES gr_longtext (longtext_id)
(
------------------------------------------
GDS Exception. 335544351. unsuccessful metadata update
Unknown columns in index FUDFVAL_6
Database connection |
Joshua M. Hamm
Developer
Systems Integration, Software Services
hammj
 
Posts: 35
Joined: Fri Dec 30, 2005 10:37 pm
Location: Sacramento CA

Re: Unable to Upgrade Database from 3.5.12 to 4.0.9

Postby admin » Wed Jan 05, 2011 2:00 pm

Can you send me (maximkr@trackstudio.com) TrackStudio 3.5 database (fdb) ?
Maxim Kramarenko (mailto: maximkr@trackstudio.com)
TrackStudio - Hierarchical Bug & Issue Tracking Software
http://www.trackstudio.com
admin
Site Admin
 
Posts: 7454
Joined: Thu Jan 01, 1970 3:00 am
Location: Smolensk, Russia

Re: Unable to Upgrade Database from 3.5.12 to 4.0.9

Postby hammj » Wed Jan 05, 2011 9:25 pm

This database has data in it that I would have to scrub first. Is the a mechinism within Server Manager that can Annonymize the database itself similar to how the export tool does when it creates an XML.
Joshua M. Hamm
Developer
Systems Integration, Software Services
hammj
 
Posts: 35
Joined: Fri Dec 30, 2005 10:37 pm
Location: Sacramento CA

Re: Unable to Upgrade Database from 3.5.12 to 4.0.9

Postby admin » Tue Jan 11, 2011 9:58 pm

Yes, you can anonymize database when export it using Server Manager.
Maxim Kramarenko (mailto: maximkr@trackstudio.com)
TrackStudio - Hierarchical Bug & Issue Tracking Software
http://www.trackstudio.com
admin
Site Admin
 
Posts: 7454
Joined: Thu Jan 01, 1970 3:00 am
Location: Smolensk, Russia


Return to TrackStudio Support

Who is online

Users browsing this forum: No registered users and 0 guests

cron