Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The baselines are stored in a DDL repository. You must create the DDL Repository schema, see install and update scripts at at

View file
nameddlrepository.zip
. DDL repository needs to be created in FDDB schema, script provided does not create FDDB schema, you may do that per your company standards. If you are upgrading from version prior to 5.1.07, then run upgrade/v4.6.0.3-to-5.1.0.7/migration.sql to upgrade your repository schema. Then, run upgrade/5.1.0.7-to-5.2.3.1/migration.sql and upgrade/5.2.3.1-to-5.4.0.4/migration.sql.  If you were already at a version higher then 5.1.0.7, then only the second migration.sql needs to be executed.  If you are creating DDL repository schema, then just run install/DDLRepositoryCreateScript.sql.

...

  • GRANT EXECUTE on dbms_crypto to <YOUR USER NAME>;

  • GRANT " SELECT_CATALOG_ROLE " TO <YOUR USER NAME>;

  • GRANT SELECT ANY DICTIONARY TO <YOUR USER NAME>;

  • grant READ on sys.dba_transformations to <YOUR USER NAME>;

  • grant READ on sys.dba_objects to <YOUR USER NAME>;

  • grant READ on sys.dba_queues to <YOUR USER NAME>;

  • grant READ on sys.dba_queue_tables to <YOUR USER NAME>;

  • grant READ on sys.dba_synonyms to <YOUR USER NAME>;

  • grant READ on sys.dba_indexes to <YOUR USER NAME>;

  • grant READ on sys.dba_cons_columns to <YOUR USER NAME>;

  • grant READ on sys.dba_nested_tables to <YOUR USER NAME>;

  • grant READ on sys.dba_all_tables to <YOUR USER NAME>;

  • grant READ on sys.dba_tab_privs to <YOUR USER NAME>;

  • grant READ on sys.dba_scheduler_jobs to <YOUR USER NAME>;

  • grant READ on sys.dba_scheduler_programs to <YOUR USER NAME>;

  • grant READ on sys.dba_scheduler_schedules to <YOUR USER NAME>;

  • grant READ on sys.dba_mview_logs to <YOUR USER NAME>;

  • grant READ on sys.dba_procedures to <YOUR USER NAME>;

  • grant READ on sys.dba_aq_agents to <YOUR USER NAME>;

  • grant READ on sys.dba_queue_publishers to <YOUR USER NAME>;

  • grant READ on sys.dba_queue_schedules to <YOUR USER NAME>;

  • grant READ on sys.dba_queue_subscribers to <YOUR USER NAME>;

  • grant READ on sys.dba_queue_tables to <YOUR USER NAME>;

  • grant READ on sys.dba_dependencies to <YOUR USER NAME>;

  • grant READ on sys.dba_sequences to <YOUR USER NAME>;

  • grant READ on sys.dba_source to <YOUR USER NAME>;

  • grant READ on sys.dba_triggers to <YOUR USER NAME>;

  • grant READ on sys.dba_views to <YOUR USER NAME>;

  • grant READ on sys.dba_roles to <YOUR USER NAME>;

  • grant READ on sys.dba_users to <YOUR USER NAME>;

  • FDORA_USER needs Create and alter Permissions for the schemas to be syncedbeing synced. Using the schema owner as FDORA_USER may be the easiest solution, and is needed if triggers don’t have schema-qualified table references.

Supported Oracle Object Types

...