-
Title
Note: Cannot install Compare Varray package because Oracle Spatial datatype is not installed. -
Description
When running ora_setup, the following notice/warning appear as the screen shot below shows:
"Loading Compare Package from
"/sw/splexsrc/splex8/util/sp_deq_pkg.plb"...Done.
Note: Cannot install Compare Varray package because Oracle Spatial datatype
is not installed.
Do you want to continue? [n] : “
-
Cause
The Oracle Spatial option is not installed in the database.
-
Resolution
The ora_setup installs some database objects in the SharePlex schema in the database. These objects include tables, sequences, packages, etc, among others. A package used by the Compare functionality for Spatial data type needs Oracle Spatial option installed in the database but such option is not installed in the database. There are 2 ways to handle this depending on your goal.
1. If you are not going to run compare/repair on Spatial data types, then you can simply ignore the notice and answer in affirmative (yes) as shown below so that the ora_setup will complete and the replication will work fine. The only functionality that will not work is compare/repair on tables having Spatial data type. Here is the screen shot of ora_setup to ignore the notice:
"Loading Compare Package from
"/sw/splexsrc/splex8/util/sp_deq_pkg.plb"...Done.
Note: Cannot install Compare Varray package because Oracle Spatial datatype
is not installed.
Do you want to continue? [n] : y
Will the current setup for sid: [DBCORT1] be used as source (including
cases as source for failover or master-master setups)? [y] : y
Setup of SharePlex objects successful . . .
Changing SharePlex connection database . . .
Setup completed successfully"
2. If you would rather install the Oracle Spatial option in the database first and then run ora_setup so that it is able to install the Compare Varray package successfully, you can choose to say “n” and re-run ora_setup once the Oracle Spatial option is successfully installed in the database. Also recompile objects as appropriate in the database.