Master database creation failed for SAP ASE 16.0 SP03 PL10 in SUSE Linux 15.5

[rishen-bhowmik]

Hi,

I'm trying to create new SAP ASE server in SUSE Linux 15.5 (AWS EC2 instance) manually. Doing fresh installation.

While installing(command:  $SYBASE/$SYBASE_ASE/bin/srvbuildres -r $SetupDir/${DSQUERY}.rs) ASE 16.0 SP03 PL10 in "SUSE Linux Enterprise Server 15 SP5", master device installation is not completing.

In log I can see below error.

What is the issue? Am i missing something (e.g. any library...)

It is and AWS EC2 instance. Log snippet:

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

00:0000:00000:00000:2025/01/23 09:09:37.16 kernel  Loaded encryption provider CommonCryptoLib 8.5.21 (), CryptoKernel version 8.5.21.
00:0000:00000:00000:2025/01/23 09:09:37.16 kernel  INFORMATION: The FIPS Certified Crypto Kernel is not enabled.
00:0000:00000:00000:2025/01/23 09:09:37.16 kernel  Begin processing to generate RSA keypair.
00:0000:00000:00000:2025/01/23 09:09:37.19 kernel  Completed processing to generate RSA keypair.
00:0006:00000:00000:2025/01/23 09:09:37.19 kernel  ASE - Dynamic Pluggable Component Interface is disabled
00:0006:00000:00000:2025/01/23 09:09:37.19 kernel  Thread 6 (LWP 2299) of Threadpool syb_default_pool online as engine 0
00:0006:00000:00000:2025/01/23 09:09:37.19 kernel  bucket manager consolidator online
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  Current process (0x30002) infected with signal 11 (SIGSEGV)
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  Current Process is running on Engine 0
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  server is using elf symbols for stack decoding (125635 symbols found)
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  Address 0x0x00007f7690089410 (), siginfo (code, address) = (2, 0x0x00007f7690089410)
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  **** Saved signal context (0x0x0000000148502dc0): ****
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  uc_flags: 0x7, uc_link: 0x(nil)
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  uc_sigmask: 0x7bfbf037 0xb 0x2 0x90089410
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  uc_stack: ss_sp: 0x(nil), ss_size: 0x0, ss_flags: 0x2
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  General Registers (uc_mcontext.gregs):
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       PC : 0x00007f7690089410 ()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel          RAX : 0x00007f7690089410  RBX : 0x00007f769000c3b0
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel          RCX : 0x0000000000000003  RDX : 0x00007f7690143b00
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       RBP : 0x0000000148503e90  RSP : 0x0000000148503348
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       R8  : 0x0000000000000002  R9  : (nil)
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       R10 : 0x0000000000000001  R11 : 0x00007f76b0defaae
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       R12 : 0x00007f7690089410  R13 : 0x00007f76900022c0
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       R14 : 0x00000001485038d0  R15 : 0x00000001485038c0
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       RDI : 0x00007f76b16d55c0  RSI : 0x00007f7690093d70
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       RIP : 0x00007f7690089410  CSGSFS : 0x002b000000000033
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       TRAPNO : 0x000000000000000e  ERR : 0x0000000000000015
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel       EFL : 0x0000000000010202
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  **** end of signal context ****
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x000000000156418a pcstkwalk+0x487()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x0000000001563b32 ucstkgentrace+0x212()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x0000000001560272 ucbacktrace+0x54()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x000000000182870c terminate_process+0x1a8c()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x0000000001591d1a kisignal+0x87e()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x00007f7690089410 ()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x00000000021f931b Snap::Validate()+0x3b()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x000000000186381d SnapValidation+0xfd()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  pc: 0x00000000008d8cc1 dsinit+0x1841()
00:0006:00000:00000:2025/01/23 09:09:37.21 kernel  end of stack trace, kernel service process: kpid 196610
00:0005:00000:00000:2025/01/23 09:10:02.09 kernel  Adaptive Server had 28634 major and 5551 minor page faults since boot, and 28634 major and 5551 minor page faults in last 25000 milliseconds.

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

But in another Suse Linux server(not EC2 instance), where the master got created successfully log shows like below:

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

00:0000:00000:00000:2024/07/13 12:35:19.53 kernel  Loaded encryption provider CommonCryptoLib 8.5.21 (), CryptoKernel version 8.5.21.
00:0000:00000:00000:2024/07/13 12:35:19.53 kernel  INFORMATION: The FIPS Certified Crypto Kernel is not enabled.
00:0000:00000:00000:2024/07/13 12:35:19.53 kernel  Begin processing to generate RSA keypair.
00:0000:00000:00000:2024/07/13 12:35:19.54 kernel  Completed processing to generate RSA keypair.
00:0002:00000:00000:2024/07/13 12:35:19.54 kernel  ASE - Dynamic Pluggable Component Interface is disabled
00:0002:00000:00000:2024/07/13 12:35:19.54 kernel  Thread 2 (LWP 8274) of Threadpool syb_default_pool online as engine 0
00:0002:00000:00000:2024/07/13 12:35:19.54 kernel  bucket manager consolidator online
00:0002:00000:00000:2024/07/13 12:35:19.56 server  No active traceflags
00:0002:00000:00002:2024/07/13 12:35:19.57 kernel  libomni1 - Component Integration Services: using 'SAP Client-Library/16.0 SP03 PL10/P-EBF29829/DRV.16.0.03.10/Linux x86_64/Linux 2.6.18-128.el5 x86_64 Native Threads/BUILD1600-027/64bit/OPT/Tue Apr  6 02:40:20 2021'
00:0002:00000:00002:2024/07/13 12:35:19.57 server  Local cache partition number has been auto tuned to 4 for default data cache cache.
00:0002:00000:00002:2024/07/13 12:35:19.89 server  Size of the 16K memory pool for each cachelet (default data cache, total cachelets:4 😞 131072 Kb
00:0002:00000:00002:2024/07/13 12:35:19.98 server  Size of the 2K memory pool for each cachelet (default data cache, total cachelets:4 😞 1434112 Kb
00:0002:00000:00002:2024/07/13 12:35:19.98 server  Size of the 16K memory pool for each cachelet (dbccdb_cache, total cachelets:1 😞 10240 Kb
00:0002:00000:00002:2024/07/13 12:35:19.98 server  Size of the 2K memory pool for each cachelet (dbccdb_cache, total cachelets:1 😞 30720 Kb
00:0002:00000:00002:2024/07/13 12:35:19.98 server  Opening Master Database ...
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Loading ASE's default sort order and character set
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Recovering database 'master'.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Started estimating recovery log boundaries for database 'master'.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Database 'master', checkpoint=(47995, 15), first=(47995, 15), last=(47995, 15).
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Completed estimating recovery log boundaries for database 'master'.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Started ANALYSIS pass for database 'master'.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Completed ANALYSIS pass for database 'master'.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Log contains all committed transactions until 2024/07/13 12:32:37.18 for database master.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Started REDO pass for database 'master'. The total number of log records to process is 1.
00:0002:00000:00002:2024/07/13 12:35:20.00 server  Completed REDO pass for database 'master'.

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

SAP ASE - HADR Enablement 

[ChrisBaker]

According to SAPNote 2489781 and SAPNote 2531326, SuSE 15.5 should be supported.  (There is also a hyperscaler entrypoint SAPNote 2922454 with additional information and links).

However, SAPNote 3018138 also states that the error you may be receiving is fixed in SP03PL11 and higher.  I would suggest moving fully to SP03PL15 (if remaining on SP03 is the current priority) as it is the last PL of SP03.  If the problem is not fixed then, please open a support incident ASAP.

Chris

[Arbi_TM]

Hello, This appears to be a known issue, described here: https://me.sap.com/notes/3018138 the workaround for situation when a new ASE server is built by using srvbuild/srvbuildres: - Move dataserver to be dataserver.bin. - Then create a text filenamed dataserver and put the full path to dataserver.bin -T11889 $@ into this text file. The parameter $@ passes arguments to the wrapper. - After that give the execute permission on the file dataserver. For example: 1. mv $SYBASE/ASE-16_0/bin/dataserver $SYBASE/ASE-16_0/bin/dataserver.bin 2. vi $SYBASE/ASE-16_0/bin/dataserver, input the following text to this file $SYBASE/ASE-16_0/bin/dataserver.bin -T11889 $@ 3. Give the execute permission on the file dataserver. chmod +x dataserver HTH

[Mark_A_Parsons]

Looks like the same problem I ran into a few years back.

While the normal solution is to add traceflag -T11889 to the RUNSERVER file, said solution assumes the dataserver has already been created.

In my case I used the following workaround:

$ cd /opt/sybase/ASE_160_SP03_PL07/ASE-16_0/bin

$ mv dataserver .dataserver

##### create new 'dataserver' file with following contents:

$ cat dataserver
/opt/sybase/ASE_160_SP03_PL07/ASE-16_0/bin/.dataserver -T11889 "$@"

$ chmod 755 dataserver

$ srvbuildres -r your.dataserver.resource.file.rs

Cleanup steps once the dataserver is created:

• mv .dataserver dataserver
• add -T11889 to the ASE's RUNSERVER file

NOTES:

• This was a one-off, quick-n-dirty solution hence the minimal script and hardcoded path.
• I don't have access to the PAM or KBAs so I don't know if this issue has been addressed in newer ASE and/or linux versions.

[rishen-bhowmik]

Though the above given solution has solved master device creation problem, but dataserver is not starting. The ASE automatically getting shutdown.

[rishen-bhowmik]

00:0006:00000:00002:2025/01/27 06:06:16.90 server Checking partition 'sysresourcelimits_52' (partition ID 52) of table 'sysresourcelimits'. The logical page size of this table is 2048 bytes. 00:0006:00000:00002:2025/01/27 06:06:16.90 server 00:0006:00000:00002:2025/01/27 06:06:16.92 server Default Sort Order successfully changed. 00:0006:00000:00002:2025/01/27 06:06:16.92 server ASE shutdown after verifying System Indexes. 00:0006:00000:00002:2025/01/27 06:06:16.92 kernel ueshutdown: exiting 00:0006:00000:00000:2025/01/27 06:06:16.92 kernel bucket manager consolidator terminating 00:0000:00000:00000:2025/01/27 06:06:16.92 kernel Main thread performing final shutdown. 00:0000:00000:00000:2025/01/27 06:06:16.92 kernel Blocking call queue shutdown.

[Mark_A_Parsons]

It looks like a) the srvbuildres process has moved past the SNAP-related issue and b) you've run into a new/separate issue.

The errorlog snippet you've posted consists of messages normally seen in a clean shutdown. If you're unable to find additional details earlier in the errorlog, and there's nothing useful in the srvbuildres output, I'd recommend opening a case with tech support.

[Arbi_TM]

Hi, Looks like you hit a separate issue. 00:0006:00000:00002:2025/01/27 06:06:16.92 server Default Sort Order successfully changed. 00:0006:00000:00002:2025/01/27 06:06:16.92 server ASE shutdown after verifying System Indexes. May I know if you did change the sort order or not? If that's the case, its expected that ASE would require bounce twice, and the second time should bring dataserver up running. Best regards