2 Replies Latest reply: May 12, 2011 10:41 AM by Asif M. Naqvi RSS

    portal version is invalid

    Umar Riaz
      hi,
      we have oracle 10g db win server 2003 >>> version = 10.2.0.4
      portal version is 10.1.2 and we are performing an upgrade by using mrua to 10.1.4
      -----------------------------
      we have successfully upgraded this portal version on dummy new db and dummy portal of same versions .
      this error arose at that time 2 but i resolved it by loading few java libraries into the db .
      i have searched this forum a lot and have applied every other solution but this setup is not working
      with our production db .
      i mean i stop the services in the exact same order and then restart them and perform every other setup like it is in the documents.
      now let me place the output of log files.
      -----------------------------------------
      there are no errors in portal > precheck log found in $ORACLE_HOME\upgradel\plsql\temp\portal\
      how ever these are found in upgrade log
      ### Show errors and warnings
      Step started at Thu Apr 21 14:50:45 2011

      ###
      ### ERROR: WWU-01013: Upgrade terminated with the following errors:
      ### 1736 : EXP-00008: ORACLE error 904 encountered
      ### 1737 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1753 : EXP-00008: ORACLE error 1003 encountered
      ### 1754 : ORA-01003: no statement parsed
      ### 1758 : EXP-00008: ORACLE error 904 encountered
      ### 1759 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1764 : EXP-00008: ORACLE error 1003 encountered
      ### 1765 : ORA-01003: no statement parsed
      ### 1769 : EXP-00008: ORACLE error 904 encountered
      ### 1770 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1776 : EXP-00008: ORACLE error 1003 encountered
      ### 1777 : ORA-01003: no statement parsed
      ### 1783 : EXP-00008: ORACLE error 904 encountered
      ### 1784 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1786 : EXP-00008: ORACLE error 1003 encountered
      ### 1787 : ORA-01003: no statement parsed
      ### 1832 : EXP-00008: ORACLE error 904 encountered
      ### 1833 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1877 : EXP-00008: ORACLE error 1003 encountered
      ### 1878 : ORA-01003: no statement parsed
      ### 1888 : EXP-00008: ORACLE error 904 encountered
      ### 1889 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1912 : EXP-00008: ORACLE error 1003 encountered
      ### 1913 : ORA-01003: no statement parsed
      ### 1915 : EXP-00008: ORACLE error 904 encountered
      ### 1916 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 1918 : EXP-00008: ORACLE error 1003 encountered
      ### 1919 : ORA-01003: no statement parsed
      ### 1974 : EXP-00008: ORACLE error 904 encountered
      ### 1975 : ORA-00904: "IFREEPOOL": invalid identifier
      ### 2011 : ### ERROR: Error during export

      -------------------------
      i tried catexp.sql > did not work
      tried catalog.sql > did not work
      tried catproc.sql > did not work
      -------------------------
      although mrua suggests that out db version is not supported but we did it on dummy db by changing few lines in mrua.xml file.it worked with that db but its not working with this production db.
      please help me as i'm stuck with this problem for 2 days now :(
      free points to anyone who at least tries to help me (i doubt it will work but please help me)
      regards !
        • 1. Re: portal version is invalid
          860720
          Hello

          Can you check if you have any invalid objects in any of the portal schema's (portal, portal_app, portal_demo, portal_public) in the database?
          If so try to run the utlrp.sql script to make them valid.
          Then try to run the upgrade again.

          Regards
          Johan
          • 2. Re: portal version is invalid
            Asif M. Naqvi
            A few possible sources of errors could be that not all instances and components that need to be shutdown would be down before running the upgrade which sometimes does not release the inventory access. That means all instances running under the ORACLE_HOME may not be cleanly down, or the utility used to bring them down might not be shutdown properly.
            Another possible reason could be the presence of invalid objects in your database, as mentioned by user 857717.

            Please see these notes (851673.1, 741984.1) on MOS for pointers to your options.

            thanks,
            AMN