3.2
Table Of Contents
- Title Page
- Contents
- Using This Guide
- Getting Started with the Interplay | Administrator
- Database Settings
- Creating an Interplay Database
- Interplay Databases, Folders, and Files
- Creating and Restoring Database Backups
- Types of Interplay Administrator Backups
- Recommendations for Backup Configuration
- Setting the Number of Database Backups to Keep
- Scheduling Automatic Database Backups
- Starting a Backup Manually
- Using an Archiving Tool for Backup
- Restoring an Earlier Version of a Database
- Performing a Partial Restore of an Interplay Production Database
- Creating a Metadata-Only Backup for Customer Support
- Performing a Consistency Check
- Viewing Database Information
- Locking and Unlocking Databases
- Managing Databases: Deactivating, Activating, and Migrating
- Moving a Database to Another Server (Non-Clustered Systems)
- Moving a Database and Users to Another Server (Non-Clustered Systems)
- Moving a Database to Another Server (Clustered Systems)
- Moving a Database and Users to Another Server (Clustered Systems)
- Moving a Database Under Low Disk Space Conditions
- Renaming a Database
- Running Database Maintenance Tools
- Identifying the Root Folder of the Interplay Server Database
- Server Settings
- User Management
- Understanding the Central Configuration Server
- Adding Users to a Central Configuration Server
- Setting User Authentication Providers and Importing Users
- Managing Users, User Groups, and User Rights
- Understanding Default User Groups, Users, and Roles
- Adding User Groups
- Adding Users Manually
- Viewing and Setting Attributes
- Understanding Standard Roles and Default Rights
- Viewing and Changing Roles
- Viewing and Setting Authentication Providers for Individual Users
- Deleting Users and User Groups
- Removing Users from User Groups
- Managing Database Roles
- Guidelines for User Management
- Site Settings
- Defining Property Layouts
- Setting the Resolutions Available for Display
- Creating Custom Properties
- Configuring Remote Workgroups
- Configuring Categories
- Setting Server Hostnames and the Workgroup Name
- Interplay Media Services View
- Interplay Transfer Status View
- Interplay Transfer Settings View
- Workgroup Transfer Presets View
- Specifying Remote Servers for Asset Tracking
- Specifying Archive Settings
- Setting the Ownership for New Database Folders
- Enabling Interplay Synced Projects
- Setting Options for Deletion
- Viewing and Setting the Metadata Override Status
- Production Engine Bus Connector
- Application Settings
- Application Database Settings View
- Setting Options in the Editing Settings Tab
- Setting Audio Mixing Defaults for Access, Assist, and MediaCentral | UX
- Sending a Source to Playback in Interplay Assist
- Setting the Shotlist Start Timecode for Interplay Access and Interplay Assist
- Setting an Automatic Timeout for Interplay Assist and Avid Instinct
- Configuring the Frame Locators Display
- Configuring the Restrictions Display
- Media Composer | Cloud Settings
- Setting Instinct/Assist User Options
- Pro Tools Plug-Ins Settings
- Application Database Settings View
- Interplay Services
- Troubleshooting
- Reuniting a Split Database
- Installed Components and Services
- Interplay Engine Configuration Files
- Valid and Invalid Characters in Interplay
- System Metadata Properties
- Server Error Codes
- Consistency Check Codes
- Index
Running Database Maintenance Tools
81
• Validate AssignedRoles Table: Use this tool to check or fix (by removing) invalid entries in
the AssignedRoles table. This table keeps information about user roles that are assigned to
database objects. The tool verifies this table for integrity and fixes entries if needed.
• Validate Property Objects: (Interplay Engine v2.7.6 or later, Interplay Engine v3.0.6 or
later.) Use this tool to check for and repair issues with database properties, for example, a
“SettingsNotRegisteredException” exception when applying Editing Settings in the
Interplay Administrator.
• Clean Up Parentless Objects: (Interplay Engine v2.7.6 or later, Interplay Engine v3.0.6 or
later.) Use this tool to check for and repair database objects that do not have a parent
anymore. Hints that such objects exist can sometimes be obtained in the NxNServer.log with
ERRORs like “root object has no parent.” The presence of such objects can cause issues
such as incomplete search results. All objects in the database must have a parent. This is true
not only for Avid assets that are displayed in the browse tree but also for all other objects,
such as users and other system objects.
When to run these tools: You can run any of these tools as part of a troubleshooting procedure,
as recommended by an Avid representative. You can also run them for maintenance during
regular maintenance windows. However, they are not designed to be run on a daily basis, because
they require Exclusive Access to the database (see below).
One approach to using the tools for maintenance is to run them in the first convenient
maintenance window. Note how long it takes to run the tools, and if any problems are reported. If
there are no problems after running the tools a second time, you probably do not need to run
them during every maintenance window. If as a result of running these tools you find an issue
that regularly causes inconsistencies, you must consult with your Avid representative to address
the root cause of the issue.
Most tools can take up to an hour to run on large databases, but usually run much quicker, and
you can safely cancel the execution at any time. Each tool includes a window that displays
logging information and options for saving the information.
There are three tools that you cannot cancel after you have started them:
• Validate AssignedTable and Validate Property Objects: Usually run only a few seconds,
regardless of the size of the database.
• Clean Up Parentless Objects: Might run for an hour on a very large database.
Exclusive Access: Keep in mind that each tool requires Exclusive Access. Exclusive Access
locks the database to prevent access by a host system other than the one used to acquire
Exclusive Access and the Engine itself. A dialog box asks if you want to acquire Exclusive
Access before running the selected tool. You must click Yes to run the tool. Exclusive Access is
automatically released at the end of the process. Consider sending out a notice to users before
running any of these tools, informing them that the database will be locked. Logged-on clients
will be automatically logged off after the database is locked.