Unable to upgrade Build Forge to 8.0 (from 7.1.3.4-1-0010)
We have Build Forge version 7.1.3.4-1-0010 running and want an upgrade to version 8.0.
Downloaded bf_8000_0456-full.zip and startet Installation Manager 'Update'. 'Test connection' button at JAS Database Configuration page comes up with: Unexpected failure:(32): No tablespace of 16KB (16384 bytes) or greater exists. Please adjust your database tablespace or bufferpools and rerun the installer. With 'db2cc' I was not able to adjust tablespaces or bufferpools. Any help welcome. Regards Andreas |
6 answers
This is caused by DB2
please refer to http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.sql.ref.doc%2Fdoc%2Fr0000890.html and http://www.db2commands.com/db2tablespaceandbufferpoolcommands |
|
Tried to modify tablespace and bufferpools with following commands:
$ db2 "alter tablespace USERSPACE1 extend (all 8000)" DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL20318N Table space "USERSPACE1" of type "AUTOMATIC STORAGE" cannot be altered using the "EXTEND" operation. SQLSTATE=42858 $ db2 "alter tablespace USERSPACE2 extend (all 8000)" DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0281N Table space "USERSPACE2" cannot be altered with additional containers because it is a system managed table space. SQLSTATE=42921 $ db2 ALTER BUFFERPOOL BUFFP1 SIZE 15000 DB20000I The SQL command completed successfully. So I was able to alter bufferpool but not the tablespaces due to type "AUTOMATIC STORAGE" (USERSPACE1) and "system managed table space" (USERSPACE2). Still getting same error. Any further ideas ? |
This issue is still being caused by the DB2 database configuration for the tablespaces.
The Build Forge installation database test uses the following query to test the tablespace sizes. db2 "select tbspace,pagesize from sysibm.systablespaces" The requirement for Build Forge is that the tablespace pagesize is 16K (16384 bytes) At a minimum, the last tablespace listed should be set to 16K pagesize, but it is recommended that all tablespaces for the Build Forge database have 16K pagesize. For example, the following output displays the tablespace USERSPACE2 with a pagesize of 4K (4096 bytes) This configuration will produce the error you encountered. TBSPACE PAGESIZE -------- ----------- SYSCATSPACE 16384 TEMPSPACE1 16384 USERSPACE1 16384 SYSTOOLSPACE 16384 SYSTOOLSTMPSPACE 16384 USERSPACE2 4096 You will need to update your tablespaces to use a bufferpool with a 16K pagesize. |
Hi,
I am seeing the same error even though all the table spaces used by BF are 16K: # db2 "select TBSPACE,PAGESIZE from sysibm.systablespaces" TBSPACE PAGESIZE ---------------------------------------------------------- ----------- SYSCATSPACE 4096 TEMPSPACE1 4096 USERSPACE1 4096 SYSTOOLSPACE 4096 TEMPSPACE2 16384 BFUSE_TEMP 16384 USERSPACE2 16384 SYSTOOLSTMPSPACE 4096 8 record(s) selected. The 4K table spaces work with default buffer pool 'IBMDEFAULTBP' which I cannot change (it can only be specified when creating the database). I am trying to upgrade from '7.1.3.3' to '8.0.010.0199'. Any ideas how I can fix or work around this issue? Thanks Jakub Comments please enable the install debug by export BF_INSTALLER_DEBUG=1 on linux, then start IM from the terminal or set BF_INSTALLER_DEBUG=1 on Windows, then start IM from the cmd, there will be more debug logs
please execute this sql:select pagesize from sysibm.systablespaces to check whether it is bigger than 16382（16*1204= 16384） |
Hi,
I've got the same problem, with the last tablespace SYSTOOLSTMPSPACE not in 16K, but the BF ones are correct.
I've set the BF_INSTALLER_DEBUG=1. Where can I find the debug logs ?
Comments The error message is seen in "Installation Manager", not in the Java part launched to create all the needed tables in DB2, and the binairies. So I don't know if the BF_* vars are the good vars to set to debug the install. Jerome,
Thanks, I didn't know I can drop this tablespace safely. I started with a clean database because Installation Manager refused the test database as there was some BF tables already :) Unfortunately, the BF Installer ends with an error :
Executing: "D:\TTS10\Logiciel\IBM\BuildForge\openssl\openssl.exe" pkcs12 -clcerts -nokeys -in "D:/TTS10/Logiciel/IBM/BuildForge/new/buildForgeKeyStore.p12" -passin pass:*** -out "D:/TTS10/Logiciel/IBM/BuildForge/new/buildForgeCert.pem"
4776:error:02001015:system library:fopen:Is a directory:.\crypto\bio\bss_file.c:169:fopen('X:/PREQ-Windows-ConsoleUpdate/49/export/ssl/openssl.cnf','rb')
4776:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:174:
4776:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:199:
An unexpected error has occured [1602], please contact support
Exit Code: 1
Which platform do you use? such as RHEL6.4 64bit. which version IM do you use? suchas IM 32bit 1.5.0 or IM 64bit 1.6.3. Which database do you use? when use DB2, please create the database according to the help:http://pic.dhe.ibm.com/infocenter/bldforge/v7r1m3/topic/com.ibm.rational.buildforge.doc/topics/preinst_db__top.html..
Hi,
I'm on Windows 2008 R2 Enterprise 64 bit, with DB2, and IM 1.6.1 32 bit.
Seems to be something with certificate stuff generated on install.
I've opened a PMR a few days ago. I'm waiting for a solution. I'll share it here :)
@Rauline, Did you get the solution for
Executing: "D:\TTS10\Logiciel\IBM\BuildForge\openssl\openssl.exe
I am also facing the same error and my installation did not proceed. Plz help me with your findings.
showing 5 of 6
show 1 more comments
|
@Jérôme RAULINE
I am also getting the same error as you got. Did you get any update from PMR on this? I am installing BF V 8.0.0.3 on Windows 2012 R2 Standard.
Thanks,
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.