Closed
Bug 377735
Opened 19 years ago
Closed 19 years ago
How to restore the old data of bugzilla2.20.2 to bugzilla2.22.2
Categories
(Bugzilla :: Administration, task)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mukul.gupta, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier:
Please help how i can restore the old data of bugzilla2.20.2 to bugzilla2.22.2
Thanks in advance.Please Help.
Reproducible: Always
Steps to Reproduce:
Step 1)
Downloaded tar file for Bugzilla2.22.2
Step 2) Taken dump from MY sql
mysqldump -u root -p --databases bugs > bugs.db.backup
Step 3) unzipped for Bugzilla2.22.2 tar file in local drive
copied old data/ directory and the "localconfig" file to the new installation.
Step 4) Ran checksetup.pl
Step 5) Bugzilla is up, done the santity check everything is fine.
Now the problem starts
I need to import data of dump taken at step 2.
Step 6) import the dump Bug taken at step 2
The url to access Bugzilla works fine but as soon as i log in then error message appears.
Analysis
There are schema changes in Bugzilla2.22.2 so when i import the dump schema changes in Named_queries,attachments and other tables goes off leading to error.
Actual Results:
Error
Expected Results:
User should be log in
We have currently running Bugzilla 2.20.2 on
Platform
-----------
OS - Windows 2000 Professional
Active State Perl - 5.8.8
My SQL - 4.1.9
Apache - 2.0.59
We want to migrate to Bugzilla2.22.2
Platform
-----------
OS - Windows 2000 Professional
Active State Perl - 5.8.8
My SQL - 4.1.9
Apache - 2.0.59
Comment 1•19 years ago
|
||
This is a support question. The right place to get support is to go to http://www.bugzilla.org/support/. When you have done your backup of the DB, you have to use this same DB when upgrading. checksetup.pl will see it and convert it to match the 2.22 schema. You cannot import an old DB on a new version of Bugzilla. That's why checksetup.pl exists.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•