Clean and Drop Scripts¶
Clean scripts and drop scripts are used during an upgrade to clear the database from obsolete objects.
Deployment of the clear and drop scripts can be performed with any Oracle tool that can run SQL and SQL scripts, like the IFS Cloud Installer or SQL*Plus.
- When using IFS Cloud Installer, chose the action File Executor and locate in the manualdeploy folder the script that you want to execute.
- When using SQL*Plus, execute the scripts from the correct location where the file is stored, i.e. the folder manualdeploy. If the output is spooled to a log file, it will be located in the same folder.
Clean scripts remove objects that have become invalid in an active component. The scripts must be manually executed directly in the database logged in as the application owner at the end of an upgrade. The clean scripts are found in the component folders below the
Clean scripts are cumulative and will contain changes from the oldest release we support upgrading from up and until the current one.
Drop scripts remove all the database objects for a component that have become obsolete. The drop scripts are executed in two steps. The first step is started from IFS installer in the normal upgrade process, and it drops business logic objects (packages, views etc.) but not any tables. The tables are however renamed to OBSOLETE_old_name_[MODULE] to mark them as complete. The other part of the drop script is physically removing the (renamed) tables from the database, and it must started as a manual action by logging on to the database as the application owner.
The drop scripts for obsolete components are stored in the Prifs component of the new track. The script removing the tables are put under prifs\manualdeploy\database\prifs and named [module]dr.sql, and the scripts for dropping business logic are stored in prifs\source\prifs\database. These are named [module].drp.
Note: Since the manual clean and drop scripts drop obsolete tables, it is recommended to verify the scripts to avoid unwanted loss of data that the customer wants to keep even though the tables are not used inside IFS Cloud anymore. Furthermore all the background jobs need to be stopped before executing these scripts.