RobinMoffatt
Programmer
Hi all,
We're trying to upgrade a test copy of our repo from 5 to 6.5, but struggling because the file that specifies the upgrade SQL is eluding us
I'm assuming that the SQL that I've extracted from the rss file using ExtractSQL.exe is that SQL used to create or delete domains (given that these are the headings in the file), and not upgrade. I've done an ODBC trace and can't see any evidence of BusObj using the rss file to work through the tables in the create clause in order and only create the missing ones, so reckon that there must be a separate upgrade file elsewhere .
In v5 there was the SQL UPG File parameter in the SBO file which pointed to the SQL statements to issue when upgrading the repository. I can't find any reference to a similar parameter in the new XML SBO file of v6.
We have to change the SQL that is issued because we are running DB2 and have to specify things like tablespaces to create the tables in etc.
I've searched the knowledge base, knowledge exchange, BoB, tek-tips, and at best have found docs (#2692 and #2656) in the knowledge base detailing the SQL that is run upgrading v5->v6 and v6->v6.5 -- but not how to change what is actually run
==> Does anyone know how we can customise the SQL that is run to upgrade the repo from v5 to v6.5? (creating a repo from scratch using customised SQL via the ExtractSQL is not really an option given the size of our repo)
TIA,
Robin.
We're trying to upgrade a test copy of our repo from 5 to 6.5, but struggling because the file that specifies the upgrade SQL is eluding us
I'm assuming that the SQL that I've extracted from the rss file using ExtractSQL.exe is that SQL used to create or delete domains (given that these are the headings in the file), and not upgrade. I've done an ODBC trace and can't see any evidence of BusObj using the rss file to work through the tables in the create clause in order and only create the missing ones, so reckon that there must be a separate upgrade file elsewhere .
In v5 there was the SQL UPG File parameter in the SBO file which pointed to the SQL statements to issue when upgrading the repository. I can't find any reference to a similar parameter in the new XML SBO file of v6.
We have to change the SQL that is issued because we are running DB2 and have to specify things like tablespaces to create the tables in etc.
I've searched the knowledge base, knowledge exchange, BoB, tek-tips, and at best have found docs (#2692 and #2656) in the knowledge base detailing the SQL that is run upgrading v5->v6 and v6->v6.5 -- but not how to change what is actually run
==> Does anyone know how we can customise the SQL that is run to upgrade the repo from v5 to v6.5? (creating a repo from scratch using customised SQL via the ExtractSQL is not really an option given the size of our repo)
TIA,
Robin.