I need to upgrade a 12.52 install to 12.53.
The reason being that "New configuration parameters have
been added in 12.5.3a."
Later installs simply check for this and I can only assume
that 12.53a does a little more than check.
So where might I download the developer edition still as I
have a database that requires this and as such I require
sybase ASE 12.53a
From: Jim Dawks
Subject: Old Releases Needed!
X-Mailer: WebNews to Mail Gateway v1.1t
Date: 7 Oct 2009 05:30:18 -0700
X-Trace: forums-1-dub 1254918618 10.22.241.41 (7 Oct 2009 05:30:18 -0700)
X-Original-Trace: 7 Oct 2009 05:30:18 -0700, 10.22.241.41
Xref: forums-1-dub sybase.public.ase.general:28419
Article PK: 77662
Subject: Re: Old Releases Needed!
X-Newsreader: Forte Free Agent 1.21/32.243
Date: 7 Oct 2009 09:13:15 -0700
X-Trace: forums-1-dub 1254931995 10.22.241.152 (7 Oct 2009 09:13:15 -0700)
X-Original-Trace: 7 Oct 2009 09:13:15 -0700, vip152.sybase.com
Xref: forums-1-dub sybase.public.ase.general:28422
Article PK: 77665
On 7 Oct 2009 05:30:18 -0700, Jim Dawks wrote:
Is there a 12.5.4 developer edition. It includes the security
enhancements of 12.5.3a.
User-Agent: Thunderbird 220.127.116.11 (Windows/20070221)
Subject: Re: Old Releases Needed!
Content-Type: multipart/mixed; boundary="------------000603060107010101010502"
X-Antivirus: avast! (VPS 091004-0, 10/04/2009), Outbound message
Date: 7 Oct 2009 09:21:13 -0700
X-Trace: forums-1-dub 1254932473 10.22.241.152 (7 Oct 2009 09:21:13 -0700)
X-Original-Trace: 7 Oct 2009 09:21:13 -0700, vip152.sybase.com
Xref: forums-1-dub sybase.public.ase.general:28423
Article PK: 77666
12.5.3a was a bit of a dead-end spur off of the normal releases ... primarily provided as a quick means of providing a
few new features prior to implementing them into the normal releases.
The 'new configuration parameters' should also have shown up (probably) in a 12.5.4 release.
Where did you see the reference to 'new configuration parameters have been added in 12.5.3a' ?
Assuming this is a continuation of the 'number of open partitions' issue ... it would appear that there was a problem
with a past upgrade process; said problem was overlooked and not addressed, thus leading to the follow-on problems
you're seeing now. ("Duh, Mark!" ?)
You have a few options ...
1 - run through the normal upgrade gauntlet again, with an eye towards addressing any/all upgrade issues
2 - build a new 15.0.3 dataserver; create your databases 'for load' in the 15.0.3 dataserver; dump the 12.5.2 (12.5.3?)
databases and load into the newly built 15.0.3 dataserver [downside to this method is that you'll need to manually
synce the data from the 12.5.x master database with the 15.0.x master database, eg, syslogins, sysloginroles, any user
objects in the master database, etc]
3 - try to patch the current 15.0.3 dataserver with the following ...
=================== ASE 15.0.3
-- log into the ASE 15.0.3 dataserver ...
-- allow updates to system tables
sp_configure 'allow updates',1
-- verify no 'number of open partitions' data in
-- configuration-related tables
select * from sysconfigures where config = 408
select * from syscurconfigs where config = 408
-- if there are records, delete them ...
delete sysconfigures where config = 408
delete syscurconfigs where config = 408
-- if any problems/errors, rollback and try again,
-- else commit the transaction
-- rollback tran
-- commit tran
# at this point, from an OS command line, bcp in the attached
# files to the master..sysconfigures and master..syscurconfigs
# tables, respectively
# these entries set the 'number of open partitions' value to 500;
# you can modify this later with sp_configure
# *.bcp files created with -c and default -r/-t settings
# *.bcp data was pulled from a ASE 15.0.3/ESD #1 dataserver
# at this point, with an OS editor, you need to add a
# 'number of open partitions' entry to the dataserver's *.cfg file
# add the 'number of open partitions' entry to the [Meta-Data Caches]
# section; result should look something like:
number of open databases = 30
number of open objects = DEFAULT
open object spinlock ratio = DEFAULT
number of open indexes = 100
open index hash spinlock ratio = DEFAULT
open index spinlock ratio = DEFAULT
partition groups = DEFAULT
partition spinlock ratio = DEFAULT
number of open partitions = DEFAULT <<-- new entry
NOTE: The white space preceding the parameter names is a single <tab>
-- now log back into the dataserver and disable the update of
-- system tables
sp_configure 'allow updates',0
-- at this point run your various checks (sp_monitorconfig, sp_configure
-- 'number of open partitions', shutdown/startup, upgrade, etc) to verify
-- that you've correctly patched your dataserver.
... and hope that's the only problem carried over from a previous failed upgrade
4 - contact Sybase TechSupport to see if they have any other suggestions on how to track down and fix issues leftover
from previous upgrade problems
408 500 497 457 500 500 100 2147483647 497 1 4 14010 number dynamic
408 500 number of open partitions 73 number of open partitions 30 -1