• Re: Oracle Rdb

    From gcalliet@gerard.calliet@pia-sofer.fr to comp.os.vms on Thu Mar 19 09:53:07 2026
    From Newsgroup: comp.os.vms

    Le 18/03/2026 |a 19:30, Simon Clubley a |-crit-a:
    On 2026-03-18, Arne Vajh|+j <arne@vajhoej.dk> wrote:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not be
    made available for VSI OpenVMS x86-64. Furthermore, extended support for
    Oracle Rdb on OpenVMS Integrity will not be extended beyond the end of 2027. >> </quote>

    Arne


    To be honest, that's not a major surprise at this point, given how much
    it had already been delayed by.

    It means Rdb people now have a 2 year window to move away from Rdb (and probably VMS as well).

    I wonder how many people are still using Rdb and how many had already
    seen the writing on the wall and already moved away.

    Simon.

    For the users of rdb, who know perfectly how Kevin Duffy (manager for
    VMS products at Oracle) plays with end support dates, 2027 is not the
    real date. Kevin, a lot of time, was able to successfully change these
    dates.

    It's worth noting that this communication is a VSI communication. As
    usual it's impossible to understand the whys, but VSI, since almost two
    years did its best to accelerate the way off rdb. This communication
    about this 2027 is one of these ways of practicing acceleration.

    VSI could make an offer to get back rdb on its natural environment?
    Realy a good idea - I have had it for years :) -. And idem about the
    whys, is has never been an idea for VSI since years.

    Would it be a signal to go out from VMS? Yes for the rdb users, and yes
    also for the non-users of rdb. Because it is one of the very bad signals
    about the VMS ecosystem as a whole.

    About Oracle. Oracle is a killer. Remember Itanium, remember MySql...
    Again the incomprehensible whys: VSI promotes use of the Oracle Cloud,
    and don't negociate with Oracle about rdb. "Kill me, my dear" seems to
    be the moto of VSI.

    About porting out to another database. I appreciate the unentional
    humour about the way you can use IA to do the job. But it's all about legacies. You have got a lot of idiomatic uses of your database, with a
    lot of idiomatic uses of your OS. You have got decades of translation of
    your job in these peculiar langages - I use the term as general langage
    -. If you have to go out the database, which involves a radical change
    around your idiomatics, you go out the both.

    Do you know Ikea? Worldwide seller of furniture. Hundreds of VMS servers around the world. Years ago, our genius VSI sales "helped" Ikea
    anticipate the end of rdb and proposed a a workaround. What do you
    think? Ikea has know abandoned VMS.

    So, Simon, yes it seems VMS users wil go out VMS. The only good
    information I can give is they will have more than two years to do the job.

    G|-rard Calliet
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From jgd@jgd@cix.co.uk (John Dallman) to comp.os.vms on Thu Mar 19 10:12:00 2026
    From Newsgroup: comp.os.vms

    In article <10pfeo6$2or$1@panix2.panix.com>, kludge@panix.com (Scott
    Dorsey) wrote:

    Well, there is that. But mostly I am thinking about them buying Sun
    because they wanted Java and then being stuck with the good part of
    Sun which they couldn't figure out what to do with and eventually
    let collapse. I liked Sun.

    I'm afraid you have the sequence mixed up. Sun was in serious trouble
    before Oracle bought them. Linux on x86-64 was taking over several of
    Sun's markets rapidly.

    Oracle had a plan for the Sun hardware business, which was to sell
    integrated packages of Sun hardware and Oracle software, after tuning the
    OS and software to offer better value for money, albeit at a high price.
    Sadly, it turned out that Sun hardware and Solaris were already pretty well-tuned for Oracle database, so the expected benefits weren't possible.


    Also, dealing with Oracle is no fun, so Linux carried on taking Sun's
    markets.

    John
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Volker Halle@volker_halle@hotmail.com to comp.os.vms on Thu Mar 19 11:46:04 2026
    From Newsgroup: comp.os.vms

    Am 18.03.2026 um 16:31 schrieb Arne Vajh|+j:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not be
    made available for VSI OpenVMS x86-64. Furthermore, extended support for Oracle Rdb on OpenVMS Integrity will not be extended beyond the end of
    2027.
    </quote>

    Arne,

    would you care to mention the original source of this quote ?

    Volker.
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From jgd@jgd@cix.co.uk (John Dallman) to comp.os.vms on Thu Mar 19 10:46:00 2026
    From Newsgroup: comp.os.vms

    In article <n21rriF4hnuU1@mid.individual.net>,
    gerard.calliet@pia-sofer.fr (gcalliet) wrote:

    About Oracle. Oracle is a killer. Remember Itanium, remember
    MySql...

    How did Oracle kill Itanium?

    They wanted to stop producing Oracle DB on HP-UX Itanium, but that was a sensible commercial decision. Oracle are unpleasant, but they aren't
    stupid. I produced commercial HP-UX and Windows software for Itanium,
    which had nothing to do with Oracle. It was a continual pain in the neck,
    with poor performance, high costs, poor sales and plenty of technical
    problems. The thing that killed Itanium was its own poor design and lack
    of large-scale commercial success.

    I'm pretty sure that VMS on Itanium was the most commercially successful Itanium operating system. I say that knowing that VMS market share
    continually declined, and the whole technical computing segment was lost.


    John
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Chris Townley@news@cct-net.co.uk to comp.os.vms on Thu Mar 19 11:00:51 2026
    From Newsgroup: comp.os.vms

    On 18/03/2026 20:32, Arne Vajh|+j wrote:
    What are the options for Rdb users on VMS x86-64?

    Here is my take.

    It depends on the application technology:
    1) C/C++
    2) Cobol/Basic/Pascal/Fortran
    3) Java/Groovy/Kotlin/Scala
    4) Python/PHP
    and the desired architecture:
    A) application on VMS & database on VMS
    B) application on VMS & database on Linux/Windows

    1A - C/C++ application on VMS & database on VMS

    Supported by vendors/projects:
    * Mimer
    * SQLite

    Working:
    * H2 in PostgreSQL mode [Note: some limitations including no cursor!]

    Possible future:
    * MySQL

    1B - C/C++ application on VMS & database on Linux/Windows

    Supported by vendors/projects:
    * PostgreSQL
    * Mimer
    * SQLServer via FreeTDS
    * practically everyone via SqlRelay [Note: adds an extra tier to solution]

    Working:
    * PostgreSQL/Mimer/SQLServer via UnixODBC [I suspect this may soon move
    to VSI supported]

    Possible future:
    * MySQL

    2A - Cobol/Basic/Pascal/Fortran application on VMS & database on VMS

    Supported by vendors/projects:
    * Mimer

    Working:
    * SQLite
    * H2 in PostgreSQL mode [Note: some limitations including no cursor!]

    Possible future:
    * MySQL

    2B - Cobol/Basic/Pascal/Fortran application on VMS & database on Linux/ Windows

    Supported by vendors/projects:
    * Mimer
    * practically everyone via SqlRelay [Note: adds an extra tier to solution]

    Working:
    * PostgreSQL
    * SQLServer via FreeTDS
    * PostgreSQL/Mimer/SQLServer via UnixODBC

    Possible future:
    * MySQL

    3A - Java/Groovy/Kotlin/Scala application on VMS & database on VMS

    Supported by vendors/projects:
    * Mimer
    * Derby/H2/HSQLDB
    * SQLite

    3B - Java/Groovy/Kotlin/Scala application on VMS & database on Linux/ Windows

    Supported by vendors/projects:
    * practically everyone

    4A - Python/PHP application on VMS & database on VMS

    Supported by vendors/projects:
    * Mimer
    * SQLite

    Working:
    * Derby/H2/HSQLDB via PJBS [Note: adds an extra tier to solution]

    4B - Python/PHP application on VMS & database on Linux/Windows

    Supported by vendors/projects:
    * MySQL
    * Mimer

    Working:
    * practically everyone via PJBS [Note: adds an extra tier to solution]

    Possible future:
    * PostgreSQL

    Arne


    Don't forget SharkSQL - they seem to be about to release a field test
    version
    --
    Chris
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 07:47:46 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 6:46 AM, Volker Halle wrote:
    Am 18.03.2026 um 16:31 schrieb Arne Vajh|+j:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not be
    made available for VSI OpenVMS x86-64. Furthermore, extended support
    for Oracle Rdb on OpenVMS Integrity will not be extended beyond the
    end of 2027.
    </quote>

    would you care to mention the original source of this quote ?

    :-)

    VSI agenda for the bootcamp!

    https://events.vmssoftware.com/malmo-bootcamp-2026-agenda

    Go down to Brett Cameron's session.

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 07:57:00 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 7:00 AM, Chris Townley wrote:
    On 18/03/2026 20:32, Arne Vajh|+j wrote:
    What are the options for Rdb users on VMS x86-64?

    Here is my take.

    Don't forget SharkSQL - they seem to be about to release a field test version

    Kerry Main started mentioning SharkSQL as an option in 2018.

    :-)

    I would like to see it first.

    And despite all the brilliant technical ideas in the
    product (I have read some of the presentations and it
    sounds very impressive), then it will be fighting an
    uphill battle: nobody knows about it, many customers
    are looking for more standardized (standardized not as
    in ISO standard but as in so widely used that other
    technologies support it out of the box) database
    technology.

    Arne


    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Craig A. Berry@craigberry@nospam.mac.com to comp.os.vms on Thu Mar 19 07:05:46 2026
    From Newsgroup: comp.os.vms


    On 3/18/26 7:57 PM, Arne Vajh|+j wrote:
    But now the alternatives are:
    * app/VMS+Rdb/VMS -> app/VMS+PgSQL/Linux
    * app/VMS+Rdb/VMS -> app/Linux+PgSQL/Linux

    I know you mentioned it elsewhere, but for some reason you omitted here
    that the least disruptive alternative is probably staying on VMS with Mimer:

    <https://developer.mimer.com/article/migration-from-rdb-on-openvms/>

    I've never used it, much less done one of these migrations, but I think
    anyone trying to figure out what to do in the absence of Rdb would be
    remiss not to look into this as an option.
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 08:24:07 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 8:05 AM, Craig A. Berry wrote:
    On 3/18/26 7:57 PM, Arne Vajh|+j wrote:
    But now the alternatives are:
    * app/VMS+Rdb/VMS -> app/VMS+PgSQL/Linux
    * app/VMS+Rdb/VMS -> app/Linux+PgSQL/Linux

    I know you mentioned it elsewhere, but for some reason you omitted here
    that the least disruptive alternative is probably staying on VMS with
    Mimer:

    Yes. Here I was talking about the migration off VMS math before
    and after.

    Staying on VMS is an option as well. Option 1A, 2A, 3A and 4A in the
    other long post.

    And for that the only two solutions are SQLite and Mimer
    (unless you happens to use a JVM language which gives you
    several extra options).

    If you want to keep everything on VMS and you need a real
    database server, then Mimer is the only option!

    I will recommend that people consider whether they really
    need a database server or if SQLite will do just fine.

    Things has changed the last 35 years:
    * HW resources has increased like X1000 and what back then
    required a "huge" database server may today work fine
    with a "small" embedded database
    * the access model has likely changed from:
    multiple clients on VMS->database on VMS
    to:
    multiple client on PC->one server on VMS->database on VMS
    which reduces the benefits of a database server over an embedded
    database.

    <https://developer.mimer.com/article/migration-from-rdb-on-openvms/>

    I've never used it, much less done one of these migrations, but I think anyone trying to figure out what to do in the absence of Rdb would be
    remiss not to look into this as an option.

    I have played a little with it.

    Mimer is definitely a nice database!

    http://www.vajhoej.dk/arne/articles/vmsdb.html#mimer

    https://www.vajhoej.dk/arne/articles/vmsdbx.html

    https://www.vajhoej.dk/arne/articles/cdb.html#mimerc

    has some examples.

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 11:20:01 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 7:47 AM, Arne Vajh|+j wrote:
    On 3/19/2026 6:46 AM, Volker Halle wrote:
    Am 18.03.2026 um 16:31 schrieb Arne Vajh|+j:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not
    be made available for VSI OpenVMS x86-64. Furthermore, extended
    support for Oracle Rdb on OpenVMS Integrity will not be extended
    beyond the end of 2027.
    </quote>

    would you care to mention the original source of this quote ?

    :-)

    VSI agenda for the bootcamp!

    https://events.vmssoftware.com/malmo-bootcamp-2026-agenda

    Go down to Brett Cameron's session.

    Hmmm.

    The question came up in the 9.2-4 webinar.

    <quote>
    PG Peter Gorley 11:02 AM
    Hello, on the agenda for the Malmo boot camp, there is a session from
    Brett Cameron and in the description it says "Oracle has recently
    announced that the Oracle Rdb database will not be made available for
    VSI OpenVMS x86-64". We were unaware of this and have not seen any
    release from Oracle, could you elaborate on this?

    VS VMS Software 11:17 AM
    Hi Peter, Thank you for your question. This seems to be a mistake in the presentation abstract, we'll be amending it shortly. We will be
    contacting yourself and other customers on this topic ASAP.
    </quote>

    Interesting!

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 11:22:16 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 11:20 AM, Arne Vajh|+j wrote:
    On 3/19/2026 7:47 AM, Arne Vajh|+j wrote:
    On 3/19/2026 6:46 AM, Volker Halle wrote:
    Am 18.03.2026 um 16:31 schrieb Arne Vajh|+j:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not
    be made available for VSI OpenVMS x86-64. Furthermore, extended
    support for Oracle Rdb on OpenVMS Integrity will not be extended
    beyond the end of 2027.
    </quote>

    would you care to mention the original source of this quote ?

    :-)

    VSI agenda for the bootcamp!

    https://events.vmssoftware.com/malmo-bootcamp-2026-agenda

    Go down to Brett Cameron's session.

    Hmmm.

    The question came up in the 9.2-4 webinar.

    <quote>
    PG Peter Gorley 11:02 AM
    Hello, on the agenda for the Malmo boot camp, there is a session from
    Brett Cameron and in the description it says "Oracle has recently
    announced that the Oracle Rdb database will not be made available for
    VSI OpenVMS x86-64". We were unaware of this and have not seen any
    release from Oracle, could you elaborate on this?

    VS VMS Software 11:17 AM
    Hi Peter, Thank you for your question. This seems to be a mistake in the presentation abstract, we'll be amending it shortly. We will be
    contacting yourself and other customers on this topic ASAP.
    </quote>

    Interesting!

    So no surprise that I had not seen it mentioned before.

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 11:30:13 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 11:20 AM, Arne Vajh|+j wrote:
    On 3/19/2026 7:47 AM, Arne Vajh|+j wrote:
    On 3/19/2026 6:46 AM, Volker Halle wrote:
    Am 18.03.2026 um 16:31 schrieb Arne Vajh|+j:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not
    be made available for VSI OpenVMS x86-64. Furthermore, extended
    support for Oracle Rdb on OpenVMS Integrity will not be extended
    beyond the end of 2027.
    </quote>

    would you care to mention the original source of this quote ?

    :-)

    VSI agenda for the bootcamp!

    https://events.vmssoftware.com/malmo-bootcamp-2026-agenda

    Go down to Brett Cameron's session.

    Hmmm.

    The question came up in the 9.2-4 webinar.

    <quote>
    PG Peter Gorley 11:02 AM
    Hello, on the agenda for the Malmo boot camp, there is a session from
    Brett Cameron and in the description it says "Oracle has recently
    announced that the Oracle Rdb database will not be made available for
    VSI OpenVMS x86-64". We were unaware of this and have not seen any
    release from Oracle, could you elaborate on this?

    VS VMS Software 11:17 AM
    Hi Peter, Thank you for your question. This seems to be a mistake in the presentation abstract, we'll be amending it shortly. We will be
    contacting yourself and other customers on this topic ASAP.
    </quote>

    Interesting!

    The bootcamp agenda has been updated. It now says:

    <quote>
    It is possible that the Oracle Rdb database will not be made available
    for VSI OpenVMS x86-64. Furthermore, extended support for Oracle Rdb on OpenVMS Integrity will not be extended beyond the end of 2027.
    </quote>

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Simon Clubley@clubley@remove_me.eisner.decus.org-Earth.UFP to comp.os.vms on Thu Mar 19 19:12:20 2026
    From Newsgroup: comp.os.vms

    On 2026-03-19, Arne Vajhoj <arne@vajhoej.dk> wrote:

    The bootcamp agenda has been updated. It now says:

    <quote>
    It is possible that the Oracle Rdb database will not be made available
    for VSI OpenVMS x86-64. Furthermore, extended support for Oracle Rdb on OpenVMS Integrity will not be extended beyond the end of 2027.
    </quote>


    Hmmm. It's very unusual for someone to make _that_ kind of a mistake, given that these materials normally need to be reviewed and approved at multiple levels.

    I also notice the correction above doesn't outright deny the original
    wording. Is the original wording what VSI actually believes is likely
    to happen even though a formal announcement has not yet been made ?

    Simon.
    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 15:32:33 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 3:12 PM, Simon Clubley wrote:
    On 2026-03-19, Arne Vajh|+j <arne@vajhoej.dk> wrote:
    The bootcamp agenda has been updated. It now says:

    <quote>
    It is possible that the Oracle Rdb database will not be made available
    for VSI OpenVMS x86-64. Furthermore, extended support for Oracle Rdb on
    OpenVMS Integrity will not be extended beyond the end of 2027.
    </quote>

    Hmmm. It's very unusual for someone to make _that_ kind of a mistake, given that these materials normally need to be reviewed and approved at multiple levels.

    It is sort of a technical presentation about database migrations and
    options available. Maybe the business people did not check it
    until someone told them about it.

    I also notice the correction above doesn't outright deny the original wording. Is the original wording what VSI actually believes is likely
    to happen even though a formal announcement has not yet been made ?

    Either there has been a total communication fuckup. Or VSI tech
    people are a lot faster coming up with technical alternatives
    than Oracle business and legal are agreeing on a specific wording
    in an announcement to customers.

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.vms on Thu Mar 19 22:52:22 2026
    From Newsgroup: comp.os.vms

    On Wed, 18 Mar 2026 21:47:20 -0400, Arne Vajh|+j wrote:

    OpenZFS is CDDL and used by Linux, but is not an Oracle product.

    Neither is the entire rest of the Linux stack. That doesnrCOt stop
    Oracle from offering it; why not ZFS as well?
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.vms on Thu Mar 19 22:53:49 2026
    From Newsgroup: comp.os.vms

    On Thu, 19 Mar 2026 10:12 +0000 (GMT Standard Time), John Dallman wrote:

    Linux on x86-64 was taking over several of Sun's markets rapidly.

    It also ran quite nicely on SunrCOs own SPARC hardware -- better than
    Solaris did, in fact.

    I remember a comment by Larry McVoy (he of BitKeeper fame) to this
    effect, from many decades ago. Danged if I could find it again ...

    Also, dealing with Oracle is no fun, so Linux carried on taking Sun's markets.

    And now Oracle is offering its own Linux distro. So if you want Linux
    without the fun, you know where to go ...
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Thu Mar 19 20:31:35 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 6:52 PM, Lawrence DrCOOliveiro wrote:
    On Wed, 18 Mar 2026 21:47:20 -0400, Arne Vajh|+j wrote:
    OpenZFS is CDDL and used by Linux, but is not an Oracle product.

    Neither is the entire rest of the Linux stack. That doesnrCOt stop
    Oracle from offering it; why not ZFS as well?

    Oracle Linux is a RHEL clone.

    Redhat decided not to put OpenZFS in RHEL.

    I believe that decision was not driven by a quality
    assessment of OpenZFS but from a legal assessment
    of the potential issues of a GPL kernel and a
    CDDL loadable kernel module.

    Canonical made a different conclusion about
    that topic.

    RHEL and clones including Oracle Linux can
    install OpenZFS fine using dnf if the customer
    wants it.

    Arne

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.os.vms on Fri Mar 20 21:44:27 2026
    From Newsgroup: comp.os.vms

    In article <10pfkj8$9ehs$1@dont-email.me>,
    Arne Vajh|+j <arne@vajhoej.dk> wrote:
    On 3/18/2026 9:36 PM, Lawrence DrCOOliveiro wrote:
    On Wed, 18 Mar 2026 20:36:44 -0400, Arne Vajh|+j wrote:
    But for Solaris then Oracle did offer an alternative: their RHEL
    clone Oracle Linux.

    Too bad if yourCOre using ZFS on Solaris, because OraclerCOs Linux doesnrCOt >> support ZFS. It does offer btrfs, though.

    Odd that Oracle wonrCOt support its own home-grown technology, isnrCOt it? >> Almost as though they donrCOt have confidence in it any more ...

    There is ZFS and there is ZFS.

    Oracle ZFS is closed source and putting that in a Linux kernel module
    would be a license problem.

    Not really. ZFS was released with OpenSolaris, and is under the
    CDDL. Any changes made since Oracle's acquisition of Sun, when
    they decided to un-open Solaris, are owned by Oracle: they could
    simply choose to release them under the CDDL. It may be
    possible to release under a different license, but I suspect
    that is hairier legally.

    OpenZFS is CDDL and used by Linux, but is not an Oracle product.

    OpenZFS is a descendent of the original ZFS code, taken from OpenSolaris/illumos. It has diverged, but there is some cross-
    pollination (mostly from OpenZFS into ZFS in illumos; I presume
    some goes into Solaris as well).

    Oracle's mishandling of ZFS (or, for that matter, Solaris) has
    nothing to do with technology, or even licensing, and all to do
    with their business practices and management. Sun's failure
    similarly.

    - Dan C.

    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.os.vms on Fri Mar 20 22:34:59 2026
    From Newsgroup: comp.os.vms

    On Thu, 19 Mar 2026 20:31:35 -0400, Arne Vajh|+j wrote:

    On 3/19/2026 6:52 PM, Lawrence DrCOOliveiro wrote:

    On Wed, 18 Mar 2026 21:47:20 -0400, Arne Vajh|+j wrote:

    OpenZFS is CDDL and used by Linux, but is not an Oracle product.

    Neither is the entire rest of the Linux stack. That doesnrCOt stop
    Oracle from offering it; why not ZFS as well?

    Oracle Linux is a RHEL clone.

    Redhat decided not to put OpenZFS in RHEL.

    I believe that decision was not driven by a quality assessment of
    OpenZFS but from a legal assessment of the potential issues of a GPL
    kernel and a CDDL loadable kernel module.

    Canonical made a different conclusion about that topic.

    Is Oracle afraid of lawsuits, do you think? Who do you suppose might
    sue them?
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Simon Clubley@clubley@remove_me.eisner.decus.org-Earth.UFP to comp.os.vms on Mon Mar 23 19:46:37 2026
    From Newsgroup: comp.os.vms

    On 2026-03-20, Dan Cross <cross@spitfire.i.gajendra.net> wrote:

    Oracle's plans weren't bad, but the market had fundamentally
    changed. They had spent so many years trying to compete against
    IBM for the enterprise space, they just gave away the low- and
    middle-end. The gap between Oracle's products and open source
    competitors in e.g. the database realm was narrowing rapidly.
    That meant there wasn't as much of a need to go with Oracle's
    preferred platform: if I wasn't using Oracle's RDBMS, what did
    it matter? Also, many of their customers had already been
    burned by vendor lock-in and were wary of putting all their
    eggs in Oracle's basket.


    Interesting viewpoint. So what you are saying is that Oracle did a DEC ?

    If true, I guess that wasn't a uniquely DEC failing after all.

    Simon.
    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.
    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.os.vms on Tue Mar 24 18:27:23 2026
    From Newsgroup: comp.os.vms

    In article <10ps5at$ei2s$1@dont-email.me>,
    Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
    On 2026-03-20, Dan Cross <cross@spitfire.i.gajendra.net> wrote:

    Oracle's plans weren't bad, but the market had fundamentally
    changed. They had spent so many years trying to compete against
    IBM for the enterprise space, they just gave away the low- and
    middle-end. The gap between Oracle's products and open source
    competitors in e.g. the database realm was narrowing rapidly.
    That meant there wasn't as much of a need to go with Oracle's
    preferred platform: if I wasn't using Oracle's RDBMS, what did
    it matter? Also, many of their customers had already been
    burned by vendor lock-in and were wary of putting all their
    eggs in Oracle's basket.


    Interesting viewpoint. So what you are saying is that Oracle did a DEC ?

    Not exactly. DEC bet the farm on VAX, then tried to save
    themselves from the sinkhole that VAX 9000 opened up, but it was
    too little, too late. Oracle's major crop is the RDBMS, and it
    continues to generate huge amounts of margin dollars.

    Rather, I think that Oracle tried to pull an IBM: they saw how
    IBM pivoted to services and how handsomely that paid, and I
    think they wanted to do something similar, where you could go to
    Oracle and get a complete soup-to-nuts solution, running their
    software on their hardware, all supported by their services
    organization.

    If true, I guess that wasn't a uniquely DEC failing after all.

    Oh, I don't think that DEC's failure was unique at all. Sun
    definitely pulled a DEC in a lot of ways: they bet too much on
    SPARC and failed to see that Solaris was really the thing that
    they could have tried to make an industry standard. They
    _almost_ succeeded with Java, but it was clear that they didn't
    understand how to monetize that.

    - Dan C.

    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@arne@vajhoej.dk to comp.os.vms on Sat Mar 28 10:28:23 2026
    From Newsgroup: comp.os.vms

    On 3/19/2026 4:53 AM, gcalliet wrote:
    Le 18/03/2026 |a 19:30, Simon Clubley a |-crit-a:
    On 2026-03-18, Arne Vajh|+j <arne@vajhoej.dk> wrote:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not be
    made available for VSI OpenVMS x86-64. Furthermore, extended support for >>> Oracle Rdb on OpenVMS Integrity will not be extended beyond the end
    of 2027.
    </quote>

    It means Rdb people now have a 2 year window to move away from Rdb (and
    probably VMS as well).

    For the users of rdb, who know perfectly how Kevin Duffy (manager for
    VMS products at Oracle) plays with end support dates, 2027 is not the
    real date. Kevin, a lot of time, was able to successfully change these dates.

    https://forum.vmssoftware.com/viewtopic.php?f=30&t=9736

    Arne

    --- Synchronet 3.21f-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.os.vms on Sat Mar 28 16:38:17 2026
    From Newsgroup: comp.os.vms

    In article <69c7e585$0$679$14726298@news.sunsite.dk>,
    Arne Vajh|+j <arne@vajhoej.dk> wrote:
    On 3/19/2026 4:53 AM, gcalliet wrote:
    Le 18/03/2026 |a 19:30, Simon Clubley a |-crit-a:
    On 2026-03-18, Arne Vajh|+j <arne@vajhoej.dk> wrote:
    I don't think have seen it mentioned before.

    <quote>
    Oracle has recently announced that the Oracle Rdb database will not be >>>> made available for VSI OpenVMS x86-64. Furthermore, extended support for >>>> Oracle Rdb on OpenVMS Integrity will not be extended beyond the end
    of 2027.
    </quote>

    It means Rdb people now have a 2 year window to move away from Rdb (and
    probably VMS as well).

    For the users of rdb, who know perfectly how Kevin Duffy (manager for
    VMS products at Oracle) plays with end support dates, 2027 is not the
    real date. Kevin, a lot of time, was able to successfully change these
    dates.

    https://forum.vmssoftware.com/viewtopic.php?f=30&t=9736

    How very sad. Condolences to his family and friends.

    - Dan C.

    --- Synchronet 3.21f-Linux NewsLink 1.2