The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

OVSD Migration from Windows Oracle 8.1.7 to Solaris Oracle 9.0 version

Highlighted
Durga Srinivas
Regular Collector

OVSD Migration from Windows Oracle 8.1.7 to Solaris Oracle 9.0 version

Hi,
We have a requirement to migrate OVSD from Oracle 8.1.7 on Windows machine to Oracle 9.0 on Solaris machine.Can somebody please let us know the guidelines for the above migration as i couldn't find them in the OVSD standard documentation.


Note : We have SD 4.5 with SP8 on windows with oracle version as 8.1.7.

Thanks
Srini
3 REPLIES
Robert S. Falko
Honored Contributor

Re: OVSD Migration from Windows Oracle 8.1.7 to Solaris Oracle 9.0 version

Srini,

You do not say anything about changing the application server(s). If not, it should be pretty simple.

1) stop application
2) export the entire schema from the current DB
3) import that schema into the new DB
4) change the application server settings so it can find the new database.

I think the OS of the database server and the version of Oracle are irrelevant.

-Josh
Durga Srinivas
Regular Collector

Re: OVSD Migration from Windows Oracle 8.1.7 to Solaris Oracle 9.0 version

Hi
Thanks for the information. When you say schema import--

Are you referring to export SD repo user & SD data user?

We tried this data migration once with the following approach

1) Exported the OVSD repo user.
2) Exported the OVSD data user.
3) Imported the OVSD repo user.
4) Imported the OVSD data user.


But during the import , we have observed some integrity constraints errors.Can you let us whether the approach we had followed was correct?

And also can you please also let me know whether you have tried such a migration and was SD stable later on?

Thanks
Srini
Robert S. Falko
Honored Contributor

Re: OVSD Migration from Windows Oracle 8.1.7 to Solaris Oracle 9.0 version

Srini,

Yes, you have got the right idea. I must admit that I have only worked with a database where the same schema contains the repo and data user, and I have not seen problems with integrity constraints.

Unless there is a real data problem, I think there are two ways, in principle, to handle this:
1) do the import twice; the second time around the dependent data should find what it is looking for.
2) disable the constraints before the import, then enable them afterwards.

Frankly, I would ask for advice from H-P on this.


-Josh
//Add this to "OnDomLoad" event