EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB324285: The error "Metadata is in an inconsistent state: Unrecognized ID '' found in table 'DSSMDOBJDEF2' column 'OBJECT_ID'" is seen when trying to upgrade or run an Intelligence Server against an Oracle 12c metadata


Community Admin

• Strategy


This Technical Note describes an issue where the error "Metadata is in an inconsistent state: Unrecognized ID '' found in table 'DSSMDOBJDEF2' column 'OBJECT_ID'" is seen when trying to upgrade or run an Intelligence Server against an Oracle 12c metadata running on Linux.

SUMMARY
This Technical Note describes an issue where the error "Metadata is in an inconsistent state: Unrecognized ID '' found in table 'DSSMDOBJDEF2' column 'OBJECT_ID'" is seen when trying to upgrade or run an Intelligence Server against an Oracle 12c metadata in Strategy 10.x running on Linux.
 
DESCRIPTION
In Strategy 10.x when upgrading an Oracle 12c metadata or configuring an Intelligence Server against the same metadata the error "Metadata is in an inconsistent state: Unrecognized ID '' found in table 'DSSMDOBJDEF2' column 'OBJECT_ID'" will be seen. This error will not be seen when using an Oracle 11gR2 metadata.
 
CAUSE
This issue occurs when the wrong IANAAppCodePage value is set in an Oracle DSN when connecting to an Oracle 12c database from Linux. This issue does not happen with Oracle 11g DSNs. With a 12c database the codepage setting must match the character set used in the database and due to how the DSNs are created this cannot be autodetected requiring it to be manually configured.
 
ACTION
 Follow the steps below to use the correct IANAAppCodePage value:
 

  1. Connect to the Oracle 12c database and run the SQL statement
    
    SELECT value FROM nls_database_parameters WHERE parameter='NLS_CHARACTERSET';

  2. Compare the value returned from the SQL statement with the table found in IANAAppCodePage Values

    For example, "WE8MSWIN1252" corresponds to "WINDOWS_1252" which is IANAAppCodePage value of "2252"
  3. Modify the IANAAppCodePage value for the DSN entry in the odbc.ini file from the default 111 to the correct value determined above
  4. Reconfigure the Iserver and the error should no longer be seen when upgrading or using the environment.

 


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017