My Oracle Support Banner

Locale Management Utility (LMU): Exporting Symbolic Strings produces invalid SLF file (Doc ID 2076213.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Siebel Tools - Version 15.0 [IP2015] and later
Information in this document applies to any platform.


Customer Statement:
Exporting strings and locale data via the Locale Management Utility (LMU) generates a broken SLF file.
The export is required for the IRM process, in order to back up the symbolic strings and locale data of unshipped languages. However, the re-import of this SLF file fails with errors.

Siebel 15.0 [IP2015] on Microsoft Windows 2008 R2 (64-bit)
Oracle Database - Enterprise Edition on Microsoft Windows 2008 R2 (64-bit)

Expected Behaviour:
After exporting Symbolic String data to an SLF file, it should be possible to re-import this file.

Actual Behaviour:
Re-import of the SLF file produces errors. In a text editor, some of the entries show unexpected blank lines within the data, while the LMU expects to find each set of data on a single line.

Error Messages:
"File has invalid format on line '37126' (On-screen error message, no SBL error number.)


By following these steps the issue can be reproduced with standard repository data:

  1. Start Tools.
  2. Select the menu entry Tools > Utilities > Locale Management...
  3. In the Options tab, select:
  1. Click the Export tab.
  2. Select "All localizable Attributes".
  3. Click the Export... button and select a file location.
  4. Click Save.
  5. Remove the locale records of the target language.
  6. After the IRM process, open the LMU utility again, repeat step 3, and select the Import tab.
  7. Select the file from step 6 as Import file and click Import.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.