Has anyone out there moved on to ASE 12+ on NT ?
We had information in this news group which indicated there was some tuning
work to be done after migration from ASE 11.5.1. I would take this to be the
usual minimal tuning work following an upgrade of any significance. Further
our initial plan would be to take the standard 12 features and not turn any
Our db's range from 2 GB to 30GB , with about 50 concurrent connections.
Has anyone else got a similar environment on NT and ASE 12+ ? If so, I would
appreciate some feedback on your experiences.
Thanking in advance.
Subject: ASE 12 and NT
Date: Mon, 4 Dec 2000 14:03:32 +1100
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
NNTP-Posting-Host: aupozx665.btal.com.au 220.127.116.11
Xref: forums-1-dub sybase.public.sqlserver.nt:1434
Article PK: 1088906
Date: Sun, 10 Dec 2000 08:32:15 -0400
From: Sheridan Martin <firstname.lastname@example.org>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
Subject: Re: ASE 12 and NT
Content-Type: text/plain; charset=us-ascii
NNTP-Posting-Host: cm-24-29-63-39.nycap.rr.com 18.104.22.168
Xref: forums-1-dub sybase.public.sqlserver.nt:1418
Article PK: 1088890
We have been experimenting with the installation of ASE 12.0 on NT. Actually we
went to Win2000 in part because we could never get a clean install of ASE 12.0
on NT 4.0 and we tried many times. Our intentions are to set up Sybase ASE on a
Laptop for use in demonstrating of our applications at locations where we can
not get a secure internet connection to our site. As I write this we have
retrenched again to 11.9.2.
We found that ASE 12.0 never installed without an error usually calling for a
DLL that it could not locate on NT 4.0 no matter how many or what level of
Service Packs we installed. I was unsure of what did not get installed or
completed as a result of this problem in that the Sybase server would come up
and appear to operate properly, but I did not want to live with it. We tried it
on several computers with the same message related to the missing DLL each
time. We found that when we installed on Windows 2000 the missing DLL problem
went away and we could get installations that completed without any problems.
This is not to say that Sybase 12.0 installations on Windows NT or Windows 2000
does not have other problems. The installation routine for Sybase 11.9.2
appears to have been written in C++ if I had to guess and runs without problems
almost every time. The installation routine for Sybase 12.0 was developed in
Java and it is timing temperamental as many Java apps are working in a Windows
desktop environment. So, sometimes the 12.0 installation will start up go a
certain distance and then hang. If you restart the installation it will begin
again and likely go to completion. I suggest that you do not have other
processes running in backgroud. I recommend that you let it settle down after
writing each screen before pressing the required keys to make selections to move
on, however it is also the case that if you walk away and wait to long you're
likely to find it frozen when you get back.
There are other issues with the 12.0 installation routine which I believe are
Java related and which I have not observed in the 11.9.2 installation. If you
have to restart or reinstall the Sybase Server given that there is no uninstall
outside of a product like Nortons Uninstall, you'll be coping files over files
that already exist. In this process the 12.0 installation routine has numerous
problems especially in recopying files to the following areas:
I should also mention that the above problem sometimes has occurred on a first
install when after having installed the Sysbase 12.0 server (disk 1) we then
installed the Sybase 12.0 client (disk 2) and it would find some files that are
redundant to those installed by the server entry it would stop.
From time to time which files in which folders are a problem will change. At
these points the installation will stop and after the posting the error message
to which you must press OK it discontinues operation. You then have to delete
that file maually and restart the install. Often multiple files in the same
folder are references each time stopping for you to remove the file. Some of
the files had attributes or locks on them which refused to go away even after
setting the computer down and restarting. After a while I knew which files in
which folder were effected and I would rename those folders at the begining of
each reinstallation and then go back and remove the folders the next time the
computer was restarted which works.
One Sybase 12.0 installation problem which may be Windows 2000 specific although
Sybase 11.9.2 does not have this problem in Win2000, so it may be the Java
related, is that it often does not make an entry in the Start menu. You lose the
references that you normally have to DSEDIT, Server Config, Help Files, etc.
The installation of the Sybase Enterprise Application Server on the same
computer can sometimes lead to problems which I believe may results from
installation conflists between the two suites determing where exactly the Sybase
directory is. I'm not sure whether it is better to install the ASE or the EAS
first. Server Config will sometimes start up with an error message indicating
that there is something wrong with its start up script.
The next recommendation I have is that you name the Administrator for the
Windows NT box 'sa'. If you don't do this every time you log into the ASE
server you'll be prompted with the name of the NT box administrator even though
you set up the ASE server with 'sa'. This is a nuisance and a small issue and
maybe there is another solution that I'm not aware of.
The Sybase 12.0 NT product makes extensive use of the Windows NT Registery.
There is no uninstall for the installed Sybase server objects. To remove a
server object that has been created you have to go into the registery and remove
all references. The Installation Guide suggests that you need only remove a few
references in locations such as HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Server. In
practice we found that t is best to remove all references to the Server Object
being removed. In addition it is best to go through the C:\Sybase folder
removing all files that make reference to the Server Object being removed. If
you remove all references for the server object in the C:\Sybase folder you will
have to reinstall the ASE server and thus you will have to rename and then
remove all of the conflicting folders. If this process is not followed you will
likely find parameters or other references to the removed Server poping up in
There should be a built in Server Object removal routine but there is not which
brings me to my first recommendation. Even though the the Server Config routine
prompts you with the name of the NT Server when you create a new Sybase server
object, don't use it. If you have to go through the registery and the C:\Sybase
folder removing all references to the server object that you wish to remove or
recreate, you don't want to accidently remove entries that reference the the
Windows NT server. Even when done right the removal of references to the server
object from the registery can result in messed registries which leads me to a
second recommendation . You need Nortons SystemWorks 2001 or a similiar product
to keep things clean in the registery especially if you are going to go in and
To get clean installs after a period on testing we found that it was best to
completely ditch the Windows NT system and start rebuilding from scratch
reinstalling Windows and then the Sybase server, then related Sybase Enterprise
Applications Server software, and then the ESDs on numerous occasions.
This leads to my last recommendation for now which is to use a product like
Nortons Ghost to make image copies of the server as you go along. In that way
you can recover from mistakes and move foward without having to reinstall from
the ground up. I recommend the addition of a hard disk on the computer to which
you can store images as you go along advancing your server.
I hope that sharing some of our experiences will be helpful in advancing the
cause. For now we have retreated to 11.9.2 in order to get our demo laptop
Date: Thu, 14 Dec 2000 17:16:45 -0500
Subject: Re: ASE 12 and NT
References: <rXOPUDaXAHA.email@example.com> <3A3377CF.1C3AB7D5@nycap.rr.com>
Content-Type: text/plain; charset="us-ascii"
Xref: forums-1-dub sybase.public.sqlserver.nt:1400
Article PK: 1088870
I have to laugh.
You should be on Oracle, the java installer is far
It works wonderfully on multiple platforms
on our sites (SGI, HPUX, NT).
Sybase installers are a mess.