3.6.1 RC! --> 3.6.2 Upgrade error

Hi,


I have just run an upgrade from 3.6.1 RC1 to 3.6.2 and have followed the instructions located at Upgrading from 3.6.0 but am receiving the following error when attempting to log back in:


     MySource Error
    [ASSERT EXCEPTION] DB Error: unknown error
    SELECT DISTINCT(l.majorid), a.type_code, t.treeid FROM sq_ast_lnk l INNER JOIN sq_ast_lnk_tree t ON l.linkid = t.linkid INNER JOIN sq_ast a ON l.majorid = a.assetid WHERE t.treeid IN ( SELECT * FROM sq_get_parent_treeids('7', 4) ) AND a.type_code IN ( SELECT type_code FROM sq_ast_typ_inhd WHERE inhd_type_code IN ('user', 'user_group') ) ORDER BY t.treeid [nativecode=ERROR: function sq_get_parent_treeids("unknown", integer) does not exist HINT: No function matches the given name and argument types. You may need to add explicit type casts.] (LINE 2424 IN [SYSTEM_ROOT]/core/include/asset_manager.inc) [SYS0270]


Can anyone help? [flips hair and bats eyelids]

Thanks...John.

Run step_02.php to create the new PostgreSQL stored procedures.

[quote]Run step_02.php to create the new PostgreSQL stored procedures.
[right][post=“7812”]<{POST_SNAPBACK}>[/post][/right][/quote]



Step 2 appeared to run without error but… I get the same error when trying to load http://domain.name/_admin/

[quote]Step 2 appeared to run without error but… I get the same error when trying to load http://domain.name/_admin/
[right][post=“7813”]<{POST_SNAPBACK}>[/post][/right][/quote]





Sorry to bump this but this problem is a show-stopper for us!

[quote]Sorry to bump this but this problem is a show-stopper for us!
[right][post=“7817”]<{POST_SNAPBACK}>[/post][/right][/quote]





Can you have a look in the database and see if the functions actually exist?


    select proname from pg_proc where proname = 'sq_get_parent_treeids';


You should have two entries in there for these two function signatures:

    sq_get_parent_treeids(VARCHAR, INT)
    sq_get_parent_treeids(VARCHAR, INT, TIMESTAMP)


If they are missing, something is not working in step_02. To get the ball rolling, you can try copying the whole functions out of <SYSTEM_ROOT>/install/pgsql_functions.xml, into the psql console. The functions are in CDATA sections, so you just want the raw code. You will probably want to specify the -n option to disable readline, otherwise the tabs in the code will expand the psql commands.

I don't think that the signatures changed from 3.6.1 RC1 to 3.6.2, but you could also try dropping the functions first using:

    DROP FUNCTION sq_get_parent_treeids(VARCHAR, INT);
    DROP FUNCTION sq_get_parent_treeids(VARCHAR, INT, TIMESTAMP);


and running step_02.php again.


Thanks for your help Marc, I appreciate it.

I have done as you have suggested and can confirm that they are both there. I also droped them as suggested and re-ran step_02.php which again appears to have run successfully and amongst other things reports in output:

    PGSQL STORED PROCEDURES CREATED
    .....(other stuff)
    sq_rb_get_parent_treeids Function
    sq_get_parent_treeids(VARCHAR, INT) Function
    sq_get_parent_treeids(VARCHAR, INT, TIMESTAMP) Function


A re-check in psql reports:

    matrixdb=> select proname from pg_proc where proname = 'sq_get_parent_treeids';
            proname
    -----------------------
     sq_get_parent_treeids
     sq_get_parent_treeids
    (2 rows)



Is a database shut-down/re-start required?
Should I follow on from step-02 with Step_03?


I am still receiving the identical error.

Hmmm… I think we're arrived at a critical juncture in our evaluation of this product :unsure:


I've done a shut-down/re-start but still receive the same error. The error itself may just be a red herring triggered by some other failure I just don't know enough about the product to be able to say for sure and frankly nor should I have to.



With an 8Gb site network comprising a dozen sub-webs and over 40,000 files a working import script is a critical component as is the systems ability to integrate and co-exist with other application systems and environments as well as the requirement for straight-forward upgrades.



I am truely grateful however, that these problems have ocurred during evaluation and not on a production machine as we would have been down for four (4) days now. As the product matures I'm sure we'll have another look at it further down the track but for now it looks as if we'll have to pass it by.



Thanks for everyone's help and assistance along the way.

Hi John, I'm sorry to hear about your frustrations. In case it helps you should know Squiz offer professional support services that cover everything from server setup to training or even content import. MySource Matrix is a complex system and while we are doing everything we can to make things easier and support users through these free forums there are times when some experience comes in handy. I'm sorry this is such a sales pitch, I just think it would be a shame for you to drop your evaluation when it’s quite possible it could be solved quickly by asking one of our team to look at your system.

Thanks John,


I'm no no doubt sure that your team could nail this in an instant under a maintenance contract :smiley: