Skip to content

Resetting Metadata

Clear the stored metadata of one object type in the MetaMiner Database (MMDB) so the MetaMiner Server (MMS) collects it again from BusinessObjects.

When to reset

  • The release notes of a new version ask for a reset of a type, for example to fill new Web Intelligence columns.
  • A fix corrects how a type was extracted, and the stored rows must be rebuilt.
  • Security metadata looks stale.

Upgrades update the MMDB schema automatically at server start. Most releases need no reset.

Talk to Infolytik Support first

A reset deletes data. Collecting a large type again (for example tens of thousands of Web Intelligence documents) can take many hours and adds load on the CMS and the Web Intelligence Processing Servers. Back up the MMDB first; see Back Up and Restore MMDB.

Option 1: reset from MMA (preferred)

For audit data, Web Intelligence deep metadata and folder security, use the one-time actions on Preferences > Settings... > Advanced in the MetaMiner Administrator (MMA):

Check box What happens at the next server start
Truncate BO audit data from MetaMiner DB on next MM Server restart Deletes all collected audit events and sessions. MMS then collects audit data again, starting from the Audit # days history to pull setting.
Truncate Webi BI4 metadata from MetaMiner DB on next MM Server restart Deletes the Web Intelligence deep metadata (data providers, queries, SQL, reports, elements, variables). If Keep Web Intelligence versions? is on, MMS keeps the rows and marks every document for processing again instead.
Force Security metadata Update to MetaMiner DB on next MM Server restart Deletes the collected security metadata (users, roles, rights and folder view rights) when security role metadata collection is on. MMS then collects it again.
  1. Check the box and click OK.
  2. Restart the server. The action runs once during start-up, then the check box clears.

Image of the MMA Settings dialog, Advanced page, with the three one-time reset check boxes

../images/admin/reset-metadata-advanced-page.png

See Advanced settings and Audit settings.

Option 2: reset a type with SQL

For the other types, empty the type's main table and every table that depends on it. When MMS starts and finds a type's table empty, it collects that type again from the beginning.

Steps

  1. Back up the MMDB.
  2. In MMA, click Stop Server.
  3. Open the Database Console without Read-only, or another SQL tool connected to the MMDB as its owner.
  4. Run the statements for the type from the tabs below, in the order shown.
  5. Start the server and watch server.log until the type has been collected again.

Image of the MetaMiner DB Console with the Crystal Reports truncate statements ready to run

../images/admin/reset-metadata-console.png

Statements per type

Reset documents (all document types)
truncate table publication_prompt_values;
truncate table destinations_email_add;
truncate table publication_formats;
truncate table publication_prompts;
truncate table destinations_disk;
truncate table destinations_email;
truncate table destinations_ftp;
truncate table destinations_inbox;
truncate table publications;
truncate table destinations;
truncate table files;
truncate table prompts;
truncate table prompts_default;
truncate table object_events;
truncate table document_datasources;
truncate table document_categories;
truncate table document_targets;
truncate table document_logons;
truncate table publication_dynamic_recipients;
truncate table publication_settings;
truncate table publication_dr_columns;
truncate table publication_personalization;
truncate table publication_global_profiles;
truncate table publication_principals;
truncate table publication_dr_recipients;
truncate table documents;
Reset Crystal Reports detail
truncate table crystal_tableprefix;
truncate table crystal_table_map;
truncate table crystal_sql_columns;
truncate table crystal_fields;
truncate table crystal_tables;
truncate table crystal_promptgroup;
truncate table crystal_bv_rel;
truncate table crystal_logons;
truncate table crystal_report_objects;
truncate table crystal_sections;
truncate table crystal_areas;
truncate table crystal_subreports;
truncate table crystal_connections2;
truncate table crystal_connections;
truncate table crystal_documents;
Reset users
truncate table user_aliases;
truncate table user_preferences;
truncate table user_attributes;
truncate table users;
Reset user groups
truncate table userusergroups;
truncate table usergroup_aliases;
truncate table usergroup_parentgroups;
truncate table usergroup_childgroups;
truncate table usergroups;
Reset folders
truncate table folders;

For folder security, use the Force Security metadata Update check box in Option 1 instead.

For Web Intelligence deep metadata, audit data and security metadata, use Option 1.

TODO: confirm the SQL reset lists with the product team

The Documents list matches the tables MetaMiner itself clears when a document is deleted. Confirm that the Crystal Reports, Users, Groups and Folders lists are complete for this release (for example whether Crystal Reports detail from the newer report-model extraction also needs a reset), and whether truncate on documents must also clear Web Intelligence and Crystal Reports detail.

Verify

  • server.log shows the type being collected again after the restart.
  • The MetaMiner Client shows the objects of that type again once the pull completes.