Unable to log-in in OIM11g during upgrade from 9.1.0.2

Team,
We are upgrading OIM from 9.1.0.2 to 11g following below guide.
http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm
Below mentioned steps have been completed successfully.
Task 1: Identify and Prepare Oracle Database for Oracle Identity Manager 11g (Optional)
Task 2: Use the Repository Creation Utility to Create the Schema in the Database
Task 3: Install Oracle Fusion Middleware
Task 4: Use Upgrade Assistant to Upgrade the Oracle Identity Manager Schema
Task 5: Create a WebLogic Domain for Oracle Identity Manager
Task 6: Start the WebLogic Administration Server
Task 7: Configure Oracle Identity Manager Server 11g(special note to copy .xldatabsekey from older installation to new version was done).
Task 8: Configure Node Manager to Start Managed Servers
Task 9: Start the SOA Managed Server
Task 10: Start the Oracle Identity Manager Managed Server
Some more tasks (five more) are remaining now.
After task10, I have added .xldatbasekey key in weblogic/enterprise. Enterprise manager shows all deployment successful (all green).
I expected that after performing Task10 was that OIM 11g user and admin console will be accessible and admin user will be able to logging however it is not happening. I am trying with xelsysdm user and I am sure I am typing the password correctly.
My Query - Should we wait for entire upgrade? To my understanding no, at least log-in into OIM11g should be happening by now?
Thanks,
MS

AFAIK, You have to complete the task Use Upgrade Assistant to Upgrade Oracle Identity Manager Middle Tier before you try login to OIM.

Similar Messages

  • Unable to log into the portal-After Upgrade from NetWeaver 7.0 to 7.3EHP1

    Dear Experts,
    We have poltal landscape(NW 7.0 Dualstack SPS27) with our customozed themes and par files(Company name,logos and colours)
    Recently we upgraded the one of portal from NW 7.0 to NW 7.3EHP1 . Upgrade has been successfilly completed with small issue.
    After upgrade all urls are working(/nwa, /sld) except /irj/portal.We know that NW 7.3 EHp1 accepts only ear file i.e we converted the our customized log on par file to ear file through par migration tool and the same was deployed successfully through NWDS 7.3 version.After deploying we are able to access the
    /irj/portal url with our customized par(means ear file) without issues,
    We are unable to log into the portal after giving the correct user id and password,getting the portal runtime error as foloows.
    Portal runtime error
    An exception occured while processing your request.Send the exception ID your administrator
    Exception id:
    see log files for details about this exception
    Default.trc log file(/server0/log)
    #EP-PIN-PRT#tc~epbc~prtc~api#C00061FD2733006C00000005000056CB#9034950000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.
    runtime#J2EE_ADMIN#4##43E00B85A79911E380F800000089DCC6#3a483a0fa79911e3903000000089dcc6#3a483a0fa79911e3903000000089dcc6#0#Thread[HTTP Worker
    [@900472845],5,Dedicated_Application_Thread]#Plain##
    08:14_09/03/14_0005_9034950
    [EXCEPTION]
    java.lang.RuntimeException: Could not create Resource Repository root folder in PCD
    at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:140)
    at com.sap.portal.resource.repository.ResourceRepositorySrv.init(ResourceRepositorySrv.java:93)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
    at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
    at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
    at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
    at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
    at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
    at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
    at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
    at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
    at com.sap.portal.resource.repository.WebResourceRepositorySrv.init(WebResourceRepositorySrv.java:71)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
    at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
    at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
            at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
            at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
            at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
            at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
            at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
            at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
            at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
            at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
            at com.sap.portal.resource.repository.WebResourceImportService$ResourceImporter.<init>(WebResourceImportService.java:248)
            at com.sap.portal.resource.repository.WebResourceImportService.importApplicationResources(WebResourceImportService.java:172)
            at com.sapportals.portal.navigation.NavigationMimeRepositoryService.loadAllPicsToWRR(NavigationMimeRepositoryService.java:186)
            at com.sapportals.portal.navigation.NavigationMimeRepositoryService.init(NavigationMimeRepositoryService.java:160)
            at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher$3.service(RequestDispatcherFactory.java:518)
            at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:363)
            at com.sap.portal.prt.core.RequestDispatcherFactory$ServiceRequestDispatcher.init(RequestDispatcherFactory.java:503)
            at com.sap.portal.prt.broker.PortalServiceItem.initServiceInstance(PortalServiceItem.java:347)
            at com.sap.portal.prt.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:210)
            at com.sap.portal.prt.broker.PortalServiceItem.load(PortalServiceItem.java:578)
            at com.sap.portal.prt.om.ObjectsManager.createObejctHandle(ObjectsManager.java:234)
            at com.sap.portal.prt.om.ObjectsManager.getObjectHandle(ObjectsManager.java:147)
            at com.sap.portal.prt.broker.PortalAppBroker.getPortalService(PortalAppBroker.java:498)
            at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:431)
            at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
    at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
            at com.sap.portal.pcm.iview.admin.PcmIviewCommon.getAdditionalAttributes(PcmIviewCommon.java:358)
            at com.sap.portal.pcm.iview.admin.PcmIviewCommon.initLayers(PcmIviewCommon.java:173)
            at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:177)
            at com.sap.portal.pcm.page.admin.AdminBasePage.getCustomImplementation(AdminBasePage.java:76)
            at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:642)
            at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:143)
            at com.sapportals.portal.navigation.LightningHelperService.getFrameworkPageAttributesValues(LightningHelperService.java:171)
            at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.prepareAttributes(PhaseConfiguration.java:71)
            at com.sapportals.portal.navigation.fpm.util.PhaseConfiguration.storeRelatedAttributesInSharedStorage(PhaseConfiguration.java:35)
            at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doFrameworkPhase(NavigationFpmListener.java:535)
            at com.sapportals.portal.navigation.fpm.NavigationFpmListener.doPhase(NavigationFpmListener.java:122)
            at com.sapportals.portal.pb.fpm.FPMContainer.distributeEvent(FPMContainer.java:63)
            at com.sapportals.portal.pb.fpm.FPM.doDocumentHook(FPM.java:179)
            at com.sapportals.portal.prt.service.document.DocumentHookMulticaster.doDocumentHook(DocumentHookMulticaster.java:100)
            at com.sapportals.portal.prt.service.document.DocumentHookService.doDocumentHook(DocumentHookService.java:119)
            at com.sapportals.portal.prt.service.document.DocumentHookServiceNew.doDocumentHook(DocumentHookServiceNew.java:186)
            at com.sapportals.portal.prt.connection.PortalHook.doDocumentHook(PortalHook.java:665)
            at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:183)
            at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
            at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
            at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:206)
            at com.sapportals.portal.navigation.PortalLauncher.doContent(PortalLauncher.java:116)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
            at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
            at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
            at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
            at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
            at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
            at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
            at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: javax.naming.InvalidNameException: Character not allowed: ':' in 'pcd:resource_repository'
    at com.sapportals.portal.pcd.pl.PcdName.checkComponent(PcdName.java:64)
            at com.sapportals.portal.pcd.pl.PcdName.checkNameComponent(PcdName.java:39)
            at com.sapportals.portal.pcd.pl.PcdName.padd(PcdName.java:636)
            at com.sapportals.portal.pcd.pl.PcdName.add(PcdName.java:626)
            at com.sapportals.portal.pcd.gl.util.StringUtils.tokenizeIntoPcdName(StringUtils.java:112)
            at com.sapportals.portal.pcd.pl.PcdName.appendUrlInternal(PcdName.java:408)
            at com.sapportals.portal.pcd.pl.PcdName.<init>(PcdName.java:245)
            at com.sap.portal.resource.repository.ResourceRepositorySrv.initRepositoryRootContext(ResourceRepositorySrv.java:121)
            ... 132 more
    1)We are suspecting this issue is related to the theme issue.How to update the theme in the upgraded portal(have a backup of themes)
    2)Want to know if we update a theme where it stored at the operating system level(in NW 7.3 EHP1 as well as NW 7.0)
    3)Is there any post steps after portal upgrade.
    Request you suggest.
    Regards
    Maruthi

    Hi
    Refer the SAP Notes
    1942399 - Fix usage of unregistered class loader while processing HTTP request in an application being updated or stopped at the same time
    1744820 - Migration 7.3 fails while executing migration of pcd_upgrade
    1703578 - WPC migration stops during connection creation
    1918086 - ERROR: Unable to get iView
    Regards
    Ram

  • Unable to  get the login page after upgrade from 11.5.10.2 to R12

    Hi ,
    We are unable to get the login page after upgrade from 11.5.10.2 to R12, all the services are up and running.
    Pls let me know if someone has come across this issue.
    Thanks&Regards,
    Apps DBA

    Hi ,
    After compile JSP files manually , now we are facing problem after logging.
    Error : You have encountered an unexpected error.
    Thanks&Regards,
    Apps DBA

  • Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

    Dear SAP Gurus,
    Greetings
    My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
    They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
    Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
    In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
    Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
    Please clarify. Thanks in advance for your time and efforts
    Regards,
    Chaps
    P.S. Points will be awarded for answers !!

    Hi,
    I think that you should read long text of OSS note 999614 carfully and you are
    aware of the fact that you will have additional migration efforts in
    case you need to migrate to new G/L later on.
    In case you are convinced that  this is the best way please feel free
    to deactivate new G/L as described in note 999614.
    Please make sure that you deactivate new G/L in all clients of your
    new system in case there were already client copies done.
    Yes this is possible and I would not automatically assume that
    error during posting of transactions are due to New GL not being activated.
    Note 756146 documents the issue and possible repercussions
    of using Classic GL.
    In the case of a new installation the new G/L accounting
    is active by default in ERP. In principle, the use
    of the classic GL is also possible for new customers, however,
    SAP does not recommend it since this requires an additional
    migration expense in later years.
    Regards,
    Aidan

  • LONGPOST.LOG Errors during Upgrade from 4.6C to ECC 6.0

    Dear all,
    We have received the below errors during our upgrade from 4.6C to ECC 6.0.
    Basically we have received three types of errors:
    1.
    4PETG065 RSUPGDEC: Table/structure "BAPE_VBAK" (component "SD-SLS" ) enhanced illegally: Error "2"
    2.
    A2PESEEF_BADI 103 BAdI implementation "/IRM/BADI_SDDOCFLOW" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZZ_MG_MASS_NEWSEG" must still be migrated A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
    3.
    3PETG447 Table and runtime object "/SSF/DHEAD" exist without DDIC reference ("Transp. table")
    3PETG447 Table and runtime object "/SSF/DTAB" exist without DDIC reference ("Transp. table")
    3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
    Can anyone help us how to solve this issues.
    Thanks & Regards
    Senthil

    Hi,
    Senthil following are ans to ur questions
    1. After the SPAU remediation is completed, should I manually release the transport or should I start the upgrade and the upgrade will release that transport?
    Ans : Once your SPAU remediation is completed you should release the requests and then start the upgrade of the DEV system.
    2. How do we import this SPDD & SPAU transport in the QA and PRD, I mean at what stage of the upgrade we need to specify/ include this transport?
    Ans : Now when you start the QA or PRD upgrade at that time you come across a phase during PREPARE called ADJUSTPRP.
    Refer following note for further information --
    SAPNote 124522 - Importing a modification adjustment in 2nd upgrade
    3. Suppose the QA & PRD has more objects to adjust than our Dev box, and this transport will not take care of the delta objects, so in that case how should we remediate, we need to create an other transport request in QA and then it will become two transports?
    Ans : First of all this should not be the scenario where you have more modified objects than that in DEV. As all the modfications should take place in DEV first and then should be transported to QA and then PRD. But in such case what you can do is complete the upgrade of QA system and then you are still having 14 days to complete the SPAU objects. So you can make another request which can be transported as a post upgrade activity once the upgrade is completed in production. For SPDD you will have to take care of the SPDD objects if there are different than those in DEV during the ACT_700 phase only or else you might risk data.
    This is the reason why SAP always asks you to follow a proper transport path.
    4. If our dev box has more objects for remediation than our QA & PRD, then will these objects be also imported into the QA & PRD box?
    Ans : Yes, thats why you should be very sure about the SPAU objects that you have found in DEV. You need to compare the objects with QA and PRD and then only make the modifications.
    I hope i have answered all your queries.
    Regards,
    Suhas

  • Error during Upgrade from 4.6c to ECC 6.0

    Hi All,
      We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table.  Please kindly help as early as possible. The upgrade process is stuck.
    Regards
    Anil Kumar K

    Hi Anil,
    Is this issue fixed? Can i know how you fixed it?
    replied to your message Re: How to adopt the index changes during upgrade.
    Thanks,
    Somar

  • Error while generating JAR files during upgrade from 11.5.9 to 11.5.10

    Hi,
    We are getting the following issue after applying 11.5.9 CU2 patch set during the process of upgrade from 11.5.9 to 11.5.10.
    -     3171663: 11.5.9 Oracle E-Business Suite Consolidated Update 2
    Executing: /u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/bin/java -Djava.security.egd=file:/dev/urandom sun.security.tools.JarSigner -keystore ******** -storepass ******** -keypass ******** -sigfile CUST -signedjar /u01/app/tinst/tinstcomn/java/oracle/apps/fnd/jar/fnddssgraphgui.jar.sig /u01/app/tinst/tinstcomn/java/oracle/apps/fnd/jar/fnddssgraphgui.jar.uns CUSTOMER
    ERROR: JarSigner subcommand exited with status 1
    No standard output from jarsigner
    JarSigner error output:
    Exception in thread "main" java.lang.NoClassDefFoundError: sun/security/tools/JarSigner
    Caused by: java.lang.ClassNotFoundException: sun.security.tools.JarSigner
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    Could not find the main class: sun.security.tools.JarSigner. Program will exit.
    Can you please advice regarding this issue....????
    Regards,
    Sreenivasulu.

    Please see these docs.
    Generate Jar File causes NoClassDefFoundError sun/security/tools/JarSigner [ID 393306.1]
    Generating Jar Files Fails with a NoClassDefFoundError: sun/security/tools/JarSigner Error [ID 801014.1]
    Thanks,
    Hussein

  • TP version problem during upgrade from 4.7 sr2 to ECC6

    Hello All,
    i am doing an upgrade from 4.7 to ECC6 (ultimately i have to upgrade to EHP4). I am stuck in phase PREPARE module Initialization finished with status failed #. Below is the error i am getting. before pasting log file i tried my best to uprade TP level by upgrading the Patch level. but its not taking effact in to SAP system. If i check TP version in STMS >> system >> Check TP tool it shows me old version.
    below is the error log excerpt from file CHECKS.LOG
       #====================================================#
    Requests and information for module Initialization #
       #====================================================#
    ERROR:   The upgrade needs a patched version of R3trans which is
             build on 21.06.06 or later.
             The R3trans in your active SAP kernel is either older or
             the version could not be determined. Call it without
             any option to determine the build date.
             If the build date is too old, you have to replace it
             before you can continue the upgrade.
             Download the latest executable available from the SAP service
             market place and update it before you continue.
             Otherwise, the upgrade tools will be corrupted.
    INFO:    The version check of the disp+work in your active SAP kernel
            determined that it has a sufficient level.
             No update of disp+work is necessary.
    ERROR:   The upgrade needs a patched version of tp with version
             number 340.16.05 or higher.
             The tp in your active SAP kernel is either older or the
             version could not be determined. Call it without any option
             to determine the version.
             If the version is too old, you have to replace it before
             you can continue the upgrade.
             Download the latest executable available from the SAP service
             market place and update it before you continue.
             Otherwise, the upgrade tools will be corrupted.
    ERROR: To be able to use ASU Toolbox, your system requires
           the ST-PI software component with at least Support Package Level 8
          After the update is done, the module must be repeated!
           For more information, see the upgrade documentation
    INFO:       The upgrade strategy for the addon ABA_PLUS
                is described in note: 632429
    INFO:       The upgrade strategy for the addon APPINT
                is described in note: 632429
    INFO:       The upgrade strategy for the addon BP-R3PF
                is described in note: 632429
    INFO:       The upgrade strategy for the addon FINBASIS
                is described in note: 438521
    INFO:       The upgrade strategy for the addon LSO
                is described in note: 503468
    INFO:       The upgrade strategy for the addon LSOFE
                is described in note: 503907
    INFO:       The upgrade strategy for the addon PI
                is described in note: 700779
    INFO:       The upgrade strategy for the addon PI_BASIS
                is described in note: 555060
    INFO:       The upgrade strategy for the addon SLL_PI
                is described in note: 1306751
    INFO:       The upgrade strategy for the addon ST-A/PI
                is described in note: 69455
    INFO:       The upgrade strategy for the addon ST-PI
                is described in note: 539977
    INFO:       The upgrade strategy for the addon WP-PI
                is described in note: 632429
       #===========================================================#
    PREPARE module Initialization finished with status failed #
       #===========================================================#
    i downloaded the 47 kernel files SAPEXEDB_304-20001172.SAR and SAPEXE_304-20001172.SAR and installed the kernel file. if i check TP version from command level it shows me 340.16.62, but in SAP STMS it shows me 340.16.03. Can somebody explain what shoulkd i do?
    Can i know also if i can update SAP Kernel from 4.7 sr2 to NW7.0 without upgrading even started?
    If somebody can tell me the exact number of CDs to use to upgrade from 4.7 SR2 to ECC6 EHp4, that would be very
    nice.
    Mani

    Hi Mani,
    ERROR: The upgrade needs a patched version of R3trans which is
    build on 21.06.06 or later.
    ERROR: The upgrade needs a patched version of tp with version
    number 340.16.05 or higher.
    show that the tp and R3trans used by the source 470 system are old.
    You should download the latest tp and R3trans for kernel 470, and
    replace the old tp and R3trans with the downloaded ones under the 470 kernel directory. The 470 kernel directory is specified by parameter DIR_EXECUTABLE which is usually /usr/sap/<SID>/SYS/exe/run.
    Please note that there is also a kernel directory under /<DIR_PUT>/<SID>/SYS/exe which is for the the target system 700. Please do not replace tp and R3trans under this directory with the ones downloaded for kernel 470.
    NO, you cannot update SAP Kernel from 4.7 sr2 to NW7.0 without upgrading even started. Kernel upgrade will be done by SAPup automatically.
    With Best Regards
    Julia

  • Need to understand impact on workflows during upgrade from EBP 3.0 to SRM 5

    Hello experts,
    Greetings to all and a Happy New Year!!
    I am new to the workflow concept, though i have a fair idea of EBP.
    We are using EBP 3.0, classic scenario.  Very soon, we would be upgrading from EBP 3.0 to SRM 5.0. I have a few questions which i need to knw before I take up the upgrade part:
    1) The impact on the worflows like Shopping cart approval, purchase contract approval etc when we upgrade from EBP 3.5 to SRM 5.0...
    2) Does EBP have their own release strategies or are the release strategies defined in R/3 and applied to the shopping cart when it is ordered in EBP? As in classic scenario, POs are created in R/3, then how does the appoval process happen?
    3) What are the necessary things, if any, that I should make sure of before upgrading?
    4) Does all workflows also get upgraded or is there any tool to upgrade the workflow?
    I am not clear with the approval concept in EBP. I know there are workflows that get triggered when a shopping cart is ordered but the approval process in this workflow is something which i want to understand. Please forward me a document, if possible, or a link will also do.
    Please let me know the necessary details.
    Thanks in advance.
    Regards,
    Ayush

    Hi Ayush,
    Most workflows will be the same, but if you have modifications on these workflows' then i'd suggest reverting back to the standards for the upgrade.
    Im not quite sure what you mean about the release strategy. What can be done though, is creating Purchase Requisitions in the R/3 and pass them to the SRM system. From here PO's can be created and the approval process will take place in accordance with your workflow rules in tcode: swb_cond.
    Before upgrading, try to have the system as clean as possible. When i say clean, i mean make sure that users are consistent, SC's, PO's etc arent left hanging. Try to avoid carrying documents over to the new system. I'd suggest archiving anything you can too.
    I don't have any documents to give you but the basic process and transactions are as follows:
    SWB_COND: Your workflow start conditions. Which WF's are on/off (defined by green/red light)
    SWI6: This will let you examine a document and its relevant WF by its object id. (SC No, PO No etc..
    SWUD: Allows for Consistency checks on your workflow and will find any inconsistencies which are occuring. (Use Test Environment and WF Tech Name i.e 14500015)
    SWDD: The workflow builder, will let you build, activate, create new version and modify the worklows in your system.
    Approval itself is simply the chain of approval which a workflow is defined to follow. You need your managers to approve/reject and the conditions for which Managers should be called for approval. Its works from Possible Approvers for workitems and Excluded Approvers for workitems.
    Understanding the WF log is the most essential thing of all. The understanding of BADI is quite important too.
    Hope this info helps you. Check help.sap.com cause everything is documented there too!
    Cheers
    Will

  • Table Enhancement Category during upgrade from 4.7 to ECC 6.0

    When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables.  The enhancement category was previously u2018not classifiedu2019 on these tables. 
    Is this really necessary?  Has anyone not changed the enhancement categories on tables that were flagged during the upgrade?  Also, what happens if we select the wrong enhancement category?

    Jane,
    This is what SAP says,
    Short Text
    Enhancement Category Selection
    Definition
    Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
    You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
    In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
    Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
    Cannot be enhanced
    The structure must not be enhanced.
    Can be enhanced or character type
    All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
    Can be enhanced or character-type or numeric
    The structure and its enhancement must not contain any deep data types (tables, references, strings).
    Can be enhanced in any way
    The structure and its enhancement may contain components whose data type can be of any type.
    Not classified
    This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
    The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
    If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
    If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
    If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
    If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
    If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

  • Impacts on MRS and MAM during upgradation from ECC 5.0 to 6.0

    Hi Gurus,
    I would like to know the impacts on MRS and MAM during the upgradation from ECC 5.0 to 6.0. The version of MRS we are using is MRSS 500, and the version of MAM is 3.0. please let me know your valuable comments.
    Thanks in advance.
    Regards
    Satish

    HELLO,
    Search the form you will get few links.
    Also many companies have gone technical upgradation , but not functional upgradation.
    Thanks
    RK

  • ABAP Code Changes During Upgrade from 4.7C to ECC6

    Hi all,
    I'm in process of collecting information for our next upgrade.
    We are on 4.7C and are planning to upgrade to ECC6. We wanted to know what changes shall be required on ABAP side during this upgrade. e.g. certain ABAP commands which are obselete, few tables , few fucntional modules being obselete.
    Any specific functional areas/transcation codes being obselete which in turn would make Uer Exit redudant etc.....
    Could somebody please help me out with some info regarding this upgrade? Some links or any hint you can give would help me a lot. (Whether technical or functional..all very welcome!).
    Thanks in advance
    Moderator message: topic too broad to be answered in a forum thread, many people had to go through this, please search for available information/documentation.
    Edited by: Thomas Zloch on Jun 14, 2011 9:31 AM

    Hi ,
    I too got an error of this type .
    The resolution is as follows :
    login as user SAP<SID> in the oracle database .
    SQL> drop tabel <tablename>;
    Restart the upgrade from PARMVNT_SHD phase.
    Regards
    Ratnajit

  • SPAU / SPDD Transport During Upgrade from 4.6C to ECC 6.0

    We are currently upgrading R/3 4.6C to ECC 6.0 SR2. During the DEV upgrade, we performed Dictionary Objects adjustments before ACT 7.00 and SPAU adjustments at the end of the upgrade. All the adjustments are collected in a transport.
    I read in another thread that we will have to choose 'SELECT FOR TRANSPORT' button in SPAU and not release it. Then, continue with the upgrade. And in the same thread, it is also mentioned that DDIC object modifications should not be handled through transports.
    Now, my question is, if I have collected the SPAU adjustments in a transport and continued with the upgrade without choosing the 'SELECT FOR TRANSPORT' button, can I do it after I complete the upgrade before I continue with QAS upgrade? Will the upgrade still automatically detect the transports and move them? And, my other question is, if DDIC modifications are not supposed to be dealt through transports, how else should they be worked upon?
    Your response ASAP will be rewarded properly.
    Thank you.

    Nick, thank you for the reference. Even though I had gone through this note before, I couldn't apply this note because, this note was refering to "R3up" which, I guess, is no more used. "SAPup" is the program currently in use. Also the location mentioned in the note to execute "R3up" is "//usr/sap/put/exe" but, "SAPup" is located under "//usr/sap/put/bin/". So, I am not sure if there is any new notes refering to this. One other question I have with regards to this note is, one of the arguments for the command R3up is, "REL". For SPDD, the note suggests to use target release. And for SPAU, the note suggest to use the release mentioned in the DDIC activation phase.
    In my case, I am upgrading from 4.6D (kernel) to 700 (kernel). The DDIC activation shows ACT_700. So, I am sure I would use "700" as value for "REL" for SPDD. But, am I supposed to use "46D" for SPAU? or should I use "700"?
    Thank you.

  • ZSearch Help: will it remain during upgradation from ECC6 to higher version

    Hi,
    During upgarde from ECC6 to higher versions, will zserach help be moved to higher version automatically or will it be removed and I have to create ZSearch Help again in the higher version.
    What about the ZTable, will it be there in higher version or I need to create it again in the higher version.
    Thanks,
    Priyanka.

    Hello Priyanka
    Upgrading your SAP system will <b>not affect</b> your Z-objects <b>directly</b>.
    However, if your Z-objects reference (i.e. use) SAP standard objects that are changed (or, rarely, are deleted) during upgrading then you may have to adjust your Z-objects. Therefore, keep your (automatic) test scripts available (e.g. eCATT) and run them immediately after the upgrade has been finished.
    Regards
      Uwe

  • Error during upgrade from OBIEE 10G to 11G

    Hello All
    I ran into this issue while trying to upgrade my 10g RPD and catalog to 11.1.1.7
    After installing 11G, I launched the upgrade utility from Oracle_Common/bin/ua in linux.
    I am getting the below error:
    UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
    Based on the Oracle Doc. it has the following desc:
    UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
    Cause: The user has chosen to perform a upgrade from an Oracle home that does not allow an upgrade.
    Action: None.
    Level: 1
    Type: ERROR
    Impact: Upgrade
    So what should I do to resolve this issue?
    Thanks in advance

    Hi,
    First of all i am not familiar on linux box.
    I tried in windows environment the rpd is deployed with out any errors.
    But i ran the ua.bat file in the following path
    \MWHOME\Oracle_BI1\bin\ua.bat.
    while i am running in oracle_common\bin\ua.bat is not responding in my local system.
    Please Mark if it helpful.
    Thanks

Maybe you are looking for