Before running any script that modifies data, always back up your schemas. |
Script | Description |
| Optimize spatial indexes and locking information. This script should be run using the HPD schema owner account. |
| Clear the recycle bin of information that was deleted. This script should be run using the HPD schema owner account. |
| Remove unneeded privileges from the HPD schema, which can increase database security. These privileges are no longer required since HPD 2.8.2. Only HPD schemas created before HPD 2.8.2 have these unneeded privileges. This script must be run by a database administrator. The following privileges are removed: • ALTER SYSTEM • DROP ROLLBACK SEGMENT • ALTER RESOURCE COST • BECOME USER • ALTER PROFILE • DROP PUBLIC DATABASE LINK • CREATE SNAPSHOT • FORCE TRANSACTION • EXECUTE ANY TYPE • EXECUTE ANY PROCEDURE • CREATE ROLLBACK SEGMENT • AUDIT SYSTEM • CREATE PUBLIC SYNONYM • RESTRICTED SESSION • CREATE PUBLIC DATABASE LINK • DROP ANY SYNONYM • CREATE ANY SEQUENCE • DROP PUBLIC SYNONYM |
| By default, indexes are created in the same tablespace as the tables. This script sets the tablespace in which newly created indexes can be created. Only new indexes created during HPD server upgrade are placed in this tablespace. This script should be run using the HPD schema owner account. |
| Delete historical feature content that is no longer linked to existing products. This can reduce database size. |
| List information about the types of relationships in the HPD database, and the number and type of features that are related using these types of relationships. This script does not modify data. This script should be run using the HPD schema owner account. |