Table of Contents

Search

  1. Abstract
  2. Introduction
  3. Installation and Upgrade
  4. 10.3 HotFix 2
  5. 10.3 HotFix 1
  6. 10.3

Updating a Localized Schema

Updating a Localized Schema

If the pre-upgrade schema includes localized lookup tables, you might see validation errors after you upgrade.
For lookup tables that were localized in version 10.2.x, the metatdata validation process generates the following types of errors:
SIP-MV-22000 The name attribute for DB bundle [<
lookup table name
>.dbBundleMapping] is not defined in the configuration
Workaround:
  1. Download the
    dbBundleConfig.xml
    file from the C_REPOS_CO_CS_CONFIG repository table.
  2. In the
    dbBundleConfig.xml
    file, and copy the
    name=<
    lookup table name
    >
    parameter from the
    bundle
    element to the
    mapping
    element.
    For example, the following snippet shows the edited
    mapping
    elements:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <dbBundleConfiguration xmlns="http://www.example.com/mdm/db-bundle-configuration"> <bundle name="LUCountry" hubObject="C_LU_COUNTRY_LCL"> <mapping
    name="LUCountry"
    keyColumn="COUNTRY_CD" countryColumn="COUNTRY_CODE" languageColumn="LANGUAGE_CODE" valueColumn="LOCALIZED_STRING"/> </bundle> <bundle name="LUState" hubObject="C_LU_STATE_LCL"> <mapping
    name="LUState"
    keyColumn="STATE_CD" countryColumn="COUNTRY_CODE" languageColumn="LANGUAGE_CODE" valueColumn="LOCALIZED_STRING"/> </bundle> <bundle name="LUCountry.LUState" hubObject="C_LU_STATE_LCL"> <mapping
    name="LUCountry.LUState"
    keyColumn="STATE_CD" countryColumn="COUNTRY_CODE" languageColumn="LANGUAGE_CODE" valueColumn="LOCALIZED_STRING"/> </bundle> </dbBundleConfiguration>
  3. Upload the edited
    dbBundleConfig.xml
    file to the C_REPOS_CO_CS_CONFIG repository table.
  4. Run the metadata validation.
(MDM-21752)

0 COMMENTS

We’d like to hear from you!