cancel
Showing results for 
Search instead for 
Did you mean: 

NZDM service startup failed!# After system refresh of BW(ABAP_JAVA)

Former Member
0 Kudos

Hi All,

After System Refresh, Java in DualStack is not starting , from theApplication Log following is the log that i am getting"FATAL: Critical shutdown with exit code [2150] was requested due to[ASJava cannot be started; core service [tc~lm~nzdm~crrsrv] failed tostart".


We have recovered the ABAP instance with the restore and recovery method and now we have take the Java export of Production and Imported the same in the

quality system. All steps finished successfully, still Java is not coming up giving the above error.


We have gone through SAP NOTe# 1713021, but not much help.Please help.


Regards,

Vicky


Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

There are 2 SAP notes speaking about this issue.

1825684 - nZDM: No data maintained for remote database connection

1713021 - nZDM/Portal: Core service [tc~lm~nzdm~crrsrv] does not start

I believe you have gone through both of them. (Not sure whether they are relevant in your case)

As you have done a system copy did you do an export and import of the Java schema ?

Regards

RB

Former Member
0 Kudos

Hi Reagan,

Thanks a lot for your time. Note number 1713021 is exactly the issue we are facing. As guided in the note we have raised an OSS with SAP and awaiting their revert.

Yes, we had done the export and import of the Java schema.

Regards,
Vikcy

Former Member
0 Kudos

Hi All,

The issue is fixed, Somehow the keyphrase value in the secstore got changes during the import.

As a result despite all the 25 phases in the import in the source system import got completed ,Java was not coming up.

Later we were left with two options(as per SAP OSS we had raised)

"1- You will need to start the system copy procedure from scratchand make sure that exporting the data is the first thing that you willdo. This is because now the ume service cannot start because it cannot decrypt its properties. Unfortuantelly this can not be fixed witha redeployment of the UME. In this case it seems that the data hasbeen exported with a different keyprase which has been changed afterthe export of the data


.2- Send the secstore files from the source and from the target systems and the possible values of the keyphrases. With this I'll forward thiscase to developer team."

Since option 1 would required us to restore the entire DB that would have taken 30 hours so we went with option 2...i.e to share the secstore files. Below is  the reply we got from SAP

" we checked the keyphrases of the securestore SOURCE and securestoreTARGET you have sent me and they are NOT equal. Have you been askedduring then procedure to specify a keyphrase?I have re-encrypted the BI7 SecStore with the keyphrase from BP7 (thesource system). Exchanging SecStore files should be done carefullybecause these files are equal to passwords".


The moment we exchanged the the old one from the correct encrypted one  Java too started in BI(ABAP+JAVA)


Regards,

Vicky



Answers (0)