The

Customer 360

upgrade fails.

Error Message ---> Object 'RESOURCE.HM_RELATIONSHIP_TYPE.ContactEmployee' already exists. Object cannot be added.

The

Customer 360

upgrade fails without restoring the database to the pre-upgrade state.

Go to the following directory:
<MDM installation directory>/hub/
Open the
upgrade.log
file and identify the errors.
Fix the issues identified in the
upgrade.log
file.
Go to the following directory:
<MDM installation directory>/app/tcr/hub/delta_change_xml/10.4 HF2
Delete the
<name of the changelist>.change.xml
files that were successfully applied.
The
upgrade.log
file contains the list of successfully applied change lists.
Run the upgrade script.

The

Customer 360

upgrade fails while promoting the change list.

Error Message ---> Object 'WRITE_CO_CHILD.CustomerOrg|CustomerOrgPortalContacts' already exists. Object cannot be added. (addWriteCOChild[id:WRITE_CO_CHILD.CustomerOrg|CustomerOrgPortalContacts,parentId:WRITE_CO_ROOT.CustomerOrg])

Go to the following directory:
<MDM installation directory>/hub/
Open the
upgrade.log
file and identify the errors.
Fix the issues identified in the
upgrade.log
file.
Go to the following directory:
<MDM installation directory>/app/tcr/hub/delta_change_xml/<upgrade version directory>
Delete the
<name of the changelist>.change.xml
file because of which the upgrade failed.
The
upgrade.log
file contains the
<name of the changelist>.change.xml
file because of which the upgrade failed.
Save the file.
Run the upgrade script.

The

Customer 360

upgrade fails in a WebSphere environment.

Error Message ---> unable to undeploy the provisioning.ear application. Application does not exist.

Log in to the WebSphere Application Server administrative console.

Click

Deployments

.

Undeploy the existing

provisioning-ear.ear

file.

Go to the following directory:

<MDM installation directory>/hub/server/

Run the

patchInstallSetup

script.

On UNIX

patchInstallSetup.sh -Ddatabase.password=<MDM Hub Master database password> -Davos.username=<ActiveVOS Console username> -Davos.password=<ActiveVOS Console password> -Davos.jdbc.database.username=<ActiveVOS database username> -Davos.jdbc.database.password=<ActiveVOS database password> -Dconsole.hostname=<host name> -Dconsole.webport=<port>

On Windows

patchInstallSetup.bat -Ddatabase.password=<MDM Hub Master database password> -Davos.username=<ActiveVOS Console username> -Davos.password=<ActiveVOS Console password> -Davos.jdbc.database.username=<ActiveVOS database username> -Davos.jdbc.database.password=<ActiveVOS database password> -Dconsole.hostname=<host name> -Dconsole.webport=<port>

After you upgrade to

Customer 360

10.4 HotFix 3, the title of the person entity draft is saved with the business entity name and does not reflect the format you set.

In the Provisioning Tool, click
Configuration
>
General Settings
, and then select
Metadata Localization
.
Click
Metadata Localization
.
In the Metadata Localization panel, under
Metadata Bundle
, click
Export
.
Extract the
besMetadata.zip
file to your local drive.
Open the
besMetadata.properties
file in a text editor.
Update the value of the following property from
{fullNm}
to
{fullNm} {lstNm}
:
CustomerPerson.label.existsFormat
Similarly, update other localized files.
Compress all the localized properties file into a .zip file.
In the Metadata Localization panel, under
Metadata Bundle
, click
Import
and select the .zip file that you created.
The metadata bundle is imported with the updated configuration.

After you upgrade to

Customer 360

10.4 HotFix 3, if you click the title of a draft record, the "The configuration of business entity has changed. Some fields might not appear in the draft" message appears even though no configuration changes were made.

In the Provisioning Tool, click
Configuration
>
Layout Designer
.
The
Layout Designer
appears.
In the
Layout Categories
panel, select the layout for which the message appears in the draft workspace.
Click
Edit
.
The
Design
page appears.
Click
Configure
icon of the data component in the workspace.
The
Record Details Component Designer
dialog box appears.
In the
Attributes layout
section, find the
draftInd
attribute, and click the
Delete
icon.
Click
Done
.
The
Design
page appears.
Click
Save
.

After you upgrade to

Customer 360

10.4 HotFix 3, the Repository Manager tool does not display the Domain Results tab in the Hub Console, and the C_REPOS_CO_CS_CONFIG repository table has no entry for domain validation.

Open a command prompt, and go to the following directory:
<MDM installation directory>/hub/server/conf
Open the
C360_version.info
file and note down the following information:
start-install-time
end-install-time
internal-version
name
external-version
variant
Run the following REST API request with the information that you noted down from the
C360_version.info
file:
POST http://<hostname>:<port>/cmx/<database_id>/validation/domain/version/ProductVersion
The following request body format includes information that you noted from the
C360_version.info
file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ComponentVersion>
<!--Use the information retrieved from the C360_version.info file-->
    <start-install-time>
install_start_time</start-install-time>
     <end-install-time>
install_end_time</end-install-time>
    <internal-version>
internal_version</internal-version>
    <name>
name_of_the_product</name>
    <external-version>
external_version</external-version>
    <install-status>
install_status</install-status>
    <variant>
variant</variant>
</ComponentVersion>
Click
Send
.
After you send the REST API request, the Repository Manager tool displays the
Domain Results
tab in the Hub Console, and an entry for domain validation gets added to the
C_REPOS_CO_CS_CONFIG
repository table.