8.1 sp2  portal upgrade errors

I am trying migrate our WLS 8.1 Portal app to SP2. I reinstalled BEA w/ sp2 and
was able to compile the app fine. Workshop updated some files and syncronized
compiler settings, etc. There was no pronlem with the build process. However,
when I tried to run the portal, it throws the following error. We have the same
code base successfuly running in sp1. Any help is greatly appreciated.
Thanks,
Anant
<Jan 16, 2004 11:45:39 AM PST> <Error> <HTTP> <BEA-101017> <[ServletContext(id=18268170,name=corpPortal,context-path=/corpPort
al)] Root cause of ServletException.
java.lang.NoClassDefFoundError: weblogic/netuix/util/JspcExtensions
at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:563)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.myee.portal.YahooLoginFilter.doFilter(YahooLoginFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6356)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

if (bookPresentationContext != null
&& bookPresentationContext.isCapable(WindowCapabilities.EDIT) )
This is the code snippet where it has a problem. I looked up the docs and there
is no isCapable() method in BookPresentationContext class.
Thanks,
Anant
"Anant Kadiyala" <[email protected]> wrote:
>
Greg,
I updated the portal libraries as you outlined. FYI, even before the
first post
of mine, I did update the portal libraries and got the errors I posted.
Just to
rule out any other factors, I checked out a fresh build and updated portal
libraries
by right-clicking on the web apps. All the netuix*.jar files you mentioned
have
sp2 in them.
When I was trying to build, it gave a different error this time. This
header.jsp
seems to be an sp2 file. There is no support dir under shell in sp1.
C:\bea_projects\myPlatformApp\myPortal\framework\markup\shell\support\
ERROR: header.jsp:23: Type com.bea.netuix.servlets.controls.page.BookPresentationContext
contains no methods with this name.
ERROR: 1 error(s), 0 warning(s).
Please advice..
Thanks,
Anant
Gregory Smith <[email protected]> wrote:
Did you do Install|Update Portal Libraries from the right-mouse-click
on
the app in Workshop? That's required to update the portal jars files
to
SP2 in the application. Doing that will prompt you to also update your
portal webapps, or you can right-mouse-click on the webapp and do
Install|Update Portal Libraries.
If you did do that, can you verify the version information in the
Manifest's of the netuix.jar jar at the app level, netuix_util.jarin
APP-INF/lib, and the WEB-INF/lib/netuix_servlet.jar in the the webapp.
If they don't say SP2, you don't have the right ones.
It is suggested you do this while the server is not running.
Greg
Anant Kadiyala wrote:
I am trying migrate our WLS 8.1 Portal app to SP2. I reinstalled BEAw/ sp2 and
was able to compile the app fine. Workshop updated some files and
syncronized
compiler settings, etc. There was no pronlem with the build process.However,
when I tried to run the portal, it throws the following error. Wehave the same
code base successfuly running in sp1. Any help is greatly appreciated.
Thanks,
Anant
<Jan 16, 2004 11:45:39 AM PST> <Error> <HTTP> <BEA-101017> <[ServletContext(id=18268170,name=corpPortal,context-path=/corpPort
al)] Root cause of ServletException.
java.lang.NoClassDefFoundError: weblogic/netuix/util/JspcExtensions
at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:563)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.myee.portal.YahooLoginFilter.doFilter(YahooLoginFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6356)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Similar Messages

  • Portal Runtime Error after Upgrade 7.01 to 7.3

    Hi,
    i have a Problem after Upgrade a BW 7.01 to 7.3 SP5 the,
    abap works fine but the Java Portal bring up Error on many time by choosing any funktion
    for example:
    try to use Portalcontent -> Systemlandscape -> SAP_BW
    this error is shown.
    Portal Runtime Error
    Tracefile:
    2011 11 24 13:05:51:546#+0100#Error#com.sap.portal.prt.connection#
    #EP-PIN-PRT#tcepbcprtc~api#C0000A11295500740000000000E900F2#9281050000000004#sap.com/irj#com.sap.portal.prt.connection#FREYAD#3##8D780B5716941                             1E1C8790000008D9E1A#a6e61adf169411e1cab50000008d9e1a#a6e61adf169411e1cab50000008d9e1a#0#Thread[HTTP Worker [@904797166],5,Dedicated_Application_                             Thread]#Plain##
    Exception ID:01:05_24/11/11_0004_9281050
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Application name : com.sap.portal.appdesigner.framework
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.pcmEditor
    Component class : com.sap.portal.admin.propertyeditor.core_functionality.PCMEditor
    -all Funktions in NWA are working
    -Diagnose an Supporttool is Green !
    Thanks Steven

    Hi Raj,
    You need to redeploy the patches in the message from Alexandra.
    How to redeploy same component with JSPM?
    JSPM does not allow to deploy an SCA with the same version (release, SP-level, patch-level) as an already deployed component. However, in some special cases you may need to redeploy an SCA with the same version. Use command line:
    go "-config=/jspm/forceMode=true" "-config=/jspm/deployVersionRule=updateAll" to redeploy all SDAs. See note #1123333 for more options.
    regards
    Steven

  • Portal Runtime Error : An exception occurred while processing a request

    Hello friends,
    After upgradation of my portal to the following patch level, SAP J2EE 6.20:
    <b>Portal Version :</b> EP 6 SP 2 patch 29 hotfix 0
    <b>Content Mgmt and Collaboration  version</b> : 6 SP2 patch 5
    i faced many performance related issues. Portal seems to be <b>very slow</b>. After logging in, most of the time I get 2 errors:
    <b>Either</b>
    <b>1></b> Iview remains blank.
    <b>Or
    2></b> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
    But when I refresh that particular iview, it works fine.
    I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found <b>the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."</b>Aug 18, 2005 6:07:42 PM # PRT-Async 2          Fatal           Exception ID:06:07_18/08/05_0669
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
    Component class : com.sapportals.portal.prt.pom.RootComponentNode
    User : tempuser
            at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
            at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
            at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    <b>Help needed.(</b>as i am helpless now.)
    Regards,
    Nilz

    Anthony,
      I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
    I created like this
             project-> rightclick->   export-> par ->selecting project-> givint protal password-> and finish.
    The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
    but the par file is  created in the NW studio Navigation bar.
      Let me know any help regarding this
    thanks
    venkat

  • Portal runtime error while selecting page layout in WPC editor

    Hello,
    in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
    The logfile shows the following :
    #1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
    usr
    sap
    EPD
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.netweaver.bc.util
    lib
    bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
    (source unavailable)
    1 error
    I have the same by clicking on "check assignments"
    Any help ?
    Thanks

    Hello Jego.
    We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
    As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
    Best regards,
    Aliaksandr Zhukau

  • PPM Portal : Runtime error in KM Navigation Iview

    Hi All,
    We have a PPM(xRPM) 4.5 portal which we recently upgraded to SPS8.
    After upgrading the SAP delivered iview "Attachment and Links" is giving below dump::
    Runtime Error
    An exception occured while processing the request.
    Additional information: com.sap.pct.cprxrpm.XRPMRepositoryFilter$1
    Exception ID = 001dbd54-026e-2e10-7c88-c3c88b7162e7      Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 03:22_31/05/11_0036_501295550
    Refer to the log file for details about this exception.
    The ivew is of type KM Navigation and is mapped to the folder '/documents'
    The exception log is below:
    at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:407)
            at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:238)
            at com.sapportals.wcm.portal.component.base.KMControllerDynPage.doOutput(KMControllerDynPage.java:134)
            at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:133)
            at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
            at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:80)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
            at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
            at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
            at java.security.AccessController.doPrivileged(AccessController.java:246)
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer
    Please suggeest the possible root cause and soluiton.
    Edited by: Sumit Oberoi on Jun 1, 2011 12:36 AM
    Regards,
    Sumit
    Edited by: Sumit Oberoi on Jun 1, 2011 12:37 AM

    Portal Restart resolved the issue.

  • NEW 9iAS PORTAL UPGRADE SCRIPTS NOW AVAILABLE

    Based on detailed customer and internal feedback, Oracle9iAS Portal Product Development is now making available NEW and significantly IMPROVED versions of the 9iAS Portal Upgrade Scripts as of 4/20/2001.
    [list]
    [*]Oracle9iAS Portal Upgrade Scripts (2.2/3.0.3.3.3 -> 3.0.6) for Windows NT
    [*]Oracle9iAS Portal Upgrade Scripts (2.2/3.0.3.3.3 -> 3.0.6) for Solaris
    [list]
    The upgrade scripts provided here (at the links above) will allow you to upgrade the following environments:
    a) Your existing WebDB 2.2 installations to Oracle9iAS Portal 3.0.6.
    b) Your existing Oracle Portal Early Adopters Release (3.0.3.3.3) to Oracle9iAS Portal 3.0.6.
    For specific upgrade documentation (also updated!), please consult the links below:
    [list]
    [*]Release notes for Oracle9iAS Portal 3.0.6 Upgrade
    [*]Oracle9iAS Portal Upgrade Guide for NT/2000
    [*]Oracle9iAS Portal Upgrade Guide for Solaris
    [list]
    NOTE: For the final step of the upgrade process, you will also need to download additional upgrade scripts to take you from Oracle9iAS Portal 3.0.6 to the current 3.0.8.9.8 Oracle9iAS Portal release.
    NOTE: Scripts and Doc for the 9iAS Portal 3.0.6 to 3.0.8 Upgrade are expected to be made available later this week (April 24-27)
    The following is a list of bugs and issues addressed with the latest 9iAS Portal 3.0.6 upgrade scripts.
    Upgrade Bugs Fixed for the 2.2 -> 3.0.6 upgrade
    1697813 - NT SCRIPT IS ASKING FOR VALUES 3 AND 4
    1697862 - APPIMP.CSH
    1697863 - UNEXPECTED ERROR ENCOUNTERED ERRORS OCCURED IN APPIMP.CSH
    1697828 - SB: MISSING LINKS FOR THE FOR ITEMS
    1697781 - MIGRATION FAILED
    1714261 : APPLICATION IMPORT SCRIPT FAILS
    1716379 : IMPORT SCRIPT TERMINATES ABNORMALLY
    1712877 : EXPORTING A APPLICATION FAILS
    1715551 : NO ACTION LINKS FOR LOVS WHEN IMPORTED FROM WEBDB SCHEMA !!
    1740211 : AFTER UPGRADE EDITING THE SCHEMA GIVING ERROR
    1697795 - MISSING TEMPLATE AFTER UPGRADE (DOC BUG)
    1697839 - 22-306:DOC: NEEDS TO DOCUMENT
    1697835 - 22-306:DOC: NEEDS TO DOCUMENT
    Additional Bug Fixes
    1703032 - IMPROVE PERFORMANCE FOR THE FOLDER IN EDIT-MODE.
    1703040 - EDIT LINKS APPEAR ON FOLDERS EVEN THOUGH USER DOES NOT HAVE PRIVILEGES.
    1703052 - SUBFOLDERS UNDER THE FOLDERS NOT ALIGNED PROPERLY
    1703063 - PERSPECTIVE PAGE RENDERS SLOWLY
    1703070 - NAVBAR LOGON/LOGOFF LINKS IS HARDCODED TO GO THE CONTENT AREA ROOT FOLDER
    1703072 - NAVBAR LOGON/LOGOFF LINKS DOES NOT WORK FOR PERSONAL FOLDERS.
    1689813 - ITEM LINK IN SEARCH RESULTS SHOULD BE DIRECT ACCESS URL
    null

    Richard,
    You'll need to have 1.0.2.2 to be installed on the middle tier before performing the upgrade for your portal 3.0.9 upgrade repository on the database end. So that means, you'll need to wait for the Linux download of iAS 1.0.2.2 to be available before beginning your upgrade of the portal repository, assuming that your middle tier of iAS is also on a Linux box.
    iAS 1.0.2.2 does indeed include Portal 3.0.9, of which Portal 3.0.9 components will be installed during the upgrade process along with the upgrade of the middle tier. During the upgrade process, the installer (from my personal experience on NT), will notify you that it is performing an upgrade installation of your middle tier, provided that you specified the middle tier's ORACLE_HOME when executing the oracle installer.
    Just be sure to read and follow the 9iAS Migration guide before beginning your upgrade of the middle tier to iAS 1.0.2.2. After upgrading the middle tier to 1.0.2.2, the actual upgrade of the portal repository was extremely simple by comparison.
    The upgrade of the portal repository took a few hours (my recommendation is to invoke it off before leaving for the evening), and it will leave a detailed logfile for you to peruse afterwards, if you choose).
    Best Regards,
    Harry

  • Portal Upgrade from Nw04 6.0 to Nw04s 7.0

    Hi all,
    I’m trying to perform the portal upgrade from version 6.0 Nw04 SP 19 to version 7.0 Nw04s.
    During the preparation I obtain the following error:
    #Java###The software component com.wilytech.jmxservice/wilytech.com could not be read from the BC_COMPVERS table; the table schema may be outdated. Fix it and then repeat the phase from the beginning.##
    I have implemented note n 873624 in order to align the keyname and the keyvendor in sap manifest.mf but with no luck, the detect start release component fails with the same error.
    Any suggestion?
    Thanks and regards 
    alessio

    Hi,
    you can find a good startup in the guide <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5e1226c7-0601-0010-7d82-a8134e833150">Enterprise Portal Migration Update</a>
    hope this helps.
    alessio

  • Portal Upgrade Failure

    Hi!
    I ran the portal upgrade script against a copy of my production database to bring it up from 3.0.8.9.8 to 3.0.9. About an hour after the script was running, the database abruptly came down. When I looked in the altert log, there were numerous ORA-07445, ORA-12805 and ORA-00600 errors that only materialized after this upgrade script started running. It filled my system up with thousands of trace files and core subdirectories which I had to delete but the filesystem never filled up. Now I can open the database but it won't stay open for very long before it abruptly shuts down. Here's a startup from my alert log:
    Fri Jul 20 14:13:51 2001
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    LICENSE_MAX_USERS = 0
    Starting up ORACLE RDBMS Version: 8.1.7.0.0.
    System parameters with non-default values:
    processes = 165
    shared_pool_size = 267665203
    large_pool_size = 614400
    java_pool_size = 20971520
    control_files = /u01/oracle/oradata/play/control01.ctl, /u01/oracle
    /oradata/play/control02.ctl, /u01/oracle/oradata/play/control03.ctl
    db_block_buffers = 58021
    db_block_size = 8192
    compatible = 8.1.0
    log_buffer = 163840
    log_checkpoint_interval = 10000
    log_checkpoint_timeout = 1800
    max_enabled_roles = 30
    remote_login_passwordfile= EXCLUSIVE
    db_domain = msd.ray.com
    instance_name = play
    service_names = play.msd.ray.com
    mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer
    sort_area_size = 165536
    sort_area_retained_size = 165536
    db_name = play
    open_cursors = 300
    os_authent_prefix =
    job_queue_processes = 1
    job_queue_interval = 60
    background_dump_dest = /u01/oracle/admin/play/bdump
    user_dump_dest = /u01/oracle/play/udump
    max_dump_file_size = 10000
    core_dump_dest = /u01/oracle/admin/play/cdump
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    SNP0 started with pid=8
    Fri Jul 20 14:13:57 2001
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
    =TCP))'...
    Fri Jul 20 14:13:57 2001
    alter database mount
    Fri Jul 20 14:14:02 2001
    Successful mount of redo thread 1, with mount id 741551593.
    Fri Jul 20 14:14:02 2001
    Database mounted in Exclusive Mode.
    Completed: alter database mount
    Fri Jul 20 14:14:02 2001
    alter database open
    Beginning crash recovery of 1 threads
    Fri Jul 20 14:14:02 2001
    Thread recovery: start rolling forward thread 1
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 3146 Reading mem 0
    Mem# 0 errs 0: /u01/oracle/oradata/play/redo01.log
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 3147 Reading mem 0
    Mem# 0 errs 0: /u01/oracle/oradata/play/redo02.log
    Fri Jul 20 14:14:04 2001
    Thread recovery: finish rolling forward thread 1
    Thread recovery: 140 data blocks read, 139 data blocks written, 893 redo blocks
    read
    Crash recovery completed successfully
    Fri Jul 20 14:14:04 2001
    Thread 1 advanced to log sequence 3148
    Thread 1 opened at log sequence 3148
    Current log# 3 seq# 3148 mem# 0: /u01/oracle/oradata/play/redo03.log
    Successful open of redo thread 1.
    Fri Jul 20 14:14:04 2001
    SMON: enabling cache recovery
    SMON: enabling tx recovery
    Fri Jul 20 14:14:07 2001
    Errors in file /u01/oracle/admin/play/bdump/play_p003_1051.trc:
    ORA-07445: exception encountered: core dump [ktugru()+72] [SIGBUS] [Invalid addr
    ess alignment] [21] [] []
    Fri Jul 20 14:14:07 2001
    Errors in file /u01/oracle/admin/play/bdump/play_p004_1053.trc:
    ORA-07445: exception encountered: core dump [ktugru()+72] [SIGBUS] [Invalid addr
    ess alignment] [21] [] []
    Fri Jul 20 14:14:14 2001
    Completed: alter database open
    Fri Jul 20 14:14:56 2001
    SMON: Restarting fast_start parallel rollback
    Fri Jul 20 14:14:56 2001
    Errors in file /u01/oracle/admin/play/bdump/play_smon_1035.trc:
    ORA-07445: exception encountered: core dump [kqrprl()+92] [SIGSEGV] [Address not
    mapped to object] [2] [] []
    ORA-12805: parallel query server died unexpectedly
    Fri Jul 20 14:16:01 2001
    PMON: terminating instance due to error 474
    Instance terminated by PMON, pid = 1027
    I am running Oracle 8.1.7, 9iAS 1.0.2.0.1 (have a separate 1.0.2.2 which I'll point to the upgraded portal), and Solaris 2.7. There were no errors in the alert log before I started the upgrade script.
    Has anyone else upgrading just their portal from 3.0.8.9.8 to 3.0.9 experienced this difficulty. Thank GAWD this wasn't my prod portal...
    Much thanks for any reply....Kate

    Thank you Bob! My problem turned out to be that the database backup I used to restore a database copy was actually taken outside of my backup window before the database was shutdown. I should have known that using the init profile allowcorrupted_logs was a harbinger of worse things. Anyway, since the database was completely destroyed by the upgrade script, I used the next week's backup to restore a copy of the databse -- this time with much better results. The upgrade script worked fine after this.
    Thanks for the heads up on the bug though. It will probably be useful. Thanks again.

  • Portal Runtime Error occurred when trying to create iView using template.

    Hi,
    When I tried to create an iView by Content Management through "Existing iView Templates", the Portal runtime error occurred.
    (However, when I tried to create an iView through "Deployed Portal Archive" or "Web Dynpro Java Application", it was successful)
    If you know the same error and the way to solve, please help me.
    Best Regards,
    Daisuke Ikari
    It occurred below system environment.
    Version: NetWeaver 7.0 SPstack18
    OS: Windows 2003 Server SP2
    RDBMS: Oracle 10.2.0.2
    And the error log is below.
    08:29_26/03/09_0002_6759950
    [EXCEPTION]
    java.lang.NoSuchMethodError: com.sapportals.portal.pcd.gl.PcdSearchControls.addExplicitAttributeCheck(Lcom/sapportals/portal/pcd/gl/IPcdAttribute;)V
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getPCDCatalog(TemplatesCacheSrv.java:184)
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.refresh(TemplatesCacheSrv.java:589)
         at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getTemplates(TemplatesCacheSrv.java:646)
         at com.sapportals.admin.templateselection.panes.InitPane.getCatalogList(InitPane.java:206)
         at com.sapportals.admin.templateselection.panes.InitPane.initTemplateList(InitPane.java:122)
         at com.sapportals.admin.templateselection.panes.InitPane.processInput(InitPane.java:59)
         at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:350)
         at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174)
         at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99)
         at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Thanks for your help. Here is the xml
    <PAREVAHRS>
    <P_PROJECT_TYPE>Food Equipment</P_PROJECT_TYPE><P_PRJ_CATEGORY>Qualification</P_PRJ_CATEGORY><P_CPM_ID>658</P_CPM_ID><P_FROM_DATE>2007/03/01 00:00:00</P_FROM_DATE><P_TO_DATE>2007/03/31 00:00:00</P_TO_DATE>
    <LIST_G_PROGRAM>
    <G_PROGRAM>
    <PROGRAM_CODE>0180</PROGRAM_CODE>
    <PROGRAM_NAME>Food Equipment</PROGRAM_NAME>
    <LIST_G_MGR>
    <G_MGR>
    <PROJ_MGR>Lamoreaux, Mr. David</PROJ_MGR>
    <LIST_G_PRJ>
    <G_PRJ>
    <PROJECT_NUMBER>249400</PROJECT_NUMBER>
    <LONG_NAME>KM-60, 100 &amp; 150 BAH, ICE MAKE 249400</LONG_NAME>
    <CUSTOMER_NUMBER>22460</CUSTOMER_NUMBER>
    <CUSTOMER_NAME>HOSHIZAKI AMERICA, INC.</CUSTOMER_NAME>
    <LIST_G_TSKEXP>
    <G_TSKEXP>
    <TASK_NUMBER>PO01START</TASK_NUMBER>
    <EXP_TYPE>100 Labor - Chargeable</EXP_TYPE>
    <EXP_DATE/>
    <QTY>9.25</QTY>
    <REV>0</REV>
    </G_TSKEXP>
    </LIST_G_TSKEXP>
    <PRJREV>0</PRJREV>
    <PRJQTY>9.25</PRJQTY>
    </G_PRJ>
    The PRJREV and PRJQTY is at the same level and they are either zero or non null values.
    - Vasu -

  • Portal upgrade without iAS upgrade

    I have upgraded my Portal instance from 3.0.6 to 3.0.6.
    But I didn't upgrade my iAS instance, and I got this message at login:
    "Call to WPG_SESSION API Failed.Error-Code:6550"
    I read somewhere that the problem might be, that I didn't upgrade iAS 1.0.2.0-> 1.0.2.2
    Is it possible to use only the mod_plsql module of the iAS 1.0.2.2 with the upgraded Portal 3.0.8?
    Will it work, or I must upgrade my whole iAS to 1.0.2.1 and to 1.0.2.2. Then why give Oracle the Portal upgrade script?
    Thanks.
    Paszty

    Thank you for your quick answer.
    I've got another question.
    Where can I find the iAS upgrade scripts?
    We have got iAS 1.0.2.1 and 1.0.2.2 install CDs, but we didn't find any upgrade options.
    We have got now an upgraded Portal 3.0.8. Which iAs upgrade must we use? 1.0.2.1 or 1.0.2.2 or both?
    Thank you.

  • Portal Runtime Error due to use of string buffer

    Hi All,
    Whenever I run a portal component in which i have used srting buffer i am getting portal runtime error like
    java.lang.StringBuffer.append(Ljava/lang/String;)Ljava/lang/AbstractStringBuilder;.
    but same code run fine from  my colleague's system/ NWDS .I reinstalled my NWDS but still same problem .What could be reson for this strange behaviour?
    Provide your inputs to solve this problem.
    Regards,
    Madhvika

    Hi,
    Check the JDK version for compiling, it should be 1.4.
    To check this in  NWDS goto menu: windows --> preference --> Java --> Compiler.
    Here check tab Compliance and Classfiles.
    If this does not solve, check if you installed JDK 1.5, if so uninstall it.
    Also check this, may be a NWDS upgrade can help:
    Re: Modify or field-symbol statement
    Regards,
    Praveen Gudapati

  • Viewing Portal Runtime Error Log

    Hi,
    I am running my Java Custom iViews in EP6 SP9. When I get a Portal Runtime Error, I would like to look at the log file generated.
    In EP6 SP2 we had the option of going to System Admin--> ..  and loking at the Portal log to check the error is there a similar functionality in SP9.
    Any help is appreciated...
    ~NAC

    See the following:
    http://help.sap.com/saphelp_nw04/helpdata/en/ba/0aa94076b63713e10000000a155106/frameset.htm
    for the changes.
    Brian

  • JPREPARE not found, to do Portal upgrade to NW2004S

    Hi all
    I am trying to upgrade Enterprise Portal EP6SP17 (NW2004) to  NW2004S-SR1 on HP-UX-PARISC-64bit/Oracle following the instructions in the Upgrade guide for 'Netweaver 2004S Java'. 
    On Page no.28 it is mentioned to start JPREPARE to prepare and verify the system for upgrade.  I could not locate the executable JPREPARE on  'NW2004s upgrade Master' CD.
    Has anyone faced the same problem in locating  JPREPARE on the media? If yes, on which DVD they found this executable? I look for feedback from anyone who did NW2004 to NW2004S Portal upgrade on any platform.
    Thanks in advance....
    Nagesh

    Thanks Siva,
    That worked too.  I was trying to run 'startserver' first before running 'startgui' and getting a different error message. But that is not required.
    For the benefit of others I am writing down the steps here:
    From the /usr/sap/jupgrade folder:
    1. Run ./PREPARE and leave it running.
    2. Run ./startgui  (from a different unix session)
    to be able to run PREPARE successfully.
    Nagesh

  • Portal upgrade from 308 to 309 on 8.1.7.2 database

    Sun Sparc Solaris, v.8
    8.1.7.2 database.
    Upgraded middle-tier from 9ias 1.0.2.1 to 1.0.2.2.
    Now trying to upgrade portal using upgrade script.
    Ran through OK first time, but noticed a lot of errors in log - checked on your forums and seem same problem as http://technet.oracle.com:89/ubb/Forum70/HTML/002149.html
    So, I tried adding systemtrig_enabled=false to init.ora.
    Try re-running the upgrade script and I get:
    **Upgrade aborted**. This version of the Oracle Portal/WebDB is not supported fo
    r upgrade.. UNKNOWN
    If I take systemtrig_enabled=false out, then the script runs OK - BUT leaves me with all the errors relating to WWSEC_API being invalid and column GRANTEE_APP_ID not existing.
    If I try and re-compile invalid objects after upgrading, I can't get rind of a lot of the invalid objects!
    If I can't set systemtrig_enabled=false to get round the problem, how do I get rid of these invalid objects??
    Thanks,
    John Ferguson.
    null

    Is this a supported workaround by oracle though?
    It appears from Metalink that I am hitting bug 1900555.The workaround is to upgrade database from 8.1.7.0 to 8.1.7.1, then do portal upgrade, then upgrade db to 8.1.7.2.
    I do not have enough spare time and available downtime from users to spend a day and a half doing this....
    Please can someone from oracle confirm svm's solution is valid alternative.
    Ta.
    null

  • Patchset 3 application for portal upgrades

    i was just wondering ... has anybody applied the patchset 3 for portal upgrades - for 3.0.9 to 9.0.4 portals? .... while my experience on these forums is quite frustrating as no body replies usually ... yet if anyone has done it then i would like to know about this patchset results.
    - did it go smoothly? specially the second part
    - did you restore the files and folders manually after applying the repository update? the list of files ... that are given for manual restoration. is it essential to restore them for complete application of this patchset? the long long documentation is ambiguous about it.
    - how did you restart the portal.

    thank you for the message.
    i asked for the experience because the long documentation in this patchset 3 tells us neither to try to access the portal application, nor to retry the patch set, if it fails in the second part of it. there is also no way to uninstall patchset 3 or any of its parts. in that scenario, they only recommend contacting the Oracle support.
    the documentation seemed a little unclear at best because it did not hint or mention about restoring files and folders after the application of the patchset in the part of documentation before application steps. it asks you to do this only after these steps that restore files and folders - some automatically and some need to be done manually. it recommends the backup at many different stages for all the system. so i did not restore those files manually because i did not have a complete back up and missed a few files. so my mistake!!
    it did not fix the error wwc-41417. i restarted all services and components but on trying to login to the portal i got it again. but it is hard to conclude if it only happened because the files were not restored.
    that is why i asked about other people's experience if they have applied it.
    how did you apply it?

Maybe you are looking for

  • HTTP Adapter with dynamic URL

    Hi all Could you please to help. I need to use receiver with HTTP adapter which in this adapter that I need to pass dynamic URL into this. I had try follow this document http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64dbb0af9f30b4e10000000a11466

  • Multiple movement types for reservation

    Dear experts , Is it possible to give multiple movement types for issue against reservations? if possible what should be the setting in "Define Movement Types for Material Reservations" We are trying to issue materials against reservation to differen

  • MacBook Pro 15" not responding after boot-up?

    My MacBook Pro 15" has an issue and won't work! Yesterday I went to my MB to load it up for my daily commute into the city. As I was loading my bag I tried to disconnect my ext. backup drive that works via Time Machine. When I left it the night befor

  • Error in pinging database

    Hi, I am trying to connect to a db2 database using java studio. I have created a connection pool with following properties: Datasource Classname: com.sun.sql.jdbcx.db2.DB2DataSource Resource Type: javax.sql.DataSource Additional properties: URL: jdbc

  • Message: Support for CPU extention SSE2

    I'm trying to install PPCS3 and I get the message that I need to update "Support for CPU extention SSE2" before I can install. Does anyone have any idea what this is all about? I sure don't. Thanks for any help or info.