My Oracle Support Banner

Migration Installation Failure Due To Silentbootstrap Requirement To Authenticate RegistryUser with Database Server (Doc ID 2526967.1)

Last updated on JUNE 23, 2021

Applies to:

Siebel CRM - Version 17.0 [IP2017] to 21.1 [Release V17]
Information in this document applies to any platform.
This is applicable to any supported database platform

Symptoms

When attempting to perform a Migration Installation from IP2016 patchset 19 to IP2017 the SES Migration fails.
The failure happens on the Silentbootstrap execution.

AI/applicationcontainer/logs/localhost_access_log.yyyy-mm-dd.txt file contains the following information:

<IP_ADDRESS> - - [04/Apr/2019:08:15:08 -0500] "POST /siebel/v1.0/cginfo HTTP/1.1" 500 1081
<IP_ADDRESS> - - [04/Apr/2019:08:15:58 -0500] "POST /siebel/v1.0/cginfo HTTP/1.1" 200 33
<IP_ADDRESS> - - [04/Apr/2019:08:16:02 -0500] "POST /siebel/v1.0/cloudgateway/GatewaySecurityProfile HTTP/1.1" 200 985
<IP_ADDRESS> - - [04/Apr/2019:08:16:03 -0500] "POST /siebel/v1.0/cloudgateway/bootstrapCG?mode=migration HTTP/1.1" 401 27

db2diag log file contains the following information:

2019-04-04-13.29.08.553000+000 I58769F484 LEVEL: Warning
PID : 3596 TID : 3548 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SIEBELDB
APPHDL : 0-530
HOSTNAME: <HOSTNAME>
EDUID : 3548 EDUNAME: db2agent (SIEBELDB) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 66 bytes
Password validation for user REGUSER failed with rc = -2146500502

2019-04-04-13.29.08.553000+000 I59255F560 LEVEL: Warning
PID : 3596 TID : 3548 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SIEBELDB
APPHDL : 0-530
HOSTNAME: <HOSTNAME>
EDUID : 3548 EDUNAME: db2agent (SIEBELDB) 0
FUNCTION: DB2 UDB, bsu security, sqlexSlsSystemAuthenticate, probe:150
MESSAGE : Failing connection IP address: <IP_ADDRESS>
DATA #1 : String, 16 bytes
application id:
DATA #2 : String with size, 32 bytes
<IP_ADDRESS>.35839.190404132916


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Have a functional IP2016 patchset 19 installation
2. Execute Migration Installation on SWSE
3. Try to execute Migration Installation on SES by setting registryuser with any arbitrary user that does not exist on the database (step 10)
4. Verify that gtwysrvr/zookeeper/version-2 directory does not get created

Changes

Migration Installation from previous Siebel 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.