Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Install
  4. Data Archive Installation
  5. Data Vault Installation
  6. Application Accelerator Installation
  7. Application Retirement for Healthcare Accelerator Installation
  8. MongoDB Accelerator Installation
  9. Salesforce Accelerator Installation
  10. After You Install
  11. Data Archive Upgrade
  12. Data Vault Upgrade
  13. Upgrading Oracle History Data
  14. Upgrading PeopleSoft History Data
  15. ILM Data Validation Option Setup
  16. Data Archive Source and Target Database Requirements
  17. Data Archive Connectivity
  18. Data Archive Uninstallation
  19. SAP Application Retirement
  20. Database Users and Privileges
  21. Data Visualization Designer Installation
  22. Data Archive Installation Requirements Checklist and Architecture Options

Installation and Upgrade Guide

Installation and Upgrade Guide

Staging User

Staging User

The staging database user stores interim tables for business rule validation and generates candidates during the archive and partitioning processes. If you enable staging for the archive source connection, the staging user also creates staging tables. The staging tables temporarily store a copy of the archived data before the archive job moves the data to the archive or history database. The staging user typically resides in the source database.

Required Privileges

The following table lists the privileges required for the staging database user:
Oracle Privileges
Microsoft SQL Server Privileges
IBM DB2 Privileges
ALTER SESSION
ALTER EVENT SESSION
ALTER SESSION
CONNECT
For information about creating connections to the SQL Server database, see http://msdn.microsoft.com/en-us/library/s4yys16a(v=vs.90).aspx
CONNECT
CREATE DATABASE LINK
Not applicable
Not applicable
CREATE PROCEDURE
CREATE PROCEDURE
CREATE PROCEDURE
CREATE SEQUENCE
CREATE SEQUENCE
CREATE SEQUENCE
CREATE SESSION
CREATE EVENT SESSION
CREATE EVENT SESSION
CREATE SYNONYM
CREATE SYNONYM
CREATE SYNONYM
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TRIGGER
CREATE TRIGGER
CREATE TRIGGER
CREATE TYPE
CREATE TYPE
CREATE TYPE
CREATE VIEW
CREATE VIEW
CREATE VIEW

Additional Privileges

The following privileges may be required depending on your specific configuration:
  • DELETE ANY TABLE. Required to access the staging tables if you use the staging user for the delete from source step. If you cannot grant this privilege, you can do a direct delete grant on all application tables that are referenced in the metadata. Or, you can configure the source connection to use the application user for the delete from source step. If you use the application user, the application user needs access to the staging tables.
  • SELECT ANY TABLE. Not required if the staging user has access to the application user tables. If you cannot grant this privilege, you can do direct select grants on all application tables that are referenced in the metadata. Also required to access the source and duplicate tables created by smart partitioning projects.
  • UPDATE ANY TABLE. If you cannot grant this privilege, you can do direct update grants on all application tables that are referenced in the metadata.
  • EXECUTE ANY PROCEDURE. Required if the archive entities execute any procedures in the application user schema.
  • ALTER ANY TRIGGER. Required if you use the staging user for the delete from source step.
  • CREATE ANY TRIGGER. Required if you use the staging user for the delete from source step. If you cannot grant this privilege, then the staging user needs direct select privileges on the application tables instead. For example, grant select on ORDERS to amstage.
  • EXECUTE ANY TYPE. Required to create staging tables with user defined types that are owned by a different user.

Oracle Applications Privileges

To access Oracle applications, users must have insert privileges on the following tables:
  • AP.AP_HISTORY_CHECKS_ALL
  • AP.AP_HISTORY_INV_PAYMENTS_ALL
  • AP.AP_HISTORY_INVOICES_ALL
  • PO.PO_HISTORY_POS_ALL
  • PO.PO_HISTORY_RECEIPTS
  • PO.PO_HISTORY_REQUISITIONS_ALL

Oracle Partition Exchange Privileges

If you configure the archive job to use Oracle partition exchange to delete source data, the staging user creates a table to identify the records to keep in the source. The archive job uses the partition in the table to swap the original source segment when the job deletes data from the source.
The following user privileges are required to use Oracle partition exchange to delete data from sources on Oracle databases:
  • ALTER ANY TABLE
  • DROP ANY TABLE
  • ALTER USER QUOTA UNLIMITED

Smart Partitioning Privileges

Create a dedicated staging user account to run smart partitioning. The staging tablespace must be the default tablespace for the staging user.
To perform smart partitioning, the staging user requires extensive privileges to run all tasks required by the smart partitioning jobs. The following staging user privileges are required to use smart partitioning:
  • CREATE TABLESPACE
  • ALTER TABLESPACE
  • DROP TABLESPACE
  • ALTER SESSION
  • CREATE ANY TABLE
  • INSERT ANY TABLE
  • DROP ANY TABLE
  • DROP ANY INDEX
  • UPDATE ANY TABLE
  • ANALYZE ANY
  • CREATE ANY INDEX
  • CREATE ANY CONTEXT
  • ALTER ANY INDEX
  • ALTER ANY TABLE
  • ALTER ANY TRIGGER
  • DROP ANY TRIGGER
  • CREATE PROCEDURE
  • CREATE SEQUENCE
  • CREATE SYNONYM
  • CREATE ANY TRIGGER
  • CREATE TYPE
  • CREATE VIEW
  • CREATE DATABASE LINK
  • SELECT ANY TABLE
  • SELECT ANY DICTIONARY
  • CREATE SESSION
  • CREATE MATERIALIZED VIEW
  • DROP ANY SYNONYM
  • CREATE ANY SYNONYM
  • CREATE ANY VIEW
  • DROP ANY VIEW
  • UNLIMITED TABLESPACE
  • ALTER USER
  • SELECT_CATALOG_ROLE
  • GRANT ANY OBJECT
  • EXECUTE ANY PROCEDURE
  • CREATE ANY DIRECTORY
  • COMMENT ANY TABLE
  • ALTER DATABASE
  • DBA
  • ADMINISTER DATABASE TRIGGER
  • EXP_FULL_DATABASE
  • IMP_FULL_DATABASE
  • EXECUTE ON SYS.DBMS_FILE_TRANSFER
  • EXECUTE ON SYS.UTL_RECOMP
  • EXECUTE ONSYS.DBMS_RLS
  • EXECUTE ON SYS.DBMS_RESUMABLE
  • EXEMPT ACCESS POLICY

0 COMMENTS

We’d like to hear from you!