Is there anyone here who has experience migrating Maximo from WebLogic to WebSphere? And similarly from an Oracle database to an SQL database? I am trying to decide whether or not to do so.

Weblogic to Websphere : This is mainly outside maximo configuration. You must check you integration queue, attached configuration LDAP integration,....
Oracle to SQL server : Officially there is no tool to do this. IBM has provided in 75 a utility called unclv that allow you to connect to your Oracle database and generate a big installation file (mainly drop table, create tabes, insert table statements)  that you will run against a sql server database using maxinst utility. This works. we used it many times for clients to switch database.  On the other hand, depending on the quality of your data, you may face some issues which requires you to  alter the generated installation file manually. 

2 advises here :

• You need a good utility to modify huge txt file. Notepad, notepad++,... wont work. I dont remmember which tool we used, but I remmember that we tried few tools before finding the right one.
• Because of date corruption,  you will find some dates that Oracle accepts and SQL server wont accept (I think dates before 1753, as I'm not sure about the exact date). So you will need to check all your dates in Oracle and make sure that they are valid in SQL server.     

I hope this Help

Mohamed Skandaji

George

Migrating from Weblogic to WebSphere shouldn't really be an issue, Maximo doesn't really care which one you're on.

The database migration will be more complex. The two database types have different stored functions to handle things like dates and null value checks, so you could run into issues when migrating queries, conditions, workflows etc. It is doable but whether it's worth it or not would depend on why you're looking to move to SQLServer.

Helen Fisher

Marketing Manager at BPD Zenith

Happy to be contacted at: helen.fisher@bpdzenith.com

George,

Maximo can run with SQL Server but it doesn't take advantage of any of the design features of SQL Server. You may find you have significant performance issues and personally, I would encourage you to think again, or at least perform some extensive performance tests with SQL Server before making a final decision. Of course, licensing costs can always be the final determinator :-)