Oracle Database 12.2.0.1 – 19c Non-CDBĪnd again the same process for non-CDBs in Oracle Database 12.2.0.1: $ sqlplus / as sysdba SQL> no leftovers and a fairly quick execution. The removal process for OWM is flawless: $ sqlplus / as sysdbaĪnd the same process works in this release of the database: $ sqlplus / as sysdba
#WORKSPACE MANAGER SSB4 HOW TO#
Please use MOS Note: 727765.1 – How to Determine if Workspace Manager is Being Used? to check whether OWM is used in your database before removing it. In general there is a MOS Note: 263428.1 – How to De-install Oracle Workspace Manager available. This is the reason why some people may want to remove OWM afterwards. The b script executes in the CreateDBCatalog.sql while all other component creation scripts reside in a different section of the create-process. You can’t deselect OWM during database creation. I’m not recommend to remove OWM without any reasons. OWM has even its own manual with 350 pages. OWM enables application developers and DBAs to manage current, proposed and historical versions of data in the same database.
Oracle Workspace Manager (OWM) is a pretty cool feature of the Oracle Database. You’ll find links to monitor proper component removal there as well as in the SQL Scripts Repository on this blog. Oracle Workspace Manager (OWM) Clean Up in Oracle Database 11.2-19cīefore you start removing anything from your database please make sure you read my introductory blog post about how to Remove and Clean Up Components from Oracle 11.2 – 19c. Therefore as part of my “Clean Up” blog series I will repeat myself just a bit but in a consistent format. Yet I didn’t cover all currently supported releases from Oracle Database 11.2.0.4 to Oracle Database 12.2.0.1. I have blogged about Oracle Workspace Manager (OWM) clean up in Oracle Database 11.2-19c just a few weeks ago:
0 kommentar(er)
