It's a very long time since I did one, but the most secure way to deal with
the problem is to create an Oracle executable that does not include the
bits you don't want to pay for; but many years ago - for UNIX systems - I
would use "make" to create new libraries and executables.
If you go to $ORACLE_HOME/rdbms/lib you will find a file called ins_rdbms.mk,
this is the control file for make-ing Oracle. If you know where the log
files are for the Oracle installation you will find there a file called
something like "make.log". At the top of the file you'll find a line like:
/usr/bin/make -f ins_rdbms.mk clean rat_on part_on dm_on olap_on sdo_on
rac_off dnfs_off ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1/
In this line "part_on" is one of the targets for make, and if you search
ins_rdbms.mk you'll find the rule that applies for part_on; just below that
there's a rule for part_off.
So you could execute make, changing the command line you find to use
part_off instead of part_on (and changing the ORACLE_HOME/as appropriate.
However, there are 3 things I would do first:
a) Wait for a sanity check for someone who's done this some time in the
last 10 years; I haven't done it since 8i
b) Talk to whoever installs Oracle at your site to make sure that my
(potentially outdated) information about make is still okay
c) Do a complete Oracle software install to a new Oracle Home - because the
install might allow you to pick No-partitioning in the setup pages, and
it's far better to do this type of thing with the official mechanisms if
they exist.
d) If you have to mess about with make, do it on the second Oracle Home.
Regards
Jonathan Lewis
