Oracle error at end of install

Squiz Matrix Installation
1

After having a few problems with the install due to haveing the CGI version of php (compiled up a nice fresh copy of the CLI version in the end) I got mysource installed. When I try and view the actual site I get the below error. I've completely removed the mysource install and deleted and re-created the DB several times, the error is always the same.

    MySource Error  
    [ASSERT EXCEPTION] DB Error: unknown error
    SELECT * FROM table(sq_get_parent_treeids('7', 4)) [nativecode=ORA-22905: cannot access rows from a non-nested table item] (LINE 7005 IN [SYSTEM_ROOT]/core/include/asset_manager.inc) [SYS0270]  


Any help would be appriciated.
2

What is your Oracle version?

3

9.2.0.6

4

I have not come across this error before, and believe that this is an oracle bug (Metalink 1702058).


A known workaround is to change the CURSOR_SETTING session variable to exact or similar. Perhaps you can change this variable and re-execute the query in sqlplus to verify if this bug is present?


    SELECT * FROM table(sq_get_parent_treeids('7', 4));
    ALTER SESSION SET cursor_sharing=exact;
    SELECT * FROM table(sq_get_parent_treeids('7', 4));
5

Thankyou, that fixed it.

6

However I'm now getting simmlar errors when logging into the admin page. I'm talking to our DBA's about moving this schema to a database running on a different version of oracle. Do you know which version this bug was fixed in? (the oracle website isn't overly helpfull about this as the bug has been unpublished and half the content is missing).


Thanks for all the assistance. I really appriciate it.

7

No patch or version has been published in response to this bug as it's a fairly recent one. Did you set the cursor sharing variable for the system ?

    ALTER SYSTEM SET CURSOR_SHARING=EXACT scope=spfile;


which assumes that you are using a spfile.
Setting it using ALTER SESSION will not persist the value beyond that session.


My only other solution for now would be to upgrade to 10g, otherwise you will have to wait for a patch to be published.
8

We've moved to a 10g server. Oracle tells us the bug was fixed in 10.2
No longer having this problem. After fixing a typo in my config it all seems to be going now.



THANKS!