SAP RS - The transaction log in database RSSD is almost full

What happened?
Error when trying to start SAP Replication Server.

Error Message:
E. 2020/12/14 21:39:52. ERROR #11061 GLOBAL RS(GLOBAL RS) - generic\sts\stscol.c(2631)

Check the log for error messages from RSSD.
I. 2020/12/14 21:39:52. Message from server: Message: 7415, State 1, Severity 10 -- 'The transaction log in database RS1_RSSD is almost full. Your transaction is being suspended until space is made available in the log.

Reason:
Cause of the error: The transaction lof of the RSSD database is (almost) full.

Solution:

use master

go

sp_helpdb RS1_RSSD  --a check

sp_helpdevice rssd_log --a check

disk resize name = "rssd_log", size = "1500M"

go

alter database RS1_RSSD log on rssd_log = "1500M"

go

SAP (sybase) ASE - The maximum number of configured devices has been reached

The case:

Creation of a new device.

Error message:

The maximum number <X> of configured devices has already been reached. Please reconfigure 'number of devices' to a larger value and retry disk initialization.

1> disk init name="DdeviceNameLog", physname="/sybvol01/sap16/data/DdeviceNameLog1.dat", size="100M"

2> go

Msg 5162, Level 16, State 1:

Server 'SRSSERVER', Line 1:

The maximum number 20 of configured devices has already been reached. Please reconfigure 'number of devices' to a larger value and retry disk initialization.

Solution:

sp_configure 'number of devices', 30

go

SAP RS: Can't connect to RS but can connect to ASE in the same server

What happened?
Can't connect to RS but can connect to ASE in the same server:

C:\SAPRS>isql64 -S RSSERVERNAME -Usa -Ppassword
CT-LIBRARY error:
        ct_connect(): user api layer: internal Client Library error: Read from the server has timed out.
CT-LIBRARY error:
        ct_connect(): network packet layer: internal net library error: Net-lib operation timed out

C:\SAPRS>isql64 -S ASESERVERNAME -Usa -Ppassword
1>

Error message:
Check in the RS log:

I. 2020/04/22 20:34:47. Check the log for error messages from RSSD.
I. 2020/04/22 20:34:47. Message from server: Message: 7412, State 2, Severity 10 -- 'Space available in the log segment has fallen critically low in database 'RS_RSSD'.  All future modifications to this database will be suspended until the log is successfully dumped and space becomes available..

Cause: 
Log space of the RSSD database (of the RS) is full.
Check it using:

sp_helpdb <RSSDNAME>
sp_helpdevice <RSSDLOGDEVICENAME>

Solution:
Add space to the RSSD log:
http://copypastenet.blogspot.com/2020/01/sap-ase-sybase-transaction-log-in.html

SAP ASE (Sybase) - Cannot create device 'DEVICENAME': no available virtual device numbers (vdevnos)

What I did?
Create a device.

Error message:
Cannot create device 'DEVICENAME': no available virtual device numbers (vdevnos)

Solution:
exec sp_configure 'number of devices', 20 
-- replace 20 with a number that is bigger than what it set now.

Cause:
There is a limit of maximum number of devices - you probably get to it.

Check the number of devices:
exec sp_configure 'number of devices'

See the devices in the server:
select * from master..sysdevices

SAP ASE (Sybase) - The transaction log in database sales is almost full. Your transaction is being suspended until space is made available in the log.

Error message:
The transaction log in database sales is almost full.  Your transaction is being suspended until space is made available in the log.

Will be repuduced whan trying to work with a table in the database.

Cause: 
Log space is full.
Check it using:

sp_helpdb <DBNAME>
sp_helpdevice <DEVICENAME>

Solution:
use master
go
disk resize name = "<DEVICENAME>", size = "500M"
go
alter database sales log on <DEVICENAME> = "500M"
go

SAP ASE (sybase) - Create a Device

-- Create a device - disk init
disk init 
  name="DeviceName", 
  physname="/sybvol01/sap16/data/DeviceName1.dat", 
  size="250M"
GO

For more parameters of disk init:

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc36272.1550/html/commands/X64061.htm