ERROR at line 1:ORA-06598: insufficient INHERIT PRIVILEGES privilege Then remove it from CDB$ROOT as otherwise you'll receive: Remove OWM from a non-CDB with: - Uninstalling OWM - Workspace ManagerĪnd from a CDB container database you’ll have to use to ensure it gets removed from the CDB$ROOT, the PDB$SEED and all PDBs. For a non-CDB use: - for a CDB container database use: - host perlġ -l /u01/app/oracle/admin/HUGO122/scripts -b owminst This is simple – just add - before the call in the scripts. And it works flawless with all versions of the Oracle database I tested it with – back since Oracle 10.1.0.5. It’s a simple script which does neither require a restart or a recompilation. Uninstalling OWM is no magic rocket science thing. What is the best option? I leave it up to you. Create the DB-create-scripts with DBCA and uncomment OWM.There are actually two options to have no OWM in your database: The conceptual sequence of having OWM not created as part of the DB options leads to the fact that “ unclicking” OWM in the DBCA is not possible as the option simply does not exist. l /u01/app/oracle/admin/HUGO121/scripts -b pupbld -u l /u01/app/oracle/admin/HUGO121/scripts -b catoctk l /u01/app/oracle/admin/HUGO121/scripts -b catproc l /u01/app/oracle/admin/HUGO121/scripts -b catalog Spool /home/oracle/sqlPlusHelp.log helpus.sql Īnd here, for comparison, just an excerpt from a CreateDBCatalog.sql for a CDB. Spool /home/oracle/CreateDBCatalog.log "SYSTEM"/"&systemPassword" See the b script in the CreateDBCatalog.sql for a non-CDB below: SET VERIFY OFF There may have been an issue in the past – but there was no evidence that OWM couldn’t be created in the. A while back I tried to find out why this has been moved – and why it never got moved back. sql where all the other components get created. When you ask the DBCA ( Database Configuration Assistant) to generate scripts for database creation you’ll find the OWM being created in the CreateDBCatalog.sql, and not in the. It gets created in the phase of the “create catalog” part. That is the interesting part – OWM does not get created in the process of database creation where all the other options and components get created (such as JAVA, Spatial, APEX etc). And I know at least two very large customers who are using the OWM on a regular basis to optimize track routing and such. It has even its own manual with 350 pages. OWM is meant to enable 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.
0 Comments
Leave a Reply. |