we are planning to upgrade our legacy systems with versions 12.5.4 to latest 16
I want to explore the option of backward compatibility. Is this automatically enabled or there is an option that needs to be installed or configured?
If there are resources for testing the compatibility, please point me to those as well.
Regards
Hi
we are using sybase 15.5 and calling soem stored procedures from a Java program. We are facing a situation where the stored procedure is ereturning the Query Plan inspite iof us not explicitly settign the Shownplan ON.
It results in JVM running out of memory and crashes.
Recently for some of the stored proc we set the WITH RECOMPILE option as well as FORCEPLAN On and Off.
Hi There,
is there a way to suppress the Sybperf messages in the ASE Errorlog? They are the cause of growth in our Errorlog.
I cannot disable 'SQL Perfmon Integration' because of a product called SCOM is using this option....
<snippet>
00:0012:00000:00000:2014/12/23 10:44:16.99 kernel Sybperf helper thread is setting up counters for a windows Performance Monitor connection
00:0012:00000:00000:2014/12/23 10:44:17.12 kernel Sybperf helper thread is cleaning up counters
</snippet>
regards,
Harry Splinter
We've downgraded our server to 15.7 SP110 and we're now getting a few errors.
One of these is "Attempted to grab wash header"
followed by the SQL text and then this
00:0023:00000:02124:2015/04/23 14:17:09.32 kernel curdb = 26 tempdb = 92 pstat = 0x10000 p2stat = 0x40101000
00:0023:00000:02124:2015/04/23 14:17:09.32 kernel p3stat = 0x40800 p4stat = 0x0 p5stat = 0x8 p6stat = 0x10000011 p7stat = 0x10000
00:0023:00000:02124:2015/04/23 14:17:09.32 kernel lasterror = 837 preverror = 0 transtate = 1
What causes this error ? (We didn't get this using SP60 or SP122).
Could it be caused by doing a downgrade or is it an issue with SP110 >
Is there a workaround ?
We downgraded from ASE 15.7 SP122 to SP100 to get away from the 815 Errors which required a server reboot.
We're now getting 622 Errors followed by a stack trace.
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel p3stat = 0x800 p4stat = 0x80 p5stat = 0x8 p6stat = 0x10000011 p7stat = 0x10000
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel lasterror = 622 preverror = 0 transtate = 3
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel curcmd = 294 program =
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel extended error information: hostname: login:
and then a stack trace and then this
00:0000:00000:00000:2015/04/24 22:59:34.05 kernel Warning: The internal timer is not progressing. If this message is generated multiple times, report to Sybase Technical Support and restart the server (alarminterval=-1087).
00:0002:00000:01966:2015/04/24 22:59:54.61 kernel timeslice -1501, current process infected at 0x15f2554 (atomic_try+0x2) 00:0002:00000:01966:2015/04/24 22:59:54.62 kernel **** Saved signal context (0x0x00002aaaee78a190): ****
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel uc_flags: 0x0, uc_link: 0x(nil)
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel uc_sigmask: 0x416000 0xa 0xfffffffa 0x61b
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel uc_stack: ss_sp: 0x(nil), ss_size: 0x0, ss_flags: 0x2
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel General Registers (uc_mcontext.gregs):
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel PC : 0x00000000015f2554 (atomic_try+0x2)
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RAX : 0x000000000c529347 RBX : 0x0000000000000001
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RCX : 0x00002aaab8236b30 RDX : 0x0000000000000001
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RBP : 0x00002aaaee78a6d0 RSP : 0x00002aaaee78a5d8
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R8 : (nil) R9 : 0x000000000000005b
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R10 : 0x00002aaaac020880 R11 : 0x00002acaa5f07ba0
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R12 : 0x00002ac7310ad5c8 R13 : 0x00002aaab8271b6c
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R14 : 0x00002aac0d811ff0 R15 : 0x00002aaab7ce5c00
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RDI : 0x00002aaab7ce5c00 RSI : 0xfffffffffffffff0
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RIP : 0x00000000015f2554 CSGSFS : 0x0000000000000033
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel TRAPNO : (nil) ERR : (nil) 00:0002:00000:01966:2015/04/24 22:59:54.62 kernel EFL : 0x0000000000000206
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel **** end of signal context ****
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel timeslice error: spid 1966 exhausted its 'time slice' of 100 milliseconds and additional 'cpu grace time' of 1500 ticks (75000 milliseconds). It has been marked for termination.
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel This Adaptive Server process has had 48 major and 1165074 minor page faults since boot.
The issue occured after a 814 error - but we've been told to expect these in SP100 and they don't cause the server to hang or need a reboot.
Are these known issues in SP100 ?
Is there any way to work around them ?
Is it better to downgrade to SP60 or are the same issues in SP60 ?
In the below SQL, data is written to SOURCE and from there to TARGET.
The DECIMAL columns in TARGET are deliberately smaller than those in SOURCE (eg a DECIMAL (12, 2) column populated from a DECIMAL (19,11) source).
When I run this in an Query tool (eg, SqlDbx) I get the messages:
"Truncation error occurred
Command has been aborted"
But when I run this using the .net Client (supplied with the Developer Edition of ASE 16.0) no exception is thrown (the INSERT fails though). The method is AseCommand.ExecuteNonQuery().
Is this deliberate?
Is this believed to be correct?
How can I tell that a truncation error has been raised?
Thanks
IF OBJECT_ID ('dbo.TARGET') IS NOT NULL
DROP TABLE dbo.TARGET
GO
CREATE TABLE dbo.TARGET
(
S_Name_NVARCHAR NVARCHAR (50) null,
S_RedComponent_DEC_15_6 decimal(15, 6) NULL,
S_BlueComponent_DEC_12_2 decimal(12, 2) NULL,
S_GreenComponent_DEC_18_10 decimal(18, 10) NULL
)
GO
IF OBJECT_ID ('dbo.SOURCE') IS NOT NULL
DROP TABLE dbo.SOURCE
GO
CREATE TABLE dbo.SOURCE
(
Name_NVARCHAR NVARCHAR (2000) NULL,
RedComponent_DEC DECIMAL (19,11) NULL,
GreenComponent_DEC DECIMAL (19,11) NULL,
BlueComponent_DEC DECIMAL (19,11) NULL
)
GO
INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
VALUES ('Beige', 272.195, 272.195, 244.42)
GO
INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
VALUES ('Bisque', 283.305, 253.308, 217.756)
GO
INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
VALUES ('Black', 0, 0, 0)
GO
INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
VALUES ('BlanchedAlmond', 283.305, 261.085, 227.755)
GO
--Is there data to migrate?
SELECT LEFT( S.Name_NVARCHAR,8000),S.GreenComponent_DEC,S.GreenComponent_DEC,S.GreenComponent_DEC
FROM (
SELECT * FROM SOURCE
) S
--Yes.migrate away!
--Next line gives a truncation error occurred in Sybase (gives a truncation error occurred in a query tool
--but fails silently in AseCommand.ExecuteNonQuery).
INSERT dbo.TARGET (S_Name_NVARCHAR,S_RedComponent_DEC_15_6,S_BlueComponent_DEC_12_2,S_GreenComponent_DEC_18_10)
SELECT LEFT( S.Name_NVARCHAR,8000),S.GreenComponent_DEC,S.GreenComponent_DEC,S.GreenComponent_DEC
FROM (
SELECT * FROM SOURCE
) S
select * from dbo.TARGET
HI All,
Below are the configuration details of my PC
processor: Intel I7
Memory: 8GB
Hard Disk: 1TB
I have installed VM ware on windows 8.1 and installed Redhat 6.5 on virtual machine.
VM mare configuration details
Memory : 2GB
hard disk: 50 GB
Download ASE from below link
http://scn.sap.com/community/developer-center/oltp-db
I have tried installing ASE 16 on RED HAT 6.5, but install failed several times, attached error message.
Error Message
----------------------------------------------------------------------------------------
Cannot run /opt/sap/OCS-16_0/bin/isql - exec failed (ENOENT)
Failed to create sample databases
---------------------------------------------------------------------------------------
Server " LOCALHOST_JSAGENT" was not created.
Failed to configure NEW JOB SCHEDULER
Kindly advise
Dear Experts,
I was trying to install ASE 16 on RHEL 6.5 using VMware 11 interface on a windows 8.1 platform (Laptop)
Software downloaded from SAP service market place
--Received following errors
Product configuration failed
bash: showserver: command not found
bash: isql: command not found
--Server is up and running
[root@localhost install]# ps -ef |grep dataserver
root 10059 1 0 21:11 pts/0 00:00:00 sh -c /opt/sybase/ASE-15_0/bin/dataserver -sT10 -d/opt/sybase/data/master.dat -e/opt/sybase/ASE-15_0/install/T10.log -c/opt/sybase/ASE-15_0/T10.cfg -M/opt/sybase/ASE-15_0 > /dev/null 2>&1
root 10060 10059 1 21:11 ? 00:01:09 /opt/sybase/ASE-15_0/bin/dataserver -sT10 -d/opt/sybase/data/master.dat -e/opt/sybase/ASE-15_0/install/T10.log -c/opt/sybase/ASE-15_0/T10.cfg -M/opt/sybase/ASE-15_0
root 13785 11401 0 22:21 pts/0 00:00:00 grep dataserver
Attached are the screen shots of the error received during installation
Any help is much appreciated
Regards
Rajesh
Hi all,
Is there a way I can understand about the transaction,
I have tried using "dbcc(3604);dbcc log;" but that doesnt help much..
After some searching i came to know to use SQLAnywhere, but couldnt find any link to download it.
Is there any other way to view the log ?
Any reference on this will also be helpful.
Thanks in advance.
We attempted an upgrade from 15.7 SP122 to SP132 but we experienced a problem with trigger permissions.
Case :
Table A in DB1 has a trigger which fires a delete from Table B in DB2
All databases, tables and triggers are owned by user 1
After the upgrade to SP132, we updated table A and the trigger fails with
DELETE permission denied on object B, database DB2, owner dbo
We extracted the trigger definition from the database and reloaded it.
We ran the updated on table A again and the process was successful.
We have a few triggers and this didn't affect all of them so far so seems like a glitch somewhere.
We're due to try the upgrade on another server so we'll be able to test this before and after the upgrade.
Hi!
I have some problem with search information about memory uses in ASE.
I can’t find information about memory for aggregate(when we use memory in query and have need big join or group by, order by and use work table).
Where take memory under these needs?
I assume that this total memory with a data cache.
Whether there can be problems in case of redistribution of this part of memory?
How to define how many it is required to memory for specific request?
Maybe somebody hade similar problem.
Using granular permissions on ASE 15.7 shows some non-intuitive behavior
Sybooks says permission "Update Any Security Catalog" is required for:
Updating, inserting, and deleting these security-related system catalogs, which are restricted from direct update
| master.dbo.syslogins | |
| master.dbo.syssrvroles | |
| master.dbo.sysloginroles | |
| db.dbo.sysroles | |
| db.dbo.sysprotects |
That makes sense, any direct update on this should require special permissions
Then there's the permission "Manage any statistics": Update or delete statistics on any table owned by anyone
However, permission "manage any statistics" is not sufficient for some tables
update index statistics sysroles
go
Msg 10331, Level 14, State 2:
Server 'ASE157', Line 1:
Permission denied, database testdb, owner dbo. You need the following permission(s) to run this command: UPDATE ANY SECURITY CATALOG.
update index statistics sysprotects
go
Msg 10330, Level 14, State 1:
Server 'ASE157', Line 1:
UPDATE STATISTICS permission denied on object sysprotects, database testdb, owner dbo
Very non-intuitive behavior.
I've raised a case with support, but they just say updating sysroles requires update any security catalog
IMHO update stats is not updating the table, manage any statistics should be sufficient
What do you think about this?
Hit any similar issues with granular permissions?
Could someone please tell me where I can find documentation on Workload Analyzer? I cannot find anything on this topic in SyBooks Online for ASE 16.0.
I've noticed that the direct link to http://infocenter.sybase.com/ has been messed up some time ago (leads to 403 forbidden page).
Could this be looked after please? Unless the page has been moved under the help.sap.com hood somewhere...
The information is still available but the entry point now is SyBooks Online
Thanks...
In 2011, SAP announced it would become the No. 2 database player by 2015.
How is everything going with ASE so far?
Its road-map seems promising, is it gaining market share?
A leap second will be inserted at the end of June.
(used NTP to sync the time)
Any SAP notes talk about this?
Will leap second impact ASE?
Is the following ASE message relay?
Warning: The internal timer is not progressing. If this messages is generated multiple times, report to Sybase Technical Support and restart the server(alarminterval=-577028)
I see that the meaning of trace flag 7773 has been switched in meaning between 15.5/15.7SPxx and 15.7SPxxx
This seems rather odd to switch the meaning of a trace flag as I'm sure many people wouldn't have spotted it (we didn't).
I'm trying to understand the CR653511
Note 1891033:In which ASE version is CR 653511 fixed and does the fix require traceflag 7773 ? …
but I'm not clear what its trying to actually fix and whether we'd actually see the issue or not.
Can anyone explain the details of this traceflag and what a good default for it should be ?
Also, is there a table explaining all the trace flags.
The eom for both versions point to the same date.
Does ase 16 have the same 31.12.2020 eom date or will that be pushed further -at least for sp 01?
We downgraded from ASE 15.7 SP122 to SP100 to get away from the 815 Errors which required a server reboot.
We're now getting 622 Errors followed by a stack trace.
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel p3stat = 0x800 p4stat = 0x80 p5stat = 0x8 p6stat = 0x10000011 p7stat = 0x10000
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel lasterror = 622 preverror = 0 transtate = 3
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel curcmd = 294 program =
00:0022:00000:01548:2015/04/24 22:58:39.54 kernel extended error information: hostname: login:
and then a stack trace and then this
00:0000:00000:00000:2015/04/24 22:59:34.05 kernel Warning: The internal timer is not progressing. If this message is generated multiple times, report to Sybase Technical Support and restart the server (alarminterval=-1087).
00:0002:00000:01966:2015/04/24 22:59:54.61 kernel timeslice -1501, current process infected at 0x15f2554 (atomic_try+0x2) 00:0002:00000:01966:2015/04/24 22:59:54.62 kernel **** Saved signal context (0x0x00002aaaee78a190): ****
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel uc_flags: 0x0, uc_link: 0x(nil)
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel uc_sigmask: 0x416000 0xa 0xfffffffa 0x61b
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel uc_stack: ss_sp: 0x(nil), ss_size: 0x0, ss_flags: 0x2
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel General Registers (uc_mcontext.gregs):
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel PC : 0x00000000015f2554 (atomic_try+0x2)
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RAX : 0x000000000c529347 RBX : 0x0000000000000001
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RCX : 0x00002aaab8236b30 RDX : 0x0000000000000001
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RBP : 0x00002aaaee78a6d0 RSP : 0x00002aaaee78a5d8
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R8 : (nil) R9 : 0x000000000000005b
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R10 : 0x00002aaaac020880 R11 : 0x00002acaa5f07ba0
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R12 : 0x00002ac7310ad5c8 R13 : 0x00002aaab8271b6c
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel R14 : 0x00002aac0d811ff0 R15 : 0x00002aaab7ce5c00
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RDI : 0x00002aaab7ce5c00 RSI : 0xfffffffffffffff0
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel RIP : 0x00000000015f2554 CSGSFS : 0x0000000000000033
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel TRAPNO : (nil) ERR : (nil) 00:0002:00000:01966:2015/04/24 22:59:54.62 kernel EFL : 0x0000000000000206
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel **** end of signal context ****
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel timeslice error: spid 1966 exhausted its 'time slice' of 100 milliseconds and additional 'cpu grace time' of 1500 ticks (75000 milliseconds). It has been marked for termination.
00:0002:00000:01966:2015/04/24 22:59:54.62 kernel This Adaptive Server process has had 48 major and 1165074 minor page faults since boot.
The issue occured after a 814 error - but we've been told to expect these in SP100 and they don't cause the server to hang or need a reboot.
Are these known issues in SP100 ?
Is there any way to work around them ?
Is it better to downgrade to SP60 or are the same issues in SP60 ?
We hit a Error 834
Error 834, Severity: 20, State: 3
00:0005:00000:02377:2015/05/05 02:57:39.91 server Illegal attempt to clean buffer: BUF=0x0x00002b12b63ed4c8, MASS=0x0x00002b12b63ed4c8,
Buf#=0, page=0x0x00002b1014c10000, dbid=93, Mass vdevno=127, vpage=4103856, Buf lpage=982, Mass stat=0x4010001, Buf stat=0x2, size=16384, cid=3 ('tempdb_cache1'), Pinned xdes=0x(nil), spid=0.
which the manual here
says
This state is only raised by diagserver. |
Isn't the diagserver a separate executable ?
But we're only running the standard executable ?
Is there another way to get this message ?
Also what causes this ? It seems to have causes a tempdb to be unavailable and a reboot to fix it.