Where is icm dba tool

When you install a new Logger, you must create its central database. When you create a database, you must specify the size of its data device or devices.

The device size must be sufficient for all the data you expect the database to hold. The size of the central database depends on the size of your call center enterprise, your expected call load, and your specific data retention requirements.

Based on your expectations and requirements, you can create a central database of the appropriate size. The same considerations that affect the size of the central database also affect the size of the HDS database. Over time, the size of your enterprise or your call volumes may change significantly.

Therefore, you may need to resize the central and HDS databases to meet new requirements. Because the real-time data in the local database are constantly overwritten by new data, the database size remains fairly constant.

You normally do not need to resize the Distributor AW real-time database. The data in the central database and HDS AW database grow as they accumulate historical data and call detail records. The growth is directly related to the following factors:.

The size of configuration data is itself insignificant typically, only a few megabytes. However, the amount of configuration data directly affects the amount of historical data generated. ICM software generates a new historical record every half hour for each service, skill group, route, trunk group, etc. Use the ICM Database Administration tool for estimating the size of these databases, based on the expected usage.

The database size remains adequate as long as your usage is consistent with the values used to size the database. If your configuration expands significantly or if you change the retention times for historical data, you may have to increase the size of the database. This may involve adding additional disks to the system.

The ICM central database can be configured to store as much historical data as you want to retain. If required for your installation, your Cisco Customer Support representative can add more disk drives to the system. Normally, the central database transaction logs are sized to handle the processing of historical data at a call rate of 35 calls per second.

In addition, the databases can be synchronized with a background call load of 35 calls per second. By default, the purge process runs each night at A. The purge process deletes records that are older than a specified number of days. When you configure the ICM databases you can specify the number of days to keep data for each historical table. Table lists the default settings for retaining historical data.

Note Five-minute data are not currently implemented in Monitor ICM historical reports; therefore, they are not normally retained in the central database. This tool provides a central utility that allows you to manage ICM database administration. Use this tool to:. This displays the ICM instances that have database on the server. Expanding the node displays the databases associated with the node.

Expanding the node database displays the a list of the individual tables in the Under databases are the table groups and the final level lists the tables in the group. To view the properties of a table, select the table from the list and right click on the mouse button and select Properties from the pop-up menu, or double click on the table from the list. From the main window, choose a node or database from the tree and then select a function from the menu bar menu or, select a node or database and click the right mouse button to display a pop-up menu.

Step 1 For the server, instance, and node Distributor or Logger , select the database that you want to estimate. The Estimate window displays. Step 3 Use this window to estimate the size of the database. Use the tabbed sections of the window to configure ICM settings that control the amount of time that data is retained in the database. Use the Save button to save the estimate to a file, or the Open button to open a previously saved estimate file.

Use the Print button to print an estimate report that includes the values entered on the screen. Use this section of the screen to estimate the ICM variables. Enter your best estimate for each of the fields. Call and Event Data. Use the tabbed section of the to configure the ICM setting that control the amount of time that data is retained in the database.

Changes that you make in this section are applied to the NT Registry and affect data purging in the database. Database Size. This section displays the actual database size and the required database size, based on the current values entered on the screen. This section displays bandwidth estimates required for the Historical data, Real-time data and the total bandwidth requirement. Use the Create function to create a database for an Admin Workstation or Logger.

You can only create one Logger database per side. Step 1 With the ICM software running, for the server and instance, select the node Distributor or Logger where you want to create the database. The Create Database window displays. Step 3 Enter the following information for the database:.

Flashcards Collections. Documents Last activity. Add to Add to collection s Add to saved. Conventions Refer to the Cisco Technical Tips Conventions for more information on document conventions. Back up the Configuration Database Complete these steps: 1.

Create a directory on a local drive. Drill down under your Customer Instance to the database see Figure 3. The default value in the Data type field is Configuration. Click Browse in order to navigate to the directory you created earlier. Click Export when you are ready to begin the backup.

Click Start in the application window. The export begins. An export completion message appears after successful export of data. Figure 5 Export Completion Message Verify Open a Windows Explorer session in order to verify the successful backup of the configuration data. Select Add. This button invokes the Add Device window. Move the database log file to a separate virtual drive. After you complete entering information in the Create Database window, select Create to close the window and create the database.

When an instance does not have any configured components, database creation occurs under the instance within a component placeholder. With Unified CCE running, for the server and instance, select the instance where you want to create the database. The Select Component dialog appears. Select the logger type and select OK. After you have completed entering information in the Create Database window, select Create to close the window and create the database.

When an instance does not have any configured components, component placeholders appear under that instance on the application tree view. If you delete the database, the component placeholders no longer appear. The Delete Database prompt appears. Select Yes to delete the database. Select Close to exit. Check the main window to verify that the database was deleted. In the event that you reach this limit, you must either recreate the database or use SQL Enterprise Manager to modify the database.

The Expand window appears:. Use the window to adjust the size allocation on the database storage device, by completing the following fields:. Select OK to expand the file and exit the screen. Use the Recreate function to recreate a database. The procedure for recreating a database is similar to the procedure for creating a database.

When you recreate a database, the information currently stored in the database is deleted. When an instance does not have any configured components, database creation occurs under a component placeholder on the application tree view. The Recreate window appears. Enter the database information. See the online help for a description of the fields. Select Create to continue. A message is displayed asking if you are sure you want to recreate the database. Select Yes to continue the operation.

The next Recreate Database window appears. Select Start to recreate the database. After the process completes, a message appears indicating the action was successful. Select OK and then select Close to exit. The Properties window appears. After you finish viewing the database properties, select Close to exit the window.

Select and expand the database to display the tables of a database. Double-click the table you want to view. The Table Properties window appears. After you finish viewing the table properties, select Close to exit the window. The Import data to or Export window appears. Check Lockout Changes , if you want to prevent changes to the database during the import or export operation. Set the Data type for the imported data.

Select Import or Export to display the Import or Export dialog. Select Start to import or export the data. After the process completes, a message appears indicating that the action was successful. You can select Cancel at any time to end the process. Use the Synchronize function to synchronize the data of two Logger databases. For the server and instance, select the Logger database to synchronize. The Synchronize window appears:. Check Lockout Changes , if you want to prevent changes to the database during the synchronize operation.

Select the server name and database for both source and target from the drop down lists. To select a server that is not on the drop down list, select Add and enter the server name in the Add Server box:. Select Synchronize. A message box appears asking for confirmation.

Select OK to continue. The next Synchronize window appears. Select Start to synchronize the data. The Configure window appears. Use this window to modify the following SQL Server parameters:. Unified ICM does not allow you to change these options, so they are dimmed. After you are finished configuring the server, select OK to complete the operation or select Cancel to end the operation without making any changes.

The Database Sizing Estimator tool enables you to perform database sizing tasks. The tool bases the estimate ion information about the configuration of the environment for example, the number of agents, skill groups, call types, and so on and database retention days.

You can supply initial values by loading values from your local Unified ICM database. When values are updated in the Database Sizing Estimator, the application recalculates its totals.

This update enables you to immediately see the affects of each change as it is made, with the values displayed in a spreadsheet. The tool enables you to engage in what-if scenarios to see the effects that various changes have on the database sizing requirements. At any time, you can load the saved XML file back into the Database Sizing Estimator, so you can continue revising your estimates. The Database Sizing Estimator tool then uses this data to provide starting values, which you can modify.

The Database Sizing Estimator can calculate a database size for a newer schema other than the deployment to which the Database Sizing Estimator is connected. The following steps describe how to start the Database Sizing Estimator. For Database Sizing Estimator field-level descriptions, see the online help.

The window displays initial default values for all fields. As you change the field values, the database size requirements update automatically. Steps 1—3 in this procedure only apply when using existing databases.

Use your existing database as the starting point. Select the database you want to use as the starting point for your sizing estimates. Select Retrieve. Modify the database information depending on your scenario. As changes are made, the Database Size Required value changes. Save your work in progress by selecting Save to File. Run the Web Setup tool for that machine in a browser, from anywhere. Under Instance Management , select Add and add the instance.

Return to the Web Setup tool. Regularly monitor the space used by the central database and transaction logs. The per-process log files contain information on Logger and database activity, as this example log file illustrates:. The Logger logs events and trace messages that show the percentage of space used in the database.

When the database becomes 80 percent full, the Logger logs an EMS warning message to the central database. If you decide that you need more database space, contact your Unified ICM support provider. The system software has automatic checks to prevent the central database from becoming full:.

Use the Database Sizing Estimator tool to size your database requirements. The purge adjustment feature affects performance of the Unified CCE system. The high CPU and disk usage due to purge adjustment could affect component performance including failures. The automatic purge ensures that the database can never become full. But, the purge means that you can lose older historical data. If the central database is growing too large, you can allocate more space. If you require more space in the central database, back up the master database before you add more space.

Your Unified CCE support provider might have options for allocating more space. Normally, you do not need to initialize the local database awdb , because initialization happens automatically during its creation. If you ever need to initialize the local database after its creation, you can do so. The Initialize Local Database main window appears. Select Start to transfer the data. As data is copied, the screen displays the number of rows processed for each table. After the transfer is complete, select Close to exit.

Because Unified ICM is a mission-critical application that runs 24 hours a day, the system software takes care of many routine administration tasks automatically. In general, the system software retains control of most of the database administration functions in order to keep external interference to a minimum.

To conserve system resources, minimize all Unified ICM process windows before configuring your system. The system software maintains a database on each side of the Central Controller and the local database awdb. Each database consists of a group of interrelated tables.