Troubleshooting
Problem
Information Analyzer issues when multiple data connections are associated with a logical database in IMAM or when multiple logical databases are imported in IMAM using the same data connection. These result in IA jobs that fail because they can't connect to the source database.
Cause
Scenario 1: Multiple data connections are associated with a logical database in IMAM
Using Information Server Metadata Asset Manager (IMAM), if one imports from the same physical source database using multiple data connections such that the imported data source metadata assets are merged into the same host/logical database identity in IMAM, this will result in multiple data connections being associated with the database. This is the default express import behavior when the same host name and logical database name for the same physical source database are specified for multiple imports with different data connections.
EXAMPLE
1) Create an odbc dsn for a text file odbc data source, TXT1.
2) Import the TXT1 data source. Note the host and database name for the TXT1 data source.
3) Create an odbc dsn for a second text file odbc data source, TXT2.
4) Import the TXT2 data source. However, when you import TXT2, specify the same host and database name such that when the import is done the data source will be merged under the same host and database as TXT1. The end result is that the database will have to two associated data connections (see IMAM>Repository Management>Browse Implemented Data Sources>Browse Assets>[selected database]>Details).
In such a scenario, Information Analyzer (IA) uses the first data connection associated with the database when running analysis jobs, even if the source column selected for the analysis job is associated with the second data connection. This will result in an IA analysis job failure.
Scenario 2: Multiple logical databases are imported in IMAM using the same data connection
Using IMAM, if one imports multiple logical databases from the same data connection (such as when users want to have multiple logical databases to represent different schemas in the same physical database), the data connection reference for the previously imported logical database is lost when the same data connection is used to import a different logical database.
EXAMPLE
1) In one IMAM import area, import a specific schema from a physical database using a specific data connection. Provide a custom logical database name when completing and sharing the metadata import.
2) In a different IMAM import area, import a different schema from the same physical database using the same data connection as in the previous step. Provide a DIFFERENT custom logical database name when completing and sharing the metadata import.
In such a scenario, the data connection reference for the logical database (imported in step 1), is no longer displayed when viewing the database details in IMAM>Repository Management>Browse Implemented Data Sources>Browse Assets>[selected database]>Details. This will result in an IA analysis job failure.
Resolving The Problem
For both scenarios, the workaround is to import the data sources such that each one has its own unique host/logical database name identity (i.e, use one unique data connection per logical database).
For scenario 1 (described above), the user would import to two different logical database names using two different data connections.
For scenario 2 (described above), the workaround is to use the same data connection and same logical database name if the user wants to use separate import areas for multiple schemas under the same physical database when importing their metadata.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21989678