What login owns the user database?
What login shows up in the sybsystemprocs..sysobjects.loginame column for the various sp_help* stored procs?
Re: Unable to reference system stored procedure with dbo prefix
↧
↧
Re: select with reformat causing blocking in tempdb
Is ddl in tran turned on and is it possible that it was something like this:
begin tran
create table #a1
select * from #a1, p1
....
↧
Re: Redistributing ASE Client DLL
Hello Dave,
check the Dev. agreement:
Go to the link https://store.sap.com/sap/cpa/ui/resources/store/html/StoreFront.html
On bottom - Database and Technology
In search field enter "SDK"
There is link that says Trial Version, but as far as I read it is free. Select it and you can read the Terms and Conditions "SAP DEVELOPER CENTER MASTER SOFTWARE DEVELOPER LICENSE AGREEMENT", the deployment should be clarified there.
Hope this will help.
Regards
Stefan
↧
Re: select with reformat causing blocking in tempdb
No.
We've checked there are no transactions anywhere.
Besides its a Worktable that's being created.
BTW, we're on Sybase 15.5
I have sp_objects_stats which shows 300s waiting on sysobjects in tempdb,
↧
Re: select with reformat causing blocking in tempdb
We've sort of found the problem - Sybase server need to be "turned off and on again".
That fixed it.
There was a stack trace earlier in the day... not sure if its any use - but this what we got.
00:15:00000:00318:2014/12/18 10:44:01.08 kernel Current process (0x66ba01d5) infected with signal 11 (SIGSEGV)
00:15:00000:00318:2014/12/18 10:44:01.09 kernel Address 0x0x000000000199ef8b (open__byname+0x4fb), siginfo (code, address) = (1, 0x0x0000000000120028)
00:15:00000:00318:2014/12/18 10:44:01.09 kernel ************************************
00:15:00000:00318:2014/12/18 10:44:01.11 kernel SQL causing error : e
00:15:00000:00318:2014/12/18 10:44:01.11 kernel Current Procedure:
00:15:00000:00318:2014/12/18 10:44:01.11 kernel Current statement number: 1 Current line number: 1
00:15:00000:00318:2014/12/18 10:44:01.11 kernel ************************************
00:15:00000:00318:2014/12/18 10:44:01.11 server SQL Text: insert #proxy_ntuple
00:15:00000:00318:2014/12/18 10:44:01.11 kernel curdb = 25 tempdb = 7 pstat = 0x10000 p2stat = 0x40901000
00:15:00000:00318:2014/12/18 10:44:01.11 kernel p3stat = 0x800 p4stat = 0x80 p5stat = 0x8 p6stat = 0x11 p7stat = 0x10000
00:15:00000:00318:2014/12/18 10:44:01.13 kernel lasterror = 0 preverror = 0 transtate = 1
00:15:00000:00318:2014/12/18 10:44:01.13 kernel curcmd = 296 program =
00:15:00000:00318:2014/12/18 10:44:01.13 kernel extended error information: hostname: login:
↧
↧
Re: Data migration from ASE 11.9.2 to 16.0
Hi Mike,
The 16.0 documentation for the LOAD DATABASE command stats that it only formally supports loads from version 12.5.4 and higher. I'm a little bothered that the upgrade message seems to think the dump is from 12.5 rather than 11.9.
It might be best to try first upgrading to 15.7 before going to 16.0. However, lets check the consistency of sysindexes first.
On your 11.9 server, start by running dbcc checktable on the sysindexes table to see if it actually reports a problem there.
use <dbname>
go
dbcc checktable(sysindexes)
go
-bret
↧
ASE audit for HA Companion Servers
Hi SAP ASE experts,
I have two ASE Companion Servers in a simetric configuration, I need to configure the sybsecurity database for this environment but I don´t know wich kinds of considerations to have, for example:
Is necessary to configure sybsecurity at each ASE server?
Sybsecurity configuration must be the same ?
Is there any procedure for failover of sybsecurity db ?
Best Regards
Jairo
↧
Re: Data migration from ASE 11.9.2 to 16.0
Hi Bret,
The 'checktable' run on the 11.9.2 cloned DB looks ok. So perhaps the error message is a result of incompatibility rather than corruption.
1> use Cust201213mds
2> go
1> dbcc checktable(sysindexes)
2> go
Checking sysindexes
The total number of data pages in this table is 19.
Table has 182 data rows.
DBCC execution completed. If DBCC printed error messages, contact a user with
System Administrator (SA) role.
1>
Based on your comments, i'll try and find an older version of Sybase (at least 12.5.4) and do an interim migration to that platform, then another hop to 16.0. I'll report back with the results. Let me know if you think i'm on the wrong track and should try something else....
Regards,
Mike
↧
Re: Data migration from ASE 11.9.2 to 16.0
You're on track. You may still get an error, but at least you'd be trying something that is documented as supported.
↧
↧
Re: Data migration from ASE 11.9.2 to 16.0
Hi Brad,
Banging my head against a brick wall here. Constructing an ASE 12.5.4 environment on a server 2012 VM (likely not supported) is proving challenging. It half works in XP compatibility mode but java is not happy.... To get a 12.5.4 staging environment working properly I would need to build a windows server 2003 VM and a windows XP client, get the ODBC drivers working properly etc. and test it. Software of this age is extremely hard to track down and license (particularly without an up to date support agreement with SAP)...
I am working on an option that is looking positive so far, though it's the last thing I wanted to do.... namely migrate the data from Sybase 11.9.2 to SQL server 2012. The SQL Server migration tool does support this early version of Sybase, and fortunately the 9 databases I need to convert are not too big or too complex so i'm cautiously optimistic. Analysis and dry-runs to date suggests this may be the least painful solution. Keen to rip the data out of this ancient environment before it dies.
Thanks for you help. This just demonstrates the folly of running a production system in a 16 year old environment; all good fun. 
↧
Logical operations on binary columns
We need to store approx 200 bitfields so we thought we'd use a binary datatype.
We can set the bit fields easily using
set bitfield = bitfield | 1
set bitfield = bitfield | 2
set bitfield = bitfield | 4
However we don't want to hard-code these values we like to use a table like this
update tableA
set bitfield = bitfield | table.value
where ..... table.mask = "MASK1"
However, it seems there is a limitation where you can only OR/AND a binary datatype with an integer.
So the column table.value can only go up to 64 bits.
Why can't we use AND/OR betweem two binary columns ?
Is there some sort of work around ?
(Any chance of any changes in ASE ?)
Incidently MS-SQL suffers the same problem.
↧
Re: Unable to reference system stored procedure with dbo prefix
This problem has now seemed to resolve itself!
I never did get a chance to reboot the ASE because of my large CREATE INDEX still going. But today when I re-tested the condition, everything's back to normal. I am certain that I am testing this in the exact same way I was previously (as described in the original post).
The only change I can think of is that the CREATE INDEX just completed. It was rebuilding a clustered index on a table with 120,000,000 rows, so it ran for a couple days. It "seems like" the dbo-prefix glitch was not present before I started building that index (though without a time machine I can't be positive), and it's definitely not present now that the index is built. But it seems like DURING the time the index was being built is when the symptom was present. Is that possible?
Anyway, I am now a happy camper, though I wish I understood what this was all about.
Thanks.
- John.
↧
Re: Data migration from ASE 11.9.2 to 16.0
It attempting that route...I almost wonder if sybmigrate might be a solution for you - it can copy schema and data from one server to another.....not sure if ever tested/certified with 11.9.x, but the CIS components are all there for it. You'd have to run it from the 15.7 side....
↧
↧
Re: Logical operations on binary columns
I think you mixed up bit and binary datatype.
Binary datatype is normally used for images, text, storing a pdf in your db, etc
If you want 1 column to store multiple values using bitmasks, than you can use an integer to do that.
e.g. see examples in system tables like sysdatabases..status (small int) and sysdatabases..status4 (int)
Sybooks: The bitwise operators are a Transact-SQL extension for use with integer type data.
So it looks like you've got to use multiple columns to achieve wat you want.
Why would you want to store 200 bitfields in 1 column?
↧
Re: SSL On Sybase ASE 15.7
useful..
↧
Re: Logical operations on binary columns
> I think you mixed up bit and binary datatype.
> Binary datatype is normally used for images, text, storing a pdf in your db, etc
I'm aware that's what they're usually used for (although I have thought varbinary would have been better)
but I need to store lots of bit fields and was hoping I could use a binary datatype, rather than have status1, status2, status3, etc
> If you want 1 column to store multiple values using bitmasks, than you can use an integer to do that.
> e.g. see examples in system tables like sysdatabases..status (small int) and sysdatabases..status4 (int)
That's what we're using at the moment - if fact we're now using unisgned bigint - that gives 64 bits.
The fact that sys* tables have multiple status fields shows it would be useful here.
> Sybooks: The bitwise operators are a Transact-SQL extension for use with integer type data.
> So it looks like you've got to use multiple columns to achieve wat you want.
Yep - that's exactly what we've found.
It seems unfortunate to not allow bitwise operations on binary datatypes. Its not a common use of them I know
but I've worked at couple of places which would have benefited from this.
We've spent some time writing our own functions that implement bitwise operations on binary fields, but would have been better if these were build in.
> Why would you want to store 200 bitfields in 1 column?
For a similar reason as the sys* tables have multiple status columns - If binary columns allowed bitwise operations - they'd only need 1 status field.
↧
Re: SSL On Sybase ASE 15.7
One more SSL related question
If a client connects via SSL and doesn't close the connection properly, than informational messages are printed in the errorlog, e.g.:
00:0007:00000:00000:2014/12/22 13:02:01.13 kernel SSL or Crypto Error Info: psn -1, vsn -1, sockp (nil) error id 12, severity -2, provider id 2.
00:0007:00000:00000:2014/12/22 13:02:01.13 kernel SSL or Crypto Error Message: 'An I/O error occurred during the underlying SSL operation. Check your I/O callback handler return values and error codes.'.
Is it possible to surpress these informational messages from OpenSSL?
↧
↧
Re: Redistributing ASE Client DLL
Thanks
↧
Re: pool is configured too small for current demands
Dear Rajesh,
Thanks for the reply, actually I had to enlarge the large pool too, but also, we had other operating system issues that the O.S. support had to solve.
BR | Peter
↧
Re: pool is configured too small for current demands
Dear Peter,
Could you please explain the OS issues you had and it would be great if you can brief the action taken by the OS support team.
Regards,
Rajesh
↧
More Pages to Explore .....
