Home > Lucent Technologies > Communications System > Lucent Technologies Intuity CONVERSANT System Version 7.0 Guide

Lucent Technologies Intuity CONVERSANT System Version 7.0 Guide

    Download as PDF Print this page Share this page

    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+.

    Page
    of 1206
    							6  
    Database Administration  Decrease Database Storage Size
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 367
    12  
    Enter exit
    Note:We recommend that you use the above commands as written. 
    However, if you are concerned about the /oracle file system size, 
    substitute the command, 
    add datafile ‘/home2/dbsA2.dbf’ 
    for 
    add datafile ‘/oracle/dbs/dbsA2.dbf’ 
    13  
    Enter /vs/bin/util/dbfrag
    The system displays the number of free database blocks.
    14  
    Check that the database size has been increased as desired.
    15  
    Enter exit
    The system exits the server manager mode.
    16  
    Enter exit
    Decrease Database Storage Size
    In order to minimize database storage and access problems, the voice 
    system provides two ways to minimize the storage space required for call 
    data: store fewer call data events, or store fewer days of information in your 
    applications. 
    						
    							6  
    Database Administration  Decrease Database Storage Size
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 368
    Reduce the Amount of Call Data Stored
    You can decrease the amount of database space needed by reducing the 
    number of stored call data events. This reduction must be accomplished at 
    the application design level. Unlike Reduce the Number of Days Data Is 
    Stored, there are no system variables to modify. This minimization technique 
    involves modifying every application that stores call data events to store 
    fewer of them.
    Reduce the Number of Days Data Is Stored
    Another way to minimize the amount of storage required for call classification 
    and call data detail information is to store fewer than seven days worth of 
    data. The voice system knows how many days of data to archive by reading 
    the contents of the croncdh file in the /vs/bin/util directory. 
    The following is a sample croncdh file:
    # Start the ORACLE DBMS
    VSUTIL=/vs/bin/util
    ORACLE_SID=A;export ORACLE_SID
    ORACLE_HOME=‘/usr/lbin/dbhome $ORACLE_SID‘
    PATH=$PATH:$ORACLE_HOME/bin;export PATH
    ulimit 2113674
    if /usr/lbin/orastat -s >/dev/null 
    						
    							6  
    Database Administration  Decrease Database Storage Size
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 369
    then 
    :
    else
     ulimit 2113674; ior w 
    fi
    # perform the cron jobs
    $VSUTIL/cdhsum
    $VSUTIL/cdhdel
    $VSUTIL/ccasum
    $VSUTIL/ccadel
    # cleanout the unwanted ORACLE log files
    $VSUTIL/logdel
    Change the Data Storage Number of Days
    Currently, the only report produced for the call classification data is the Call 
    Classification Summary report. Therefore, saving zero days worth of call 
    classification data saves database space without affecting the reports 
    produced by the voice system. Storing zero days worth of data means that 
    only the call classification data for the current day is available until the clean 
    up and summary programs run each night after midnight. The voice system 
    always maintains the current day’s data. 
    						
    							6  
    Database Administration  Decrease Database Storage Size
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 370
    To change the number of data days, modify the following commands in the 
    croncdh file, where 
    x is the number of days of data to store:
    $VSUTIL/cdhdel -
    x
    $VSUTIL/ccadel -
    x
    Note:If cdhdel and ccadel do not have any arguments, the default of 
    seven days is used, as illustrated in the sample croncdh file in 
    Reduce the Number of Days Data Is Stored
     on page 368
    . 
    To store two days worth of call detail data information, and four days of call 
    classification data, modify your croncdh file as follows:
    # Start the ORACLE DBMS
    VSUTIL=/vs/bin/util
    ORACLE_SID=A;export ORACLE_SID
    ORACLE_HOME=‘/usr/lbin/dbhome $ORACLE_SID‘;export 
    ORACLE_HOME
    PATH=$PATH:$ORACLE_HOME/bin;export PATH
    if /usr/lbin/orastat -s >/dev/null
    then 
    :
    else
     ulimit 2113674; ior w 
    fi
    # perform the cron jobs 
    						
    							6  
    Database Administration  Increase Shared Pool Size
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 371
    $VSUTIL/cdhsum
    $VSUTIL/cdhdel -2
    $VSUTIL/ccasum
    $VSUTIL/ccadel -4
    # cleanout the unwanted ORACLE files
    $VSUTIL/logdel
    /vs/bin/util/dbcheck -w 15,20
    Increase Shared Pool Size
    Perform this procedure to allocate additional memory resources for ORACLE. 
    You may need to do this if trying to write to several database tables at once 
    and you receive the ORACLE error message number ORA-04031 in the 
    message log.
    Note:This procedure increases the amount of main memory that 
    ORACLE uses.1  
    Check the message log for ORA-04031. The text portion of this message 
    indicates there is not enough shared memory space.
    2  
    Access the /oracle/dbs/initA.ora file.
    3  
    Place a pound sign (
    #) in front of the value 
    shared_pool_size=3500000
    .
    4  
    Remove the 
    # from the front of the value 
    shared_pool_size=6000000
    . 
    						
    							6  
    Database Administration  Rollback Segment
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 372
    5  
    Save and exit the file.
    6  
    Enter /oracle/bin/ior c to stop the database system.
    7  
    Enter /oracle/bin/ior w to start the database system.
    Rollback Segment
    A rollback segment is a storage buffer that records actions that can be 
    undone under certain circumstances. The rollback segment grows as needed 
    as long as there is available space in the database. However, the rollback 
    segment does not automatically decrease in size and some ORACLE 
    operations can cause the rollback segment to grow dramatically. 
    Consequently, you may wish to restore the rollback segment to the original 
    size by first eliminating it, and then recreating it.
    The installation of the Base ORACLE software package creates one rollback 
    segment called R1.
    This section provides information on verifying and reducing the size of this 
    rollback segment. 
    						
    							6  
    Database Administration  Rollback Segment
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 373
    Verify or Reduce the Size of the Rollback Segment
    Note:The procedure to reduce the size of the R1 rollback segment 
    requires that the voice system and the database system be 
    stopped. If possible, avoid reducing the size of the rollback 
    segment when call traffic is heavy. The procedure to verify the size 
    of the rollback segment does not require that the voice system 
    and the database system be stopped. Consequently, you may 
    verify the size of the rollback segment at any time.
    Use the following procedure to verify or reduce the size of the rollback 
    segment: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 /vs/bin/util/rb_init to display the current size of the rollback 
    segment, R1.
    The system displays a message similar to the following:Rollback segment R1 is currently 653312 bytes in size, would 
    you like to reduce the size of this rollback segment? (y/n) 
    						
    							6  
    Database Administration  Rollback Segment
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 374
    The original size of the rollback segment was set to 653312 bytes. If the 
    current size is close to this number, or if it is less than 1/4 of your total 
    database size, you do not need to reduce the size of the rollback 
    segment.~
    To terminate this procedure, go to step 4
    .
    ~
    To continue with this procedure and reduce the size of the rollback 
    segment, go to step 5
    .
    4  
    To terminate the rb_init command without reducing the size of the 
    rollback segment, enter n
    The system returns to the system prompt 
    #. You have completed this 
    procedure.
    5  
    Enter y to reduce the size of the rollback segment.
    The system executes the rb_init command. The system displays the 
    following message If the voice system is running:The voice system is running. Is it OK to stop the voice 
    system? (y/n) 
    						
    							6  
    Database Administration  Rollback Segment
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 375
    6  
    Enter y to shut down the voice system and continue with the procedure to 
    reduce the size of the rollback segment.
    The system displays the following message if the database system is 
    running:The database system is running. Is it OK to shutdown the 
    database? (y/n)
    7  Enter y
    The system stops the database system and executes the rb_init 
    command.
    When the rb_init command is finished, the system displays the following 
    message:Would you like to restart the voice system? (y/n)
    8  Enter y to restart the voice system, or enter n to wait to start the voice 
    system.
    If you do not wish to restart the voice system and the database at this 
    point, you may do so manually at a later time. 
    						
    							6  
    Database Administration  Voice System Database Administration
    Intuity™ CONVERSANT® System Version 7.0 Administration 
    585-313-501 Issue 3 January 2000 376
    Voice System Database Administration
    Use the following procedure to access the Database Administration window: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 cvis_menu
    The system displays the Voice System Administration menu (Figure 42 on page 59
    ).
    4  
    Start at the Voice System Administration menu and select:
    The system displays the Database Access ID Table window (Figure 165 on 
    page 377
    ).
    > Database Administration
    > Configuration Management 
    						
    All Lucent Technologies manuals Comments (0)

    Related Manuals for Lucent Technologies Intuity CONVERSANT System Version 7.0 Guide