Current Device Structures,

X30_data_001                      15360.0 MB data only            Jul 22 2013 10:37PM                3227632

X30_data_002                      15360.0 MB data only            Jul 22 2013 10:37PM                    336

X30_data_003                      15360.0 MB data only            Jul 22 2013 10:37PM                    112

X30_data_004                      15360.0 MB data only            Jul 22 2013 10:37PM                      0

X30_data_005                      15360.0 MB data only            Jul 22 2013 10:37PM                      0

X30_data_006                      15360.0 MB data only            Jul 22 2013 10:37PM                   7424

X30_log_001                        5120.0 MB log only             Jul 22 2013 10:37PM       not applicable

X30_log_002                        5120.0 MB log only             Jul 22 2013 10:37PM       not applicable

X30_log_003                        5120.0 MB log only             Jul 22 2013 10:37PM       not applicable

X30_log_004                        5120.0 MB log only             Jul 22 2013 10:37PM       not applicable

X30_data_007                      15360.0 MB data only            Jan 18 2016  8:07AM                   4336

X30_data_008                      15360.0 MB data only            Jan 18 2016  8:10AM                  15216

X30_data_009                      15360.0 MB data only            Feb  1 2016  8:36AM               14515120

X30_data_010                      15360.0 MB data only            Feb  1 2016  8:37AM               15667200

X30_data_011                      15360.0 MB data only            Feb  1 2016  8:39AM               15667200

X30_data_012                      15360.0 MB data only            Feb  1 2016  8:40AM               15667200

Hello,

If you're using SAPinst to install SRS I assume it is for HADR in a Business Suite environment purpose.

SRS 15.7.1 GA version (media 51043974 - DVD - Replication Server 15.7.1 Linux x86-64 64-bit) , has never been certified for Business Suite, hence SAPinst will fail.

SRS 15.7.1 started to be certified for Business Suite since SP 100.

To get a SRS SP certified for Business Suite, go to SWDC -> Support Packages and Patches | SAP Support Portal -> Support Packages and Patches -> A-Z index -> Select Sybase Replication Server.

Only the SP with the mention 'also certif. for Bus. Suite' can be used for HADR in a Business Suite environment.

HTH

Regards,

Cris

Hello Itumeleng,

As this space is specific to SAP ASE for Business Suite applications, I'd add that

1) not all SAP ASE patches will be certified for Business Suite. And we can have the case where some patch may be not compatible with some specific Netweaver version .

2) instrumented patches are not really applicable in a BS environment

3) one-off are an exception in a BS environment

If you're not running ASE in a Business Suite environment, keep in mind the right space for your questions then is the SCN SAP Adaptive Server Enterprise (SAP ASE) for Custom Applications (for the next time ! )

Thank you!

Regards,

Cris

Hello Amarnath Chindaluru,

These are the latest lines of SM1.log file (SID.log):

...

00:0006:00000:00016:2016/02/12 00:18:41.70 kernel  Connection from IPv6 client ::1/62966

00:0006:00000:00016:2016/02/12 00:18:41.77 kernel  Connection from IPv6 client ::1/62967

00:0006:00000:00016:2016/02/12 00:18:41.82 kernel  Connection from IPv6 client ::1/62968

00:0008:00000:00256:2016/02/12 00:19:09.26 server  Error: 1105, Severity: 17, State: 2

00:0008:00000:00256:2016/02/12 00:19:09.26 server  Can't allocate space for object 'TBTCO' in database 'SM1' 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:0006:00000:00256:2016/02/12 00:19:09.36 server  Error: 1105, Severity: 17, State: 2

00:0006:00000:00256:2016/02/12 00:19:09.36 server  Can't allocate space for object 'SNAP' in database 'SM1' 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:0006:00000:00019:2016/02/12 00:20:09.26 server  Error: 1105, Severity: 17, State: 2

00:0006:00000:00019:2016/02/12 00:20:09.26 server  Can't allocate space for object 'TBTCO' in database 'SM1' 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:0006:00000:00019:2016/02/12 00:20:09.34 server  Error: 1105, Severity: 17, State: 2

00:0006:00000:00019:2016/02/12 00:20:09.34 server  Can't allocate space for object 'SNAP' in database 'SM1' 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:0008:00000:00019:2016/02/12 00:21:09.27 server  Error: 1105, Severity: 17, State: 2

00:0008:00000:00019:2016/02/12 00:21:09.27 server  Can't allocate space for object 'TBTCO' in database 'SM1' 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:0008:00000:00019:2016/02/12 00:21:09.34 server  Error: 1105, Severity: 17, State: 2

00:0008:00000:00019:2016/02/12 00:21:09.34 server  Can't allocate space for object 'SNAP' in database 'SM1' 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:0007:00000:00030:2016/02/12 00:22:09.26 server  Error: 1105, Severity: 17, State: 2

00:0007:00000:00030:2016/02/12 00:22:09.26 server  Can't allocate space for object 'TBTCO' in database 'SM1' 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:0007:00000:00030:2016/02/12 00:22:09.32 server  Error: 1105, Severity: 17, State: 2

00:0007:00000:00030:2016/02/12 00:22:09.32 server  Can't allocate space for object 'SNAP' in database 'SM1' 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:0008:00000:00019:2016/02/12 00:23:09.26 server  Error: 1105, Severity: 17, State: 2

00:0008:00000:00019:2016/02/12 00:23:09.26 server  Can't allocate space for object 'TBTCO' in database 'SM1' 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:0008:00000:00019:2016/02/12 00:23:09.33 server  Error: 1105, Severity: 17, State: 2

00:0008:00000:00019:2016/02/12 00:23:09.33 server  Can't allocate space for object 'SNAP' in database 'SM1' 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.

This is the output of the sp_helpdb and sp_spaceused isql commands:

How to solve this situation?

Best regards,

João Dimas

Hello again Amarnath,

I believe now everything is ok.

I found this notification in dbacockpit:

Then I add a new device to the SM1 database with the following isql commands:

use master

go

alter database SM1 ON SM1_data_002='5000m'

go

So I believe now is ok:

Best regards,

João Dimas

Hello Joao Dimas,

Happy to here your issue is solved. Moving further your SM1 database is allocated with 98304 MB. So maximum you can alter up to 96 GB approx using alter database command.

Again to resize the disk further you can use

use master

go

disk resize name='device name',size='size in mb'

go

ex: disk resize name='SM1_data_001',size=xxxxm'

Please mark the thread if it was helpful

Best Regards,

Amarnath

You can read the logs as below :

00:0008:00000:00256:2016/02/12 00:19:09.26 server  Error: 1105, Severity: 17, State: 2

00:0008:00000:00256:2016/02/12 00:19:09.26 server  Can't allocate space for object 'TBTCO' in database 'SM1' 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.

It states that 'default' segment is full in database 'SM1'. So you need to add the default segment for SM1 database.

I suggest you to add sufficient size to the default segment, As it contains actual data.

Hope this is helpful.

~Gaurav

bkpprd:prdadm 15> dpmon pf=/sapmnt/PRD/profile/PRD_DVEBMGS00_bkpprd

*** ERROR => CTrcOpen: fopen dev_dpmon

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

trc file: "dev_dpmon", trc level: 1, release: "720"

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

sysno      00

sid        PRD

systemid   390 (AMD/Intel x86_64 with Linux)

relno      7200

patchlevel 0

patchno    400

intno      20020600

make       single threaded, Unicode, 64 bit, optimized

profile    /sapmnt/PRD/profile/PRD_DVEBMGS00_bkpprd

pid        11066

Mon Feb 15 11:06:23 2016

kernel runs with dp version 138000(ext=119000) (@(#) DPLIB-INT-VERSION-138000-UC)

length of sys_adm_ext is 588 bytes

*** ERROR => DpSysAdmExtCreate: ShmCreate (ATTACH) failed (3) [dpxxtool2.c  692]

*** ERROR => DpIPCInit2: DpSysAdmExtCreate [dpxxtool2.c  409]

*** ERROR => DpMonInit: DpExtProcAttach [dpxxmon.c    1082]

DpMonInit failed - possibly no dispatcher running

DpMon: External/Internal dplib version: 119/138

*** ERROR => main: DpMonInit [dpxxmon.c    580]

bkpprd:prdadm 16>

New to sybase so need clarification. We are refreshing a Netweaver 7.4 SPS5 system that is on Sybase 15.7. Per the SWPM system copy guide,

1) We need to create mainfest file on source system(Production system in our case)

2) Dump database to file system or whichever backup process is in place

3) Copy files from step 1 and 2 to target

4) Start SWPM, choose homogenous system copy

5) Select to use existing database installation

6) Give manifest file location along with database dump file when asked

Questions

1) Wouldn't copying manifest file warrant similar directory structures, passwords etc....on target system. What if directory structures between source and target are different. How can we address the difference. Do we edit manifest file to our directory structures on target system.

2) Should we only take DB backup or any other databases(master, systemtools etc....) are also needed

3) Sybase doesn't seem to work around DB SID. When i issue load command on target, should i be using source SID or target SID.  If its source SID, would SWPM be changing the SID and Schema because they seem to be hardcoded in SAP profiles for ODBC/JDBC connections. Please advise

Regards

Kalyan

Hi gurus,

after ASE upgrade from 15.7.0.63 to 15.7.0.135, i'm facing lots of deadlocks in ASE file <SID>.log.
Following an example:

0:0003:00000:00257:2016/02/17 15:00:02.69 server  Deadlock Id 445 detected

Deadlock Id 445 detected. 1 deadlock chain(s) involved.

Deadlock Id 445: Process (Familyid 0, Spid 166, Suid 3) was executing a SELECT command in the procedure 'sp_writejoboutput' at line 54 at nested level 1.

Deadlock Id 445: Process 166 was involved in application 'JS Agent'.

Deadlock Id 445: Process 166 was involved on host name ''.

Deadlock Id 445: Process 166 was involved in transaction 'sp_writejoboutput'.

SQL Text: sp_writejoboutput '673411', 'Changed database context to ''saptools''.

(return status = 0)

'

Executing procedure: sp_writejoboutput

Subordinate SQL Text:

select @user_name=jsh_user_req, @tot_size=jsh_size from sybmgmtdb..js_history where jsh_exid=@run_id

Deadlock Id 445: Process (Familyid 0, Spid 257, Suid 3) was executing a UPDATE command in the procedure 'sp_js_agent' at line 272 at nested level 1.

Deadlock Id 445: Process 257 was involved in application 'JS Agent'.

Deadlock Id 445: Process 257 was involved on host name ''.

Deadlock Id 445: Process 257 was involved in transaction '$upd'.

SQL Text: sp_js_agent 'setstate=C1,id=673410'

Executing procedure: sp_js_agent

Subordinate SQL Text:

update sybmgmtdb..js_history set jsh_state=@state where jsh_exid = @id

Deadlock Id 445: Process (Familyid 0, Spid 257) was waiting for a 'update row' lock on row 31 page 6551 of the 'js_history' table in database 'sybmgmtdb' but process (Familyid 0, Spid 166) already held a 'exclusive row' lock on it.

Deadlock Id 445: Process (Familyid 0, Spid 166) was waiting for a 'shared row' lock on row 30 page 6551 of the 'js_history' table in database 'sybmgmtdb' but process (Familyid 0, Spid 257) already held a 'exclusive row' lock on it.

Deadlock Id 445: Process (Familyid 0, Spid 166) was chosen as the victim.

Victim process host = `', user = `jstask' program name = `JS Agent' host processes = `77528' .

End of deadlock information.

Following the corresponding log for <SID>_JSAGENT.log:

00:75024:76920:2016/02/17 15:00:02.73 worker  Server message: Your server command (family id #0, process id #166) encountered a deadlock situation. Please re-run your command.

00:75024:76920:2016/02/17 15:00:02.73 worker  jso_FlushBuffer: jsd_GetResults() failed for xid 673411

There deadlock happens periorically during scheduled internal ASE activities started by JS Agent (find attached image that shows those activities)

I am not able to find any sapnote or sap document which allows me to eliminate these deadlock.
Does anyone help me to find a solution?

Thanks to anyone would contribute!
Massimo Solleretto

Hello,

I 'm reading some ASE 15.5   performace tunning papers , which  are advising to move from using raw devices for sybase database partition to filesystems , we are planing to start using it for user database devices also, beside the already : tempdb and db's transaction log segments. How about the ASE internal db's :master, systemprocs ? What is the general perfomance advise for  Ase 15.7 and above ?

Thank you

Isabella

Hi Isabella,

master and sybsystemprocs are not hig usage databases. So from performance perspective you can leave them on filesystem devices.

Have you tested that raw devices are really faster in your environment? I've been at several different sites and my experience is that disk performance depends on the whole hardware setup. So for an environment X with storage y and controller z raw devices are faster; and for environment A with storage b and controller c filesystem devices are faster.

Regarding tempdb: it is also possible to put tempdb on a ram disk / tempfs. As tempdb is recreated when ASE is started, there is no need to store the data on disk. You have expand tempdb with "alter database" on tempfs.

After a reboot of the box the files are gone. So you have to create them manually with the "touch" command. Size 0 is sufficient, ASE will expand it during startup.

Here you might want to test the best number of devices for tempdb. A customer, I know, is using tempdb with 16 devices.

Best regards,

Juergen

Hi Isabella,

I aggree with Jurgen. You can store system databases like master, sybsystemprocs, sybmgmtdb ... in the file system as data files. There should be no performance impact for your system. This is also the standard setup for all ASE databases where SAP Business Suite is running on top.

PS: If you want to run SAP Business Suite on ASE you have to use data files anyway because raw devices are not supported for this setup. 

Best regards

Christoph

Hello Ralf,
I'm kind of surprised that you are trying to use ASE Cockpit since you have Netweaver based-applications. ASE Cockpit has been desgined to monitor what we call "standalone ASE", that is , ASE for non-Business Suite applications. And besides that there are configurations steps to apply.

But to monitor/configure you ASE running for ASE application it is strongly recommended to use DBACockpit, you should be able from there to configure ATM and Data Collector Framework.

Kind regards,
Victoria.

Hello Experts,

Thanks is Advance.

We are in plan to build a new system using Backup restore method. Backup is taken on disk.

System Details

SAP ERP 6.0 EHP6

ASE version 15.7.101

Below are the query requires your expert advice.

1 During the system copy database is by SWPM during installation when its prompt to restore database.

Does it necessary that structure of Source and target needs to be exactly same here I am referring to sap data devices?

2 Also please let me know the command for doing the restore and steps?

let me know if pre steps need to be done in order to do the installation successfully.

I found one note 1591387 for homogenous system but it seems it not yet released or getting updated can some one let me know when it would be available.

Regards

Ravi Pandey

Hi Ravi,

Please use below steps and let me know if you need any more information.

1. Install Target system - SAP ERP 6.0 EHP6 with ASE version 15.7.101(Make sure have the similar file systems with more size than source system)

2. Take the backup from Source and move on to the Target system.

3. Restore Database using below command:

load database TSID from "/backup/SID_11042015.dmp"

4.  Execute below command as part of the post steps

online database TSID

5. Proceed similar post steps which followed as part of the system copy

Regards,

Karthik

Hi experts,

we have a lot of SAP systems running on ASE.

How can I find out, what is the bottleneck in the ASE?

I know there are a lot of parameters and possibilities to increase (memory, caches, disc-structure, ...)

But I want to do it effective and so 1st I want to find out, what is the bottleneck?

My 1st idea would be the saptempdb, as I have one slow system on which the saptempdb is very small.

The saptempdb is used by 100%, for sure, but how do I find out now, if this is a bottleneck or not?

ASE Data cache is by around 99,5% btw.

I've already found about saptempdb, that it is used for sorting, indexing, .... but still don't see how big it should be and how it should be concepted.

Kind regards

Hello Massimo,

could you please have a look at this SAP Note?

2279496 - Deadlock has occurred frequently in JS log

Regards,

Valerio

Hi guys,

Which one of these versions are currently more stable in your experience, I need to upgrade customer to latest stable

Targeted ASE 15.x Release Schedule and CR list Information - SAP ASE - SCN Wiki

I want to choose between SP135 HF and SP136.

Keeping in mind once this is done I would then need to do a major upgrade to 16.x.

Also @SAP please release note https://websmp130.sap-ag.de/sap/support/notes/2239584 or advise why it is not released.

Kind Regards,

Johan

Hi Massimo,

The note listed by Valerio target SP134 updates, secondly that having been said the reorg might assist in improving the situation slightly.

Have you done an inspection into your scheduled maintenance activities in DBACOCKPIT?

Looking at your screen image I can see for example that a lot of things are kicking of at the same time.

Just looking at these below in bold they seem to kickoff activities at the same time of hour.

dbh_15min 0.15.30.45* * * *

dbh_5min   0.5.10.15.20.25.30.35.40.45.50.55* * * *

dbh_30min  0.30.* * * *

This almost looks similar to a cron entry for me on unix/linux. I might be misunderstanding your situation or what each one of these dbh activities does but I would investigate removing some of possible or running them less frequently for a starter if possible. Could you provide more information on your OS and SAP version?

Please check note 1835880 - SYB: How to diagnose issues with Sybase ASE Job Scheduler, ATM, or Scheduled Jobs

Also worth checking 2168445 - Run 'update statistics' and 'truncate table' concurrently may hit hang issue

Kind Regards,

Johan