The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Service pack 23 error

SOLVED
Go to solution
Highlighted
Denis_35
Collector

Service pack 23 error

I migrated with sp17 to sp23.
In logserver.txt there was a error:

13/07/2007 09:09:24 JDBC error 1540: [SQL2000]Cannot sort a row of size 8195, which is greater than the allowable maximum of 8094., SQL state: 01000 for query: SELECT T1.ser_id AS C0
,GETDATE() AS C1
,T2.cit_name1 AS C2
,T1.ser_description AS C3
,T3.sei_information AS C4
,T4.per_name AS C5
,T1.ser_cat_oid AS C6
,T1.ser_sta_oid AS C7
,T1.ser_oid AS C8
,T5.rcd_ordering AS C9
,T1.ser_lockseq AS C10
,T1.reg_created AS C11
,T1.reg_modified AS C12
,T1.reg_modified_by_oid AS C13
FROM ((((( itsm_servicecalls T1
LEFT OUTER JOIN itsm_persons T4 ON (T4.per_oid = T1.ser_ass_per_from_oid))
LEFT OUTER JOIN itsm_ser_information T3 ON (T3.sei_ser_oid = T1.ser_oid))
LEFT OUTER JOIN itsm_configuration_items T2 ON (T2.cit_oid = T1.ser_cit_oid))
INNER JOIN rep_codes T5 ON (T5.rcd_oid = T1.ser_sta_oid))
INNER JOIN rep_accounts T6 ON (T6.acc_oid = T1.reg_created_by_oid))
WHERE T1.reg_created >= CONVERT(DATETIME,?,120)
AND T5.rcd_ordering != ?
AND (T1.reg_created >= CONVERT(DATETIME,?,120)
AND T5.rcd_ordering != ?)
Values:
2006/1/1 2:0:0
50
2006/1/1 2:0:0
50java.sql.SQLException: [SQL2000]Cannot sort a row of size 8195, which is greater than the allowable maximum of 8094.
Пт, 13/07/2007 09:09:24 ServerGui Buffer full, cleared ServerGui logFile Monitor window

With what it can be relateded?

My configuration:
Application server: Windows 2003 Server, jre 1.4.2_09-b05, SD 4.5.
Database server: Windows 2003 Server, СУБД - SQL 2000 sp4.

8 REPLIES
Mike Bush
Honored Contributor

Re: Service pack 23 error

Denis - are you saying this happened once during the upgrade or is happening repeatedly now when a client makes a particular enquiry? It probably refers to an SEI_INFORMATION field which has got long but I thought the limit on this was 4000?
Denis_35
Collector

Re: Service pack 23 error

At migration no mistakes have arisen.
For example: the error appears if to set search of the Service call on a field "Information" containing some word.
George M. Meneg
Honored Contributor
Solution

Re: Service pack 23 error

Hello Denis,

Actually this is not service desk error. It is a limitation of MSSQL server that generates an error if the column size is more than 8094 bytes. In some tickets the information field is long enough that when this ticket is included in a view the error is generated.
menes fhtagn
Mark O'Loughlin
Honored Contributor

Re: Service pack 23 error

Hi,

would the option in the database wizard to update the text fields to larger field types (CLOB) help with this issue?
Denis_35
Collector

Re: Service pack 23 error

Excuse me what the option?
How can i use it?
Mark O'Loughlin
Honored Contributor

Re: Service pack 23 error

Hi, have a read of the attachment.

It is listed as "ITSM008420" in SP 20.

It came with SP19. It can be run at anytime on the DB but is a one way process. You cant go back "easily" is what HP support will say. You dont have to run a DB upgrade to do this.

Bear in mind that if you have reporting tools that look for a certain type of field does it work with CLOB.

I cant seem to attach the pdf that provides all the details you need.. I can email it to you if you want.

Its also referenced in this ER.
Vasily Kamenev
Honored Contributor

Re: Service pack 23 error

HI
This is SQL 2k restriction, migrate to SQL 2005.

Vasily
Craig R Taylor
Collector

Re: Service pack 23 error

I think the option to convert a column to a CLOB is limited to Oracle and not MS-SQL.
You can observe a lot just by watching. - YOGI BERRA
//Add this to "OnDomLoad" event