Installing as Plain SQL

For environments where you can't install a .control file — many managed/cloud PostgreSQL offerings don't grant filesystem access to the server at all. This is exactly the scenario orafce_no_c exists for (see Why Replace orafce with orafce_no_c): there's no C to compile, so a plain SQL script is enough to install everything a real extension would.

Installing

psql -d <database> -f install/orafce_no_c_standalone.sql

This creates the exact same 10 schemas and objects as the extension install mode — same functions, same behavior. The only differences are operational, not functional:

	CREATE EXTENSION	Standalone script
Appears in pg_extension	Yes	No
Version tracking	Yes	No
DROP EXTENSION works	Yes	No — use the uninstall script instead

If real orafce is already installed in this database, or any of the 10 target schema names already exists, this fails immediately with a clear error and rolls back cleanly — see Why It Refuses to Install Over Real orafce.

Uninstalling

psql -d <database> -f install/orafce_no_c_standalone_uninstall.sql

See Uninstalling for the full detail on what this removes.

Where these scripts come from

install/orafce_no_c_standalone.sql and install/orafce_no_c_standalone_uninstall.sql (and extension/orafce_no_c--1.0.sql, for the other install mode) are all generated from the per-package sources under sql/ — never hand-edited. See Regenerating the Install Scripts.

Continue to Installing the VARCHAR2/NVARCHAR2 Types.