APAR status
Closed as documentation error.
Error description
When running the portal-post-upgrade task where your 6.1 server is not pointing to the same physical ldap as your previous server, the migration code will attempt to update the vmm config pointing to the prior ldap server. This can cause problems if there was a failure of the post upgrade task by keeping the portal from starting during the next round of the task
Local fix
If you have a backup of the wimconfig.xml file replace that file into the wim directory and then restart the post-upgrade task This is going to be documented as a doc defect in that you should not be moving ldap servers during a migration. and if you need to go to an ldap server that is not supported in 6.1 it is best practices to upgrade the ldap server but still have both portals pointing to the same physical ldap server
Problem summary
doc was missing some statements added those
Problem conclusion
doc is missing statments
Temporary fix
Comments
APAR Information
APAR number
PK72933
Reported component name
WEBSPHERE PORTA
Reported component ID
5724E7600
Reported release
610
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-29
Closed date
2008-10-17
Last modified date
2008-10-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]
Document Information
Modified date:
21 December 2021