Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(2 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

"[DOM_10079] Cannot start service [my_metadata_manager_service] on any node specified for the service. Check the service log and resolve any error listed for the service" when Metadata Manager is unable to start on Informatica 9.1.x
Problem Description

Metadata Manager is unable to start on Informatica 9.1.x, and the following error is displayed:

[DOM_10079] Cannot start service [my_metadata_manager_service] on any node specified for the service. Check the service log and resolve any error listed for the service. Then restart the service.

Cause

When Metadata Manager first starts, the associated Repository Service is checked for the Metadata Load folder. If it is not there or it has an incorrect version, Metadata Manager will import $INFA_HOME/services/MetadataManagerService/mm-etl/MetadataManagerETL.xml.

On some UNIX/Linux environments, this import fails and a core file is found in the same directory.

Solution

To resolve this issue, manually run pmrep on MetadataManagerETL.xml. After this completes successfully, Metadata Manager would start. 

Again, when Metadata Manager is started it will check the associated Integration Service PowerCenter repository for a Metadata Load folder and either create/populate or update it and PowerCenter pmrep is used from the working directory.

The working directory is the Metadata Manager File location/mmetl (defaults to $INFA_HOME/services/MetadataManagerService/mm_files/MM Service Name/mmetl) and this will contain all the import files used.

Example

-bash-3.2$ ls -arlt
total 33372
-rw-rw-r-- 1 infa9 infa9   284037 Jun 22 09:25 pmrep.log
-rw------- 1 infa9 infa9     2896 Jun 22 11:41 pmrep.cnx
-rw-rw-r-- 1 infa9 infa9    51589 Jun 22 11:41 M_HTTPS_FILE_GETTER.XML
-rw-rw-r-- 1 infa9 infa9 17706083 Jun 22 11:41 MetadataManagerETL.xml
-rw-rw-r-- 1 infa9 infa9     1149 Jun 22 09:20 impcntlmap.xml
-rw-rw-r-- 1 infa9 infa9     3536 Jun 22 09:20 impcntl.dtd
-rw-rw-r-- 1 infa9 infa9 16049782 Jun 22 11:41 imm_repo.rep
drwxrwxr-x 5 infa9 infa9     4096 Jun 22 09:25 ..
drwxrwxr-x 2 infa9 infa9     4096 Jun 22 09:20 .

The pmrep command using the above would be pmrep objectimport -i MetadataManagerETL.xml -c impcntlmap.xml -l pmrep.log. 

Errors could be caught in pmrep.log. The above was successful, and had the following last 10 lines:

-bash-3.2$ tail -n 10 pmrep.log
Validating the flow semantics of Worklet WL_TRUNCATE_STAGE...
...flow semantics validation completed with no errors.

Validating tasks of Worklet WL_TRUNCATE_STAGE...
...Worklet WL_TRUNCATE_STAGE tasks validation completed with no errors.

Worklet WL_TRUNCATE_STAGE inserted.
------------------------------------------------------------------------------

724 Processed, 0 Errors, 0 Warnings 

More Information

In this specific case, the users who faced this issue had a core file generated in this directory. It is recommended that you contact Informatica Global Customer Support to confirm the issue.

Applies To
Product: Metadata Manager
Problem Type:
User Type:
Project Phase:
Product Version: Metadata Manager 9.1.0; PowerCenter Advanced Edition 9.1.0
Database:
Operating System:
Other Software: Metadata Manager

Reference
Attachments
Last Modified Date:10/15/2012 2:13 AMID:136201
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)