Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies Intuity CONVERSANT System Version 7.0 Guide
Lucent Technologies Intuity CONVERSANT System Version 7.0 Guide
Have a look at the manual Lucent Technologies Intuity CONVERSANT System Version 7.0 Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 347 SERVICE Table The SERVICE table contains the following information:• CID — Numeric field that specifies a non-unique identification number that joins multiple SERVICE.CID to one CALL.CID. Each call creates one or more SERVICE records, depending on the number of services used to handle the call. All SERVICE records associated with a call have the same SERVICE.CID as the CALL.CID in the CALL record. See Relationship Between the CALL, SERVICE, and EVENT Tables on page 351 . • SID — A numeric field that specifies a unique identification that joins one SERVICE.SID to multiple EVENTS.SID. • SERVICE—Variable length character field that specifies the service (application) name. This field can be up to 16 characters in length. • START_TIME — Date field that specifies the starting time of each service. • END_TIME — Date field that specifies the ending time of each service.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 348 CDHSUM Table The CDHSUM table contains the following information:• SUMID — Numeric field that specifies a unique identification number which joins CDHSUM.SUMID to EVSUM.SUMID. • SERVICE— Variable length character field that specifies the service (application) name. This field can be up to 16 characters in length. • START_TIME — Date field that specifies the start of the hour (for example 10:00:00). • DURATION — Numeric field that specifies the sum of service run times during this hour in seconds. • USAGE — Numeric field that indicates the total number of times the service was run for calls during a one-hour period. Note:Records are generated on per hour and per service basis.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 349 EVENTS Table The EVENTS table contains the following information:• SID — Numeric field that specifies a non unique identification number. Note:Each service run during a call creates a certain number of event records, depending on the number of events defined. All events records associated with this call have the same SID number as the SID field of the corresponding SERVICE record. See Relationship Between the CALL, SERVICE, and EVENT Tables on page 351 . • EVENT_NUMBER — Numeric field that is an internal mapping number of each of the defined events. Their values can be found in the appl .D file in the /att/trans/sb/ appl directory. The value stored in EVENT_CNT, EVENT_TM, or EVENT_STR is the value of the Script Builder event variable when the script terminates. Two of the following three fields will have null values when the script terminates: • EVENT_CNT — Numeric field that will contain the value of the event variable if the event type is a Script Builder number, otherwise it is null. • EVENT_TM — Date field that will contain the value of the event variable if the event type is a Script Builder time or date, otherwise it is null. • EVENT_STR — Character field that contains the value of the event variable if the event type is a Script Builder character string, otherwise it is null.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 350 EVSUM Table The EVSUM table contains the following information:• SUMID — Numeric field that specifies a unique identification number. Note:The values in this field are related to the SUMID values in the CDHSUM table. • EVENT_NUMBER — Numeric field that specifies the internal mapping between the event and an internal number. • SUM_TOT — Numeric field that indicates the total number of occurrences for this event. Note:If the event type is a numeric, the value in SUM_TOT is the sum of the values of this event field for all the calls. For example, if an event field, NUM_TRANS, keeps track of the number of transactions for each call, SUM_TOT will contain the sum of NUM_TRANS for all calls during this time period. On the other hand, if the event type is not a number, each call will increment SUM_TOT by one.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 351 TRASUM Table The TRASUM table contains the following information:• START_TIME — Date field that specifies the start of hour (for example 10:00:00). • CHANNEL — Numeric field that indicates the channel number. This field can be up to 3 digits in length. • CALL_TOT — Numeric field that specifies the total number of calls. • DUR_TOT — Numeric field that specifies the total duration in seconds. Note:Records are generated on per hour and per channel basis. No calls during this hour on this channel result in no record. OLDCDH View The OLDCDH view is an ORACLE database view provided to be compatible with the CDH table that is not supported in newer releases. Relationship Between the CALL, SERVICE, and EVENT Tables The relationship between these three call data handling tables can be summarized by the following statements and in Figure 164 on page 352 : • Each telephone call creates one record in the CALL table.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 352 • Each record in the CALL table is linked to one or more records in the SERVICE table. • Each record in the SERVICE table is linked to zero or more records in the EVENTS table. Figure 164. Relationship of CALL, SERVICE and EVENTS Tables
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 353 Resize Call Data Tables The sizes of the call data handling tables are defined in /oracle/dist/cdh.sql file. Although the sizes are carefully engineered, it is possible that one or more of the tables should be increased to accommodate the heavier traffic on the system or the greater number of events defined in your applications. The most likely candidates for resizing are the EVENTS, SERVICE, and CALL tables, and their index tables. Use the following procedure to increase the size of a call data table: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter cd /oracle/dist The system changes to the oracle/dist directory. 4 Enter cp cdh.sql o.cdh.sql The system saves the original copy of the cdh.sql file to a file named o.cdh.sql. 5 Enter dbused The system displays the number of megabytes used by the table.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 354 6 Write down this number. 7 Use the UNIX vi editor to modify the cdh.sql file as follows: a Find the create table xxx statement block, where xxx is the table name (for example, CALL, SERVICE or EVENTS). b Modify the statement storage (initial 999k) to a bigger number, where 999 is the current initial size for the table and k stands for kilobytes (1024 bytes). Note:The new values specified should be at least twice as large as the current table size you wrote down in step 6 . You may use the megabyte format, 99m, where m is mbytes (1,000,000 bytes = mbyte). For example, modify the storage statement to read: storage (initial 3m) to make the table have an initial size of 3 mbytes. 8 Enter stop_vs The systems stops the voice system. See stop_vs on page 865 in Appendix A, Summary of Commands for more information about the stop_vs command. Note:If you do not want to preserve existing call data, skip step 9 through step 11 .
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 355 9 Enter systblsav file The system saves the table storage information, where file is a UNIX file or a device name where the data will be saved (such as, /dev/rmt/c0s0). 10 Enter sqlplus \@ /oracle/dist/cdh.sql The system reinitializes the table(s). 11 Enter systblres file The system restores the table storage information from the UNIX file or device name where it was saved in step 9 (such as, /dev/rmt/c0s0). 12 Enter start_vs The system restarts the voice system. See start_vs on page 863 in Appendix A, Summary of Commands for more information about the start_vs command.
6 Database Administration Call Data Tables Intuity™ CONVERSANT® System Version 7.0 Administration 585-313-501 Issue 3 January 2000 356 Verify Call Data Tables Periodically, the field definitions of a table need to be reviewed for accuracy, or to assist with troubleshooting. Use the following procedure to verify the field definitions of a table (such as, the CCA table):1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 1 Enter sqlplus sti/sti The system starts a sqlplus session. 2 Enter describe CCA The system displays the current definition of the CCA table, similar to the following:Name Null? Type ---------- ----- ----- START_TIME DATE PHONE_NUM VARCHAR2(16) RESULT_CODE VARCHAR2(1)