Problem reinstalling SAP ASE

[oneeyeman1]

Hi, ALL,

A long time ago I downloaded and successfully installed SAP ASE 16.0 SP3 on one of my Linux boxes.

Now since that install becomes unusable, I removed the directory and trying to install it again from scratch.

I rerun the setup.bin and went through the wizard and then I went thru the configuration wizard. And then it just stays there.

I tried to run the installer in the console mode and it turns out that it is stuck in the server build procedure.

What could be the issue? I can post a log file from the install - just tell me which one.

Thank you for the help and any pointer.

EDIT:

Logs attached.

The archive can not be attached. It checks the MIME-type of the file.

Which other file I should attach?

Thank you.

The sap_error.txt is the result of running "grep -ri error *" inside Sybase/log folder.

ASE_Suite.txt

sap_error.txt

[bo2l]

Could you attach this log? /sybase/log/ASE_Suite.log, and if a .zip file can be attached here please zip the /sybase/log folder and attach.

[oneeyeman1]

@bo2l, how do I attach the log in the reply? I don't see any relevant field or button...

[Mark_A_Parsons]

@oneeyeman1 you have a couple options for uploading a file:

1. edit the original question (look for three periods - '...' - at the top right of the question and pick 'Edit Question' from the drop down menu)
2. provide an 'Answer' to your own question (ie, 'Comments' don't appear to allow file attachments); you should be able to 'Answer' your own question

[Mark_A_Parsons]

Can you upload the *.log file(s) from the /opt/sap/ASE-16_0/install directory?

Of particular interest is the dataserver errorlog file (REINCLOUD.log), but any other *.log files may be of use if it turns out the issue is not related to the core ASE installation.

Also, do not filter out any lines (eg, don't run a 'grep' to keep/remove lines).

[oneeyeman1]

@MarkAParsons,

Following you reply I was able to download and install version 16.1.

However, during setup I got an errors - screenshots are attached.

The error(s) is about SAP HADR.

What is this piece? Will my server start up successfully?

Thank you.

EDIT:

I tried to run the following script:

[code]

cd /opt/sap
su
source SYBASE.sh
cd ASE-16_1/install
startserver -f RUN_REINCLOUD

[/code]

And I got following output:

[quote]

IgorReinCloud /opt/sap/ASE-16_1/install # 00:0000:00000:00000:2026/05/06 19:45:35.40 kernel SySAM: Using licenses from: /usr/local/flexlm/licenses/license.dat
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: Checked out graced license for 1 ASE_CORE (2026.0315) will expire Mon 03 Aug 2026 01:29:23 AM CDT.
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: Failed to obtain license(s) for ASE_CORE feature from license file(s) or server(s).
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: Cannot find license file.
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: The license files (or license server system network addresses) attempted are listed below.
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: License feature name: ASE_CORE
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: License filename: /opt/sap/SYSAM-2_0/licenses
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: License search path: /opt/sap/SYSAM-2_0/licenses
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: FlexNet Licensing error:-1,359. System Error: 2 "No such file or directory"
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel Error: 131274, Severity: 17, State: 1
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel SySAM: WARNING: ASE will shutdown on Mon 03 Aug 2026 01:29:23 AM CDT, unless a suitable ASE_CORE license is obtained before that date.
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel This product is licensed to:
00:0000:00000:00000:2026/05/06 19:45:35.81 kernel Checked out license ASE_CORE
00:0000:00000:00000:2026/05/06 19:45:35.82 kernel Adaptive Server Enterprise (Edition not set - under grace)
00:0000:00000:00000:2026/05/06 19:45:35.87 kernel basis_dlock: file '/opt/sap/data/master.dat' already in use by an ASE
00:0000:00000:00000:2026/05/06 19:45:35.87 kernel kdconfig: unable to read primary master device
00:0000:00000:00000:2026/05/06 19:45:35.87 server kiconfig: read of config block failed
IgorReinCloud /opt/sap/ASE-16_1/install #

[/code]

I don't know if this is related to the configuration error.

Thank you.

[Mark_A_Parsons]

@oneeyeman1

Your latest comment and attachments point at a smattering of issues ...

1. The image with the message "The product configuration failed." is a generic message that states something went wrong during the installation; details will have been supplied in other windows/messages and/or in the various installation logs. For the most part this image doesn't tell us anything useful.
2. The image with the message "The Replication Management Agent failed to start." would seem to indicate that you told the installation process to a) install the HADR product and b) create (at least some of) the HADR components (this would include the Replication Management Agent - RMA); if you really want to know what the issue was with the RMA creation you would need to review the log file(s) mentioned in the message. Having said that ...
3. In your comment you mention "The error(s) is about SAP HADR.  /  What is this piece?".  From this it sounds like you don't know what HADR is and therefore you probably don't want to install HADR; however, from the bits-n-pieces of details provided it would appear you did ask the installer to not only install the HADR software but to also create (at least some of) the HADR components.
4. You attempted to manually startup the ASE instance (startserver -f RUN_REINCLOUD) but that failed with the message "kernel basis_dlock: file '/opt/sap/data/master.dat' already in use by an ASE"; as the message states, the ASE instance was already up and running; at that point had you run a 'ps -aef' you should have seen  a process running the /opt/sap/ASE-16_1/bin/dataserver binary; by itself this error message is not an issue ... it's merely telling you the ASE instance is already up and running

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

We're not told the series of steps, options and arguments you provided to the installer so I'm going to assume you did something like the following:

1) When asked to choose from the following ASE installation steps:

• Typical (this is referring to a typical ASE installation and consists of the basics you'll need to get an ASE instance up and running)
• Typical SAP  ASE, database always-on option (as stated in small print: this is ASE *plus* the High Availability / Disaster Recovery - HADR option; fwiw, 'always-on' == 'HADR'; this is an advanced option that should only be chosen if you are looking to setup a HADR environment)
• Full (this is referring to all ASE components; does not include always-on==HADR)
• Custom (same as Full but you get to pick-n-choose which components to install)

From what you've posted it appears you chose to install the Typical SAP  ASE, database always-on option.  (Since you don't know what HADR is, and assuming you just want the barebones basic ASE software installed, you should have chosen the Typical option.)

2) After the software (ASE and HADR in this case) is installed the installer will ask if you want the installer to create some instances of various components (eg, ASE dataserver, backupserver , etc).  I'm guessing you requested to create a basic HADR environment; during the creation of the HADR components you received the error message (attached image) stating there was a problem starting the RMA).  (Again, choosing the Typical option should not install the HADR components, which in turn means the RMA would not be installed/configured, which in turn would eliminate the RMA error message).

3) I'm guessing you also asked the installer to create an ASE instance (named REINCLOUD); since you don't mention any other installer-related error messages I'm going to assume this ASE instance was in fact a) created and b) successfully started since ...

4) After the installer finished (albeit with errors) you chose to manually start the ASE instance (startserver -f RUN_REINCLOUD), but because the installer has already started this ASE instance you were provided with the errorlog message "'/opt/sap/data/master.dat' already in use by an ASE".

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

Suggested next steps ...

1. Make sure all sybase processes are shutdown and/or killed (this includes dataserver and backupserver binaries as well as any HADR-related binaries; if in doubt run 'ps -aef' and look for anything running under the /opt/sap directory, then kill any such processes
2. Delete the entire directory /opt/sap; you want to start over from scratch with no lingering issues from the previous/failed installation(s).
3. Run the installer and when it asks you to Choose Install Set, chose the first option - Typical; again, I'm assuming you only want to install the base minimum software to get an ASE instance up and running
4. After the installer exits, and assuming no errors/issues, and assuming you requested a sample ASE instance to be created, the ASE instance should already be up and running; if the ASE instance is not running for some reason then go ahead and manually start the ASE instance (startserver -f RUN_...)

[oneeyeman1]

@MarkAParsons,

thank you for the reply. See my answers below.

1. So what log file(s) should I check?

Basically all I need is to install the server in order to test my C++ code.

I have a laptop with Linux where I want to install it.

I have a home network, but I will be running and testing it locally on the same laptop.

I also have a Windows laptop and another Linux laptop.

2. Yes - I really do. Maybe there is something here that needs to be updated, like kernel or some system utility? I presume that the installer is run on multiple different machines and is successfully finishes up. So this makes me very curious.

3. Yes, that is correct. I don't know what the HADR is and I probably don't need it. But I also know that there was no issue with 16.0. And so I do want to find out what the issue is.

Sybase was the very first DBMS I got familiar with and so I really want to make sure that everything is great.

4. Yes - I rechecked and the server was already running. Thx for that.

5. I did not choose Typical. I chose Custom when I did the install And then I selected Trial License.

I then selected the thing to install. I unchecked the Perl/Python client software and chose the License Server.

After the installation I selected to configure everything.

I pretty much chose everything as default. The only thing I did was I set the server name passwords.

Everything was done successfully except the error messages in the screenshots.

6. I can try to re-install the server, but as stated I'd really like to find out what the problem is with the HADR (or its components).

Thank you.

[henry-1_]

Reinstall issues in SAP ASE usually happen because the previous installation was not fully cleaned up.

Most common causes are:

• Leftover ASE folders or system files still present
• Port or server name already in use
• Old environment variables (like SYBASE) not removed
• Installer trying to reuse existing configuration

Simple fix:

1. Stop ASE services
2. Remove old ASE directories completely
3. Check and free used ports
4. Clean environment variables
5. Reboot system
6. Run installer again as admin/root

 In most cases, a clean removal + fresh install resolves the issue.

[ryan_hansen]

This is also an option for installations if it doesn't add everything you want or need "-DDO_NOT_SETENV_AND_REGISTRY=false" This is a new and is needed to fully install registry and environment variables. There were conflicts with multiple products and PATH being filled to a max size. For example ODBC needs to add registry entries to the Windows ODBC manager to be used.

[ryan_hansen]

I should have added this but you can uninstall with flags as well: uninstall.exe -i silent -DUNINSTALL_DELETE_DATA_FILES=TRUE -DUNINSTALL_DEL_FILE_SCOPE_1=DataAccess -DUNINSTALL_DEL_FILE_SCOPE_2=DataAccess64 -DUNINSTALL_DEL_FILE_SCOPE_3=OCS-16_0

[oneeyeman1]

@MikeAParsons, I just tried to get a newer version.

However, I got the following message:

You are signed in with a P-user ID. Visitors with an S-user ID will benefit from more tools and enhanced functionality. If you are an SAP customer, contact a user administratior in your company to request such an ID. Your SAP Local Support Center can help you identify your administrators. If you already own an S-user ID, log out now and log in with your S-user ID.

2 things

1. I'm not part of the company. Just a solo developer.

2. In the past that login gave me an ability to get the software.

What do I do at that time?

Thank you.

[Mark_A_Parsons]

@oneeyeman1

It's not clear (to me) what you are doing, or what URL/link you are using, when you receive that message re: S-user vs P-user.

I have a P-user login.

With my P-user login I just verified:

1. I can download the ASE trial (aka evaluation) software (windows or linux version) @ https://www.sap.com/products/data-cloud/sybase-ase/trial.html [ this is the same link Bart posted in an earlier answer ]
2. I can generate a 1-yr EValuation license @ https://go.support.sap.com/minisap/#/minisap [ this is the same link I posted in an earlier comment ]

[bart_van_kuijk]

=> However, I wonder - how come the initial install went thru without any issues?
The 'Snap::VAlidate' issue is linked to Linux compiler version. It started appearing after Linux OS patch level / minor version upgrade. 
So, you would have run with a different (lower) OS patch level when it worked.

=> Express Edition
This was discontinued, I believe. There is this trial option :
https://www.sap.com/products/data-cloud/sybase-ase/trial.html?url_id=text-us-sapcom-ase-trial-softwa...

Bart

 

[oneeyeman1]

@Bart,

1. As stated - this particular laptop was just lying somewhere in my safe place. I know better for updating OS when the software not from the repo is installed. 😉

2. Express is not trial. Trial will have to be removed after the trial period. And my development will be much longer than 3 month.

Any suggestions?

Thank you.

[Mark_A_Parsons]

@oneeyeman1

The trial license (aka EValutation license) can be updated/extended in 1-year intervals @ https://go.support.sap.com/minisap/#/minisap.  I have a pair of ASE installations that are a few years old and they run just fine on my (annually updated) EV license.

As for the express (XE) license, the license file has a generic key that should work on any host (ie, HOSTID=ANY).  In the past I've been able to copy the express license file (*XE.lic) to newer ASE installations and ASE successfully started up on said license (ie, the newer ASE software still recognized the XE license). [NOTE: It's been a couple years since I tested this workaround so I don't know if it still works with the latest ASE distributions.]

[Mark_A_Parsons]

We really need to see the actual error message and any related stack traces.

During the dataserver creation an errorlog should be generated for the new dataserver ($SYBASE/$SYBASE_ASE/install/<dataserver_name>.log).

The file size should be relatively small so you should be able to upload it as an attachment (either edit your original question, or start a new 'Answer' to your question)

If the file has grown sufficiently large (eg, trying to build the dataserver several times) then consider renaming the file, running the install/build again, and then upload the new *.log file.

In the meantime, if you are running into the snap:validate stack trace issue (as alluded to by Bart), this has been addressed a couple times in this community (eg, this Q&A).  The workaround in that linked Q&A (assuming you're experiencing the same exact issue) does not require going to a newer version of the ASE product.  [As for why you were able to successfully install the product before ... *shrug* ... hard to say without knowing more about the old vs new environments; could be a difference in the OS/kernel, a different ASE PL## version, ????]

[bart_van_kuijk]

As you reference SP03 and that the install gets stuck, it is very likely you are hitting a known issue. SP03 is an older code line and I assume you may be using an older PL level as well. Does the ASE startup log show signal 11 error with no function in Address:

Current process (0x1d000f) infected with signal 11 (SIGSEGV)
Address 0x0x00007efda8089360 () ...

followed by a stack trace that includes the function Snap::Validate:

()
Snap::Validate
SnapValidation
dsinit

followed by
Warning: The internal timer is not progressing. If this message is generated multiple times, report to SAP Technical Support and restart the server (alarminterval=0).


If so,  you are hitting an issue because of an incompatibility between ASE compiler and Linux OS (patch) versions. You need to use at least :
- ASE 16.0 SP03 PL11 or
- ASE 16.0 SP04 PL01

 If you are starting out again, I would not recommend to go with SP03 but install latest, which is SP04 PL08.

Kind regards

Bart

[ryan_hansen]

You can also add environment variable LAX_DEBUG=true which will give more output to the cmd prompt window as well. I would suggest using a newer version as well and 16.1 is the major version going forward.

[oneeyeman1]

@bart_van_kuijk, yes, I think I saw something like this in the log.

However, I wonder - how come the initial install went thru without any issues?

In regards to installing newer version - this allows me to install Express Edition. Will it be available in the versions you referenced?