Want to get rid of Google Ads, click here.
+ Reply to Thread
Results 1 to 6 of 6

Thread: Upgrade to 7.10 - Operator Table corrupt

  1. #1
    Junior Member
    Join Date
    Jan 2008
    Location
    Wellington, New Zealand
    Posts
    7

    Default Upgrade to 7.10 - Operator Table corrupt

    Hi - I've upgraded a system from SC 6.1.2 to 7.01, then from 7.01 to 7.10. We keep getting this error once we have upgrade to 7.10 on the Operator table, if we do a true search on the table (while stil logged into SM from the upgrade):

    sqociExec error statement=SELECT m1."NAME" FROM OPERATORM1 m1 WHERE ((m1."NAME" LIKE :SM_NAME_0)) ORDER BY m1."NAME" ASC (se.search.engine,select.records)
    sqociExec error: sqlcode=904 message=ORA-00904: "M1"."NAME": invalid identifier (se.search.engine,select.records)

    Once we log out we cannot log back in.

    Anyone have any ideas on this?

    Cheers Carl.

  2. #2
    Senior Member
    Join Date
    Apr 2006
    Location
    Poland
    Posts
    680

    Default

    The ORA-00904 means: The column name entered is either missing or invalid.
    Have you looked for this column using any SQL tool - I mean does it exist ?
    The other thing to check: dbdict.
    When you log out and then you can not log in- that is because the queries from
    opeartorm1 does not work.

    If there is a demo db available with 7.1 (and it should be) - install it on Oracke and try to do the unload, then load it tou upgraded system.

    HTH
    Artur

  3. #3
    Junior Member
    Join Date
    Jan 2008
    Location
    Wellington, New Zealand
    Posts
    7

    Default

    Thanks for your help.

    Yea the table and rows exist when we check in Oracle itself.

    We had a Oracle DBA Look at it and he said that the query is using capital "NAME' but the row name inside the db is lowercase (name) so he thinks this might be the problem. However, all other tables we check (contact, location etc..) are all fine, so not sure about this....

  4. #4
    Senior Member mateuszk's Avatar
    Join Date
    Nov 2006
    Posts
    302

    Default

    Wait, last time I checked standard setup of Oracle
    resulted in case insensitive column names?
    Never mind.

    Either:
    a. adjust the SQL mapping in SM (that's where the case originates from)
    b. rename columns in Oracle accordingly

    Code:
    SELECT m1."NAME" FROM OPERATORM1
    Yepp, I'd definitively had a look at SQL Mapping, m1."NAME" looks plain ugly.

  5. #5
    Junior Member
    Join Date
    Jan 2008
    Location
    Wellington, New Zealand
    Posts
    7

    Default

    Well - we renamed all the lower case Oracle colunm names to upper case in the Operator Table and now we can log on fine. so thats good - but will need to check the system to see how many other problems there are with lower/upper case column names as checking the contacts and location tables these also have a mix of lower/upper case column names and seem to work fine....

    Cheers!

  6. #6
    Junior Member
    Join Date
    Jan 2008
    Location
    Wellington, New Zealand
    Posts
    7

    Default

    We tried doing an upgrade from a OOTB install direct from the DVD media. We installed 6.1.2.0 build 0073, pushed P4 to Oracle 10g, upgrade to 7.01.048 the upgraded to 7.10.023. Totally no customer mods/data etc.. and we still got the operator table issue..... weird??

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts