We have a Service Desk Server 4.5 SP 23 in a Windows 2003 Server Service Pack 1, which is supported by Support Pack SD0036, properly installed. Its database is SQL Server 2000 SP4. We are planning to migrate to Oracle 9i. We do the following:
1. Stop the SQLServer Database, pilotosd. 2. Run the db_confwizard –internal, which backups the DB successfully (you can see the attached file logdatabase_backup.txt 3. We modify server settings, so it successfully points to the new DB in Oracle (the connection is tested successfully) 4. We run the db_confwizard –internal again, with the restore option. It begins creating objects and inserting data successfully, until it hangs as you can see the attached screenshot Screenshot.png 5. It also reports some errors, which you can see in the attached log logdatabase.txt
We need to migrate to Oracle immediately, because our IT department is planning to discontinue SQL Server support.
Are we doing anything wrong? Is this the proper way to do this?
We increased memory and the sd_dbconfwizard -internal finished, and the SD server started.
Although it didn't hang, we had two main problems:
- ORA-01401: inserted value too large for column. It left out about 700 rows from the following tables: ITSM_ADDRESSES ITSM_CONFIGURATION_ITEMS ITSM_INCIDENTS ITSM_ORGANIZATIONS ITSM_PERSONS ITSM_SER_CUSTOM_FIELDS ITSM_SERVICECALLS
- Consequently, when it tries to apply Foreign Key constraints, it has orphan records, and it reports ORA-02298: cannot validate (PILOTOSD.SCS_SER_OID_FK) - parent keys not found
Although it works, we don't want to take this system intro production, because there are a lot of rows missing and it's not secure, due to missing foreign keys.