More Mac Oracle10g Problems
|
jlangdale
Joined: 2003-11-09
Posts: 38 |
Posted: Mon, 2005-02-07 16:01
|
|
Starting over with updated code on my gallery 2 installation. Ok I'm getting a too long identifier message in GalleryToolkitPropertyMimeTypeMap.sql for the indexes. Remember to make the identifiers shorter. I'm also getting problems again with the CreateBitOr.sql file. I thought we fixed this but obviously not. Looks to be needed to be done by hand using sqlplus in stages. Maybe breaking it up into 3 files? I dunno, I can't remember what we did to fix this now. Maybe looking at the old thread will help refresh my memory. |
|
Posts: 8601
i installed on solaris oracle 9i last week.. i added a semicolon at the end of CreateBitOr.sql to make it work on that platform.. if you saw the cvs comment for that checkin (no, i don't expect that you did..) it said "i hope this still works for oracle 10g".. perhaps not. try removing that last semicolon and see if that works. i hope we don't need oracle version detection to get the syntax correct for this file!
i didn't have any problem with TkPropertyMimeTypeMap.. we haven't changed that one in some time... the last checkin on that file was to shorten the index name under 30 characters for oracle.. are you using a long table prefix? (something other than g2_ )
Posts: 38
Oh yea sorry, I changed it to g24_ so it wouldn't interfere with my current g2 version. That may be why it broke.
Btw, do you think there is any chance of easily moving my current g2_tables into the new version? I know that is a alpha to alpha move, but I'm just wondering if it's not easiler to try than to simply remake and reimport all my stuff.
I removed the CreateBitOr.sql and shorten the index myself with my longer prefix. The install finished with no errors, however, the main page errored out. It was saying something about the BIT_OR stuff. So, I figured I'd use the new code. Deleting the old objects and making the new ones errored out, forgot to purge the recyclebin. After that, it worked ok. I didn't see much difference between the CreateBitOr.sql code and my old code tree. Anyway, my old version of g2 seem to work too.
My reluntance to completely clear everything and reinstall is because I'm not totally familar with Oracle10g as you can tell. I want to figure out how to backup my current g2 install and database, and how I can restore it before I totally wipe it. Hence why I renamed the prefix.
Old: http://24.202.107.64:81/gallery2.32/main.php
New: http://24.202.107.64:81/gallery2.4/main.php
Posts: 8601
first it would be great if you could try a clean install with the most recent nightly snapshot and a table prefix 3 chars or shorter.. let me know if CreateBitOr.sql fails (what is the error msg?).. if it does then retry with the very last semicolon removed and see if that does it.
upgrade support wasn't added until alpha4 so it may be tricky to upgrade from alpha3.. i suggest deactivating and uninstalling every module you can (did alpha3 even have uninstall?) then comparing your 2 side by side sets of db tables to see what has changed.. look for A_*.sql files to see which changes have happened since alpha-4 and will be performed by the upgrader.. other changes you'll need to make by hand. make those first, then put the new code in place and access G2 to invoke the upgrader... it may work, or it may blow up in your face