RAM migrate after upgrade 7.5 not work
After we upgrade RAM from 7.2 to 7,5 , the first day is no problem, but in second day it always show error as:
Migration Required
The Rational Asset Manager repository is not the correct version.
IBM Rational Asset Manager V7.2.0.2
The current database version is 7.5.0.2.v20110127 and the software that is installed expects the database version 7.2.0.2.v20100201.
The current index version is 7.5.0.2.v20110128 and the software that is installed expects index version 7.2.0.2.v20100210.
The current Rational Team Concert project version is 7.5.v20100720 and the software that is installed expects version 7.2.0.2.v20100211.
Click the Migrate button to perform the migration. Before migrating, back up the database and persistence storage in case there are errors during migration.
But we click "Migration" multiple times, can not resolve this problem.
How we can check which configuration cause this problem?
Thanks.
Migration Required
The Rational Asset Manager repository is not the correct version.
IBM Rational Asset Manager V7.2.0.2
The current database version is 7.5.0.2.v20110127 and the software that is installed expects the database version 7.2.0.2.v20100201.
The current index version is 7.5.0.2.v20110128 and the software that is installed expects index version 7.2.0.2.v20100210.
The current Rational Team Concert project version is 7.5.v20100720 and the software that is installed expects version 7.2.0.2.v20100211.
Click the Migrate button to perform the migration. Before migrating, back up the database and persistence storage in case there are errors during migration.
But we click "Migration" multiple times, can not resolve this problem.
How we can check which configuration cause this problem?
Thanks.
12 answers
Something is wrong .... you have upgraded RAM (on some cluster) to 7.5.0.2 and updated the database.
From some reason you are running RAM 7.2.0.2 pointing to the 7.5.0.2 DB.
Was you clustered restored, or reverted back to 7.2.0.2?
You can not "migrate" the DB back to an earlier version.
From some reason you are running RAM 7.2.0.2 pointing to the 7.5.0.2 DB.
Was you clustered restored, or reverted back to 7.2.0.2?
You can not "migrate" the DB back to an earlier version.
Gmendel,
Thank you for your reply. Do you know any reason maybe cause this issue? We just take a snapshot for the RAM server, then this error reported.
Now we have upgraded our RAM server to 7.5.0.2, but the following error reported:
Caused by: java.lang.IllegalStateException: Unable to submit asset "69958DF0-25CE-4C07-6BF1-2C8F9397476D "
at com.ibm.ram.repository.assets.AssetManager.submitAssetWithState(AssetManager.java:4921)
at com.ibm.ram.repository.assets.AssetManager.submitAssetAsDraft(AssetManager.java:4520)
at com.ibm.ram.repository.web.upload.SubmitAssetHandler.uploadAsset(SubmitAssetHandler.java:332)
at com.ibm.ram.repository.web.upload.SubmitAssetHandler.doFinishAction(SubmitAssetHandler.java:926)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:127)
... 42 more
Caused by: com.ibm.ram.common.data.exception.RAMRuntimeException: Asset has an irrepairable collision detected.
at com.ibm.ram.repository.assets.RAMAsset.getManifestAccessor(RAMAsset.java:172)
at com.ibm.ram.repository.assets.RAMAsset.getShortDescription(RAMAsset.java:259)
at com.ibm.ram.repository.rest.RestUtils.copy(RestUtils.java:350)
at com.ibm.ram.repository.rest.RestUtils.getAsset(RestUtils.java:280)
at com.ibm.ram.repository.assets.AssetManager.submitAssetWithState(AssetManager.java:4867)
... 50 more
Thank you for your reply. Do you know any reason maybe cause this issue? We just take a snapshot for the RAM server, then this error reported.
Now we have upgraded our RAM server to 7.5.0.2, but the following error reported:
Caused by: java.lang.IllegalStateException: Unable to submit asset "69958DF0-25CE-4C07-6BF1-2C8F9397476D "
at com.ibm.ram.repository.assets.AssetManager.submitAssetWithState(AssetManager.java:4921)
at com.ibm.ram.repository.assets.AssetManager.submitAssetAsDraft(AssetManager.java:4520)
at com.ibm.ram.repository.web.upload.SubmitAssetHandler.uploadAsset(SubmitAssetHandler.java:332)
at com.ibm.ram.repository.web.upload.SubmitAssetHandler.doFinishAction(SubmitAssetHandler.java:926)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:127)
... 42 more
Caused by: com.ibm.ram.common.data.exception.RAMRuntimeException: Asset has an irrepairable collision detected.
at com.ibm.ram.repository.assets.RAMAsset.getManifestAccessor(RAMAsset.java:172)
at com.ibm.ram.repository.assets.RAMAsset.getShortDescription(RAMAsset.java:259)
at com.ibm.ram.repository.rest.RestUtils.copy(RestUtils.java:350)
at com.ibm.ram.repository.rest.RestUtils.getAsset(RestUtils.java:280)
at com.ibm.ram.repository.assets.AssetManager.submitAssetWithState(AssetManager.java:4867)
... 50 more
the DB was migrated to 7.5.0.2 ... you have to use that level of RAM software.
See if can go to the Help->About page to check the level you are running (assume it is 7.2.x...).
Make sure that the (<server>/ram.setup) server setup application is a 7.5.0.2 or higher level - 7.5.1 is out already).
If it is not, use the WAS admin console to update that application (EAR).
Go to the ram.setup url and update the RAM server application.
see: http://publib.boulder.ibm.com/infocenter/ramhelp/v7r5m1/topic/com.ibm.ram.installguide.doc/topics/t_install_ram_was_main.html for more information
See if can go to the Help->About page to check the level you are running (assume it is 7.2.x...).
Make sure that the (<server>/ram.setup) server setup application is a 7.5.0.2 or higher level - 7.5.1 is out already).
If it is not, use the WAS admin console to update that application (EAR).
Go to the ram.setup url and update the RAM server application.
see: http://publib.boulder.ibm.com/infocenter/ramhelp/v7r5m1/topic/com.ibm.ram.installguide.doc/topics/t_install_ram_was_main.html for more information
We have converted back the RAM to 7.2 version, but when click the "asset" tab , it report the following error:
Network server name:usaxram012ccxraCell01/usaxram012ccxraNode01/server1
An unexpected error has occurred.
Specific details regarding this error have been recorded in ramDebug.log file with the following ID: F58BE5D2-60C4-7E00-0ADB-A535F2FE92C8
then when click "My dashboard", the following error showed:
Connection authorization failure occurred. Reason: User ID or Password invalid.DSRA0010E: SQL State = null, Error Code = -99,999
But in ram setup page and administrations->configurations, the DB connection no any error throw out.
In ramdebug.log, only following error show:
CRRAM0001E 1723709 ERROR web pagecode.error.Error - 035BBD52-DDEE-8AF5-7748-2F21F54EF966 - null
CRRAM0001E 1765444 ERROR web pagecode.error.Error - 2696CF30-1204-9B16-10D9-AFC923D277B0 - java.io.FileNotFoundException: JSRServlet: ibmjsfres/hxclient_core_v3_1_4.js could not be found
at com.ibm.faces.webapp.JSResourceServlet.doGet(JSResourceServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1152)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ram.repository.web.filters.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:72)
Network server name:usaxram012ccxraCell01/usaxram012ccxraNode01/server1
An unexpected error has occurred.
Specific details regarding this error have been recorded in ramDebug.log file with the following ID: F58BE5D2-60C4-7E00-0ADB-A535F2FE92C8
then when click "My dashboard", the following error showed:
Connection authorization failure occurred. Reason: User ID or Password invalid.DSRA0010E: SQL State = null, Error Code = -99,999
But in ram setup page and administrations->configurations, the DB connection no any error throw out.
In ramdebug.log, only following error show:
CRRAM0001E 1723709 ERROR web pagecode.error.Error - 035BBD52-DDEE-8AF5-7748-2F21F54EF966 - null
CRRAM0001E 1765444 ERROR web pagecode.error.Error - 2696CF30-1204-9B16-10D9-AFC923D277B0 - java.io.FileNotFoundException: JSRServlet: ibmjsfres/hxclient_core_v3_1_4.js could not be found
at com.ibm.faces.webapp.JSResourceServlet.doGet(JSResourceServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1152)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ram.repository.web.filters.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:72)
We have converted back the RAM to 7.2 version...
I am little confused as to what you mean by converting back to 7.2. You
mean you restored the DB back to a 7.2 level? As Gili mentioned earlier
the migration message shows your DB is a RAM 7502 level and software was
still on 7.2 or some downlevel version of RAM.
Gili's suggestion was to ensure you installed the Server Setup EAR to
the 7.5.0.2 level and then run Server Setup to upgrade your RAM
server/application.
If it is not, use the WAS admin console to update that application (EAR).
Go to the ram.setup url and update the RAM server application.
What version of RAM do you have installed? Go to the about page on the
web client (browser). Paste the version information here.
Peter Walker
RAM Development
1) We finished upgrade RAM from 7.2.0.2 to 7.5.0.2 in 12/22, successfully tested RAM related functions in 12/23
2) We took a snapshot in 12/23 night
3) When we back for work in 12/26, found the RAM WAS server was down grade to 7.2 again, but DB still in 7.5 version. We not sure why this happened, like gmendel means for some reason, the migration can not still running because of the DB and server version not match.
4) We directly upgrade our RAM server to 7.5 but it does not work. Hence, we revert back to the snapshot which taken in 12/23, then run all the upgrade steps again, but the DB connection problem always reported and we can not find any invalid setting. The details can be found in my comment of 12/30.
Currently both our RAM and DB server is 7502 level. The RAM detail version is testfix2a-52166.
Thanks.
2) We took a snapshot in 12/23 night
3) When we back for work in 12/26, found the RAM WAS server was down grade to 7.2 again, but DB still in 7.5 version. We not sure why this happened, like gmendel means for some reason, the migration can not still running because of the DB and server version not match.
4) We directly upgrade our RAM server to 7.5 but it does not work. Hence, we revert back to the snapshot which taken in 12/23, then run all the upgrade steps again, but the DB connection problem always reported and we can not find any invalid setting. The details can be found in my comment of 12/30.
Currently both our RAM and DB server is 7502 level. The RAM detail version is testfix2a-52166.
Thanks.
Since we want to test if this DB error caused by our RAM upgrade from 7.2 to 7.5, we revert back our RAM server to the 7.2 , the version is: V7.2.0.2 Build: RAM7202-I20100315_0942
But the UI mess up, so we must restore to default theme. When we try to upload our customize template, it shows error with:
An unexpected error has occurred.
In the stack trace, the message is:
<No>
After check RAM server trace log, it exception log like this:
0000003f ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Faces Servlet. Exception thrown : javax.servlet.ServletException
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:209)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1152)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ram.repository.web.security.RAMServletFilter.doFilter(RAMServletFilter.java:418)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ram.repository.web.filters.GZipFilter.doFilter(GZipFilter.java:45)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:524)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:751)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:125)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
---- Begin backtrace for Nested Throwables
java.lang.IllegalArgumentException
at javax.faces.component.SelectItemsIterator.next(SelectItemsIterator.java:149)
at javax.faces.component.SelectItemsIterator.next(SelectItemsIterator.java:124)
at javax.faces.component.UISelectOne.matchValue(UISelectOne.java:141)
at javax.faces.component.UISelectOne.validateValue(UISelectOne.java:114)
at javax.faces.component.UIInput.validate(UIInput.java:645)
at javax.faces.component.UIInput.executeValidate(UIInput.java:849)
When we want to submit an asset, after select community, when choose an asset type, its type will be change to blank and same error with upload customize template show, the message is "An unexpected error has occurred", the trace log information also same.
This block us to submit asset from RAM UI.
But the UI mess up, so we must restore to default theme. When we try to upload our customize template, it shows error with:
An unexpected error has occurred.
In the stack trace, the message is:
<No>
After check RAM server trace log, it exception log like this:
0000003f ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: Faces Servlet. Exception thrown : javax.servlet.ServletException
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:209)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1152)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ram.repository.web.security.RAMServletFilter.doFilter(RAMServletFilter.java:418)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ram.repository.web.filters.GZipFilter.doFilter(GZipFilter.java:45)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:524)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:751)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:125)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
---- Begin backtrace for Nested Throwables
java.lang.IllegalArgumentException
at javax.faces.component.SelectItemsIterator.next(SelectItemsIterator.java:149)
at javax.faces.component.SelectItemsIterator.next(SelectItemsIterator.java:124)
at javax.faces.component.UISelectOne.matchValue(UISelectOne.java:141)
at javax.faces.component.UISelectOne.validateValue(UISelectOne.java:114)
at javax.faces.component.UIInput.validate(UIInput.java:645)
at javax.faces.component.UIInput.executeValidate(UIInput.java:849)
When we want to submit an asset, after select community, when choose an asset type, its type will be change to blank and same error with upload customize template show, the message is "An unexpected error has occurred", the trace log information also same.
This block us to submit asset from RAM UI.
page 1of 1 pagesof 2 pages