CDATA[ERROR] gone with SWPM

[Former Member]

Hi experts,

It seems that with SWPM the good old tip of changing [CDATA[ERROR]] to [CDATA[OK]] to bypass an error is not available anymore.

On a failed step I was not able to find a [CDATA[ERROR]] tag in the keydb.xml file.

Did you notice the same behavior, does anyone find what is the new tag for error ?

Best regards

[former_member182307 · Accepted solution]

You' re right. Unfortunately, the missing CDATA[ERROR] doen't help but you' re still able to identify the failing step this way :

In the sapinst.log you should be able to find the error message with the appropriate failing step.

It should be something looking like this :

|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|users|0|createAccounts

In this example the failing step key is createAccounts.

You then have a look at the keydb.xml file , looking for this stepkey :

<strval><![CDATA[|NW_ABAP_CI|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|users|0|createAccounts]]>

        </strval>

      </fld>

      <fld name="STATUS">

<strval><![CDATA[ ]]>

        </strval>

      </fld>

Here the CDATA field is empty instead of bieng in ERROR.

You replace the CDATA for this stepkey with :

<strval><![CDATA[OK]]>

Save the keydb.xml, restart the sapinst, and there you are !

HTH

Best regards,

Steve.

[ACE-SAP · Accepted solution]

In fact the CDATA[ERROR] has not gone, it has just move to a different file.

I get an error on a system copy with latest SWPM (so many bugs with this tool !)

In the controllerKdbClient.dmp file I found my CDATA[ERROR]

<strval><![CDATA[|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|onehost|0|NW_System|ind|ind|ind|ind|system|0|createSystemDirectories]]>

        </strval>

      </fld>

      <fld name="STATUS">

        <properties>

          <property name ="USED_HOSTNAME" value ="my_host_name" />

        </properties>

        <strval><![CDATA[ERROR]]>

        </strval>

      </fld>

      <fld name="STOP_BEFORE">

        <strval><![CDATA[]]>

        </strval>

      </fld>

      <fld name="STOP_AFTER">

        <strval><![CDATA[]]>

        </strval>

      </fld>

      <fld name="STATE_SET_BY_STEP_STATE_EDITOR">

        <strval><![CDATA[]]>

        </strval>

      </fld>

    </row>

  </table>

Using Steve advice I was able to skip the step... just for fun because I did not help with the problem I have.

Thank you very much Steve !

[Former Member]

Hello Guys,

why not use an parameter SAPINST_USE_STEPSTATE=true when starting SWPM here you can skip any implementation step?

Regards

Stan

[ACE-SAP]

Hello Stanislav,

thank you for the information, I've never heard about that option, did not find any reference to it, and it is not recognized by sapinst either...

Where did you get that option from ?

Regards

Program is starting... Please wait!

WARNING [iaxxcprpmg.cpp:374]

CIaPropertyManager::checkIfPropertySupported()

Unknown property SAPINST_USE_STEPSTATE

SAPinst build information:

--------------------------

abi version : 722

make variant: 720_REL

build : 1426667

compile time: Jul 16 2013 17:44:16

[ACE-SAP]

Just getting back on this old thread to link it with Tom Cenens's blog that provide some explanation on the SAPINST_USE_STEPSTATE=true ...

The step state editor is included when you run SAPinst with parameter SAPINST_SET_STEPSTATE=true. The editor itself pops up after the SAPinst summary screen and allows you to edit the steps that will run in a graphical way . In the above example, I skipped all the steps that belong to "Create and load database" as you can see in the screenshot (the small "skip" icon is visible there) to avoid the data load which I didn't want to run anymore.

[ACE-SAP]

Hello

I'm facing the same problem.

Did you find a way to force the status of a failing step ?

Regards

[former_member182307]

Hello,

I' ve noticed this.

I recently had to skip a step in order to perform a system copy ( it was about creating the SAP OS users which I did manually ) .

Then in my case, i found out the failing step key in the sapinst log file ( something like createUsersDo in my case ) .

The correspondig CDATA key was empty.

I put CDATA[OK] ( in the keydb.xml file ), the "usual" way. Saved the file, restart the sapinst and the step was skipped .

Best regards.

Steve.

[ACE-SAP]

Hello Steve,

Thanks a lot for the information.

The problem is that it's not that easy to identify the CDATA key that match the failing step.

Searching for [CDATA[ERROR]] was really easy...

I do not feel it is a change that helps ;-(

Regards