Sep 11, 2017 at 07:53 AM

Sybase - Error: 605 on version 160sp02pl04

189 Views Last edit Sep 19, 2017 at 02:22 PM 2 rev

Hi

I'm getting these Error: 605 errors:

00:0006:00000:00301:2017/09/11 00:02:00.41 server Error: 605, Severity: 21, State: 1 00:0006:00000:00301:2017/09/11 00:02:00.41 server An attempt was made to fetch logical page '3538743' from cache 'default data cache'. Page belongs to database 'MEQ' (4), object 'MARCH' (219495363), index 'MARCH~0' (2), partition 'MARCH~0_219495363' (219495363) and not to database 'MEQ' (4), object 'VRSD' (2104026079), index 'VRSD~0' (2), partition 'VRSD~0_2104026079' (2104026079). 00:0006:00000:00301:2017/09/11 00:02:00.41 kernel ************************************ 00:0006:00000:00301:2017/09/11 00:02:00.41 kernel SQL causing error : update index statistics MEQ.SAPSR3.[VRSD] using 100 values with partial_hashing 00:0006:00000:00301:2017/09/11 00:02:00.44 kernel ************************************ 00:0006:00000:00301:2017/09/11 00:02:00.44 kernel curdb = 4 tempdb = 6 pstat = 0x10000 p2stat = 0x40901000 00:0006:00000:00301:2017/09/11 00:02:00.44 kernel p3stat = 0x800 p4stat = 0x40000000 p5stat = 0x8 p6stat = 0x1 p7stat = 0x110000 00:0006:00000:00301:2017/09/11 00:02:00.44 kernel lasterror = 605 preverror = 0 transtate = 1 00:0006:00000:00301:2017/09/11 00:02:00.44 kernel curcmd = 326 program = JS Agent - sapsa 00:0006:00000:00301:2017/09/11 00:02:00.44 kernel extended error information: hostname: login: sapsa

I found SAP note 2011331, resolution is:

Upgrade ASE to a release with a fix for SAP CR 761958:

SAP ASE 16.0 GA PL02
SAP ASE 16.0 SP01
SAP ASE 16.0 SP02

My Sybase version is:

1> select @@version

2> go

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

Adaptive Server Enterprise/16.0 SP02 PL04/EBF 26122 SMP/P/x86_64/Enterprise Linux/ase160sp02pl04x/2586/64-bit/FBO/Fri Jun 10 11:33:16 2016

How do I know if this CR fix is in my current version? Will updating Sybase fix the issue?