It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,192

question asked: Nov 11 '10, 1:21 a.m.
question was seen: 5,256 times
last updated: Nov 11 '10, 1:21 a.m.

Related questions

RAFW: 7.1.2 Upgrade

0
Benjamin Chodroff (898●52●31) | asked Nov 11 '10, 1:21 a.m.
I am upgrading from 7.1.1.4 to 7.1.2 on SLES 10. I upgraded the bits, ran a integratetobf.sh removeAll and I get this error message during createAll: 


Error while creating WSRR RAFW libraries for BuildForge 

Error creating WSRR libraries:

Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating WSRR libraries:

Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record.

com.ibm.rational.rafw.wsadmin.RafwException: Error while creating WSRR RAFW libraries for BuildForge 

Error creating WSRR libraries:

Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating WSRR libraries:

Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record.

	at com.ibm.rational.bfw.framework.integration.BuildForgeIntegrationConfigUtility.createRafwLibraries(BuildForgeIntegrationConfigUtility.java:476)

	at com.ibm.rational.bfw.framework.integration.BuildForgeIntegrationConfigUtility.main(BuildForgeIntegrationConfigUtility.java:1624)

Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating WSRR libraries:

Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record. Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record.

	at com.ibm.rational.bfw.framework.integration.bpm.WSRRProjectCreationWizard.createRafwLibraries(WSRRProjectCreationWizard.java:124)

	at com.ibm.rational.bfw.framework.integration.BuildForgeIntegrationConfigUtility.createRafwLibraries(BuildForgeIntegrationConfigUtility.java:470)

	... 1 more

Caused by: com.ibm.rational.rafw.wsadmin.RafwException: Error creating RAFW_WSRR_Common_Database_Helper_Library library

 Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record.

	at com.ibm.rational.bfw.framework.integration.bpm.WSRRProjectCreationWizard.createWsrrConfigDBHelperLibrary(WSRRProjectCreationWizard.java:351)

	at com.ibm.rational.bfw.framework.integration.bpm.WSRRProjectCreationWizard.createRafwLibraries(WSRRProjectCreationWizard.java:101)

	... 2 more

Caused by: com.buildforge.services.common.api.APIException: Unable to allocate new project step record.

	at com.buildforge.services.client.api.APIClientConnection.call(APIClientConnection.java:607)

	at com.buildforge.services.client.dbo.Step.create(Step.java:114)

	at com.buildforge.services.client.dbo.Project.addStep(Project.java:1678)

	at com.ibm.rational.bfw.framework.integration.BuildForgeFacade.addConditionStepToProject(BuildForgeFacade.java:295)

	at com.ibm.rational.bfw.framework.integration.bpm.WSRRProjectCreationWizard.createWsrrConfigDBHelperLibrary(WSRRProjectCreationWizard.java:329)

	... 3 more



Any suggestions?

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Benjamin Chodroff (898●52●31) | answered Nov 11 '10, 2:33 a.m.
Any suggestions?


After running integratetobf.sh removeAll/createAll a few times, manually deleting out the libraries it claimed it hadn't created because it had no UUID record in <rafw_home>/buildforge.conf but they actually existed, and sometime in there also noticing that DB2 was complaining the transaction log was full while running a bfschema -R so I ran this: 
db2 update database configuration for BFT using LOGFILSIZ 10000

Very odd upgrade... Anyone else experience this?

TL;DR everything appears to be working, the 7.1.2 upgrade is done
0
permanent link
Timothy Robertson (216●1●4●3) | answered Nov 11 '10, 10:56 a.m.
Ben,
I have not seen this before, but it looks like this is a problem with the BF services layer. From the looks of it, you might not have been able to create a new step in the UI as well.
Another point, did you have a specific need to run removeAll? This certainly isn't required for an upgrade. You will need to make sure you deploy the new war file, but you can simply run createLibraries again to add any new libraries you might want. Did you also notice that we've made it interactive? This way, if say you won't manage WSRR/WVE/WPS/WESB cells you don't have to add the libraries. Cool huh?

--tim
0
permanent link
Benjamin Chodroff (898●52●31) | answered Nov 11 '10, 2:05 p.m.
I did not try adding steps through the UI, but I was able to manually delete libraries through the UI... not sure :)

I had to run removeAll because when I tried to run createAll the first time (non-iteractive) it failed with the same problem, so I wanted to start fresh. The error given by integratetobf provided no help on what to try to fix it.

I like the interactive mode for managing the different products... but I'd love it if there were command line flags for a full automation. I know it's not a typical use case for customers, but I like automating as much as possible and integratetobf.sh has always been a manual step when creating the proof of technology because you have to enter the agent port, password, etc. Or, ideally, which RAFW libraries were installed/upgraded would be provided through Installation Manager grouped by product and then saved in the response file so we wouldn't need to run integratetobf and could easily select exactly what we wanted.

Your answer

Register or to post 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.