Topic
6 replies Latest Post - ‏2013-06-17T15:33:09Z by Mauricio Poblete G.
SystemAdmin
SystemAdmin
5842 Posts
ACCEPTED ANSWER

Pinned topic Not a supported database version: V600-609

‏2009-04-08T10:22:38Z |
Problem(Abstract)
When running the Validation Utility as part of the Maximo 6 to 7 upgrade you receive the following error in the Validate<tdate/timestamp>.log file.

Symptom
Validate Log:

Not a supported database version: V600-609
BMXAA6849I - Validate completed with errors.

Cause
The Validation Utility does not recognize the MAXVAR value for Maximo 6.2.3.
Ensure that your current Fix Pack of Maximo 7 is compatible with the Maximo 6 database revision. Consult the Fix Pack release notes for details.
Environment
Maximo 6.2.3 to be upgraded to Maximo 7.1.1.4.
Resolving the problem
Using a text editor, open the VersionSequence.xml file located in \ibm\SMP\maximo\tools\maximo\classes\psdi\upgrade\

Add a line to the file for the version we are having an error with:
<VERSION versionnum="V600-609 11/1/2008" dir="V600"/>

You file should look like this:

<?xml version="1.0" encoding="UTF-8"?>

<document docid="VersionSequence">
<VERSION versionnum="V510-13 12/10/2002" dir="V510_13"/>
<VERSION versionnum="V510-38 12/10/2002" dir="V510_38"/>
<VERSION versionnum="V520-14 12/19/2005" dir="V520"/>
<VERSION versionnum="V600-609 11/1/2008" dir="V600"/>
<VERSION versionnum="V600-664 11/1/2008" dir="V600"/>
<VERSION versionnum="V7100-001 4/2/2008" dir="V7100"/>
</document>
Save the file, and try re-running the Validation Checker.
Updated on 2013-02-06T00:27:18Z at 2013-02-06T00:27:18Z by swkim90049
  • swkim90049
    swkim90049
    261 Posts
    ACCEPTED ANSWER

    Re: Not a supported database version: V600-609

    ‏2013-02-06T00:27:18Z  in response to SystemAdmin
    We have the same error, but we are going from 6.2.8 to 7.1.1.10

    Our database version is V600-785.

    What is the solution in our situation.

    Does anyone know?

    Below is the error message we received.

    BMXAA6806I - Reading the properties file maximo.properties.
    MaxUpgVersion: V600-785
    java.lang.Exception: Not a supported database version: V600-785
    at psdi.configure.Validate.getCalloutSubdir(Validate.java:11192)
    at psdi.configure.Validate.endSetupInstance(Validate.java:12562)
    at psdi.configure.CommonShell.endSetup(CommonShell.java:1682)
    at psdi.configure.CommonShell.setup(CommonShell.java:1073)
    at psdi.configure.Validate.setup(Validate.java:12770)
    at psdi.configure.UpgradeUI.runValidate(UpgradeUI.java:506)
    at psdi.configure.UpgradeUI.actionPerformed(UpgradeUI.java:341)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:18
    79)
    at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.jav
    a:2199)
    at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel
    .java:450)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:288
    )
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonL
    istener.java:264)
    at java.awt.Component.processMouseEvent(Component.java:5529)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3148)
    at java.awt.Component.processEvent(Component.java:5294)
    at java.awt.Container.processEvent(Container.java:2001)
    at java.awt.Component.dispatchEventImpl(Component.java:3996)
    at java.awt.Container.dispatchEventImpl(Container.java:2059)
    at java.awt.Component.dispatchEvent(Component.java:3844)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4249
    )
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3929)

    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3859)
    at java.awt.Container.dispatchEventImpl(Container.java:2045)
    at java.awt.Window.dispatchEventImpl(Window.java:1810)
    at java.awt.Component.dispatchEvent(Component.java:3844)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:545)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchTh
    read.java:268)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThre
    ad.java:197)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:191)

    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:183)

    at java.awt.EventDispatchThread.run(EventDispatchThread.java:144)
    Not a supported database version: V600-785 Tue Feb 05 16:13:48 PST 2013
    BMXAA6849I - Validate completed with errors. Tue Feb 05 16:13:48 PST 2013
    • Mauricio Poblete G.
      Mauricio Poblete G.
      5 Posts
      ACCEPTED ANSWER

      Re: Not a supported database version: V600-609

      ‏2013-06-06T19:49:52Z  in response to swkim90049

      HI,

      We have the same problem here and we still cannot find the answer.

      Did you manage to solve this error? how did you do it?

      In advance, thank you very much.

      • swkim90049
        swkim90049
        261 Posts
        ACCEPTED ANSWER

        Re: Not a supported database version: V600-609

        ‏2013-06-06T22:40:28Z  in response to Mauricio Poblete G.

        I think when you run the Validation tool, you have to make sure you perform it from the correct Admin Workstation. Some steps require you to perform the Validation from the Maximo 6 admin workstation, while other times, the Validation may require you to perform the validation from the Maximo 7 admin workstation. Read instructions carefully. If you are going from Maximo 7.1 to 7.5, you will need to pass your 7.1 Admin Workstation Integrity Checks after you perform the updatedb.bat that goes from 6.2.8 to 7.1.1.11

        • Mauricio Poblete G.
          Mauricio Poblete G.
          5 Posts
          ACCEPTED ANSWER

          Re: Not a supported database version: V600-609

          ‏2013-06-12T20:43:39Z  in response to swkim90049

          Great tip. I was running the updatedb from maximo 7.1 instead 6.2.8. 

           

          Now the validation passed and when we tried to run the upgrade, the process stops with the following error log. in bold font type the weird SQL because the applicationauth table doesn't have a sigoptionid field thus the error.

          We checked the tech ref from IBM and the sigoptionid field doesn't belong to the applicationauth table. but there is the statement trying to delete where there is no sigoptionid column. 

          We also checked the classes used to upgrade and we think that the statement came from 

          TreeMap treemap = util.getObjectMeta(s1, false, true, false, true, true, false, false);
          HashMap hashmap = (HashMap)treemap.get(s1);
          TreeMap treemap1 = getKeyColumns(hashmap);
          TreeMap treemap2 = getColumnsFromTable(hashmap);
          ArrayList arraylist = sysdataelement.getDeleteSql(s1, con, util, treemap2, treemap1);
          doSql(arraylist);

          But I'm not sure where the relationship between applicationauth table and sigoptionid field resides. 

          I think that there is an xml file with this relationship, but we are not able to find it yet.

          Do you have any idea how can I fix this?

          In advance, thanks lot. I will try to answer your question in order to find the solution.

           

          PS: the Log from the upgrade.

          Delete From sigoption Where sigoptionid is null
          go
          Tue Jun 11 13:01:59 CLT 2013
          Delete From applicationauth Where sigoptionid is null
          go
          rollback
          go
          com.inet.tds.at: Msg 207, Level 16, State 1, Line 1, Sqlstate S0022
          [MSQ08-MCC2]Invalid column name 'sigoptionid'.
          at com.inet.tds.aq.a(Unknown Source)
          at com.inet.tds.k.b(Unknown Source)
          at com.inet.tds.k.a(Unknown Source)
          at com.inet.tds.k.a(Unknown Source)
          at com.inet.tds.af.b(Unknown Source)
          at com.inet.tds.af.execute(Unknown Source)
          at psdi.configure.CommonShell.doSql(CommonShell.java:333)
          at psdi.upgrade.Upgrade.doSql(Unknown Source)
          at psdi.configure.CommonShell.doSql(CommonShell.java:306)
          at psdi.upgrade.Upgrade.removeSysData(Unknown Source)
          at psdi.upgrade.Upgrade.loadMetaData(Unknown Source)
          at psdi.upgrade.Upgrade.process(Unknown Source)
          at psdi.configure.UpgradeUI.runUpgrade(UpgradeUI.java:631)
          at psdi.configure.UpgradeUI.actionPerformed(UpgradeUI.java:344)
          at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1879)
          at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2199)
          at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:450)
          at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:288)
          at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:264)
          at java.awt.Component.processMouseEvent(Component.java:5571)
          at javax.swing.JComponent.processMouseEvent(JComponent.java:3143)
          at java.awt.Component.processEvent(Component.java:5336)
          at java.awt.Container.processEvent(Container.java:2001)
          at java.awt.Component.dispatchEventImpl(Component.java:4038)
          at java.awt.Container.dispatchEventImpl(Container.java:2059)
          at java.awt.Component.dispatchEvent(Component.java:3871)
          at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4249)
          at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3929)
          at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3859)
          at java.awt.Container.dispatchEventImpl(Container.java:2045)
          at java.awt.Window.dispatchEventImpl(Window.java:1812)
          at java.awt.Component.dispatchEvent(Component.java:3871)
          at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:588)
          at java.awt.EventQueue.access$000(EventQueue.java:119)
          at java.awt.EventQueue$1.run(EventQueue.java:549)
          at java.awt.EventQueue$1.run(EventQueue.java:548)
          at java.security.AccessController.doPrivileged(AccessController.java:214)
          at com.ibm.oti.security.CheckedAccessControlContext.securityCheck(CheckedAccessControlContext.java:30)
          at com.ibm.oti.security.CheckedAccessControlContext.securityCheck(CheckedAccessControlContext.java:34)
          at sun.misc.JavaSecurityAccessWrapper.doIntersectionPrivilege(JavaSecurityAccessWrapper.java:44)
          at java.awt.EventQueue$2.run(EventQueue.java:563)
          at java.awt.EventQueue$2.run(EventQueue.java:562)
          at java.security.AccessController.doPrivileged(AccessController.java:214)
          at com.ibm.oti.security.CheckedAccessControlContext.securityCheck(CheckedAccessControlContext.java:30)
          at sun.misc.JavaSecurityAccessWrapper.doIntersectionPrivilege(JavaSecurityAccessWrapper.java:39)
          at java.awt.EventQueue.dispatchEvent(EventQueue.java:560)
          at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:268)
          at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:197)
          at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:191)
          at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:183)
          at java.awt.EventDispatchThread.run(EventDispatchThread.java:144)
          [MSQ08-MCC2]Invalid column name 'sigoptionid'. Tue Jun 11 13:03:37 CLT 2013
          BMXAA6819I - Upgrade completed with errors. Tue Jun 11 13:03:37 CLT 2013

          Attachments

          • swkim90049
            swkim90049
            261 Posts
            ACCEPTED ANSWER

            Re: Not a supported database version: V600-609

            ‏2013-06-12T21:46:53Z  in response to Mauricio Poblete G.

            I checked both my upgrade logs from 6.2.8 to 7.1.1.11 and 7.1.1.11 to 7.5.0.4. I could not find the field you mentioned "sigoptionid" for that table.

            You could try is to create a field manually in the applicationauth table called sigoptionid with a default value of 0.

            If that helps the upgrade to pass, you can later drop that sigoptionid field from that table.

            Only other thing I can suggest to you is to try all over and make sure you apply the Fix Pack 7.1.1.11 before you perform the upgrade.
            Updated on 2013-06-17T16:01:18Z at 2013-06-17T16:01:18Z by swkim90049
            • Mauricio Poblete G.
              Mauricio Poblete G.
              5 Posts
              ACCEPTED ANSWER

              Re: Not a supported database version: V600-609

              ‏2013-06-17T15:33:09Z  in response to swkim90049

              Thanks swkim90049,

               

              Finally we manually created the field and run the integrity, validate processes and fixed the errors associated to this field. the upgrade finalize sucessfully. 

               

              Thanks for your replies. Now we are facing a new problem upgrading from 7.1.1.10 to 7.5, but i will search in the forum before post it. 

               

              Best regards

        • This reply was deleted by Mauricio Poblete G. 2013-06-12T20:52:14Z. Reason for deletion: duplicated reply