My Oracle Support Banner

PostinstallDBSetup Crashes in Workflow Upgrade Step Due to Insufficient Memory Allocation (Doc ID 2984358.1)

Last updated on OCTOBER 31, 2023

Applies to:

Siebel CRM - Version 22.12 and later
Oracle Solaris on SPARC (64-bit)

Symptoms


While updating Siebel environment ( running on Solaris) from 20.4 to 23.1 version, the PostInstallDbSetup utility run  is taking more than 16 hours and sometimes crashing. 

The PostInstallDbSetup_timestamp.log shows that the utility is erroring out during Workflow Migration step ( log is incomplete because the utility never completes):

Mon Feb 6,2023 [15:52:36] : Completed Update TYPE_CD in S_WFA_DPLOY_DEF
Mon Feb 6,2023 [15:52:36] : Running siebdevcli.exe
Mon Feb 6,2023 [15:52:36] : /app/siebel/siebel_ses/siebsrvr/bin/siebdevcli /c /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/SeedSchemaManifest/PostInstallDBSetup.cfg /l ENU /u sadmin /p ****** /d "VSKSIB02_ES_DSN" /WorkflowUpgrade wfmigrationdr
Mon Feb 6,2023 [15:52:36] : Run row_id.sql against VSKSIB02_ES_DSN
Mon Feb 6,2023 [15:52:36] : /app/siebel/siebel_ses/siebsrvr/bin/odbcsql /u siebel /p ****** /s "VSKSIB02_ES_DSN" /separator / /a /v /c rem /e /h /o /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/row_id.out /l /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/row_id.log /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/row_id.sql /f CP1252
Mon Feb 6,2023 [15:52:37] : Run create_process_WorkflowUpgrade.sql against VSKSIB02_ES_DSN
Mon Feb 6,2023 [15:52:37] : /app/siebel/siebel_ses/siebsrvr/bin/odbcsql /u sadmin /p ****** /s "VSKSIB02_ES_DSN" /separator / /a /v /c rem /e /h /o /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/create_process_WorkflowUpgrade.out /l /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/create_process_WorkflowUpgrade.log /app/siebel/siebel_ses/siebsrvr/log/PostInstallDBSetup_2023-02-06_15-23-35/create_process_WorkflowUpgrade.sql /f CP1252

 

Siebdevcli logs show:

GenericLog GenericError 1 0000000263e12c4a:0 2023-02-07 08:46:40 Setting up and Writing ... Workflow Process
ObjMgrLog Error 1 0000000263e12c4a:0 2023-02-07 08:46:40 (workspacemgr.cpp (2936)) SBL-DAT-60289: Implicit Edit Failed. The user who has created the workspace is only allowed to edit it.
GenericLog GenericError 1 0000000263e12c4a:0 2023-02-07 08:46:41 Finished Compiling Objtype: Workflow Process, SRF Load: 25s, Write: 1s, Total: 0:26m
GenericLog GenericError 1 0000000263e12c4a:0 2023-02-07 08:46:41 Finished Compiling Streams
GenericLog GenericError 1 0000000263e12c4a:0 2023-02-07 08:46:41 Processing Language 'ENU'.....
GenericLog GenericError 1 0000000263e12c4a:0 2023-02-07 08:46:48 Finished Setting Up Streams
ObjMgrBusCompLog Error 1 0000000263e12c4a:0 2023-02-07 08:47:06 (oracon.cpp (5050)) SBL-DBC-00111: An error has occurred writing to a record.

Please continue or ask your systems administrator to check your application configuration if the problem persists.
ObjMgrBusCompLog Error 1 0000000263e12c4a:0 2023-02-07 08:47:06 (oracon.cpp (1255)) SBL-DAT-00381: A record that contains identical values to the record you have created already exists.

 The customer environment had 28 integration workspaces, each with more than 100 workflow versions.

The truss output shows return code Err#12 ENOMEM ( the maximum possible size of a data segment (compiled into the system) would be exceeded; insufficient space exists in the swap area to support the
expansion; or the new break value would extend into an area of the address space defined by some previously established mapping).

8246/1: 15715.3985 read(31, " q\0 T\0 G\0 l\0 u\0 Z\0".., 8111) = 8111
8246/1: 15715.3989 read(31, " K\0 j\0 M\0 5\0 M\0 C\0".., 8111) = 8111
8246/1: 15715.3993 read(31, " H\0 R\0 z\0 M\0 S\0 o\0".., 8111) = 8111
8246/1: 15715.3997 read(31, " l\0 v\0 d\0 X\0 Q\0 K\0".., 8111) = 8111
8246/1: 15715.4001 read(31, " v\0 R\0 m\0 9\0 y\0 Q\0".., 8111) = 8111
8246/1: 15715.4004 read(31, " T\0 m\0 F\0 t\0 Z\0 Q\0".., 8111) = 7524
8246/1: 15715.4091 brk(0x4FEA0410) = 0x00000000
8246/1: 15715.4092 brk(0x4FF50410) = 0x00000000
8246/1: 15715.4102 write(34, " G e n e r i c L o g\t G".., 102) = 102
8246/1: 15715.4109 brk(0x4FF50410) = 0x00000000
8246/1: 15715.4110 brk(0x50000410) = 0x00000000
8246/1: 15715.4133 brk(0x50000410) = 0x00000000
8246/1: 15715.4134 brk(0x500AE410) Err#12 ENOMEM
8246/1: 15715.4135 Incurred fault #6, FLTBOUNDS %pc = 0xFF109774
8246/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000004
8246/1: 15715.4136 Received signal #11, SIGSEGV [caught]
8246/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000004
8246/1: 15715.4137 lwp_sigmask(SIG_SETMASK, 0x0003962B, 0x00000000, 0x00000000, 0x00000000) = 0xFFBFFEFF [0xFFFFFFFF]
8246/1: 15715.4140 open("T202305291740_P008246.fdr", O_WRONLY|O_APPEND|O_CREAT, 0664) = 38
8246/1: 15715.4149 write(38, " F D R C V 2 0 0 6 0".., 500068) = 500068

 The (relevant part of) address mapping of the process:

core 'core' of 8246: /app/siebel/siebel_ses/siebsrvr/bin/siebdevcli /c /app/siebel/siebel_s
00006000 8K r-x---- /lib/librt.so.1
0000A000 16K r-x---- /lib/libpthread.so.1
00010000 384K r-x---- /app/siebel/siebel_ses/siebsrvr/bin/siebdevcli
00070000 48K r-x---- /app/siebel/siebel_ses/siebsrvr/bin/siebdevcli
00080000 16K r-x---- /lib/libthread.so.1
00086000 8K r-x---- /lib/libxnet.so.1
0008A000 40K rwx---- /app/siebel/siebel_ses/siebsrvr/bin/siebdevcli
00094000 48K rwx---- [ anon ]
000A0000 3456K rwx---- [ anon ]
00400000 1306624K rwx---- [ anon ]
50000000 8K rwx---- [ heap ]
50020000 2048K r-x---- /app/siebel/siebel_ses/siebsrvr/lib/libsscactbc.so
50220000 40K r-x---- /app/siebel/siebel_ses/siebsrvr/lib/libsscactbc.so
50238000 32K rwx---- /app/siebel/siebel_ses/siebsrvr/lib/libsscactbc.so
50250000 256K r-x---- /app/siebel/siebel_ses/siebsrvr/lib/libsscfxc.so
50290000 8K r-x---- /app/siebel/siebel_ses/siebsrvr/lib/libsscfxc.so
502A0000 16K rwx---- /app/siebel/siebel_ses/siebsrvr/lib/libsscfxc.so
[..]

 

Changes

Update installation of 23.1 Siebel on 20.4 older version. 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.