WebSphere Portal Server - WMM tables not copied when Migrating IBM Portal 6 FP1 from

Author

WMM tables not copied when Migrating IBM Portal 6 FP1 from

2007-01-22, 1:30 am

Hi everyone!

I am having trouble with migrating the out-of-the-box Portal 6 with FP1 applied install from Cloudscape to SQL Server Standard Edition 2000 SP4.

Basicly the portal throws exceptions during startup (see SystemOt.log extract below) that indicate that tables for WMM domain have not been transfered onto SQL Server.

The migration process (have tried both wizard-based and manual) completed succesfully (as you should be able to see in ConfigTrace.log file attached below) however no WMM database tables have been transfered.

I have managed to dig out WMM database SQL scripts from portal install directory and ran them on SQL server. That has fixed the problem, however the tables contain no data and users can't log in to the portal.

We are going to have to find a way to sucesfully transfer the WMM tables using IBM portal tools as creating tables manually may cause more problems in the future.

[b]In the meantime I need to find a way to create an admin user in the WMMUSERREG table. There are constrains so I can't edit it directly.[/b]

Have tried this SQL:

[i]INSERT INTO WMMUSERREG (USER_ID, LOGONID, SALT) VALUES (-1000, 'admin' , '');[/i]

However the following error is thrown:

-----------------------

[i]Server: Msg 547, Level 16, State 1, Line 1
INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'wmmf_40'. The conflict occurred in database 'wmmdb', table 'WMMDBMBR', column 'WMMDBMBR_ID'.
The statement has been terminated. [/i]

-----------------------

[b]I need someone with IBM Portal 6 database structure knowledge to help me come up with an SQL insert statement that will take into account all constraits etc.[/b]

Please HELP!

EXTRACT FROM SystemOut.log:
-----------
[19/01/07 11:57:08:271 EST] 0000000a CacheServiceI I DYNA1001I:
WebSphere Dynamic Cache instance named
ws/com.ibm.wps.ac.ContainedRolesCache initialized successfully.
[19/01/07 11:57:12:033 EST] 0000000a SystemOut O WMM Implementation
Version: WMM5.1.x_060912 (October 11 2006)
[19/01/07 11:57:12:158 EST] 0000000a WSMM Message E DBAttributeCache init
The following SQL Exception occured during processing:
"java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]Invalid object name 'WMMDBATR'.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
.......
---- Begin backtrace for Nested Throwables
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]Invalid object name 'WMMDBAMTYP'.
.......
---- Begin backtrace for Nested Throwables
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]The cursor was not declared.

-----------

2007-02-23, 1:18 pm

I have the same problem. Did you solve the problem?

2007-02-23, 1:18 pm

Problem solved. I found that the SQL Server DBA created the WMM database with wrong collation

[02/23/07 11:08:24.425 GMT-03:00] Driver Name: SQLServer
[java] [02/23/07 11:08:24.425 GMT-03:00] Driver Version: 2.2.0040
[java] [02/23/07 11:08:24.425 GMT-03:00] Validating Database Collation....
[java] [02/23/07 11:08:24.449 GMT-03:00] Collation for P60_COMMUNITY is Albanian_CS_AS
[java] [02/23/07 11:08:24.450 GMT-03:00] Database collation is not valid for this environment.
[java] [02/23/07 11:08:24.450 GMT-03:00] Checking default database settings...
[java] [02/23/07 11:08:24.451 GMT-03:00] Error executing validation

We recreate the database, restore a previous backup and transfer the database again

Hope this help

2007-03-21, 7:21 pm

We resolved this issue. It was MS SQL Server specific.

Basically Default DB must be selected for the WMMDBuser as WMMDB and similarly for all the other users and databases ( e.g RELEASEUSR is RELEASEDB). If this is not done the database transfer wizard may fail.