cancel
Showing results for 
Search instead for 
Did you mean: 

SAP ASE 16.0 sp_sysmon raises 2749 error

kazuootani
Explorer
0 Kudos

Hello,

ASE 16.0 SP02 PL05

sp_sysmon raises 2749 error when passing section name to second parameter.

1> sp_sysmon "00:00:01",housekeeper
2> go
===============================================================================
Sybase Adaptive Server Enterprise System Performance Report
===============================================================================

Server Version: Adaptive Server Enterprise/16.0 SP02 PL05/EBF 26190 SMP/
P/Sun_svr4/OS 5.10/ase160sp02pl05x/2714/64-bit/FBO/Sun D
ec 4 09:22:56 2016
Run Date: Mar 23, 2017
Sampling Started at: Mar 23, 2017 14:57:55
Sampling Ended at: Mar 23, 2017 14:57:56
Sample Interval: 00:00:01
Sample Mode: No Clear
Counters Last Cleared: Mar 23, 2017 14:56:49
Server Name: ase160
===============================================================================

Housekeeper Task Activity
-------------------------
per sec per xact count % of total
------------ ------------ ----------
Garbage Collections 0.5 0.5 1 n/a
Pages Processed in GC 0.0 0.0 0 n/a

Statistics Updates 0.0 0.0 0 n/a

Msg 2749, Level 16, State 3:
Server 'ase160', Procedure 'sp_sysmon_analyze', Line 538:
Number of argument position specifiers in RAISERROR command is greater than the number of arguments passed.
(0 rows affected)
(return status = 0)
1>

In addition to "housekeeper", "esp" and "monaccess" also
causes the same error.

In versions ASE 15.x, it runs normally.
It seems to be a bug of sp_sysmon in ASE 16.0.
Can anyone check this behavior?

Regards,
Kazuo Otani

Accepted Solutions (1)

Accepted Solutions (1)

former_member188958
Active Contributor
0 Kudos

I've published KBA 2447113 on this issue with an attachment containing a fixed version of the stored procedure.
If you don't have access to KBAs you can extract the script for sp_sysmon_analyze using defncopy and fix it yourself, there are just two small changes to make:

1) at the very end of the file (line 538), add ", @section" to the raiserror 18532 call

begin
raiserror 18532 @msg, "sp_sysmon", @section
raiserror 18534 @msg, "sp_sysmon"
end

2) A little bit higher up, add a new line containing "else" before the line containing 'if (@section = "nvcache")'

end /* } */
else
if (@section="nvcache")
begin /* { */

-bret

Answers (2)

Answers (2)

kazuootani
Explorer
0 Kudos

Thanks Bret

I confirmed normal sp_sysmon run after the modification of sp_sysmon_analyze you suggested.

Kazuo Otani

former_member188958
Active Contributor
0 Kudos

I agree, this is a bug. I've opened new CR 806690