cancel
Showing results for 
Search instead for 
Did you mean: 

sp_helpdb fails with Msg 11021

0 Kudos

Hi.

When trying to run sp_helpdb with arguments, some info are missing and returns "

Msg 11021, Level 16, State 2"

Appreciate any help with this.

1> sp_helpdb master
2> go
name db_size owner dbid created durability status
------ ------------- ----- ---- ------------ ---------- ------------------
master 13,0 MB sa 1 Dec 09, 2009 full mixed log and data

(1 row affected)
Msg 11021, Level 16, State 2:
Server 'FNR', Line 1:
Function STR invoked with wrong number or type of argument(s).
device segment
------ ----------
master default
master logsegment
master system
(return status = 0)


1> select @@version
2> go

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Adaptive Server Enterprise/15.5/EBF 17336 SMP/P/Sun_svr4/OS 5.8/ase155/2391/64-bit/FBO/Tue Nov 10 01:27:55 2009

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member188958
Active Contributor
0 Kudos

Hi Paul,

This is a very old ASE version, I have to recommend upgrading it to 16.0 on general (and as it turns out, specific) principles.

There were a couple of reports of this error 8-10 years ago and a bug (Cr 646295) was opened for it, but has not been fixed (probably because the issue has not been reported on later releases). The bug is also strange, with conversion between FLOAT and NUMERIC datatypes appearing to be somehow mysteriously bound up with the PCI module (used to enable server-side JAVA) and (possibly) a client running on windows with a region setting of "German".

Suggested workarounds for the CR were:

Disable PCI by sp_configure "enable pci", 0
OR Don't use German Germany in region setting in the pc OR Setup the "Decimal symbol" to '.' as opposed to ',' in the pc OR Boot ASE with trace flag 4065

Traceflag 4065 causes ASE to use an alternate method for converting FLOAT to NUMERIC.

If you do upgrade ASE to 15.7 or higher and still experience the issue, please open a support incident.

Cheers,
Bret Halford
Support Architect, ASE