Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

3.3 - 3.4 Update error

miscs
2010-03-17
2012-11-13
  • miscs
    miscs
    2010-03-17

    Hi all,

    i upated our po form 3.3 to 3.4 today and most parts are working. thanks for the new release, looks very promising so far!

    unfourtunaly i ran into an error updating Categories 1.0d7

    "Categories 1.0d7  /packages/categories  Upgrade." :

    failed to install Categories, version 1.0d7. The following error was generated:

    psql:categories-create.sql:42: ERROR:  relation "category_trees" already exists
    psql:categories-create.sql:65: ERROR:  relation "category_tree_translations" already exists
    psql:categories-create.sql:99: ERROR:  relation "categories" already exists
    psql:categories-create.sql:101: ERROR:  relation "categories_left_ix" already exists
    psql:categories-create.sql:102: ERROR:  relation "categories_parent_ix" already exists
    psql:categories-create.sql:140: ERROR:  relation "category_translations" already exists
    psql:categories-create.sql:176: ERROR:  relation "category_tree_map" already exists
    psql:categories-create.sql:178: ERROR:  relation "cat_tree_map_ix" already exists
    psql:categories-create.sql:211: ERROR:  relation "category_object_map" already exists
    psql:categories-create.sql:213: ERROR:  relation "cat_object_map_ix" already exists
    psql:categories-create.sql:231: ERROR:  relation "category_temp" already exists
    psql:categories-create.sql:261: ERROR:  relation "category_links" already exists
    psql:categories-create.sql:263: ERROR:  relation "category_links_rev_ix" already exists
    psql:categories-create.sql:265: ERROR:  relation "category_links_id_seq" already exists
    psql:categories-create.sql:301: ERROR:  relation "category_synonyms" already exists
    psql:categories-create.sql:304: ERROR:  relation "category_synonyms_locale_ix" already exists
    psql:categories-create.sql:306: ERROR:  relation "category_synonyms_name_ix" already exists
    psql:categories-create.sql:308: ERROR:  relation "category_synonyms_id_seq" already exists
    psql:categories-create.sql:336: ERROR:  relation "category_synonym_index" already exists
    psql:categories-create.sql:339: ERROR:  relation "category_syn_index_trigram_ix" already exists
    psql:categories-create.sql:341: ERROR:  relation "category_syn_index_synonym_ix" already exists
    psql:categories-create.sql:365: ERROR:  relation "category_search" already exists
    psql:categories-create.sql:368: ERROR:  relation "category_search_date_ix" already exists
    psql:categories-create.sql:370: ERROR:  relation "category_search_id_seq" already exists
    psql:categories-create.sql:397: ERROR:  relation "category_search_index" already exists
    psql:categories-create.sql:400: ERROR:  relation "category_search_ind_trigram_ix" already exists
    psql:categories-create.sql:402: ERROR:  relation "category_search_ind_query_ix" already exists
    psql:categories-create.sql:425: ERROR:  relation "category_search_results" already exists
    psql:categories-create.sql:428: ERROR:  relation "category_results_similarity_ix" already exists
    psql:category-tree-package.sql:237: ERROR:  syntax error at or near "c" at character 19
    QUERY:  update categories c set parent_id = (select t.category_id from categories s, categories t where s.category_id = c.parent_id and t.tree_id = copy.dest_tree and s.left_ind +  $1  = t.left_ind) where tree_id =  $2
    CONTEXT:  SQL statement in PL/PgSQL function "category_tree__copy" near line 38
    psql:category-tree-package.sql:237: LINE 1: update categories c set parent_id = (select t.category_id fr…
    psql:category-tree-package.sql:237:                           ^
    psql:category-synonym-package.sql:268: ERROR:  trigger "category_synonym__insert_cat_trans_trg" for relation "category_translations" already exists
    psql:category-synonym-package.sql:273: ERROR:  trigger "category_synonym__update_cat_trans_trg" for relation "category_translations" already exists
    CONTEXT:  SQL statement "SELECT  acs_object_id_seq.nextval from dual"
    PL/pgSQL function "acs_object__new" line 12 at select into variables
    PL/pgSQL function "acs_sc_contract__new" line 7 at assignment
    psql:categories-init.sql:15: ERROR:  duplicate key violates unique constraint "acs_sc_contracts_name_un"
    CONTEXT:  SQL statement "insert into acs_sc_contracts ( contract_id, contract_name, contract_desc ) values (  $1 ,  $2 ,  $3  )"
    PL/pgSQL function "acs_sc_contract__new" line 16 at SQL statement
    psql:categories-init.sql:19: ERROR:  current transaction is aborted, commands ignored until end of transaction block
    psql:categories-init.sql:23: ERROR:  current transaction is aborted, commands ignored until end of transaction block
    psql:categories-init.sql:32: ERROR:  current transaction is aborted, commands ignored until end of transaction block
    psql:categories-init.sql:50: ERROR:  relation "acs_named_objects" already exists
    psql:categories-init.sql:52: ERROR:  relation "acs_named_objs_name_ix" already exists
    psql:categories-init.sql:53: ERROR:  relation "acs_named_objs_package_ix" already exists

    NOTE: If the error comes from a sql script you may try to source it manually. When you are done with that you should revisit the APM and try again but remember to leave the manually souced sql scipts unchecked on the previous page.

    any help highly appreciated!
    thanks in advance!

     
  • rssm
    rssm
    2012-06-15

    Hi there

    I just started with project-open version 3.5 on cent os 5.5 and had same problem and was kinda disheartened that there was no solution suggested.. Being a newbie, finally nailed down the problem after a marathon session to a very simple problem in postgress regarding alias names and possibly another bug in the code itself. Please try by replacing the UPDATE query starting at line 214 in file category-tree-package.sql (/web/projop/packages/categories/sql/postgresql)
    from
    update categories c set parent_id = (select t.category_id
    from categories s, categories t
    where s.category_id = c.parent_id
    and t.tree_id = copy.dest_tree
    and s.left_ind + v_new_left_ind = t.left_ind)
    where tree_id = p_dest_tree;

    to

    update categories set parent_id = (select t.category_id
    from categories s, categories t
    where s.category_id = categories.parent_id
    and t.tree_id = p_dest_tree
    and s.left_ind + v_new_left_ind = t.left_ind)
    where tree_id = p_dest_tree;

    Note that alias has been removed and p_dest_tree replaces copy.dest_tree.

    You may want to copy all the statements from categories-drop.sql and execute them in psql before attempting this to get rid of stale entries as a result of previous aborted (?? non acid ?? ) transactions. At least I had to to do that !!

    Hope that helps.

     
  • Frank Bergmann
    Frank Bergmann
    2012-06-15

    Hi RSSM,

    Sorry, I really don't understand a) your problem and b) the solution you found for it.

    The original mail from MISCS refers to an upgrade some 2 years ago. You will never need to see these versions at all (you're on a fresh install of V3.5).

    Also, the query you refer to should work in all PostgreSQL version from 7.2 until 8.4…

    Cheers,
    Frank

     
  • CTC
    CTC
    2012-06-19

    Hi there,
    I just installed project open and, after the first configuration, I got, after login, the following error. Could you help me to tell what is the problem?
    Thank you

    Database operation "0or1row" failed
    (exception ERROR, "ERROR:  table row type and query-specified row type do not match
    DETAIL:  Query has too few columns.
    CONTEXT:  SQL statement "INSERT INTO im_tickets ( ticket_id, ticket_status_id, ticket_type_id, ticket_creation_date ) values (  $1 ,  $2 ,  $3 , now() )"
    PL/pgSQL function "im_ticket__new" line 36 at SQL statement
    ")

        while executing
    "ns_pg_bind 0or1row nsdb0 {
            SELECT im_ticket__new (
                   :ticket_id,            - p_ticket_id
                   'im_ticket',           - object_type
                   now(),                 - creation_date
                   :error_…"
        ("uplevel" body line 1)
        invoked from within
    "uplevel $ulevel

    • "
          ("postgresql" arm line 2)
          invoked from within
      "switch $driverkey {
                      oracle {
                          return [uplevel $ulevel $args]
                      }
             …"
          invoked from within
      "db_exec 0or1row $db $full_name $sql"
          invoked from within
      "set selection "
          ("uplevel" body line 2)
          invoked from within
      "uplevel 1 $code_block "
          invoked from within
      "db_with_handle -dbn $dbn db {
                  set selection
              }"
          (procedure "db_string" line 27)
          invoked from within
      "db_string ticket_insert {}"
          invoked from within
      "set ticket_id "
          ("uplevel" body line 314)
          invoked from within
      "uplevel {
      # /packages/intranet-forum/www/intranet/forum/new-system-error.tcl
      #
      # Copyright (C) 2003 - 2009 ]project-open[
      #
      # All rights reserved. Ple…"
          (procedure "code::tcl::/web/projop/packages/intranet-forum/www/new-syste…" line 2)
          invoked from within
      "code::tcl::$__adp_stub"
          invoked from within
      "if {  } {

          # ensure that data source preparation procedure exists and is up-to-date
          adp_init tcl $__adp_stub
    …"
        ("uplevel" body line 3)
        invoked from within
    "uplevel {

        if {  } {

          # ensure that data source preparation procedure exists and is up-to-date
          adp_init t…"
        (procedure "adp_prepare" line 2)
        invoked from within
    "adp_prepare"
        invoked from within
    "template::adp_parse [file root ] {}"
        (procedure "adp_parse_ad_conn_file" line 6)
        invoked from within
    "$handler"
        ("uplevel" body line 2)
        invoked from within
    "uplevel $code"
        invoked from within
    "ad_try {
                    $handler
                } ad_script_abort val {
                    # do nothing
                }"
        invoked from within
    "rp_serve_concrete_file "
        (procedure "rp_serve_abstract_file" line 60)
        invoked from within
    "rp_serve_abstract_file "$root/$path""
        ("uplevel" body line 2)
        invoked from within
    "uplevel $code"
        invoked from within
    "ad_try {
                   rp_serve_abstract_file "$root/$path"
                   set tcl_url2file()
                   set tcl_url2path_info() [ad_conn path_…"

     
  • Frank Bergmann
    Frank Bergmann
    2012-06-22

    Hi,

    Which version are you using? Also, what exactly means "installed"? Do you use the Windows installer or VMware?
    Also, please provide us the URL that produced the error. It seems as if you were trying to create a new ticket, which
    is definitely not the first page after login… Maybe you clicked on a "Report this error" button?

    Cheers,
    Frank