The forum will be down for maintenance over the weekend of August 18-20, 2017. The forum will be shut down on the evening (EDT) of Friday, August 18. Downtime is unknown but may be up to two days. The forum will be restarted as soon as maintenance is complete.

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.

asked 30 Aug '13, 11:47

starter's gravatar image

starter
46225
accept rate: 0%

edited 30 Aug '13, 18:37

Volker%20Barth's gravatar image

Volker Barth
30.9k309457667


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

permanent link

answered 30 Aug '13, 11:54

Mark%20Culp's gravatar image

Mark Culp
23.2k9132273
accept rate: 40%

edited 30 Aug '13, 11:58

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?

permanent link

answered 30 Aug '13, 18:36

Volker%20Barth's gravatar image

Volker Barth
30.9k309457667
accept rate: 33%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×412
×52
×22

question asked: 30 Aug '13, 11:47

question was seen: 1,450 times

last updated: 30 Aug '13, 18:37