Headstart Utilities Failure w/Designer 6.0

Hello:
I've just tried to install Headstart 2.1.2 with the new patches
for Designer 6/Developer 6 on Windows NT 4.0 SP 4. I've checked
all of the logs (in my ORANT\HSD21 folder) and I don't see any
errors in any of them.
However, when I go to start the Headstart Utilities
Administration and log in as the Headstart Utilities owner, I
get the following:
I get a number of "FRM-40733: PL/SQL built-in DBMS_ERROR_TEXT
failed". This comes up 5 times in a row.
Then I get "FRM-40735: PRE-FORM trigger raised unhandled
exception ORA-03114". This comes up once, and the form exits.
This last one seems to indicate that the logon has failed, but I
can log on using SQLPlus 3.3 and SQLPlus 8.0 with no problems,
using exactly the same ID/password.
If it matters, I'm using Oracle 8.1.5.0.0, Developer 6.0
downloaded from Technet with the dev60 patches and Designer 6.0
with no additional patches. They all seem to be working OK
(I've generated a test form w/o Headstart and it runs OK).
I've also run the following as suggested in another of your
posts:
select object_name from user_objects where status='INVALID';
which returns no rows.
Help!!
TIA
Eric Raskin
null

Headstart Team (guest) wrote:
: Jeff Esposito (guest) wrote:
: : Headstart Team (guest) wrote:
: : : Eric Raskin (guest) wrote:
: : : : Headstart Team (guest) wrote:
: : : : : Eric Raskin (guest) wrote:
: : : : : : Hello:
: : : : : : I've just tried to install Headstart 2.1.2 with the
new
: : : : patches
: : : : : : for Designer 6/Developer 6 on Windows NT 4.0 SP 4.
: I've
: : : : : checked
: : : : : : all of the logs (in my ORANT\HSD21 folder) and I
don't
: : see
: : : : any
: : : : : : errors in any of them.
: : : : : : However, when I go to start the Headstart Utilities
: : : : : : Administration and log in as the Headstart Utilities
: : owner,
: : : : I
: : : : : : get the following:
: : : : : : I get a number of "FRM-40733: PL/SQL built-in
: : : : : DBMS_ERROR_TEXT
: : : : : : failed". This comes up 5 times in a row.
: : : : : : Then I get "FRM-40735: PRE-FORM trigger raised
: : unhandled
: : : : : : exception ORA-03114". This comes up once, and the
form
: : : : exits.
: : : : : : This last one seems to indicate that the logon has
: : failed,
: : : : but
: : : : : I
: : : : : : can log on using SQLPlus 3.3 and SQLPlus 8.0 with no
: : : : problems,
: : : : : : using exactly the same ID/password.
: : : : : : If it matters, I'm using Oracle 8.1.5.0.0, Developer
: 6.0
: : : : : : downloaded from Technet with the dev60 patches and
: : Designer
: : : : 6.0
: : : : : : with no additional patches. They all seem to be
: working
: : OK
: : : : : : (I've generated a test form w/o Headstart and it runs
: : OK).
: : : : : : I've also run the following as suggested in another
of
: : your
: : : : : : posts:
: : : : : : select object_name from user_objects where
: : : : status='INVALID';
: : : : : : which returns no rows.
: : : : : : Help!!
: : : : : : TIA
: : : : : : Eric Raskin
: : : : : Eric,
: : : : : I'm sorry to say I have bad news for you. The error you
: run
: : : : into
: : : : : is caused by the following bug in Forms 6.0, which only
: : : : : reproduces with Oracle 8.1.5 on NT:
: : : : : 966970: CONNECTION LOST WHEN INVOKING PACKAGED
PROCEDURE
: : WITH
: : : : : PLSQL-TABLE AS ARG OFMO899
: : : : : Only work around is to use 8.0.5, or 8.1.5 on a UNIX
: : machine.
: : : : You ain't kiddin' about the "bad news" part, are you?
: : Just
: : : : to be sure I understand, this is only on the development
: : : : machines, right? I can still run 8.1.5 on NT for the
: actual
: : : : database?
: : : : Eric
: : : I wish I was kidding! This is a problem you might run into
on
: : : your production database as well. The moment you have a
forms
: 6
: : : application that calls a server-side procedure which has a
: : PL/SQL
: : : table of records as parameter, the connection is lost.
: : : Headstart-generated applications will all run into this, as
: : : Headstart uses such a server-side procedure for message
: : : handling.
: : : We have raised this issue with Forms Development, and have
: : asked
: : : for a patch. (although it might turn out to be a server bug
: : : instead of a forms bug...).
: : This is very bad news, as I was looking to leverage
: : headstart with 8.1.5/Designer/Developer 6.0 for rapid
: development
: : and deployment of an application to the web.
: : I'm sure there are a few of us in this boat.
: : Questions:
: : 1) Does this problem exist for 8.1.5 in a Unix deployment?
: : Specifically, can I be assured of reliable forms generation
via
: : headstart if my 8.1.5 database lives in Unix?
: : 2) Assuming Forms Development agrees with you and is working
on
: a
: : patch, may I offer to help test that patch?
: : Jeff
: Jeff,
: This is only a problem with Oracle 8i on NT. Note that it is
not
: just a Headstart problem. If you generate a form with Designer,
: and the block is based on a MAPI procedure, it won't run on
8.1.5
: on NT either, because the MAPI procedure has a PL/SQL table of
: records as a parameter, just like the Headstart message
handling
: routine. Thanks for your offer, but given the wide impact of
this
: bug, Oracle will be able to create sufficient testcases
: themselves.
Hello,
does the same problem exist on Oracle 8.0.5 on Windows NT and/or
Digital Unix too?
We are currently thinking about using Headstart and if the
problem exists on 8.0.5 the workaround you provided might be a
big problem for us ...
thx in advance
null

Similar Messages

  • DBMS_ERROR_TEXT failure with Headstart Utilities Admin form

    I have installed the Headstart Oracle Designer for Designer/Developer 6.0, following instructions found in the patch for 6.0. Whenever I try to start the Headstart Utilities Administration form, I get an error stating that DBMS_ERROR_TEXT failed. Has anyone else had this problem?

    Janine,
    When I run the Utilities Administration against an Oracle 8.1.6.1.0 database on Sun Solaris, I don't have any problems.
    Can you run other Headstart generated applications on this database, like the Headstart Demo or the Foundation Application? In other words, is it only the Utilities Admin that gives the error?
    regards, Sandra

  • ORA-20998: Transaction Failed on Headstart Utilities 6.5 installation

    Hello,
    I am having problem when running insthsu.sql script to install
    Headstart utilities 6.5. We are doing client/server approach. The
    server is Sun 450 - Oracle 8.1.7.0.0
    Designer 6i Release 4 repository was installed on the server.
    How far was the installation:
    1. Installed HST65 --> No problem found
    2. Installed HDEMO65 --> No problem found
    3. Failed on the following statement on insthsu.sql script:
    ... installing Quality Check utilities
    execute hsu_qa_app.install;
    error message:
    hsu65@devl> execute hsu_qa_app.install
    BEGIN hsu_qa_app.install; END;
    ERROR at line 1:
    ORA-20998: Transaction Failed
    ORA-06512: at "HST65.QMS$ERRORS", line 128
    ORA-06512: at "HST65.QMS_TRANSACTION_MGT", line 814
    ORA-06512: at "HSU65.CG$AIS_HSU_UTILITIES", line 39
    ORA-04088: error during execution of
    trigger 'HSU65.CG$AIS_HSU_UTILITIES'
    ORA-06512: at "HSU65.HSU_INSTALL", line 132
    ORA-06512: at "HSU65.HSU_QA_APP", line 40
    ORA-06512: at line 1
    Any idea or direction where should I go from here?
    Thanks,
    Sanny Subowo

    Ali,
    You are running into a bug in the install form. It sees the tables that you imported manually (like the message told you to do), and then complains about them. The best thing to do is change the code in the hsdinst.fmb where the check for existing objects is performed in program units CHECK_USERS:
    function hsu_objects_exist
    return boolean
    is
    cursor c_chk
    is
    select 'x'
    from user_objects
    where object_name like 'BL_%'
    -- or object_name like 'HSU_%'
    -- or object_name like 'OMR_%'
    So comment out the two lines as indicated above and recreate the fmx.
    Kind regards,
    Peter

  • Unhandled exception when starting headstart utilities 6i

    Installed Designer 6i (4.1.1), Developer patch 7, Headstart 6.5.
    Try to launch Headstart utilities, logon, get the context workarea question. Choose the only one we've got, and get error message:
    Unhandled exception in SET_CONTEXT_WORKAREA:ORA-4020:deadlock detected while trying to lock object HSU65.BLAPI, trg block: WKA, trg item:WKA.
    CONTEXT_WORKAREA_IRID
    Anyone any ideas?
    Thanks!

    Ernst,
    Did you recently upgrade your Oracle Designer version?
    You probably have to re-run the grants script, that grants access on Repository objects to the Utilities owner.
    To do this, log on to SQL*Plus as the Oracle Repository Owner, and run the following script, located
    in the [Headstart Home]\hsu\scripts directory, with the following command line parameters.
    d6grtsyn.sql [Headstart Home] [Utilities Owner schema name]
    for example:
    d6grtsyn.sql c:\hsd65 hsua65
    SQL*Plus will be closed automatically. The log file d6grtsyn.log will be created in the Headstart Home.
    Check this log file for any errors.
    kind regards,
    Sandra

  • Error on HSU_OUTPUT dir when using Headstart Utilities

    Hi all,
    Does anyone have experience with the following problem: when I try to run the Headstart Utilities - Quality checks (elements) - Functions check, I get the following error:
    "Could not create file, possibly because output-directory does not exist. Check output directory in Windows Registry (HSU_OUTPUT)"
    My Registry has the following entry:
    Local Machine\Software\Oracle\Headstart
    which contains keys named HSU_OUTPUT, HTML_BROWSER and IMAGEFILE_PATH.
    So the entry seems to be OK, it refers to an existing dir, what's the problem?
    Regards, Ronald
    P.S. The other checks are working fine, I used entities, sequences and domains without a problem.

    Sandra,
    I've tried to reproduce the error I got in the beginning, but now I'm getting a database error (ORA-02291: integrity constraint (HSU21.HSU_QAR_USE_FK1) violated - parent key not found) While I was looking into that I noticed the following:
    In the package procedure HSU_QA_FUN.run there's a call to HSU_QA.INIT. In the INIT-call the user-id (3rd arg) is hard coded to be 1. In the HSU_QA_ENT.run the call is used with p_use_id, which I would expect te be correct. I noted that in the installation scripts the code is the same, so it's not a change we made.
    My question is: is there to be a pre-defined user in HSU_USERS with user-id 1? Or should the '1' in the call to init be changed into p_use_id, like in HSU_QA_ENT?
    Thanks for your help,
    Ronald

  • Headstart utilities (Find Window)

    I have used the HeadStart Utilities - Create Find Windows on my
    module, which has only one module component (SOT).
    I run the Create Find Windows utility and get the following
    error:
    "CDA-01151: Bound Item (Module Unit
    2554971643047902815540063643913191820, Name ID): Cannot set
    UPDATE_FLAG - the Column is in a non-updateable Constraint"
    Headstart utilities : Revision 6.5.0.1
    I tried different module and it was the same thing.
    I would like to know the reason.
    Regards

    I'm not sure, but probably there are bound items in your
    component, which are in a not updatable constraint, such as a
    primary key which can't be updated, or foreign keys, etc.
    Try setting these to updatable, and if necessary, after the
    utility back. Why it doesn't work as it is, I don't know either.
    Regards
    Jessica

  • Changes to tables not being picked up by certain Headstart Utilities

    I modified an existing table in our repository by adding a new column to the table. This column has the same properties as another column in the table. The Headstart utility 'Maintain Default Events For Entities' had been run for all tables before the new column was added. As expected, all the columns in the table had UPDATE events created for them, except of course the new column.
    As none of the events associated with this table had been used, I ran the 'Cleanup Unused Event for Entities' utility for the table and then re-ran the 'Maintain Default Events For Entities' utility for the table, in order to create an UPDATE event on the new column. This however, was not the case as an UPDATE event was not created for the new column. It appears to have been completely ignored.
    I have checked for the obvious i.e. was the table change applied properly in the repository and had the database been properly re-generated from the server model and everything appears to be correct.
    I have noticed that certain Headstart utilities, 'Enforce CDM Ordering Standard for columns' and 'Set column display length' do pick up the new columns. 'Enforce CDM Ordering Standard For Attributes' however, is another utility that does not pick up the new column.
    Any solutions and explanations for the above would be much appreciated.
    Thank You,
    Aneesha.
    null

    Aneesha,
    In your formulation of the problem, you seem to sometimes be using the terms "table" and "column" when you actually mean "entity" and "attribute". This makes it a bit hard for me to reconstruct your steps. Did you create both a new attribute on the entity, and a new column on the table, and are the two linked together (i.e. if you go to the attribute, is the "Implemented by Columns" node filled correctly?
    Kind regards,
    Peter
    null

  • Problems saving results of Headstart Utilities Journalling

    Unique key conflict when re-using Utility Maintain journal tables.
    We experience the same problems.
    Colum names are not too long.
    We are working with an unversioned repository and Headstart Utilities 6.0.5.4
    Als the Static Domain rules utility is not able to update prior generated Triggers.
    Workaround is to drop the previously generated triggers!
    However, this workaround is not an option for the Journal tables, because Module table usages are referencing this table.
    Please let us know as soon as possible.
    Joep

    Unique key conflict when re-using Utility Maintain journal tables.
    We experience the same problems.
    Colum names are not too long.
    We are working with an unversioned repository and Headstart Utilities 6.0.5.4
    Als the Static Domain rules utility is not able to update prior generated Triggers.
    Workaround is to drop the previously generated triggers!
    However, this workaround is not an option for the Journal tables, because Module table usages are referencing this table.
    Please let us know as soon as possible.
    Joep

  • Problems saving results of Headstart Utilities

    I've problems with two utilities concerning journalling:
    1. Maintain journal tables HSU_CJNT Revision 6.5.0.4
    This package does not want to save the changes made to the journal tables in the repository. The error is CDA-01305: Column: UID 1 uniqueness violation. Version of Repository is 6.5.69.2.0
    2. Maintain journalling business rules HSU_JNBR Revision 6.5.0.2
    This package also doen't want to save adjustments, in this case to the BR's Errors :
    CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS) in Container (Name MAT)
    CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD) in Container (Name MAT)
    CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL) in Container (Name MAT)
    Anyone any suggestions/patches?

    Willem,
    Regarding your problems:
    1. Maintain journal tables HSU_CJNT Revision 6.5.0.4
    This package does not want to save the changes made to the journal tables in the repository.
    The error is CDA-01305: Column: UID 1 uniqueness violation. Version of Repository is 6.5.69.2.0This UID requires the column name to be unique within the table.
    What could be the case is that your table has two or more columns that have almost identical names, and only differ
    after the 26th character. The utility creates column names like OLD_<column name> and NEW_<column name>.
    If for example you have 2 columns in the same table that are called VERY_VERY_LONG_COLUMN_NAME1 and
    VERY_VERY_LONG_COLUMN_NAME2, the utility applies the algorithm 'OLD_'||substr(r_col.col_name, 1, MAX_IDENTIFIER_LENGTH - 4)
    and come up with OLD_VERY_VERY_LONG_COLUMN_NAME, for both of the original columns!
    Could you check if this is the reason for the failure? If so, you could try renaming the columns, or changing the algorithm for deriving the journal column names in package hsu_cjnt.
    2. Maintain journalling business rules HSU_JNBR Revision 6.5.0.2
    This package also doen't want to save adjustments, in this case to the BR's Errors :
    CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_INS) in Container (Name MAT)
    CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_UPD) in Container (Name MAT)
    CDA-02035: Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL): Uniqueness conflict with Database Trigger (Table 2642375373300319097291377310396885686, Name BR_ADS_JRN_DEL) in Container (Name MAT) It seems like the utility tries to create new database triggers, but they already exist in the Container (=Application System or Folder).
    It could be that the database triggers already exist in a different workarea than the one you are running the utility in.
    The utility can see only the objects in the context workarea, so it doesn't know about the possible existence of the triggers in another workarea.
    You can check this by running the following query while logged in as a Repository user or the Utilities owner:
    select name
    from ci_database_triggers
    where table_definition_reference = 2642375373300319097291377310396885686
    If it selects the trigger names BR_ADS_JRN_INS etc, but you cannot see those triggers in your workarea, then they must exist in another workarea.
    Try to include them in your workarea or run the utility in the other workarea.
    Could you check if this is the case?
    kind regards, Sandra

  • ANNOUNCEMENT: Headstart Utilities Patch 6.5.2.3 now available on Supplement Option!

    All,
    Subscribers of the Supplement Option can now download Headstart Patch 6.5.2.3 and Headstart for Apps patch 6.5.2.3
    from My Oracle, using the iDevelopment Accelerators link in the Supplement Offering portlet.
    The main purpose of this patch is to improve the performance of the CDM RuleFrame engine
    when large transactions are involved.
    During development and testing of this patch the following improvements of the CDM RuleFrame engine
    were measured on an Windows 2000 laptop with RDBMS 8.1.7.1.1.
    - 100 DML statements, 3 Business Rules per statement performance improved from 1.45 sec to 1.05 sec (28%)
    - 500 DML statements, 3 Business Rules per statement performance improved from 23.760 sec to 8.48 sec (64%)
    - 1000 DML statements, 3 Business Rules per statement performance improved from 78.79 sec to 19.260 sec (76%)
    - 2000 DML statements, 3 Business Rules per statement performance improved from above 300 sec to 48.22 sec (83%)
    - 5000 DML statements, 3 Business Rules per statement performance improved from ??? to 143.41 sec
    It evolves that the RuleFrame engine takes up more time for larger transactions now in a rather linear way.
    This means that within 15 minutes more than 100.000 business rules can be validated
    on a small windows 2000 laptop.
    Besides this performance improvement, the patch also implements the following enhancements to CDM RuleFrame:
    - The utility 'Create CAPI Custom Service' makes it possible to include a CAPI Custom Service
    (that is, your own package or function) in more than one CAPI
    - The utility 'Create VAPI Definition' can now also create VAPI's for subtypes (controlled by new utility parameter)
    Furthermore, several Utilities bugs have been fixed in this patch. See the readme in the patch for more details.
    If you don't have the Supplement Option, contact your local Oracle Consulting representative.
    For more information, read the original announcement of the Supplement Option in this forum at
    Re: Archiving the data .
    kind regards,
    The Headstart Team.

    I was running just the base version of Headstart until yesterday, when I applied all 3 patches at once. On the base version this column wasn't being included in the CAPI, and now it is, so I guess the change could've come about in any of the patches.
    The name of my table is reg_photos, and the column that has Complete=No is large_image.
    The specific areas of the CAPI where it's included and which cause compilation errors are:
    There's public cursors at the start of the package where the column is being selected:
    -- public cursors
    -- cursor to select one particular row
    cursor c_rpho
    ( b_project_code in varchar2
    , b_photo_no in number
    ) is
    select rpho.rowid the_rowid
    , rpho.project_code
    , rpho.photo_no
    , rpho.photo_type
    , rpho.photo_date
    , rpho.small_image
    , rpho.large_image
    , rpho.created_by
    , rpho.creation_date
    , rpho.last_updated_by
    , rpho.last_update_date
    from reg_photos rpho
    where rpho.project_code = b_project_code
    and rpho.photo_no = b_photo_no
    -- cursor to select all rows
    cursor c_rpho_all
    is
    select rpho.rowid the_rowid
    , rpho.project_code
    , rpho.photo_no
    , rpho.photo_type
    , rpho.photo_date
    , rpho.small_image
    , rpho.large_image
    , rpho.created_by
    , rpho.creation_date
    , rpho.last_updated_by
    , rpho.last_update_date
    from reg_photos rpho
    It's also included in function get_char_value but this isn't causing a compilation error:
    elsif upper(p_column_name) = 'LARGE_IMAGE'
    then
    return l_row.large_image;
    And also in procedure validate_row:
    g_current_ind.large_image := true;
    I guess it's easy enough to go in and comment all the references out, but I would've thought that columns of this nature should not be included in the CAPI in the first place?
    Thanks,
    Kim.

  • Oracle Headstart Designer 2.1.2 Utilities - Database Auth Scheme DB.030

    I'm trying to use the Database Auth Scheme DB.030, but without
    much success.
    I've created roles and users, granted system priviliges and run
    the .sql file. I added a role to a module under its Security
    tab, open Headstart Utilities and select my database, new role
    and correct schema in DB.030. When I hit Run, I get the
    following information: -
    Information
    Message
    Deleted old group object privileges created by this utility.
    Created privilege for group 'CC_OP' and
    table 'OSS_ANONYMOUS_REQ_DEFS'.
    Created privilege for group 'CC_OP' and table 'OSS_DOCUMENTS'.
    Modified privilige for group 'CC_OP' and table 'OSS_DOCUMENTS'.
    I was expecting to see extra entries in role_tab_privs, but
    nothing extra gets added.
    Has anyone got a guide to using DB.030, or can tell me what I'm
    doing wrong. There isn't any information about DB.030 in my
    Utilities manual.
    Thanks.

    I'm not aware of any bugs related to this code.
    In you utility preferences window, set the debug level to 'Debug
    Detailed'. This will cause your log file to give you much more
    information. You can examine the utility code to try to
    determine where it might be going wrong. You can find the name
    of the utility package in the online help for the utility. You
    can then use something like PL/SQL Developer to examine the code.
    Regards,
    Lauri

  • Install Headstart 9i Utilities without 9ias ?

    Hi,
    i don't know if it was possible to install the headstart utilities without 9iAS.
    The DBA have some performances problems and waits for support answer.
    Temporaly i wan't to install the Hsd9i utilities, perhaps using Oc4j ?
    Any suggestion very apprecied.
    Regards.
    Philippe

    I once installed Headstart 6i without the 9iAS.
    In my case I needed only a running HTTP and Forms 6i Server.
    I don't know if Forms9i has Forms 9i Server ??
    I have heard also that it's possible to run Forms 9i (wth Headstart) with an OC4J server. In ths wa you can run the foms in a c/s enviroment, assumed you have an OC4J instance running on the client.
    Hope this helps.

  • Adding container headstart to 'GLOBAL WORK AREA'

    I am trying to install HEADSTART 10G r2 for designer 10.2 into Designer. I got everything working the demo, utilities and the designer forms templates.
    Finally I want to imported the headstart 10G R2 Dump file (versioned) into designer. The import did not work first because we needed to use IMP 10.2 but designer uses IMP 10.1. But that problem is solved.
    At the moment I have a container with headstart 6.5.4.0a which I want to include (with Edit Workarea of Include Workarea) into the WA 'GLOBAL WORK AREA'. But that failes with the error message
    - CDR-01006: Failed to process rule specification.
    - CDR-01059: Rule INCLUDE_FOLDER has an invalid path (headstart=Application
    - CDR-01000: Unable to locate object with path headstart=Application System.
    I did everything mentioned in the document 'installation instructuctions for oracle Headstart 6.5.4.0 for 10g R2'.
    please can anybody give me a clue what I can do to include this container in the WA.
    Thanks
    Franc

    To add to the above, I've been using WSBR_API.ADD_ITEM(p_text, ...), and when I check out the WWSBR_ALL_ITEMS it would seem as though the text field is a CLOB. This would lead me to think that my error is caused by me trying to push a CLOB through a VARCHAR2.
    What's the standard way, using the API, of adding an item that is a CLOB?

  • Problem using "Create Business Rule Design Definition" utility

    Hi everyone,
    I tried to create a business rule with Headstart Utilities - Create Business Rule Design Definition (Revision 6.0.0.20) and I got the following errors :
    Errors
    Message
    Combination of Message Prefix and Message Number (SGM-ENG) does not match format AAA-NNNNN.
    Activity aborted with ORACLE internal errors.
    -1400 ORA-01400: cannot insert NULL into ("HST50"."QMS_MESSAGE_TEXT"."LANGUAGE")
    I suppose that the utility concatenate the message prefix and the language to build the error message.
    Our Oracle Designer version is 6.0.3.9.0, Headstart 2.1.2 with patch 12.4 and Developper is 6.0.5.35.3
    Any patch available?
    Regards,
    Jerome Couture

    Tim,
    Headstart should be able to check out any tables you need.
    We think we have the user settings
    done correctly, but there may be something that we
    have missed. How can we get Headstart to
    automatically check-out the table(s) for which we
    want to run the Business Rules design transformer?The user settings you need are (see also pages 5-7 and 5-10 in the Headstart User's Guide):
    - Under 'Process the following objects', choose 'Checked out by anyone'
    - Also check the check box '... also Checked In objects'
    - Choose whether you want to automatically check out with or without lock
    If this does not help, please run the utility with log level 'Debug Detailed' (can also be set in the User Preferences) and report the last few lines of the log messages. They should give an indication of why the check out does not succeed.
    Hope this helps,
    Sandra Muller

  • Composite foreign key, LOV, WSG, Designer 6i

    Hello,
    I have one composite foreign key that consists of 3 columns,
    which belongs to three different tables (there are
    master-detal-detail relationships between those 3 tables). Let's
    call those tables A, B and C.
    Now, I'd like to generate wsg module (based on table D) that has
    all three columns displayed. Also, I'd like to generate three
    dependant LOVs in such way that I am able first to select row
    from table A using first LOV. Second LOV should display rows from
    table B, but only those rows that are in context of A. Similary,
    third LOV should display rows from table C, but only rows in
    context of B.
    Is there any way to this in Designer 6i Release 4 ? This way
    default behaviour in Designer 2.1.2 and 6.
    Thanks.
    Goran Oparnica
    IN2 d.o.o.
    Zagreb

    The Headstart Utilities are part of the Headstart Oracle Designer package which is downloadable from OTN. Headstart Oracle Designer is an accelerator suite consisting of Templates, Object Libraries, Preference Sets, PL/SQL libraries and utilities to make using Designer to generate Forms applications easier.
    To get more information on Headstart you can go to the OTN home page, choose Internet Tool under the Products section on the menu. Under the Headstart 'Internet Developer Suite', click on Headstart Oracle Designer
    Regards,
    Lauri

Maybe you are looking for