Reset SAPSA/SA password – Sybase ASE

In case you forgot the passwords for Sybase ASE users SA or SAPSA, these can be reset using below steps.

I have use the steps from below SAP Notes:

2228120 – How to reset sapsa password – SAP ASE for Business Suite and SAP BW

1796540 – SYB: Password changes with sybctrl

1. Login with syb<sid>. Ensure that database is shutdown. You can check this with showserver.
   
2. Change current directory to the install path. Make a copy of RUN_<SID> file.
3. Edit the RUN_<SID> file and make following entries.
   
4. Start your ASE server by executing the RUN_<SID> file on command line –> a new password will be printed into terminal screen follow the last system database online information. It will look like below screen:Note: This new and temporary password is *only* printed on the terminal screen, it is not output to the errorlog. *Do not close* this session for now until we changed the sapsa password on next steps. Once the session is killed/closed, the password will no longer be valid.
5. Now you can login to isql to reset the SA and SAPSA passwords.
   
6. You can test now if the passwrod change has worked.
   
7. Now the passwords are changed it is required to update the securestore of the application server to use the right passwords.
   
8. Propogate the changes using sybctrl command (tool availalbe in the kernel directory of application server)
9. Check connectivity again
   

 

 

2277965 – DUMP DATABASE appears to hang – SAP ASE

Starting Sybase ASE Database (Linux)

Make sure you are logged in with user syb<sid>.

From the environment variables find you Sybase ASE install Directory:

Travesrse to the install path:

Here you see the configuration files (Runserver) RUN_<SID> (Database server) and RUN_<SID>_BS (Backup server).

Use command startserver to start each server process.

You can either start them individually or together.

• -f runserverfile – specifies the relative path name of a runserver file, which is used as a reference each time you start an SAP ASE server or Backup Server. By default, the runserver file is in the current directory and is named RUN_servername. If you start a second SAP ASE server on the same machine, startserver creates a new runserver file named RUN_servername.
• -m – starts an SAP ASE server in single-user mode, allowing only one system administrator to log in, and turns the allow updates to system tables configuration parameter on. Use this mode to restore the master database. The system administrator can use thedbo use only parameter of sp_dboption for system administration activities that require more than one process, such as bulk copying or using the data dictionary. startserver normally starts up only one server per node.The -m parameter creates an m_RUNSERVER file and overwrites any existing m_RUNSERVER file.

After both the processes are started the control is not returned back until you hit a key.

Now you can check the status of server using command showserver.

 

2570084 – How to start Backup Server manually – SAP ASE

2307016 – How to manually configure and start ASE Cockpit for an existing ASE server – ASE 16.0 SP02 PL02

2581558 – Starting SAP ASE Backup Server as windows service reporting error “The service did not respond to the start or control request in a timely fashion”support-grace , support grace, Application version, License version, lic, Sysam, grace period, ASEServer, SAPASE, .lic, FLEXnet Licensing error, key, old license file, datestamp, support renewal date, sybase license , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

How to analyze saptools database growth in Sybase ASE database and contain it

SAPTOOLS database mainly contains the monitoring data for Sybase ASE database.

You can decide the duration this data can be retained by configuring the collector parameters in DBACOCKPIT.

Ensure that the message level is set to error. If not this may significantly increase the growth of this database.

If the history of monitoring is not required anymore, you can also delete the data and log using the prune option.

SQL0204N

The retention policy can be set individually by selecting each data collector and changing the “Days Kept In History” parameter.

Below are some SAP Notes related to SAPTOOLS database:

2100175 – SYB: Increased space allocation of data collectors ‘Tables’ and ‘Indexes’

1927012 – DBA Cockpit shows warnings “Required data collector xxx is not set up properly” – SAP ASE for Business Suite

1615695 – SYB: ‘saptools’ database running out of space

1687320 – SYB: ‘saptools’ database running out of space (2)

2006899 – How to configure reorg on saptools database in DBA Cockpit – SAP ASE for Business Suite

2497314 – How to recreate database saptools when it is corrupted and no clear backup – SAP ASE for Business Suite

2381666 – How to enlarge saptools database through DBA Cockpit – SAP ASE for Business Suite

 

 

Scheduling failed on Sybase ASE

Error in DB13 while running SAP on Sybase database – “Scheduling Failed”.

These errors are intermittent and not reproducible.

Below I outline some steps to troubleshoot this issue:

Check for errors in log files (<SID>, <SID>_BS, <SID>_JSAGENT> under installation directory:

Ex: “D\:sybase\<SID>\ASE-15_0\install.

If you cannot read these files (Because it is in use), copy it to another directory .

Try to dump the transaction log using below command:

dump transaction <SID> to “<Dump Directory>”.

If you are able to successfully dump or truncate the log file, then try to delete the further schedules and try to reschedule the backup again from DB13.

If you are not able to dump or truncate the transaction log , database might be in a standstill (Root cause explained at the end).

In that case, stop SAP and restart the DB services (SQL Server and Backup Server).

In our case, we found following errors in the <SID> log file when the issue happened.

Error: 8213, Severity: 20, State: 3
server Failed to acquire address lock on object DDLOG

Note: There were no Dump DATABASE or Create INDEX were running on the database during that time.

This is caused by a bug in the ASE database as explained in the SAP Note 2337582.

Database had to be updated to one of the release mentioned in the note to resolve the issue.

Important Notes:

2178977 – Job scheduling fails on DBA Planning Calendar – SAP ASE for Business Suite

 

2477608 – DBA Planning Calendar shows duplicate entries with status scheduling failed – SAP ASE for Business Suite

 

2688308 – How to troubleshoot Job Scheduler issues in Standalone ASE

 

2249796 – Unable to create SAP schedules from DBA Cockpit – SAP ASE for Business Suite

 

2692998 – Unable to schedule database job due to ASE Error SQL4002

 

2099027 – Database Extractor Setup Failed for SAP ASE for Business Suite

 

2494044 – Unable to setup job scheduler Solution manager 7.2

R3trans and hdbuserstore

When you change the password of connecting user of SAP HANA database, same should be updated in the key file of the HDBUSERSTORE on the Application Server.

You should be logged in with <SIDADM> for this procedure.  Take care of this specially if you application server and database are running on same server.

#> hdbuserstore SET DEFAULT <hostname>:3<instance Number>15 <user> <password>

Note: User option -i along with the command if you want to enter the options (mainly password) interactively.

Example:

hdbuserstore SET DEFAULT hanahost:30015 SYSTEM Hana@123

Once updated check the list using the below command.

#> hdbuserstore list

DATA FILE : /home/appadm/.hdb/hanahost/SSFS_HDB.DAT
KEY FILE : /home/appadm/.hdb/hanahost/SSFS_HDB.KEY

KEY DEFAULT
ENV : HANAHOST:30015
USER: SYSTEM

You can now check the connectivity with the DATABASE using R3trans -d.

If R3trans -d reports error, check the connectivity with hdbsql using the key created above.

#> hdbsql -U <KEY>      #Key is “DEFAULT” in our example.

This should connect to the database without any issues.

You might receive error sql code  rcSQL = -10709 in case of connectivity issues. Please check the host name and port again in case of issues.

In case of any issues/questions please leave a comment below. Happy learning.

 

Important Notes:

2250144 – FAQ: SAP HANA Secure User Store

2563762 – hdbuserstore still using old hostname after updating

2399996 – How-To: Configuring automatic SAP HANA Cleanup with SAP HANACleaner

2653777 – Phyton connection to HANA database using hdbuserstore-key fails

2416706 – Check file permissions for SAP HANA client hdbuserstore on application server

2130496 – Application does not start after takeover-HANA Disaster Recovery

 

2709350 – How To set a HANA System License via HDBSQL

 

 

System Copy – Sybase ASE

It is one of the most simplest system copies i have ever done. Ensure that Source and Target databases are running on the same release.

No need to uninstall the application or perform a rename using SWPM

I have not mentioned the pre and post processing steps as they are common to all databases and it will differ from customer and customer based on their system usage.

Once you have completed the pre-processing , perform the below steps.

I will assume “TRG” as your target database and “SRC” as your source database.

• Copy the latest full backup file and required transaction backup files to the target server
• Stop SAP Application on the target server.
• Login to SQL/ISQL using “sa” or “sapsa” user ID on target server.
• Drop the target database using below command. This might take few minutes based on database size.

drop database TRG

• Create database TRG using below command.

create database TRG on TRG_data_001=’398743M’ log on TRG_log_001=’20480M’ for load

Note:

1. Size used above are depiction only. This should be equal to or more than your source device sizes.
2. Replace the device names TRG_data_001 and TRG_log_001 with appropriate device names.

• Now load the created database using the source backup using below command.

load database TRG from “D:\backup\SRC.dmp”

Note: Assuming “D:\backup\SRC.dmp”. This might take some time based on the source backup size.

• Now load the log backups to perform point in time recovery using below commands.

load transaction TRG from “D:\logbackup\SRC_001.trn”

load transaction TRG from “D:\logbackup\SRC_002.trn”

etc…

• Bring the restored database online.

Online database TRG.

Now you are all set to start SAP and perform post processing.

 

Note: Even though i have not mentioned pre and post steps here, do remember to make the rdisp/wp_no_btc to 0 in your profile parameter before starting SAP.

 

Important Notes:

2542361 – System copy/migration with sybase database – SAP ASE for BS

1697542 – SYB: System copy with target SAP Adaptive Server Enterprise