Are necessary to stop ASE server and replication in order to DUMP and DISK RESIZE in ASE?

[SAPSupport]

Issue : 

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

ASE @Site1
##
00:0003:00000:00025:2024/10/29 22:43:08.03 server  Error: 1105, Severity: 17, State: 2
00:0003:00000:00025:2024/10/29 22:43:08.08 server  Can't allocate space for object 'js_output' in database 'sybmgmtdb' because 'default' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.
...
00:0003:00000:00019:2025/03/12 14:45:03.83 server  Error: 1105, Severity: 17, State: 2
00:0003:00000:00019:2025/03/12 14:45:03.83 server  Can't allocate space for object 'js_history' in database 'sybmgmtdb' because 'default' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.
00:0003:00000:00019:2025/03/12 14:45:03.83 kernel  Job Scheduler (js__exec_handler): Exception 3602 raised.
00:0003:00000:00019:2025/03/12 14:45:03.83 kernel  Job Scheduler got exception for execution token 1.
##

Our actions for this problem: 

1.Take the backup of sybmgmtdb database in primary Site1 node.

dump database sybmgmtdb to "/path/sybmgmtdb.dmp"

If we run it when primary DB, application and Replication is online and running then should it be a problem ?

OR 

2.

Check database current log devices:

sp_helpdb <SID>
go

To resize an existing log device:

use master
go
disk resize name = '<existing_log_device_name>', size = '<size in GB>G'  -- size is what is being added, not the total target size of the device
go
alter database <dbname> log on <existing_log_device_name> = '<size in GB>G' 
go

If we run it when primary DB, application and Replication is online and running then should it be a problem ?

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

Dear customer, 

Regarding to this error, it is important to consider that the DEFAULT segment is a DATA one, not a LOG one. 

About the other requests:

No, it are not necessary to stop the replication and ASE server (such as the disk resize are executed into ISQL connection). 

We just have an advise about the disk resize with replication server:

1. First, double check that there is enough space to increase the size.
2. It is recommended to increase the same amount on the device in the other site of replication.

Here is a document about the disk resize: 

disk resize | SAP Help Portal

[Arbi_TM]

Hi,

A few comments from me:

sybmgmtdb does not participate in replication, so no worries about the operations on it which won't affect replication and application.

Moreover, you can take a look at this KB on how to handle table growth in sybmgmtdb
https://me.sap.com/notes/2361809

Tony