Problem: Applying Oracle Patch 184.108.40.206 incorrectly causes ArcSDE to stop working
Upgrading to Oracle Patch 220.127.116.11 incorrectly may cause problems affecting ArcSDE usage.
Investigation has revealed the following causes in the majority of cases:
-- Workflow issues when installing the Oracle patch. -- Oracle issues in relation to the install of the patch. See the listing of Metalink documents in the Solution below.
If the patch is installed correctly, it should work with ArcSDE. ESRI's has confirmed this.
Solution or Workaround
The following is the recommended upgrade path for applying database patches.
Setup ArcSDE at the accepted base version of the database; for example, ArcSDE 9.0 = Oracle 18.104.22.168.
Test to verify the functionality needed works as desired.
Take a full backup of the database.
Apply the database patch.
Restart ArcSDE and test to verify it functions as it did before DBMS patch was applied.
If a problem is encountered, contact an assigned Oracle representative. If need be, return to the previous version of the database.
Related Metalink Documents: Oracle Metalink Note: 263792.1 : 22.214.171.124 Patch Set - Known Issues Oracle Metalink Note: 271828.1 : Upgrade To 126.96.36.199 Hangs When Running Catpatch.Sql Note: 271084.1 ALERT: ORA-600[KSLAWE:!PWQ] RAISED IN V92040 OR V92050 ON SUN 64BIT ORACLE Oracle Metalink Note: 273506.1 : Errors While Applying 188.8.131.52 Patchset Bug 3527674 HPUX: 184.108.40.206 install fails on HP 11.00 Bug 3544619 Solaris: UDLM 220.127.116.11 is missing 18.104.22.168 Patch Set for Solaris 32bit Bug 3583686 : Oracle Spatial : SDO_FILTER against partitioned table