I've never been able to get these instructions to work completely. Hopefully I'm making some obvious mistake that you'll be able to avoid. If you figure out what the problem is, let me know at developer@firstworks.com.
Installing a license for 12.5Unlike previous versions of Sybase ASE, version 12.5 needs to be licensed before it can be installed. If you downloaded Sybase ASE, you should have received an email from sybase with a license code in it. Follow these instructions to license Sybase ASE.
Log in as the sybase user.
Start the license server by running startd.sh $SYBASE/$SYBASE_SYSAM
Make sure lmgrd is running by running "ps -efa | grep lmgrd", sometimes it doesn't start.
The license manager client is a Java program. Sybase ASE ships with java version 1.2.2 but I've never been able to get the program to run properly under that version. I have been able to get it working with Sun's JDK 1.3.1. If you have Sun's JDK 1.3.1 installed, edit /opt/sybase-12.5/SYSAM/bin/lmgr and change JAVA_HOME=$SYBASE/shared-1_0/jre-1.2.2 to JAVA_HOME=/usr/java/jdk1.3.1_07.
Run lmgr. A graphical license manager application should pop up.
Leave the radio button for Ase checked and click Next.
When the "Do you have a Sybase Software Asset Management Certificate to register?" dialog pops up, click Yes.
On the screen titled "Enter the information provided on your Sybase License Certificate", enter the Order Number, Feature Name, Feature Count, Software Version and Authorization Code from the email you received from Sybase when you downloaded the software. Click Done.
Now that the software has been licensed, it can be initialized.
Initializing an 12.5 ServerAfter installing Sybase Adaptive Server Enterprise, you can initialize the server by following these steps.
First, su to the sybase user using the -l option.
su -l sybase
You should be presented with the a great deal of text.
Run asecfg. A dialog will appear. Click Configure a new server.
Another dialog will appear, prompting you to Click the check boxes for the types of servers to create and provide names for these servers.
select Adaptive Server
enter a server name, I usually use localhost but any name will do
select OK
A new dialog will appear, prompting you to enter filenames for Master and Sybsystemprocs device files, and device and database sizes for each.
enter /opt/sybase-12.5/ASE/master.dat for the Master device file
enter /opt/sybase-12.5/ASE/sybsystemprocs.dat for the Sybsystemprocs device file
Select Edit Advanced Adaptive Server Attributes
A new dialog will appear, prompting you to enter filenames for the Sybsystemdb device file, size and database sizes.
enter /opt/sybase-12.5/ASE/sybsystemdb.dat for the Sybsystemdb device file
Select Go Back
This should return you to the previous dialog.
Select Build Server!
A warning dialog may appear indicating that the files are not raw device files. Ignore this warning and select Yes to proceed.
A Status Output dialog will appear. As the database is built, the dialog provides feedback about the process. When it's done, select OK.
For me, this step always fails. I've tried lots of different things to try to make it work, but it never does. Hopefully it will work for you.You should now be returned to the original dialog. Click Exit.
Starting the Database at Boot TimeThe RPM distribution of Sybase ASE installs a script in /etc/rc.d/init.d which starts the database at boot time. For non-RPM distributions, you may need to install a script like the following. Replace /opt/sybase-11.9.2 with whatever directory Sybase ASE is installed in.
#!/bin/sh export SYBASE=/opt/sybase-12.5 export PATH=$PATH:$SYBASE/ASE-12.5/bin:$SYBASE/ASE-12.5/install case "$1" in start) for i in `ls $SYBASE/ASE-12.5/install/RUN_*` do su -c "startserver -f $i" sybase > /dev/null 2>&1; done ;; stop) kill `ps -efa | grep sybase | grep -v grep | awk '{print $2}'` ;; *) echo $"Usage: $0 {start|stop}" exit 1 esac exit 0
Install this script and run it with the "start" option to start up the database. Running it with the "stop" option shuts the database down. To access a database, it must be running.