Create v8 FP4 DB from v7.2 FP4 bkup

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • R. Clausen

    Create v8 FP4 DB from v7.2 FP4 bkup

    I am wanting to create a database in UDB (WIN) v8 FP4 using a backup
    from UDB (WIN) v7.2 FP4. When the restore is complete, I get a DB2
    Message 'The command completed successfully.', however, when I try to
    view a table in the Control Center I get a DB2 Message 'IBM CLI Driver
    SQL5035N The database requires migration to the current release.'.
    This migration message occurs when I restore the database into a newly
    created instance in v8 or into the DB2 instance. When I issue the DB2
    migrate database command, I get an error 'SQL0456N In the definition
    of routine "SYSPROC.SNAPSH OT_DBM", the SPECIFIC name "SNAPSHOT_D BM"
    already exists in the schema.' I have created several databases
    previous to this one from a v7.2 FP4 backup on this v8 FP4 server with
    no problem. I need to know how to resolve this and why this is
    occurring on this database and not on the others. Thank you for any
    insight and suggestions!
  • Blair Adamache

    #2
    Re: Create v8 FP4 DB from v7.2 FP4 bkup

    You could try running db2updv8 - it's a utility that adds any new
    functions added in a fixpak (the functions must be recorded in the
    catalogs).

    R. Clausen wrote:
    [color=blue]
    > I am wanting to create a database in UDB (WIN) v8 FP4 using a backup
    > from UDB (WIN) v7.2 FP4. When the restore is complete, I get a DB2
    > Message 'The command completed successfully.', however, when I try to
    > view a table in the Control Center I get a DB2 Message 'IBM CLI Driver
    > SQL5035N The database requires migration to the current release.'.
    > This migration message occurs when I restore the database into a newly
    > created instance in v8 or into the DB2 instance. When I issue the DB2
    > migrate database command, I get an error 'SQL0456N In the definition
    > of routine "SYSPROC.SNAPSH OT_DBM", the SPECIFIC name "SNAPSHOT_D BM"
    > already exists in the schema.' I have created several databases
    > previous to this one from a v7.2 FP4 backup on this v8 FP4 server with
    > no problem. I need to know how to resolve this and why this is
    > occurring on this database and not on the others. Thank you for any
    > insight and suggestions![/color]

    Comment

    • R. Clausen

      #3
      Re: Create v8 FP4 DB from v7.2 FP4 bkup

      Blair Adamache <badamache@2muc hspam.yahoo.com > wrote in message news:<btmugq$ib b$1@hanover.tor olab.ibm.com>.. .[color=blue]
      > You could try running db2updv8 - it's a utility that adds any new
      > functions added in a fixpak (the functions must be recorded in the
      > catalogs).
      >
      > R. Clausen wrote:
      >[color=green]
      > > I am wanting to create a database in UDB (WIN) v8 FP4 using a backup
      > > from UDB (WIN) v7.2 FP4. When the restore is complete, I get a DB2
      > > Message 'The command completed successfully.', however, when I try to
      > > view a table in the Control Center I get a DB2 Message 'IBM CLI Driver
      > > SQL5035N The database requires migration to the current release.'.
      > > This migration message occurs when I restore the database into a newly
      > > created instance in v8 or into the DB2 instance. When I issue the DB2
      > > migrate database command, I get an error 'SQL0456N In the definition
      > > of routine "SYSPROC.SNAPSH OT_DBM", the SPECIFIC name "SNAPSHOT_D BM"
      > > already exists in the schema.' I have created several databases
      > > previous to this one from a v7.2 FP4 backup on this v8 FP4 server with
      > > no problem. I need to know how to resolve this and why this is
      > > occurring on this database and not on the others. Thank you for any
      > > insight and suggestions![/color][/color]

      Unfortunately, the db2updv8 utility did not work. First, the
      deactivate command failed with the SQL5035N The database requires
      migration to the current release. Second, I tried to run db2updv8
      with the database in the DB2 instance and using the command--db2updv8
      -d legalja, I got the error SQL1024N A database connection does not
      exist. (I thought it was odd to get this error since the
      documentation said that a database connection will be automatically
      established.) Then when I tried to connect to the database with the
      command--connect to legalja, and got SQL5035N The database requires
      migration to the current release.

      We are using Workgroup Server Edition. Help and suggestions welcomed!

      Comment

      Working...