Restoring Data after Migrating from SQL2000 to SQL2005
Support,
I have ServiceDesk 7.0.15 migrated from MSSQL 2000 to MSSQL 2005 and all appears to be fine. I can access all of the data, make and save changes to all components, and all is behaving as I would have expected. Backups have been running for about 28 days with no problems. I needed to restore a ServiceDesk Plus backup created using the .\bin\backUpData.bat, but when I attempt to restore the data using the .\bin\restoreData.bat, I receive the following ERROR:
Please wait ! Restoring in Progress...................
0-----------------------50------------------------100(%)
QUERY = INSERT INTO aaaaccadminprofile (ACCOUNTPROFILE_ID,NAME,EXP_AFTER,DELETEO
N_EXPIRY,NVRLOGIN_EXPLT,IDLE_SESSION,EXPEW_THRES,FORCEOUT_ONEXP,SIMUL_LOGIN,ALLO
WED_BADLOGIN,LOCK_PERIOD,LOGIN_CRITERIA,rowguid) VALUESnull
java.sql.BatchUpdateException: The floating point value '08E9253' is out of the
range of computer representation (8 bytes).
I can, however, restore a ServiceDesk Plus backup created using the .\bin\backUpData.bat from before I migrated to SQL 2005 with no problem to the exact same server. The issue is that all of the backups that have been performed since the migration 28 days ago will not restore and I receive the same error. I was under the assumption and they looked OK, that the backups are/were good after the migration, but they will not restore.
Current Configuration on the web server
OS: Server 2003 Standard 32bit
Original Configuration on the SQL server
OS: Server 2003 Standard 32bit
Database Engine: MSSQL 2000 Standard 32bit
Compatability: MS SQL 2000 (80)
Current Configuration on the SQL server
OS: Server 2003 Standard 64bit
Database Engine: MSSQL 2005 Standard 64bit
Compatability: MS SQL 2005 (90)
What I have tried:
1) Re-installed ServiceDesk version 7.0.15 as the backup version 7.0.15. - twice. NO PROBLEM.
2) Restored data from BEFORE the SQL 2005 migration, EVEN the datasets that were from MSSQL 2000. NO PROBLEM.
3) Backup up the existing dataset that is currently running and working fine on the SQL 2005 server. NO PROBLEM.
4) Attempted restoring data from the server that currently running a fine dataset from several different days after the SQL 2005 migration back to a server running SQL 2005. WILL NOT RESTORE ANY OF THEM from after migration to SQL2005.
5) Attempted restoring data from the server that currently running a fine dataset from several different days after the SQL 2005 migration back to a server running SQL 2000. WILL NOT RESTORE ANY OF THEM from after migration to SQL2005.
Impact: HIGH - current backups are bad. Disaster recovery is at HIGH RISK.
Urgency: Effects Business - Cannot upgrade to v7.0.17 without compromising system.
--pete
US Government, US Geological Survey
New to ADSelfService Plus?