![]() $ $ORACLE_HOME/perl/bin/perl -n 1 -c 'CDB$ROOT' -e -b owm_clean_cdb -d '''.''' bĪs a result of this two-phase-operation the clean up process from a Multitenant container database works flawless as well. $ $ORACLE_HOME/perl/bin/perl -n 1 -C 'CDB$ROOT' -e -b owm_clean_pdbs -d '''.''' b emoval from all PDBs including the PDB$SEED:.Hence to complete the removal successfully and without errors it must be split up in two phases: If all is done in one pass then you’ll receive this error sequence: ERROR at line 1:ORA-06598: insufficient INHERIT PRIVILEGES privilege In contrast the OWM removal from a CDB is a bit more complicated. SQL> leftovers and a fairly quick execution. 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 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. select count(*)įrom dbo.I have blogged about Oracle Workspace Manager (OWM) clean up in Oracle Database 11.2-19c just a few weeks ago: After some further analysis we discovered that data older then 90 days was still retained within the logging database. Initially we thought this would be normal because of the huge number of users we served in combination with a retention time of 90 days. It took us several days to cleanup almost 550 million records of Sampling mode data from dbo.tblLogs (delete from dbo.tblLogs where lngClassId = 48). Soon as all Sampling mode data was deleted we reanalysed the logging database again, but found it was still quite large. This time we noticed several components, like “General Errors Log” & “User Event Logs : Session Refresh” were consuming lots of database space. HOWTO: Clear certain entries from the tbllogs table in an Ivanti Workspace Control Database Ivanti has an extensive support article, which describes how to clean specific type of records from the tbllogs table. The console crashed repeatedly and wasn’t able to do the cleanup anymore.ĭeleting the records can be done with the Workspace Manager Logging Management Tool, but the amount of records was so much we decided to run all cleaning on the SQL server itself. Sampling Mode was by far using most space within our logging database. Initially we tried to delete the Sampling Mode data from within the Ivanti Workspace Control Console, but there was just to much data. The tool was created by a former employee Patrick van Grinsven. Soon it became clear what exactly was using so much space within the logging database. We contacted Ivanti Support to investigate the huge increase in logging database size. They told me about a useful tool called “ Workspace Manager Logging Management Tool“. During regular maintenance at a customer we noticed the Ivanti WorkSpace Control logging database was getting quite big. The logging database had reached a size of more than 1TB, something of which the cause was not immediately clear. Sure they had lots of users and were keeping lots of auditing data, but the increase in database size couldn’t be related to additional users or something else.
0 Comments
Leave a Reply. |