Failed to commit objects to server : Undefined Info Store

[miroslav_123]

After upgrade of BO from 4.3 sp2 to 4.3 sp4, I got error "Failed to commit objects to server : Undefined Info Store" when I try to create new user or when I try to update current one. Would you please give me any tips to to solve the problem.

[TommyC]

SP4 Patch 500 don't solve the problem.

[lionel_rison]

3437779 - Failed to commit objects to server : Undefined Info Store error while creating Users/Groups, logging in with LDAP authentication In BI 4.3 SP04

 

Symptom

• After update to 4.3 SP4 Patch 1, when trying to create a user or a group an error message shows up:
  "Failed to commit objects to server : Undefined Info Store error"
  
  
• Not able to create Enterprise Users, Groups, Add new AD mapped groups. 
• Issue seem to be happening only to customers using Oracle 19c or an Oracle DB as the CMS DB with BI version 4.3 SP4 Patch 100+
• The issue may also occur when logging in with LDAP authentication:
  Account information not recognized: Internal error: An unknown exception has occurred

CMS logs may contain the following messages:

"CheckType: Not a valid type 3"

"Assert Failure: (Infostore.cpp:12526). (False : Unknown Exception caught while committing. Someone must be held accountable.)."

"InfoStoreSubSystem::CommitSingleObjectWithRetry"

"Unknown internal error encountered."

"OracleStatement.cpp"

Other Terms

User, group, ad, error, BI 4.3 SP4, Oracle, parameterization, CMS, DB, database,

Reason and Prerequisites

 Environment:

• SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.2 / 4.3)
• Windows
• Linux / Unix 
  
• Oracle 19c

Steps to Reproduce:

1. Update BI to 4.3 SP4 Patch 1
2. Logon to CMC
3. Go to Users and Groups
4. Try to create a user or a group, receives an error: "Failed to commit objects to server : Undefined Info Store error"

Cause:

• The issue is caused by a unsupported non-unicode NLS character set configured on the database level.
  

  Oracle has two values 'NLS_CHARACTERSET' and 'NLS_NCHAR_CHARACTERSET'
  which are responsible for data type of CHAR, VARCHAR2, LONG, CLOB data and NCHAR, NVARCHAR2, and NCLOB data respectively.
  When either of the 2 Character set values are set to anything that isn’t AL16UTF16 or AL32UTF8, then we encounter issues with the CMS converting UTF-16 strings to UTF-8 because of the use of a non-unicode character set.

• For example 'WE8MSWIN1252’ (which is a Western European character set) is unsupported character set because it is non-unicode

• We can determine those values by running the below SQL query:
  
  SELECT * FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER IN ('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET');

Solution

• The supportability of CMS Character sets for use in a CMS DB are documented in KBA 1462274
• This is a limitation and restriction of the BI Platform product, where the CMS DB is required to use a unicode character set
• If encountering this issue, please refer to your database vendor for further support on how to change your database's character set -- from our knowledge the character set cannot be modified once the database has been created otherwise there is a chance of data corruption, it must be set before the database is created.
• The database must be configured as per our documentation, otherwise if using a unsupported configuraton the issue falls outside of SAP scope of supportability

[miroslav_123]

Thank you 🙂

[TommyC]

I have the same problem and it look like the 3437779. Anyone have found a way to resolve without converting their DB ? All the previous version work with our DB before that.