[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::repository

Title:Oracle CDD/Repositorynce
Notice:Current versions are V7.0-01 and V6.1-03eld Test 3
Moderator:8292::PJACOBN
Created:Thu Jan 21 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1094
Total number of notes:4913

1046.0. "DEADLOCK when accessing CDD " by ORAREP::TAVIS::MIRO () Wed Feb 05 1997 04:47

    In our project we have 3 dictionaries:
    
    1. Fields - has definitions of elements and globals
    2. Records - record definitions
    3. Users
    
    The developers hav read access to the first 2 dictionaries and
    read write access to the users dictionary.
    
    For each developer we have a directory in the USERS dictionary where
    the developer keeps his/her private record definitions.
    
    The developers accesses the FIELDS and RECORDS dictionaries in READ
    access only.
    
    The CONFIGURATION manager is the only person that is allowed to update
    the first 2 Dictionaries.
    
    Questions:
    ----------
    
    1. As noted in note 1039 CDD open a read write transaction when a
       developer performs compile of a COBOL program . It should NOT.
    
    2. When we have several developers concurrently defining new records and
       ACMS tasks in their own private directory within the USERS dictionary
       we get DEADLOCKS.
       
       - How could we solve this problem ?
    
       - IS our design wrong ?
       
    3. Please advise.
    
    Thanks
    Moshe
    
    
    
T.RTitleUserPersonal
Name
DateLines
1046.1Has the support been contacted ?8292::PJACOBPatrick JACOB-pjacob@fr.oracle.comThu Apr 03 1997 11:3315
    
    Hi Moshe,
    
    nothing looks wrong in your design. Please contact your Oracle Support
    Service so that they can investigate and officially report the DEADLOCK 
    problem. You will probably need to supply necessary scripts that
    generate the deadlocks.
    
    The READ WRITE transaction during COBOL compilation is a separate
    problem. It will probably has to be officially reported too. I suspect
    a relation with CDD$DEFAULT translation which need to be analyzed.
    
    Hope this helps.
    
    Patrick