Error in GENSTATUS during upgrade from CRM 4.0 to CRM 2007

Dear experts
We have 12 errors in GENSTATUS after upgrading our CRM system from 4.0 to 2007. I don't know how to solve them - I had a look at SDN forum, OSS notes without success. Our system was previously connected to MSA but we want to turn it off part of this upgrade.
Below are the generation errors. I couldn't solve any of them:
CNBCCPSAP00070            CG          GNREP                  E              F              Could not find active BDoc for TRANS_ID CNBCCPSAP00070 - Identification not possible via TransID / Name
CNBCCPSAP00070            CG          LUTAB                   E              F              Could not find active BDoc for TRANS_ID CNBCCPSAP00070 - Identification not possible via TransID / Name
MSV_COUNTER               CG           GNREP                  E              F              Could not update reference to old MSG-segment 4156822E5E3B1C1CE10000000A1552B4
MSV_COUNTER               CG           LUTAB                   E              F              Could not update reference to old MSG-segment 4156822E5E3B1C1CE10000000A1552B4
0000000001CG 5ABEB7BA9F5BD3118A5F00A0C9AA8D71                PUBLI                    E              F              Database access error using table SMOG_GFUGR
F000000272CG F3CFBBF7F736D844995523584B67E937     PUBLI                    E              F              Generation error REPL_TEMPLATE_SUBCHECK
F000000273CG CDF390E3E874144F8399B0F88E37F9F2      PUBLI                    E              F              Generation error REPL_TEMPLATE_SUBCHECK
MSV_COUNTER               HT           GNREP                  E              F              Could not update reference to old MSG-segment 4156822E5E3B1C1CE10000000A1552B4
MSV_COUNTER               HT           LUTAB                   E              F              Could not update reference to old MSG-segment 4156822E5E3B1C1CE10000000A1552B4
0000000034HT B49F577F7D5BD3118A5F00A0C9AA8D71  PUBLI                    E              F              Generation error REPL_TEMPLATE_SUBCHECK_IL2
F000000273HT 42411AD9608668DAE10000000A1552B6    PUBLI                    E              F              Generation error REPL_TEMPLATE_SUBCHECK
F000000272HT 42411ADC608668DAE10000000A1552B6    PUBLI                    E              F              Generation error REPL_TEMPLATE_SUBCHECK
Thanks a lot in advance for your help
Best regards
Stephanie

Hi Stephanie
Did you find a resultion to your genstatus issue.
We are in a similar issue currently - we have the following errors
CNBCCPSAP00070            CG
CNBCCPSAP00070            CG
DOC_HEADER                CG
S000000290CG 98FBC48FBE4A0040888E14E1C27C7262
CAMPAIGN_WRITE            CG
Look forward to your response on this
Regards
Eddie

Similar Messages

  • 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

  • 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

  • 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

  • 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

  • Collision Detection during Upgrade from CRM 4.0 to CRM 2007

    We are in the process of doing an upgrade from CRM 4.0 to CRM 2007. As part of this upgrade we are following the steps detailed in the mobile upgrade guide. we are currently working on the collision
    resolution issues in the mobile area. The latest issue on the UI layer is caused by changes on tiles like docactdocu2 or capsearch2 that were reverted to standard SAP.
    When solving the collisions we have been working on sub objects to these tiles. When changes to theses sub objects were finished not only the collision for the sub object was solved but no collision on the parent object was shown. But the result was that the parent objects have returned to SAP standard on vital objects like custom anchors and/or custom controllers are missing on these tiles resulting in build errors. You can easily see what happened in the version tree of these objects as no merge between the changed branch and the SAP branch took place.
    Returning to the tiles version from the changed branch is not possible though this function is offered in the version tree.
    Why is the collision resolution functionality not working as we would expect. Why can we not chsange the tile version to the changed branch.
    Has anyone else experienced these issues
    Regards
    Eddie

    Hi Shankar
    We resolved collisions on script level like "docactdocu2onLoad" by merging or accepting the change list (SAP) version. With the collision on script level being resolved the tile the script belongs to (in this case "docactdocu2") also vanished from the collision list.  The result was that the tile was reverted to the SAP version.
    With the change list being released we cannot go back to the custom version of the tile except by using the version tree. But the option "Copy to Open Version" offered by a right click on the version node wanted does not work.
    Any ideas
    Regards
    Eddie

  • 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

  • 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.

  • 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

  • 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

  • Error 0x8007000E-0x2000C in upgrade from 7 pro to 8.1 pro

    Issue with error on  upgrade from 7 pro to 8.1 pro of error 0x8007000E-0x2000C.  I have tried the install several times and this error returns every time.

    Hi,
    First, we need check the system requirements for Window 8.1:
    System requirements
    http://windows.microsoft.com/en-in/windows-8/system-requirements
    Or, you can firstly run upgrade assistant tool to help you determine if you are able to install Windows 8.1.
    http://windows.microsoft.com/en-in/windows-8/upgrade-from-windows-7-tutorial
    if all things have been done, we can collect the following logs, maybe we can find something about this failure:
    C:\Windows\Panther\Setupact.log
    C:\$Windows.~BT\Sources\panther\setupact.log
    Alex Zhao
    TechNet Community Support

  • ERROR upload: Error in uploadXMLFiles after upgrading from 10.2.0.4

    After upgrading from 10.2.0.1 to 10.2.0.4 on a newly installed Oracle server, I could not use dbconsole any more. It would not display the login page at http://myserver:1158/em. I tried different browser IE, FireFox, and Chrome. It is the same. Then I checked the %ORACLE_HOME/{server_sid}/sysman/log/emagent.trc and found this errors in it:
    2010-02-04 14:11:45 Thread-2552 WARN command: Job Subsystem Timeout set at 600 seconds
    2010-02-04 14:11:45 Thread-2552 WARN upload: Upload manager has no Failure script: disabled
    2010-02-04 14:11:45 Thread-2552 WARN upload: Recovering left over xml files in upload directory
    2010-02-04 14:11:45 Thread-2552 WARN upload: Recovered 0 left over xml files in upload directory
    2010-02-04 14:11:45 Thread-2552 WARN metadata: Metric collectSnapshot does not have any data columns
    2010-02-04 14:11:46 Thread-2552 WARN metadata: Metric Disk_Path does not have any data columns
    2010-02-04 14:11:46 Thread-2552 WARN metadata: Metric osm_diskGroupPolicies does not have any data columns
    2010-02-04 14:11:50 Thread-352 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds.
    I tried emctl secure, upload, start and stop many times. It is still the same. It is a new server and a new database. Any idea?
    TIA!

    I did not change password. It is not password issue.
    According to Oracle support,
    1) the error "2010-02-04 14:11:50 Thread-352 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds" can be ignored.
    2) The error: 2010-02-05 02:52:19 Thread-3864 ERROR util.files: nmeufile_remove D:/oracle/product/10.2.0/db_1/orsvp04.OCTAGONRESEARCH.COM_vp/sysman/recv\00000000365.lk: Error in lfidlb. Error = 0 (No error)
    could be because I used "emctl start agent" , which are not allowed command for DBconsole. The correct one is "emctl start dbconsole"
    Thanks for your input!

  • An error has occurred after upgrading from MBAM 1.0 to 2.0

    The upgrade went fine, uninstalled MBAM v1.0 from SQL and IIS servers, rebooted servers and re-installed with MBAM v2.0.  However, now when I go to the webportal every page shows the "An error has occurred" message. 
    I've checked the webconfig files under the Help Desk Website folder and it's got our server path in it.  the webportal was working before the upgrade.

    Good to hear it was a simple fix. I'm about to upgrade our production environment tomorrow night. Going from MBAM 1.0 to 2.0 SP1. Not sure where you upgraded from, but did you run into any issues. I've been looking and haven't seen anyone encounter any
    real issues. We are not doing the SCCM integration btw.

  • Error ORA-03113 when upgrading from 11.2.0.1 to 11.2.0.3

    I keep on getting this error when upgrading from 11.2.0.1 to 11.2.0.3
    [Thread-57] [ 2012-04-20 13:18:28.207 CEST ] [SummarizableStep.genSummary:409]  Generating Summary for:=Pre Upgrade ,status is:=Successful
    [Thread-57] [ 2012-04-20 13:18:28.208 CEST ] [SummarizableStep.genSummary:409]  Generating Summary for:=Oracle Server ,status is:=Failed
    oracle.sysman.assistants.util.step.StepExecutionException: ORA-03113: end-of-file on communication channel
    Upgrade failed due to running the step "Upgrading Oracle Server"
            at oracle.sysman.assistants.dbma.backend.component.SubComponent.executeSubStepImpl(SubComponent.java:738)
            at oracle.sysman.assistants.dbma.backend.component.SubComponent.executeStepImpl(SubComponent.java:585)
            at oracle.sysman.assistants.dbma.backend.component.Component.executeStepImpl(Component.java:317)
            at oracle.sysman.assistants.dbma.backend.SummarizableStep.executeImpl(SummarizableStep.java:183)
            at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
            at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
            at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2708)
            at java.lang.Thread.run(Thread.java:637)
    [Thread-57] [ 2012-04-20 13:18:28.209 CEST ] [SummarizableStep.executeImpl:212]  Throwing exception e from SummarizableStep
    [Thread-57] [ 2012-04-20 13:18:28.209 CEST ] [BasicStep.configureSettings:304]  messageHandler being set=oracle.sysman.assistants.util.UIMessageHandler@4805e9f1
    oracle.sysman.assistants.util.step.StepExecutionException: ORA-03113: end-of-file on communication channel
    Upgrade failed due to running the step "Upgrading Oracle Server"
            at oracle.sysman.assistants.dbma.backend.component.SubComponent.executeSubStepImpl(SubComponent.java:738)
            at oracle.sysman.assistants.dbma.backend.component.SubComponent.executeStepImpl(SubComponent.java:585)
            at oracle.sysman.assistants.dbma.backend.component.Component.executeStepImpl(Component.java:317)
            at oracle.sysman.assistants.dbma.backend.SummarizableStep.executeImpl(SummarizableStep.java:183)
            at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
            at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
            at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2708)
            at java.lang.Thread.run(Thread.java:637)
    [Thread-57] [ 2012-04-20 13:18:31.000 CEST ] [CompManager.isModeSet:9822]   DB Upgrade Mode Setting := 1
    [Thread-57] [ 2012-04-20 13:18:31.001 CEST ] [CompManager.isModeSet:9823]   Mode := 1 is set
    [Thread-57] [ 2012-04-20 13:18:31.001 CEST ] [SQLEngine.done:2189]  Done called
    [Thread-57] [ 2012-04-20 13:18:31.001 CEST ] [Database.getStepSQLInterface:787]  OH in database: /app/oracle/product/11.2.0.3/db_1Any clues about what could be wrong? I am planning to upgrade with the manual steps if it does not work :(

    Pl post OS details - are you using DBUA to upgrade ? Are there any errors in the database alert log ?
    ORA-00600 [kodpunp-nulltds], ORA-00600 [kokeeiix1], [600] When Upgrading To 11GR2 [ID 1367827.1]     
    HTH
    Srini

  • Why am i getting an error when trying to upgrade from 10.7.5 to 10.9

    when i try and upgrade from 10.7.5 osx lion to 10.9 i get an error, i have 2GB of memory and 144MB of storage. can someone help?

    This would indicate that your MacBook Air does not meet the requirements for Mavericks.
    To install Mavericks, you need one of these Macs:
    iMac (Mid-2007 or later)
    MacBook (13-inch Aluminum, Late 2008), (13-inch, Early 2009 or later)
    MacBook Pro (13-inch, Mid-2009 or later),
    MacBook Pro (15-inch or 17-inch, Mid/Late 2007 or later)
    MacBook Air (Late 2008 or later)
    Mac mini (Early 2009 or later)
    Mac Pro (Early 2008 or later)
    Xserve (Early 2009)
    Your Mac also needs:
    OS X Mountain Lion, Lion, or Snow Leopard v10.6.8 already installed
    2 GB or more of memory
    8 GB or more of available space

Maybe you are looking for