we are planning to extract/copy a very small part of our main Database (Oracle 11g Standard), plus the related Windows client application,
to another environment/PC which will be isolated from our company's infrastructure.
Due to extremely reduced functionality (only a few tables), there won't be the need for a standard edition, but It would be extremely nice if we could use the same client program,
as we do in our main database environment.
Will we have to pay for this use? Because it will be not for testing or development.
Or is express edition free for all types of use?
I'm not sure about that, because some parts of Oracle Database licensing informations are distinguishing between production and development use.
Thank you for answering my question.
Express Edition is free for production use. It only uses 1 CPU (even if more are available) and is limited to 11GB of data.
Make sure you are not using the program for development, design, manufacture or production of nuclear, chemical or biological weapons of mass destruction or development of missile technology; AND you are not resident or exporting the program to Balkans, Belarus, Burma, Cote d'Ivoire, Cuba, Democratic Republic of the Congo, Iraq, Iran, Lebanon, Libya, North Korea, Somalia, Sudan and Syria; AND the 1GB RAM, 11GB user data, single instance on one processor restrictions are ok with your SDLC... Roll out the system into production :)
I am very sure that our PC Magazines and Books we produce, are not of any kind of chemical or biological weapon.
And they are only selled in Germany, and you can read them without being afraid that the book detonates itself, after you've read it.
Futhermore, the related database and it's Software is not going anywhere else but Germany, too.
But thanks for the advice
I'm running it in production, and have run into some issues where I recommended to management to just spring the few hundred bucks for SE.
The basic problem is it has the bugs of a first release. For my system, a few have been minor, but there has been an extreme growth of the sysaux tablespace. For me, it wound up being simplest to just make a gold backup and restore that whenever the problem manifests, but I can only do that because I can reload all new data. I have to make more gold when DDL changes.
I think the lack of bugfixes turns XE from a great idea to a bad one. It's supposed to be appropriate for environments with no DBA, but that is just plain wrong.