Upgrade from 15.0.3 to 15.5 question

[LNielsen]

I am doing a upgrade from ASE 15.0.3 to ASE15.5. Do I just
shutdown the server, run the runInstaller in the same
directory as ASE 15.0.3, and then startup the server?

It seems too easy.

[Rob V [ Sybase ]]

Yes, that should basically be enough. Moving from 15.0.3 -> 15.5 is not a
major upgrade as from 12.5->15. Upgrading from 15.0.2 to 15.5 is very
similar to upgrading from 15.0.2 to 15.0.3.
Make sure the scripts (installmaster etc) have been loaded in 15.5 -- check
with sp_version.

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:r...@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------

<LNielsen> wrote in message news:4b57670b.610...@sybase.com...

[syb_dba]

If you receive compilation errors similar to the following,
then i would recommend running dbcc upgrade_object in each
of the databases:

"execution of procedure ProcName failed because of errors
parsing the source text in syscomments during upgrade."

We ran into some of these errors when upgrading from 15.0.2
to 15.0.3. Might apply to the upgrade to 15.5 also

[Cory Sane [TeamSybase]]

Rob,
Do you need a new license for sysam?
I tried last week and the server failed due to sysam errors.

--
Cory Sane
[TeamSybase]
Certified Sybase Associate DBA for ASE 15.0
"Rob V [ Sybase ]" <ro...@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY> wrote in message news:4b5789d6$1@forums-1-dub...

[Rob V [ Sybase ]]

Not that I know....

R.

"Cory Sane [TeamSybase]" <cory!=sane> wrote in message
news:4b5913ce$1@forums-1-dub...

[Wildthing]

If it helps I just did the same thing this weekend and have the
following issues:
If you're in a 64bit linux environment - make sure the LD_LIBRARY_PATH
points to $SYBASE/$SYBASE_OCS/lib3p64 - you get library errors on start
up without it. Wasn't an issue in 15.0.3.

LIKE operator not operating as it should eg WHERE Name LIKE "FRED%"
would pull "Fred Bloggs" but not "Fred". However Name like "FRE%" would
pull "Fred". Sybase looking into this at mo. Be aware. Anyone else with
any ideas would be helpful though.

We had some legacy 11.9.2 code that had "DATENAME(cdw,<datevalue>)"
always comes back as "Monday" - this worked fine in 15.0.3. Need to use
dw not cdw. Btw cdw still a type in DATEPART.

If I come across anything else I'll post.

Also

>>> "Tips, Tricks& Recipes for Sybase ASE" (ASE 15 edition)

[Bret Halford]

On 1/25/2010 4:20 AM, Wildthing wrote:

> LIKE operator not operating as it should eg WHERE Name LIKE "FRED%"
> would pull "Fred Bloggs" but not "Fred". However Name like "FRE%" would
> pull "Fred". Sybase looking into this at mo. Be aware. Anyone else with
> any ideas would be helpful though.

A few more details on this:

this issue seems to be only on case-insensitive sort orders.
however, the issue doesn't seem to be case sensitivity but that
the % wildcard isn't working properly as a match to 0 characters,
i.e., it doesn't match the end of string.

So Like "FRED%" returns "Fred." or "FRED." but not "Fred" or "FRED"

CR is 616224 (with 615102 marked as a duplicate)

[Wildthing]

If anyone else has the same issue use a PATINDEX instead - but dont use
PATINDEX("%",<VARCHAR>) - it won't work - Use PATINDEX("_%",<VARCHAR>)
instead.

I think the Sybase testing department get a big "F" on this one and owe
me a beer for the grief they've put me through. :)

[Wildthing]

Sybase Support and Engineering depts get "A+" though.

:D