cancel
Showing results for 
Search instead for 
Did you mean: 

Install Sybase 12 Developers edition with OEM key?

Former Member
4,638

We have an update we’ve written to install Sybase 12 and copy the data from an old (Sybase 9) database to the new Sybase 12 version. We made this release a few months ago using the free developers version so we could test and insure it all worked. Now that we’ve officially become an OEM, we are trying to update the install by swapping out the developers version and replace it with the OEM version. We expected this to be an easy switch, but we’ve been having some issues replacing the developers version of Sybase 12 with the OEM version in our update. At one point during our testing we installed the developers version with the OEM key on a system, and Sybase logged the message “OEM Authenticated Version”. Does this mean the developers version is the same as the “OEM” version and only the key is different? If all we have to do is swap the developers key for the OEM key in our original install/upgrade to Sybase 12, that makes things a lot easier on us as we have a working install/upgrade with the developer’s version.

Accepted Solutions (0)

Answers (2)

Answers (2)

MarkCulp
Participant

The only file that you really need to swap out is the *.lic files in your original install (that you created using your developer key) to the .lic files that you installed (using your OEM key). All of the other files (from the developer version) will be identical... unless you have download/upgraded to a newer EBF/SP (in which case you can/should use the newer versions of the files).

You should also verify that your final install that you are deploying to your customers are in your OEM install (i.e. the set of files that you got on your computer when you used your OEM key). This is necessary because the OEM key that you are using may not actually install of the same files that you got on your computer when you used the developer key. I.e. Ensure that you are licensed to use all of the components that you are using.

HTH

VolkerBarth
Contributor
0 Kudos

The following FAQ shows a similar way by using the DBLIC tool with the -k option to change the product key afterwards:

Can I upgrade a SQL Anywhere 12 developer edition to a paid version?