Error in phase MAIN_SHADOW/START_SHDI_FIRST (Upgrade EHP)

[Former Member]

Hi experts,

I try to upgrade my productive system from ECC 6.0 to ECC 6.0 EHP7; but I have a problem in the phase start_shdi_first, it can not start and the disp+work process appear with SELW status.

The error that appear in dev_w0 is:

B  DBI: init TBI BUFFER (data):  start=7000000a0501000  length=14149888  end=7000000a127f900

B  dbprotocol: table logging switched off for all clients

B  db_tbi_install(): tbi_init_singletons() -> rc = false

B  db_tbiinit failed

M  *** ERROR => ThrtDatabaseEnvInit: db_init failed (4) [thrtDatabase 48]

M  *** ERROR => ThrtDatabaseEnvInit failed (4) [thxxext.c    181]

M  *** ERROR => ThCallHooks: event handler ThrtStartup for event CREATE_SHM failed (4) [thSos.c      2080]

M  *** ERROR => ThIPCInit: hook failed [thxxhead.c   1290]

M  ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c   1028]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: ThIPCInit (step TH_INIT, thRc ERROR-CORE-INIT_FAILED, action STOP_WP, level 1) [thxxhead.c   2149]

My system is AS/400 with more than 100GB RAM; so it is not problem of memory.

I tried to pacth the kernel, but I have the same problem.

What could be the reason?

Thanks in advance,

Regards,

[former_member188883 · Accepted solution]

Hi Victor,

It looks to be a problem with shared memory segments.

ERROR => ThCallHooks: event handler ThrtStartup for event CREATE_SHM failed (4) [thSos.c      2080]

Can you open the Unix shell on IBMi simulator and perform cleanipc <nr> shadow instance number.

If possible take a restart of Production instance and clear ipc segments.

Hope this helps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi,

My system have more than 100GB RAM, I think it is not problem of memory.

I think the problem is:

1931675 - IP multicast configuration for dispatcher wakeup mechanism

IBM i (OS/400) Operating system:

• All currently supported operating system (OS) releases support IP multicast.
• In a standard network configuration, usually no additional configuration steps are needed to enable a multicast environment.
• Routing considerations:

Multicast traffic uses the default route if not specified otherwise. You can configure a special multicast default route.The default route can be configured by the following command (this was usually already done when the IBM i server was set up, so you should not have to do that):ADDTCPRTE RTEDEST(*DFTROUTE) SUBNETMASK(*NONE) NEXTHOP(<Gateway IP>) BINDIFC(*NONE) TEXT('Default Route')A default multicast route that can be different to the standard default route can be configured with this command:ADDTCPRTE RTEDEST(*DFTMCAST) SUBNETMASK(*NONE) NEXTHOP(<Local IP>) BINDIFC(*NONE) TEXT('Default Multicast Route')

• It has to be ensured, that multicast datagrams are not blocked by firewall settings.

If you have configured a local IBM i firewall, i.e. IP packet rules are active, then you have to ensure that the desired multicast traffic is explicitly allowed.

Please follow the link to the IBM i infocenter for more information about packet rules:

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzajb/rzajbrzajb0ippacketsecuritysd.htm

I have two virtual IPs and one physical IP; what command I should execute it?

Thanks in advance,

regards.

[Reagan · Accepted solution]

Provide the developer traces of the shadow system.

Regards

RB

[Former Member · Accepted solution]

The error appear in the first post.

B  DBI: init TBI BUFFER (data):  start=7000000a0501000  length=14149888  end=7000000a127f900

B  dbprotocol: table logging switched off for all clients

B  db_tbi_install(): tbi_init_singletons() -> rc = false

B  db_tbiinit failed

M  *** ERROR => ThrtDatabaseEnvInit: db_init failed (4) [thrtDatabase 48]

M  *** ERROR => ThrtDatabaseEnvInit failed (4) [thxxext.c    181]

M  *** ERROR => ThCallHooks: event handler ThrtStartup for event CREATE_SHM failed (4) [thSos.c      2080]

M  *** ERROR => ThIPCInit: hook failed [thxxhead.c   1290]

M  ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c   1028]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: ThIPCInit (step TH_INIT, thRc ERROR-CORE-INIT_FAILED, action STOP_WP, level 1) [thxxhead.c   2149]

The before SAP Note describe my problem, but I do not know what I have to execute.

regards,

[Reagan · Accepted solution]

I am not sure how you concluded that the SAP note 1931675 is addressing the issue you are facing.

If you are sure then refer to this SAP note and check whether you see error messages as described in the SAP note 1932555 - Dispatcher startup issue with SAP Kernel 740

Regards

RB

[Former Member · Accepted solution]

I think it is more possible, because here appear the same problem and it was the solution:

[Reagan · Accepted solution]

In that case the solution part on the SAP note 1931675 - IP multicast configuration for dispatcher wakeup mechanism gives you the commands to be executed on the IBM i systems.

Have you tried that ?

Regards

RB

[Former Member · Accepted solution]

Hi,

In my before post I wrote the part of the note where appear for AS/400, but I do not know how write the command.

Multicast traffic uses the default route if not specified otherwise. You can configure a special multicast default route.The default route can be configured by the following command (this was usually already done when the IBM i server was set up, so you should not have to do that):ADDTCPRTE RTEDEST(*DFTROUTE) SUBNETMASK(*NONE) NEXTHOP(<Gateway IP>) BINDIFC(*NONE) TEXT('Default Route')A default multicast route that can be different to the standard default route can be configured with this command:ADDTCPRTE RTEDEST(*DFTMCAST) SUBNETMASK(*NONE) NEXTHOP(<Local IP>) BINDIFC(*NONE) TEXT('Default Multicast Route')

I have two virtual IPs and one physical IP; what command I should execute it?

Thanks in advance,

regards,

[Reagan · Accepted solution]

Hello

Unfortunately I have no experience with IBM i systems, so I cannot guide you here.

I would consult this with an IBM i system specialist.

Regards

RB

[Former Member · Accepted solution]

Solved with applying multicast.

[Former Member · Accepted solution]

Can you please let us know by which commands/procedure this issue has been solved.

Whats the multicast configuration has been done.

[Former Member · Accepted solution]

Hi,

I follow the SAP NOTE 1931675 - IP multicast configuration for dispatcher wakeup mechanism