cancel
Showing results for 
Search instead for 
Did you mean: 

NW_GetSidNoProfiles was executed with status ERROR

tj_wilkinson2
Participant
0 Kudos

Hello,

On target system of system copy I get the following error when trying to

use the SID of the system I'm refreshing (SMP).

ERROR 2007-04-09 13:11:39

FCO-00011 The step getSID with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|getSID was executed with status ERROR .

I tried deleting SMP prior to the refresh with dltr3sys. This does not work - even with the suggested patch levels I found. I had to manually remove everything to do with the instance, but it appears something is still there if this installation fails.

If anyone has any ideas on how to completely clean up the old system so I can reinstall it, I would appreciate it. Thanks much.

~TJ

Accepted Solutions (0)

Answers (5)

Answers (5)

tj_wilkinson2
Participant
0 Kudos

Thanks to all who provided input. SAP helped be resolve this. The problem - if anyone's interested - the file '/usr/sap/sapservices' contained an entry for my SID. I had to remove that and then things worked and I was able to reuse the SID.

~TJ

Former Member
0 Kudos

Hello TJ,

this line

DeleteSIDnnUser: Error deleting user SMP45 of system SMP on host .

does not look good to me. It sounds as if it cannot determine the hostname.

DeleteSIDnnUser: Error deleting user SMP45 of system SMP on host <hostname>. (<hostname> being empty)

I don't know the reason for this and I'm not sure it can be circumvented.

Try DLTUSRPRF SMP45 manually, then re-do the DLTR3SYS call.

Best regards, Barbara

Former Member
0 Kudos

Hello TJ,

StopInstance: Program R3INLPGM does not exist (ILE).

This is the problem with removing stuff manually .. Please crtr3sys (at least) and apply a kernel to the system so that r3sid400\r3inlpgm exists again.

Then try to remove the instances and the system again.

Best regards, Barbara

tj_wilkinson2
Participant
0 Kudos

I applied the kernel, and am no longer getting that error, but it still seems to have problems deleting the users. I even patched the dltsapusr before this run. Thank you.

~TJ

DLTR3INST SID(SMP) INST(45)

Checking input parameters...

Deleting instance 45 of system SMP...

Found existing system SMP on localhost(USALJAVA).

Deleting objects of instance 45 of system SMP...

Checking input parameters...

Stopping sapstartsrv for instance 45 of system SMP...

Command for starting system Job is SBMJOB CMD(CALL PGM(R3INLPGM)

PARM('/usr/sap/SMP/SYS/exe/run/sapcontrol' '-prot' 'NI_HTTP' '-nr' '45'

'-function' 'StopService')) JOB(SAPSTRSRV) JOBD(R3SMP400/R3_45)

JOBQ(QSYS/QUSRNOMAX) USER(SMPadm) SYSLIBL(SYSVAL) CURLIB(CRTDFT)

INLLIBL(R3SMP400 QTEMP QGPL) SRTSEQ(HEX) CCSID(500) CPYENVVAR(YES)

ALWMLTTHD(*YES)

Job 055771/SMPADM/SAPSTRSRV submitted to job queue QUSRNOMAX in library

QSYS.

sapstartsrv for instance 45 of system SMP stopped.

Object changed.

Object changed.

Object changed.

Object changed.

Object changed.

Deleting directory "/usr/sap/SMP/DVEBMGS45/j2ee"...

Deleting directory "/usr/sap/SMP/DVEBMGS45/SDM"...

Deleting objects of instance 45 of system SMP...

Deleting directory "/usr/sap/SMP/DVEBMGS45"...

Deleting objects of instance 45 of system SMP...

Name matching pattern not found.

Name matching pattern not found.

No subsystem R3_45 active.

Object R3_45 in R3SMP400 type *SBSD deleted.

Object R3_45 in R3SMP400 type *CLS deleted.

0 entries deleted. 0 entries not deleted from job queue R3_45 in library

R3SMP400.

Object R3_45 in R3SMP400 type *JOBQ deleted.

Object R3_45 in R3SMP400 type *JOBD deleted.

Library R3WRK45 deleted.

Deleting instance user SMP45 on all system hosts...

0 files deleted. 0 files not deleted.

Ownership of object SMP45 in QUSRSYS type *MSGQ changed.

0 changes made to distribution lists.

Object SMP45 in QSYS type *USRPRF deleted.

Object SMP45 in QUSRSYS type *MSGQ deleted. Deleted instance user SMP45 locally.

DeleteSIDnnUser: Error deleting user SMP45 of system SMP on host .

DeleteInstObjects: Error deleting instance user of instance 45 in system

SMP.

DltR3Inst: Error deleting instance objects of instance 45 of system SMP.

DLTR3INST: Failed to delete instance 45 of system SMP.

Errors occurred in command.

Errors occurred in command.

Former Member
0 Kudos

Hello TJ,

to delete the system, I suggest that you try to bring your current system (that you want to delete) into a state where DLTR3SYS and DLTR3INST can be executed successfully.

Use those tools directly as QSECOFR-like user in green screen, SAPinst does not do much else if you use the Uninstall routine.

So if DLTR3SYS/INST claim they cannot run, try reconstructing the system with CRTR3INST/CRTR3SYS (to get a default environment) on exactly the data you want to delete. Use the same SID and inst numbers that you want to delete.

Ignore messages like "... already exists". Then run DLTR3INST on all instances and finish with DLTR3SYS. If you get error messages, please copy and paste them to the forum.

Best regards, Barbara

tj_wilkinson2
Participant
0 Kudos

Barbara,

Thank you for your response. I was able to crtr3sys and crtr3inst without any problem, but when I tried to dltr3inst, I get the log below.

I see that there's an error in the DLTSAPUSR, but it's not one of the ones needing patched according to note 936965 for a 700 kernel.

If anyone has any additional suggestions, I would much appreciate it. Thank you.

~TJ

DLTR3INST SID(SMP) INST(45) DLTHOME(*NO)

Checking input parameters...

Deleting instance 45 of system SMP...

Found existing system SMP on localhost(USALJAVA).

Deleting objects of instance 45 of system SMP...

Checking input parameters...

StopInstance: Program R3INLPGM does not exist (ILE).

O4STPSAP: Stopping instance 45 of system SMP on host USALJAVA failed.

Errors occurred in command.

Errors occurred in command.

Object changed.

Object changed.

Object changed.

Object changed.

Object changed.

Deleting objects of instance 45 of system SMP...

Deleting directory "/usr/sap/SMP/SCS45"...

Deleting objects of instance 45 of system SMP...

Name matching pattern not found.

Name matching pattern not found.

No subsystem R3_45 active.

Object R3_45 in R3SMP400 type *SBSD deleted.

Object R3_45 in R3SMP400 type *CLS deleted.

0 entries deleted. 0 entries not deleted from job queue R3_45 in library

R3SMP400.

Object R3_45 in R3SMP400 type *JOBQ deleted.

Object R3_45 in R3SMP400 type *JOBD deleted.

Library R3WRK45 deleted.

Deleting instance user SMP45 on all system hosts...

Keyword DLTHOME not valid for this command.

Error found on DLTSAPUSR command.

Errors occurred in command.

Signal SIGABRT raised (abnormal termination).

Application error. C2M1601 unmonitored by QC2UTIL1 at statement

0000000006, instruction X'0000'.

Errors occurred in command.

tj_wilkinson2
Participant
0 Kudos

If I try to clean it up with the uninstall from the master CD (picking no profiles since they're already gone) I get:

ERROR 2007-04-09 14:09:20

FCO-00011 The step getSID with step key |NW_Uninstall|ind|ind|ind|ind|0|0|NW_GetSidMaybeProfiles|ind|ind|ind|ind|1|0|NW_GetSidNoProfiles|ind|ind|ind|ind|2|0|getSID was executed with status ERROR .

Former Member
0 Kudos

Hi TJ,

if I get you right, you do have a problem with a homo-copy after a wrong DLTR3SYS/DLTR3INST ...

As you can imagine, that if the first crashes, the second is pretty in danger, I would say "all is ok" here

I would get rid of the homo-copy and delete first.

You should get rid of al libs with R3sid* and have a look in the IFS for /usr/sap/sid and /sapmnt/sid. Finally, I would delete the sid* and sapsid* users with leaving their objects and putting them to r3owner. If you did this, I would start the homo-copy from scratch ...

btw:

Did you patch the ISERPACKx ?

Did you check for a new copy template as note attachment ?

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

tj_wilkinson2
Participant
0 Kudos

Volker,

Thank you for the response. I had tried all you suggested except for looking for ISERPACK and new control file. I'm using the SR1 release of Solution Manager media, which I believe doesn't need the ISERPACK. At least it didn't when I downloaded it and did the installations initially.

~TJ