You can monitor a resource load run to determine whether it is successful. If a resource load fails, troubleshoot the failure and load the resource again.
I am trying to load a business intelligence or a data modeling resource, but the load fails because of inconsistencies in the model.
If the load fails because of inconsistencies in the model, perform one of the following actions:
Fix the inconsistencies in the model and reload the resources.
In the imm.properties file, change the
MitiValidationLevel
property value from basic to NONE. Restart the Metadata Manager Service and reload the resources.
I am trying to load a resource, but the load fails because Metadata Manager cannot find an IME file.
Check the value of the PowerCenter Integration Service Process property $PMSourceFileDir. Metadata Manager stores transformed metadata for packaged and universal resources in IME files in the
$PMRootDir/SrcFiles
directory. If the $PMSourceFileDir property is not set to
$PMRootDir/SrcFiles
, Metadata Manager cannot find the IME files.
When I try to load a PowerCenter resource where the PowerCenter repository type is IBM DB2, the load fails. I get the following error in the DB2CLI log file: "SQL0101N The statement is too long or complex."
Check the value of the DB2 statement heap size configuration parameter. Increase the STMTHEAP value up to 16,384 pages.
When I try to load a PowerCenter resource where the PowerCenter repository type is IBM DB2, the load fails with deadlocks on the DB2 database.
Check the values of the MAXLOCKS, LOCKLIST, and LOCKTIMEOUT DB2 configuration parameters.
Update the parameters as follows:
MAXLOCKS = 10 per application
LOCKLIST = 16,384 or greater
LOCKTIMEOUT = 60 or greater
When I load a Business Objects, Cognos, or OBIEE resource, Metadata Manager returns an out of memory error.
The Metadata Manager Agent can return this error if you extract a large amount of metadata from the metadata source. If you receive this error, perform either of the following actions:
Reduce the number of worker threads that the Metadata Manager Agent uses to extract metadata asynchronously from the metadata source. You can view and update the number of worker threads in the configuration properties when you create or edit a resource. If the number of worker threads is not set in the configuration properties, you can view the number of worker threads that the Metadata Manager Agent uses in the following log file:
Try to increase the maximum Java Virtual Machine (JVM) heap size that the Metadata Manger Agent can allocate. On 64-bit Windows, the Metadata Manager Agent can run a 64-bit JVM with a virtually unlimited maximum JVM heap size. On 32-bit Windows, configure multiple resources, each with a subset of the total models that you want to extract from the metadata source.
I am assigned the Load Resources privilege for the Metadata Manager Service, but I get an "insufficient privileges" error when I try to load Business Glossary resources.
To load Business Glossary resources, the Load Resource, Manage Resource, and View Model privileges are required. You also need write permission on any business glossary resource that you want to load.
When I load a Cloudera Navigator resource, Metadata Manager returns an out of memory error.
To load Cloudera Navigator resources, the maximum heap size for the Metadata Manager Service must be at least 4096 MB (4 GB). Some Cloudera distributions require an even larger heap size. To increase the maximum heap size, open the Administrator tool, select the Metadata Manager Service, and increase the value of the