Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator 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.
  • 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

0 COMMENTS

We’d like to hear from you!