Support package / add on import error in DB2 V9.1 / windows 2003 system

Hi
I have installed ERP 6.0 IDES version in Windows 2003 server with DB2 LUW 9.1 / FP5.
I have selected "Row Compression" and "Deferred Table Creation" during installation.
Now when I am importing add on BI Content 7.03, I am getting error during Movename tabs phase.
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package ALL, tp step "6", return code 0008
The error message in the file D:\usr\sap\trans\log\P090113.IDS is as follows,
2 ETP301
3 ETP361 "96" Shadow-Nametabs activated, DDL executed
2 ETP362 "6" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/01/13 02:57:51")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/01/13 02:58:07")
2 ETP301
1 ETP172 MOVE OF NAMETABS
1 ETP110 end date and time : "20090113025807"
1 ETP111 exit code : "8"
1 ETP199 ######################################
I have read some notes it may be due to "Row compression" and "Deffered table creation" option in DB2. Please help me in resolving this issue if it is DB2 related.
Regards,
Nallasivam.D

Hi,
Please find the real error message which I found in the same log file. This is a new installation.
System configuration details:
ERP 6.0 IDES SR3 + Windows 2003 enterprise server SP2 + DB2 V9.1 / FP5
BASIS and ABAP support pack level: (700) 13.
Error message:
3 ETP399 INDEX IN "IDS#BTABI"
3 ETP399 LONG IN "IDS#BTABD COMPRESS YES"
3 ETP399 
2WETP000 02:53:26: Retcode 1: error in DDL statement for "/OSP/T_REPINFO                " - repeat
2EETP345 02:53:38: Retcode 1: SQL-error "-107-SQL0107N  The name "IDS#BTABD COMPRESS YES" is too lo
2EETP345 ng.  The maximum length is "18".  SQLSTATE=42622" in DDL statement for "/OSP/T_REPINFO   
2EETP345             "
2 ETP399  -
DB-ROLLBACK() -
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399 
2WETP000 02:54:05: Retcode 1: error in DDL statement for "/SAPPO/CMP_ASG                " - repeat
2EETP345 02:54:17: Retcode 1: SQL-error "-107-SQL0107N  The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng.  The maximum length is "18".  SQLSTATE=42622" in DDL statement for "/SAPPO/CMP_ASG   
2EETP345             "
2 ETP399  -
DB-ROLLBACK() -
2EETP334 02:54:17: error in DDL, nametab for "/SAPPO/CMP_ASG" not activated
3 ETP399 IN "IDS#POOLD"
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399 
2WETP000 02:54:17: Retcode 1: error in DDL statement for "/SAPPO/CSCRN_HDR              " - repeat
2EETP345 02:54:29: Retcode 1: SQL-error "-107-SQL0107N  The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng.  The maximum length is "18".  SQLSTATE=42622" in DDL statement for "/SAPPO/CSCRN_HDR 
2EETP345             "
2 ETP399  -
DB-ROLLBACK() -
2EETP334 02:54:29: error in DDL, nametab for "/SAPPO/CSCRN_HDR" not activated
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399 
2WETP000 02:54:29: Retcode 1: error in DDL statement for "/SAPPO/F_ASG                  " - repeat
2EETP345 02:54:41: Retcode 1: SQL-error "-107-SQL0107N  The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng.  The maximum length is "18".  SQLSTATE=42622" in DDL statement for "/SAPPO/F_ASG     
2EETP345             "
2 ETP399  -
DB-ROLLBACK() -
2EETP334 02:54:41: error in DDL, nametab for "/SAPPO/F_ASG" not activated
Regards,
Nallasivam.D

Similar Messages

  • Error whiel instaling r12 on window 2003

    Hi,
    Am geting following error while installing r12 on window 2003.please help me to figure out the exact error.. thank you
    Executing home registration for s_weboh_oh...
    Registering using Registration Driver
    M:\oracle\R12\apps\tech_st\10.1.3\appsutil\driver\regclone.drv
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\template\adouiweboh.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\ouicli.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\ouicli.pl to M:\oracle\R12\inst\apps\R12_tychio\out\ouicli.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\template\txkstubcfg1013.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\txkstubcfg1013.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\txkstubcfg1013.pl to M:\oracle\R12\inst\apps\R12_tychio\out\txkstubcfg1013.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\template\apachectl_sh_1013_oh.tmp
    dest : M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\bin\apachectl
    backup : M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\bin\apachectl to M:\oracle\R12\inst\apps\R12_tychio\out\apachectl
    setting permissions: 700
    Executing script in InstantiateFile:
    M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib -I M:\oracle\R12\apps\apps_st\appl\au\12.0.0\perl -I M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\mod_perl\site\5.8.3\lib\MSWin32-x86-multi-thread M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\ouicli.pl
    script returned:
    Beginning OUI CLI cloning for s_weboh_ohSun Jun 5 18:55:13 2011
    M:\oracle\R12\apps\tech_st\10.1.3\appsutil\jdk\jre\bin\java.exe -classpath M:\SR12\startCD\Disk1\rapidwiz\jlib\java;M:\oracle\R12\apps\tech_st\10.1.3\oui\jlib\OraInstaller.jar;M:\SR12\startCD\Disk1\rapidwiz\jlib\xmlparserv2.jar;M:\SR12\startCD\Disk1\rapidwiz\jlib\ojdbc14.jar oracle.apps.ad.clone.util.OracleHomeCloner -OUICLI -e M:\oracle\R12\inst\apps\R12_tychio\appl\admin\R12_tychio.xml -nolink -oaVar s_weboh_oh -homestub weboh -log M:\oracle\R12\inst\apps\R12_tychio\admin\log\ohclone.log
    running OUI CLI home cloning:
    M:\oracle\R12\apps\tech_st\10.1.3\oui\bin\setup.exe -nowait -clone -silent -force -nolink -waitForCompletion session:ORACLE_HOME=M:\oracle\R12\apps\tech_st\10.1.3 oracle.as.j2ee.top:s_asInstanceName=R12_tychio_WEBOH oracle.as.j2ee.top:s_adminName=oc4jadmin oracle.as.j2ee.top:s_adminPassword=welcome ORACLE_HOME_NAME=R12_tychio_WEBOH -J-Doracle.installer.noLink=true
    Finished OUI CLI cloning for s_weboh_oh with return code: 0Sun Jun 5 19:05:13 2011
    [SC] ChangeServiceConfig SUCCESS
    .end std out.
    .end err out.
    Executing script in InstantiateFile:
    M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib -I M:\oracle\R12\apps\apps_st\appl\au\12.0.0\perl -I M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\mod_perl\site\5.8.3\lib\MSWin32-x86-multi-thread M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\txkstubcfg1013.pl
    script returned:
    .end std out.
    .end err out.
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\template\adouiweboh.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\ouicli.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\ouicli.pl to M:\oracle\R12\inst\apps\R12_tychio\out\ouicli0.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\template\txkstubcfg1013.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\txkstubcfg1013.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\clone\txkstubcfg1013.pl to M:\oracle\R12\inst\apps\R12_tychio\out\txkstubcfg10130.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.3\appsutil\template\apachectl_sh_1013_oh.tmp
    dest : M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\bin\apachectl
    backup : M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\bin\apachectl to M:\oracle\R12\inst\apps\R12_tychio\out\apachectl0
    setting permissions: 700
    Completed home registration for s_weboh_oh
    Executing home registration for s_tools_oh...
    Registering using Registration Driver
    M:\oracle\R12\apps\tech_st\10.1.2\appsutil\driver\regclone.drv
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\template\adouitools.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\ouicli.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\ouicli.pl to M:\oracle\R12\inst\apps\R12_tychio\out\ouicli1.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\template\txkstubcfg1012.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\txkstubcfg1012.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\txkstubcfg1012.pl to M:\oracle\R12\inst\apps\R12_tychio\out\txkstubcfg1012.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\template\ftrace_cfg_1012.tmp
    dest : M:\oracle\R12\apps\tech_st\10.1.2\forms\server\ftrace.cfg
    backup : M:\oracle\R12\apps\tech_st\10.1.2\forms\server\ftrace.cfg to M:\oracle\R12\inst\apps\R12_tychio\out\ftrace.cfg
    setting permissions: 700
    Executing script in InstantiateFile:
    M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib -I M:\oracle\R12\apps\apps_st\appl\au\12.0.0\perl -I M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\mod_perl\site\5.8.3\lib\MSWin32-x86-multi-thread M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\ouicli.pl
    script returned:
    Timed out( 3750000 ): Interrupted Exception
    Beginning OUI CLI cloning for s_tools_ohSun Jun 5 19:05:25 2011
    M:\oracle\R12\apps\tech_st\10.1.3\appsutil\jdk\jre\bin\java.exe -classpath M:\SR12\startCD\Disk1\rapidwiz\jlib\java;M:\oracle\R12\apps\tech_st\10.1.2\oui\jlib\OraInstaller.jar;M:\SR12\startCD\Disk1\rapidwiz\jlib\xmlparserv2.jar;M:\SR12\startCD\Disk1\rapidwiz\jlib\ojdbc14.jar oracle.apps.ad.clone.util.OracleHomeCloner -OUICLI -e M:\oracle\R12\inst\apps\R12_tychio\appl\admin\R12_tychio.xml -nolink -oaVar s_tools_oh -homestub tools -log M:\oracle\R12\inst\apps\R12_tychio\admin\log\ohclone.log
    running OUI CLI home cloning:
    M:\oracle\R12\apps\tech_st\10.1.2\oui\bin\setup.exe -nowait -debug -clone -silent -force -nolink -waitForCompletion session:ORACLE_HOME=M:\oracle\R12\apps\tech_st\10.1.2 oracle.as.j2ee.top:s_asInstanceName=R12_tychio_TOOLS oracle.as.j2ee.top:s_adminName=ias_admin oracle.as.j2ee.top:s_adminPassword=welcome ORACLE_HOME_NAME=R12_tychio_TOOLS -J-Doracle.installer.noLink=true
    Executing script in InstantiateFile:
    M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib -I M:\oracle\R12\apps\apps_st\appl\au\12.0.0\perl -I M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\mod_perl\site\5.8.3\lib\MSWin32-x86-multi-thread M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\txkstubcfg1012.pl
    script returned:
    .end std out.
    .end err out.
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\template\adouitools.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\ouicli.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\ouicli.pl to M:\oracle\R12\inst\apps\R12_tychio\out\ouicli2.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\template\txkstubcfg1012.pl
    dest : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\txkstubcfg1012.pl
    backup : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone\txkstubcfg1012.pl to M:\oracle\R12\inst\apps\R12_tychio\out\txkstubcfg10120.pl
    setting permissions: 700
    instantiate file:
    source : M:\oracle\R12\apps\tech_st\10.1.2\appsutil\template\ftrace_cfg_1012.tmp
    dest : M:\oracle\R12\apps\tech_st\10.1.2\forms\server\ftrace.cfg
    backup : M:\oracle\R12\apps\tech_st\10.1.2\forms\server\ftrace.cfg to M:\oracle\R12\inst\apps\R12_tychio\out\ftrace0.cfg
    setting permissions: 700
    M:\oracle\R12\inst\apps\R12_tychio\admin\log\adcvmlog.xml does not exist. Ignore it
    [AutoConfig Error Report]
    The following report lists errors AutoConfig encountered during each
    phase of its execution. Errors are grouped by directory and phase.
    The report format is:
    <filename> <phase> <return code where appropriate>
    [APPLY PHASE]
    AutoConfig could not successfully execute the following scripts:
    Directory: M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\bin\MSWin32-x86-multi-thread\perl.exe -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\5.8.3\lib -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib\MSWin32-x86-multi-thread -I M:\oracle\R12\apps\tech_st\10.1.3\perl\site\5.8.3\lib -I M:\oracle\R12\apps\apps_st\appl\au\12.0.0\perl -I M:\oracle\R12\apps\tech_st\10.1.3\Apache\Apache\mod_perl\site\5.8.3\lib\MSWin32-x86-multi-thread M:\oracle\R12\apps\tech_st\10.1.2\appsutil\clone
    ouicli.pl INSTE8_APPLY -1
    AutoConfig is exiting with status 1
    RC-50013: Fatal: Instantiate driver did not complete successfully.
    M:\oracle\R12\apps\tech_st\10.1.2\appsutil\driver\regclone.drv

    Shuq,
    Please see my last reply in this thread -- Error - Installing Oracle EBS 12.1.1 for Windows (32-bit) on XP Prof SP3
    Thanks,
    Hussein

  • What is Plug-in, SUpport Package, Add in and how R3 and BW are interdep

    Hello Every One,
    Can some one explain me in simple words about the terms, Plug-ins, SUpport Packs, Service Packs, Add-in's, SAP Notes and how R3 and BW are interdependant in the above mentioned terms? Can anyone give a simple example?
    regards,
    kishore

    Hi,
    <b><u>Plug-ins:[/</u>b]
    Additional program which enhances the functionality of an existing program. Additional functions which may not be needed or are mutually exclusive are often implemented as plug-ins.
    For example ICMAN contains various plug-ins for the various network protocols which it supports (HTTP, SMTP, FTP,...).
    The interface between mySAP.com components (for example, SAP APO, SAP BBP, SAP BW, SAP CRM) and one or more SAP R/3 systems.
    The SAP R/3 Plug-In unites the plug-ins APO-CIF, CRM-R3A, BW-BCT and B2B-PRO-PI. This simplifies maintenance significantly and guarantees compatibility between the individual mySAP.com components. With SAP R/3 Plug-In, you can use several mySAP.com components simultaneously in a single system. SAP R/3 Plug-In supplies the mySAP.com component transaction data and master data in real time.
    Technically, there are two versions of each release of the SAP R/3 Plug-In, a PI version and a PI-A version.
    The technical names of the software components are PI and PI_A
    <b><u>SUpport Packs</u></b>
    A set of corrections for serious software errors in the SAP system.
    Support Packages are compiled periodically and made available in the SAP Service Marketplace.
    <b><u>Service Packs</u></b>
    A grouping of different services for a quotation.
    A service package can be agreed between a service provider and a customer within a service contract or as part of a complex service plan, which can also be additionally agreed in a service contract.
    EXAMPLE
    A "Winter Car Check" service package containing the following services is agreed in a contract:
    Cooling water check
    Brake fluid check
    Battery inspection
    Light inspection
    <b><u>Add-in's</u></b>
    add-ins are enhancements to the standard version of the system. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software
    http://help.sap.com/saphelp_erp2004/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
    <b><u>SAP Notes</u></b>
    Documentaion Prepared by SAP for publishing clarity in case of corrections or changes happening to the SAP Software.
    <b><u>R3 and BW are interdependant</u></b>
    Then BW takes the Data from R/3 : so there has to be Support Pluggins which are mapped to the BW server.So the SAP Supported R/3 Versions should be used.
    Eg: SAP Stoped the Support for r/3 4.0 series
    regards
    Happy Tony

  • Error Installing patch 6272725 on Windows 2003 server

    Hi all,
    I am trying to install the RUP3 patch on Windows 2003 server. I am getting the following error when installing patch 6272715 which is required to be installed before installing patch 6141000. If i continue installing patch 6141000 after ignoring this error, i get same error during installation of patch 6141000. Please can any one suggest me what i should do to get rid this error.
    AD utilities can support a maximum of 999 workers. Your
    current database configuration supports a maximum of 83 workers.
    Oracle recommends that you use between 2 and 4 workers.
    Enter the number of parallel workers [2] :
    AutoPatch will run in parallel mode.
    Did not need to apply new applterr.txt.
    Applying new applprod.txt (if any)...
    Did not need to apply new applprod.txt.
    Performing version checking for driver files...
    Log and Info File sync point:
    Mon Nov 26 2007 12:33:27
    AutoPatch found some files which it will not apply.
    These files are listed in the AutoPatch informational message file.
    Copying driver files into installation area...
    No driver files were selected for copying.
    Skipping...
    ForceCopy driver files into installation area for Specified driver
    since no such action is present for this driver file
    Screening out files not valid for this installation...
    Determining valid on-site files...
    Extracting object modules from product libraries...
    setEnvAdrelink: Error: Cannot open registry key:
    SOFTWARE\ORACLE
    aiosp2() Error: failure in usdspn()
    Contents of error buffer are:
    "usdsop cannot create a new process
    Cause: usdsop encountered an error creating a new process. [Reason].
    Action: Check that your system had enough resources to start a new process. Cont
    act your system administrator to obtain more resou (RE"
    An error occurred while extracting files from library.
    Continue as if it were successful [No] :
    --- Thank You.

    Sir,
    I am posting the output as told by you.
    G:\>which ls
    ls: Command not found.
    G:\>c:
    C:\>ls
    'ls' is not recognized as an internal or external command,
    operable program or batch file.
    C:\>cd e:\cygwin\bin
    C:\>e:
    E:\cygwin\bin>which ls
    ls: Command not found.
    E:\cygwin\bin>
    I am also posting the output of adadmin utility in which i tried ti relink FND programs
    Enter list of products to link ('all' for all products) [all] :
    Generate specific executables for each selected product [No] ?
    AD Administration can relink your Oracle Applications programs with debug
    information. Oracle recommends that you do not relink your programs
    with debug information unless asked to do so by Oracle Support Services.
    Relink with debug information [No] ?
    Relinking selected modules in Application Object Library.
    setEnvAdrelink: Error: Cannot open registry key:
    SOFTWARE\ORACLE
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 33: a
    wk: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 203:
    tr: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 534:
    cat: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 538:
    tr: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 538:
    tr: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 538:
    tr: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 548:
    awk: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 573:
    cat: command not found
    /cygdrive/g/ora12/VIS/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh: line 575:
    rm: command not found
    Usage: adrelink force=y [<optional args>] <targets>
    or: adrelink force=y [<optional args>] filelist=<file>
    where <targets> = { <product module> [<product module>] ... }
    and <product module> = "<product> <module name>"
    - <product> should be in lower case
    - <module name> should exactly match the executable name
    Valid <optional args> are:
    envfile=adsetenv.sh
    Used only by the 'adsetup' script
    link_debug=y
    Will we link executables with debug or not? Default is 'n'
    backup_mode=none
    Which executables will we back up when linking with force=y?
    Default is 'file'. Meanings are:
    - none: do not back up any executables
    - all : back up all executables
    - file: do what $APPL_TOP/admin/adlinkbk.txt says to do
    Type 'adrelink examples' to see some examples of running adrelink.
    An error occurred while relinking application programs.
    Continue as if it were successful [No] :
    It is clear that there is some problem with Cygwin. I have renamed the following executabes after the cygwin installation.
    gcc to cc
    egrep to grep
    gawk to awk
    gnumake to make
    i have also copied which.exe to "Windows\system32" directory from "cygwin\bin" folder and
    Copy LINK.exe to "Windows\system32" directory from "VC98" directory.
    Please tell me if there is something wrong with Cygwin installation.

  • [b]Error in installation database in Windows 2003 server[/b]

    Hi, I have a problem. I am trying to install a database Oracle Enterprise Edition 10.1.0.2.0 in a machine that has Windows 2003 Server. On having finished the installation and begin the Database Configuration Assistant appears the error ora-12546 TNS permission denied. In the file listener.log
    the following messages appear:
    TNS-12500: TNS:listener failed to start a dedicated server process
    TNS-12546: TNS:permission denied
    TNS-12560: TNS:protocol adapter error
    TNS-00516: Permission denied
    32-bit Windows Error: 5: Input/output error
    In the alert.log appear:
    OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified O/S-Error: (OS 1) Incorrect function. !
    I install in local mode, not remote and using Administrator user.
    Help me, please!
    Regards
    Carlos

    Hello,
    There is a note in SAP that indicates that EMT64/x64 is not compatible with Oracle 9.2 (nota 12546) There is Oracle's FAQ that indicates Oracle's versions and Windows that he(she) supports EMT64.
    http://www.oracle.com/technology/tech/windows/faq.html#x86-64
    Since you can see it(he,she) indicates that Oracle 9.2 is supported in Windows 32 bits with technology EMT64
    And that alone the version 10g 2 be reread it(he,she) is compatible with Windows 2003 SEVER 64 bits with technology EMT64
    I hope that this costs(suits) us to solve our problems
    A greeting

  • Error in installation database in Windows 2003 server 64 bits

    Hi, I have a problem. I am trying to install a database Oracle Enterprise Edition 9.2.6 in a machine that has Windows 2003 Server 64 bits
    . On having finished the installation and begin the Database Configuration Assistant appears the error ora-12546 TNS permission denied. In the file listener.log
    the following messages appear:
    TNS-12500: TNS:listener failed to start a dedicated server process
    TNS-12546: TNS:permission denied
    TNS-12560: TNS:protocol adapter error
    TNS-00516: Permission denied
    32-bit Windows Error: 5: Input/output error
    I see the note 722966 and my procesador is EM64T
    I install in local mode, not remote and using Administrator user.
    Help me, please!

    Hello,
    There is a note in SAP that indicates that EMT64/x64 is not compatible with Oracle 9.2 (nota 12546) There is Oracle's FAQ that indicates Oracle's versions and Windows that he(she) supports EMT64.
    http://www.oracle.com/technology/tech/windows/faq.html#x86-64
    Since you can see it(he,she) indicates that Oracle 9.2 is supported in Windows 32 bits with technology EMT64
    And that alone the version 10g 2 be reread it(he,she) is compatible with Windows 2003 SEVER 64 bits with technology EMT64
    I hope that this costs(suits) us to solve our problems
    A greeting

  • Error in accessing application on windows 2003 server

    error on accessing the application on windows 2003 server R12
    500 Internal Server Error
    Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
    First time i login sucessfully but now its not working.

    Hi Mushy;
    500 Internal Server Error
    Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.First try to run autoconfig and retest issue. If you have still same error check log file for more details
    Also check:
    500 Internal Server Error Servlet error:
    500 Internal Server Error  Servlet error:
    R12 Startup Issue
    Regard
    Helios

  • Admin Console errors in fresh install on Windows 2003 Enterprise.

    I have attempted to install 6.1 SP4 on two different Windows 2003 Enterprise boxes. Neither has W2K3 SP1 on them. The installs proceed using a typical install with no errors reported. All defaults were accepted during the install. I can start the server for the Admin and web server instances. I can hit the default page on the web server instance. When I attempt to launch the admin console, I am prompted to logon, as expected. I enter my credentials and promptly get an HTTP 500 error. I check the logs in C:\Sun\WebServer6.1\https-admserv\logs\errors and find the following line:
    [26/Apr/2005:12:43:26] failure ( 2596): for host 192.168.175.128 trying to GET /https-admserv/bin/index, cgi_scan_headers reports: HTTP4044: the CGI program C:\Sun\WebServer6.1\bin\https\admin\bin\index.exe did not produce a valid header (program terminated without a valid CGI header. Check for core dump or other abnormal termination)
    I searched for others reporting similar problems and the closest I could come to an answer was to make sure cookies were enabled on the brower (they are). I get the same error in IE and Firefox, both locally and remotely. After becoming frustrated with one W2K3 server, I decided to try on another. Exactly the same errors.
    Increased loglevels in the server.xml provide no additional logging for this problem. Any pointers to a resolution would be most appreciated as I'm about ready to scrap Sun and move to Apache.
    Thanks,
    Sean

    Yes, there appear to be problems where certain old versions of Netscape and iPlanet products can leave old DLLs lingering in the Windows system32 directory.
    I'd check for the following files in the Windows system32 directory (typically C:\WINNT\system32 or C\WINDOWS\system32):
    libnspr4.dll
    libplc4.dll
    libplds4.dll
    nss3.dll
    nssckbi.dll
    smime3.dll
    ssl3.dll
    nsldap32v50.dll
    nsldappr32v50.dll
    nsldapssl32v50.dll
    If you find any of these files, you can try replacing them with a copy from your Web Server install. Don't forget to backup first.
    Please report back what you find!

  • AVCHD Import Error In Log And Transfer Window

    Hey,
    I just bought FCE4 and also a canon hf100 camera. When i try to ingest clips from the camera (in avchd format) with the log and transfer window an error icon comes up and says : "error: no data" and the file is not successfully imported. I tried switching my audio preferences to normal stereo instead of matrix but that did not help.
    Any help would be great!
    Jackson

    What format exactly did you shoot with that camera? What settings are you using in FCE?

  • Can't Drop a table in DB2 UDB on Windows 2003 server Ent EDT

    Previus step:
    Database DB2 ibm for a sap BW production got error in log - cause: no space on disk.
    system mark database as bad.
    system connection with db was restored with sap and ibm support
    I'm in disaster recovery situation,
    we have rebuilded index and table that got problem in db2dart report.
    Now Sap system go up, we have successfully  dumped 29 of 30 tables with db2dart /ddel command, now there is only a table that got problem:
    sapbw2.rsbatchdata
    we can't drop this table.
    We try with this step:
    1) db2dart bw2 /ddel
       (table id)1837     (tablespaceid)10 0 9000000
       we obtain a SQL file
    2) db2dart bw2 /mt
       (table id)1837     (tablespaceid)10 (password that you provide)
    3) db2 drop bw2 sapbw2.rsbatchdata after this command we got a crash database.
    2008-05-29-16.33.59.148000+120 I5094483F478       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : section stmt
    DATA #1 : Hexdump, 29 bytes
    0x000000003806E1F4 : 6472 6F70 2074 6162 6C65 2073 6170 6277    drop table sapbw
    0x000000003806E204 : 322E 5253 4241 5443 4844 4154 41           2.RSBATCHDATA
    2008-05-29-16.33.59.148000+120 I5094963F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section stmt
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095124F174       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: informational text for dump
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095300F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: Unrelocation Needed
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095468F204       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: Section relocated; reltables in global cache inaccessible
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.148000+120 I5095674F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section ptr
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5095834F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section size
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5095995F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dynamic ptr
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096155F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dynamic size
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096316F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: shared dynamic ptr
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096483F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: shared dynamic size
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.163000+120 I5096651F169       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dynamic section header
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5096822F164       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: offset in section
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5096988F153       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: opcode
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5097143F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: agg_mode
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5097300F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: section1
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.179000+120 I5097457F168       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: End of dumped section
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.241000+120 I5097627F438       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
    MESSAGE : Context info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for
              additional data.
    2008-05-29-16.33.59.273000+120 I5098067F452       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Private workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.33.59.288000+120 I5098521F451       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Shared workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.33.59.304000+120 I5098974F450       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
    MESSAGE : Package Cache info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000
              for additional data.
    2008-05-29-16.33.59.335000+120 I5099426F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** DRDA ASCB ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5099594F171       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** DRDA CMNMGR CB ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5099767F171       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** RECEIVE BUFFER ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5099940F169       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** SEND BUFFERS ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5100111F174       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** CONNECTION HANDLE ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.335000+120 I5100287F172       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** DRDA ATTRIBUTES ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.351000+120 I5100461F171       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: **** AS UCINTERFACE ****
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.351000+120 I5100634F468       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error detected"
              DIA8501C A buffer pool logic error has occurred.
    2008-05-29-16.33.59.351000+120 I5101104F331       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    2008-05-29-16.33.59.820000+120 I5101437F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.820000+120 I5101595F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5101753F400       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_AGENT_CB Pointer:
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA4AB0 : 0001 E637 0000 0000                        ...7....
    2008-05-29-16.33.59.835000+120 I5102155F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5102317F398       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_TRAN_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA4AA0 : 8087 FD0F 0000 0000                        ........
    2008-05-29-16.33.59.835000+120 I5102717F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5102878F397       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_APP_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA4AA8 : 0083 FD0F 0000 0000                        ........
    2008-05-29-16.33.59.835000+120 I5103277F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.835000+120 I5103437F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN PERM CURSORS: >>
    2008-05-29-16.33.59.851000+120 I5103787F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN PERM CURSORS: <<
    2008-05-29-16.33.59.851000+120 I5104134F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN TEMP CURSORS: >>
    2008-05-29-16.33.59.851000+120 I5104484F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN TEMP CURSORS: <<
    2008-05-29-16.33.59.851000+120 I5104831F346       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS:  >>
    2008-05-29-16.33.59.851000+120 I5105179F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
    2008-05-29-16.33.59.851000+120 I5105545F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.851000+120 I5105702F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
    2008-05-29-16.33.59.851000+120 I5106068F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5106225F342       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS: <<
    2008-05-29-16.33.59.866000+120 I5106569F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLI_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5106725F167       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5106894F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5107054F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.866000+120 I5107215F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.929000+120 I5107373F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.929000+120 I5107530F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.945000+120 I5107688F168       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.945000+120 I5107858F373       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : locklist
    DATA #1 : String, 59 bytes
    Check
    t1srv5bw\db2dumpBW2\l57042.000 for additional data.
    2008-05-29-16.33.59.960000+120 I5108233F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108394F152       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLCA
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108548F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108708F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.976000+120 I5108872F412       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
    DATA #1 : Hexdump, 2 bytes
    0x00000000056ABEA8 : 0800                                       ..
    2008-05-29-16.33.59.976000+120 I5109286F425       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
    DATA #1 : Hexdump, 8 bytes
    0x00000000056ABECA : 4E55 4C4C 4944 2020                        NULLID 
    2008-05-29-16.33.59.976000+120 I5109713F491       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->rdbname =
    DATA #1 : Hexdump, 18 bytes
    0x00000000056ABEB8 : 4257 3220 2020 2020 2020 2020 2020 2020    BW2            
    0x00000000056ABEC8 : 2020                                        
    2008-05-29-16.33.59.976000+120 I5110206F491       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgname =
    DATA #1 : Hexdump, 18 bytes
    0x00000000056ABEDC : 5351 4C43 3245 3037 2020 2020 2020 2020    SQLC2E07       
    0x00000000056ABEEC : 2020                                        
    2008-05-29-16.33.59.976000+120 I5110699F416       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgcnstkn =
    DATA #1 : Hexdump, 8 bytes
    0x00000000056ABEEE : 4141 4141 4163 4555                        AAAAAcEU
    2008-05-29-16.33.59.991000+120 I5111117F406       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgsn =
    DATA #1 : Hexdump, 2 bytes
    0x00000000056ABEF6 : CB00                                       ..
    2008-05-29-16.33.59.991000+120 I5111525F496       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pStatementText =
    DATA #1 : Hexdump, 29 bytes
    0x00000000062D0CC0 : 6472 6F70 2074 6162 6C65 2073 6170 6277    drop table sapbw
    0x00000000062D0CD0 : 322E 5253 4241 5443 4844 4154 41           2.RSBATCHDATA
    2008-05-29-16.33.59.991000+120 I5112023F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS APPL CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112183F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS NESTED APPL CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112350F166       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS SP REGISTERS CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112518F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS TRAN CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.33.59.991000+120 I5112678F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS NESTED TRAN CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5112845F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS COORD CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113006F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS NESTED CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113168F164       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS INVOCATION CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113334F165       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS ACTIVE STMT CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113501F164       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: NLSWA:DatabaseApp
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.007000+120 I5113667F153       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: nlsacb
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.023000+120 I5113822F157       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: dbNLSAppCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.023000+120 I5113981F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: UnicodeNLSAppCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.023000+120 I5114145F464       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
    MESSAGE : Error -2045771763 when reading LSN 000006BDB601F7A1 from log file
              S0000000.LOG tellMe 0 dpsAcbFlags 0 setSkipOutputBuf 0
    2008-05-29-16.34.00.023000+120 I5114611F468       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
    MESSAGE : NOTE: The log state was marked bad by another process, this message
              is not an indication of an error with the logger process
    2008-05-29-16.34.00.523000+120 I5115081F457       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpgrlg, probe:10
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.538000+120 I5115540F459       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlptudo, probe:1010
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.538000+120 I5116001F455       LEVEL: Warning
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlptudo, probe:4350
    MESSAGE : LSN being undone:
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA87A8 : 0000 06BD B601 F7A1                        ........
    2008-05-29-16.34.00.538000+120 I5116458F157       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_TENTRY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5116617F166       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5116785F155       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5116942F154       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.554000+120 I5117098F390       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlptud1, probe:1880
    MESSAGE : Due to error during UNDO, database will be brought down.
    2008-05-29-16.34.00.570000+120 I5117490F459       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, data protection, sqlpxrbk, probe:3040
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.570000+120 I5117951F155       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.570000+120 I5118108F154       LEVEL: Error
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.00.570000+120 I5118264F384       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : cr_error:
    DATA #1 : Hexdump, 4 bytes
    0x00000000056AF4C8 : 0100 0000                                  ....
    2008-05-29-16.34.00.570000+120 I5118650F465       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrrbck_dps, probe:20
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.00.585000+120 I5119117F692       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -902   sqlerrml: 1
    sqlerrmc: 2
    sqlerrp : SQLRL281
    sqlerrd : (1) 0x87020002      (2) 0x00000002      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.00.585000+120 I5119811F418       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, global services, sqlzerdm, probe:40
    DATA #1 : Hexdump, 4 bytes
    0x0000000005AA8B08 : 0D00 1086                                  ....
    2008-05-29-16.34.01.070000+120 I5120231F461       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrrbck, probe:40
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.01.070000+120 I5120694F474       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:88
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
              DIA8414C Logging can not continue due to an error.
    2008-05-29-16.34.01.070000+120 I5121170F435       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:190
    DATA #1 : Hexdump, 4 bytes
    0x0000000005AA8F6C : 0200 0287                                  ....
    2008-05-29-16.34.01.070000+120 I5121607F383       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : UCstate:
    DATA #1 : Hexdump, 4 bytes
    0x00000000056AFA70 : 4200 0004                                  B...
    2008-05-29-16.34.01.070000+120 I5121992F692       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -984   sqlerrml: 1
    sqlerrmc: 2
    sqlerrp : sqlrrbkd
    sqlerrd : (1) 0x8610000D      (2) 0xFFFFFC2C      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.01.070000+120 I5122686F508       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10
    MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected.  The
              diagnostic data returned is (SRVDGN): "SQLERRP:sqlrrbkd
              SQLCODE:-984".
    2008-05-29-16.34.01.085000+120 I5123196F691       LEVEL: Error
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -984   sqlerrml: 1
    sqlerrmc: 2
    sqlerrp : sqlrrbkd
    sqlerrd : (1) 0x8610000D      (2) 0xFFFFFC2C      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.01.085000+120 I5123889F375       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
    RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
    2008-05-29-16.34.01.085000+120 I5124266F692       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1034   sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLRR09E
    sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
               (4) 0x00000000      (5) 0xFFFFFFE2      (6) 0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)   
               (7)      (8)      (9)      (10)        (11)    
    sqlstate:     
    2008-05-29-16.34.01.085000+120 I5124960F152       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLCA
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.085000+120 I5125114F385       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : CREATOR
    DATA #1 : Hexdump, 8 bytes
    0x0000000037E6D1AE : 4E55 4C4C 4944 2020                        NULLID 
    2008-05-29-16.34.01.085000+120 I5125501F385       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : PACKAGE
    DATA #1 : Hexdump, 8 bytes
    0x0000000037E6D1CC : 5351 4C43 3245 3037                        SQLC2E07
    2008-05-29-16.34.01.101000+120 I5125888F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: CREATOR
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126044F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: PACKAGE
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126200F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: REQUEST TYPE
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126361F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: APM COMMON INFO
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.101000+120 I5126525F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: CONTEXT MCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.116000+120 I5126685F161       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: CONTEXT MEM CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.116000+120 I5126848F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: PACKAGE ENTRY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.116000+120 I5127010F438       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlC_dump, probe:25
    MESSAGE : Context info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for
              additional data.
    2008-05-29-16.34.01.116000+120 I5127450F452       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Private workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.34.01.116000+120 I5127904F451       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_sqlW_raw_dump, probe:25
    MESSAGE : Shared workspace info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000 for additional data.
    2008-05-29-16.34.01.132000+120 I5128357F450       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, access plan manager, sqlra_cache_full_dump, probe:25
    MESSAGE : Package Cache info dumped! Check
    t1srv5bw\db2dumpBW2\a71646016.000
              for additional data.
    2008-05-29-16.34.01.132000+120 I5128809F376       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"
    2008-05-29-16.34.01.132000+120 I5129187F331       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:902
    2008-05-29-16.34.01.601000+120 I5129520F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.601000+120 I5129678F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.601000+120 I5129836F400       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_AGENT_CB Pointer:
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA8970 : 0001 E637 0000 0000                        ...7....
    2008-05-29-16.34.01.601000+120 I5130238F160       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_AGENT_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.616000+120 I5130400F398       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_TRAN_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA8960 : 8087 FD0F 0000 0000                        ........
    2008-05-29-16.34.01.616000+120 I5130800F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.616000+120 I5130961F397       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_APP_CB Pointer
    DATA #1 : Hexdump, 8 bytes
    0x0000000005AA8968 : 0083 FD0F 0000 0000                        ........
    2008-05-29-16.34.01.616000+120 I5131360F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.616000+120 I5131520F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN PERM CURSORS: >>
    2008-05-29-16.34.01.616000+120 I5131870F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN PERM CURSORS: <<
    2008-05-29-16.34.01.632000+120 I5132217F348       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 21 bytes
    OPEN TEMP CURSORS: >>
    2008-05-29-16.34.01.632000+120 I5132567F345       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 22 bytes
    OPEN TEMP CURSORS: <<
    2008-05-29-16.34.01.632000+120 I5132914F346       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : >> Begin CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS:  >>
    2008-05-29-16.34.01.632000+120 I5133262F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=33, indexid(IID)=0, class=0
    2008-05-29-16.34.01.632000+120 I5133628F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.632000+120 I5133785F364       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : SQLD_CCB:
    DATA #1 : String, 49 bytes
    pool(TID)=0, obj(FID)=23, indexid(IID)=0, class=0
    2008-05-29-16.34.01.632000+120 I5134151F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLD_CCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5134308F342       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : << End CURSOR dump:
    DATA #1 : String, 19 bytes
    CLOSED CURSORS: <<
    2008-05-29-16.34.01.648000+120 I5134652F154       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLI_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5134808F167       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_AGENT_PRIVATECB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5134977F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_APP_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5135137F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLE_TRAN_CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.648000+120 I5135298F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_LFPB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.710000+120 I5135456F155       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_ACB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.710000+120 I5135613F156       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_DBCB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.710000+120 I5135771F168       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLP_TRAN_ENTRY_ARRAY
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.726000+120 I5135941F373       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : locklist
    DATA #1 : String, 59 bytes
    Check
    t1srv5bw\db2dumpBW2\l79922.000 for additional data.
    2008-05-29-16.34.01.741000+120 I5136316F159       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS AGENT CB
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.741000+120 I5136477F152       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: SQLCA
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.757000+120 I5136631F158       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.757000+120 I5136791F162       LEVEL: Severe
    PID:7164 TID:6016 NODE:000 Title: RDS UCINTFC PID
    Dump File:
    t1srv5bw\db2dumpBW2\71646016.000
    2008-05-29-16.34.01.757000+120 I5136955F412       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->rdbcolidLen =
    DATA #1 : Hexdump, 2 bytes
    0x00000000056ABEA8 : 0800                                       ..
    2008-05-29-16.34.01.757000+120 I5137369F425       LEVEL: Severe
    PID     : 7164                 TID  : 6016        PROC : db2syscs.exe
    INSTANCE: DB2BW2               NODE : 000         DB   : BW2
    APPHDL  : 0-11                 APPID: *LOCAL.DB2BW2.080529143349
    MESSAGE : RDS UCINTFC: pCurrentPID->pkgnamcsn.rdbcolid =
    DATA #1 : Hexdump, 8 bytes
    0x00000000056ABECA : 4E55 4C4C 4944 2020                        NULLID 

    I can't use db2drop because this command crash my db with this table.
    So I must take another way.
    ============================================================
    About DB2 Administration Tools Environment
    ============================================================
    DB2 administration tools level:
    Product identifier           SQL08025
    Level identifier             03060106
    Level                        DB2 v8.1.12.99
    Build level                  s060429
    PTF                          WR21370
    ============================================================
    Java development kit (JDK):
    Level                        IBM Corporation 1.4.2
    ============================================================

  • Semaphore 50 Error in SAP MMC on Windows 2003???

    Hi All
    I am having a bit of a nightmare this morning where as I have an App Server that won't start!
    Every time I start it up I get a SEM 50 for ALL of the processes (Dialog, Background UPdate etc.)
    I am not sure how to fix this, but in the mean time I have attached the developer trace for one of the errors, any help would be great!!
    trc file: "dev_w0", trc level: 1, release: "700"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ
    B
    B Tue Jan 22 12:00:06 2008
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\PRD\D00\exe\dbmssslib.dll' ...
    B  Library 'C:\usr\sap\PRD\D00\exe\dbmssslib.dll' loaded
    B  Version of 'C:\usr\sap\PRD\D00\exe\dbmssslib.dll' is "700.08", patchlevel (0.87)
    B  New connection 0 created
    M sysno      00
    M sid        PRD
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    102
    M intno      20050900
    M make:      multithreaded, ASCII, optimized
    M pid        1504
    M
    M  kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
    M  length of sys_adm_ext is 360 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 1504) [dpxxdisp.c   1301]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          18080     (904)
    M  DpShMCreate: sizeof(tm_adm)          35889936     (17936)
    M  DpShMCreate: sizeof(wp_ca_adm)          90000     (60)
    M  DpShMCreate: sizeof(appc_ca_adm)     90000     (60)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=2000/8/2112040/2112048
    M  DpShMCreate: sizeof(comm_adm)          2112048     (1048)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)          0     (96)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1280)
    M  DpShMCreate: sizeof(wall_adm)          (224040/329544/56/100)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 06D60040, size: 38760504)
    M  DpShMCreate: allocated sys_adm at 06D60040
    M  DpShMCreate: allocated wp_adm at 06D61A28
    M  DpShMCreate: allocated tm_adm_list at 06D660C8
    M  DpShMCreate: allocated tm_adm at 06D660F8
    M  DpShMCreate: allocated wp_ca_adm at 08FA0408
    M  DpShMCreate: allocated appc_ca_adm at 08FB6398
    M  DpShMCreate: allocated comm_adm at 08FCC328
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 091CFD58
    M  DpShMCreate: allocated gw_adm at 091CFD98
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 091CFDC8
    M  DpShMCreate: allocated wall_adm at 091CFDD0
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation view
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M
    M Tue Jan 22 12:00:07 2008
    M  ThInit: running on host sapapp10
    M
    M Tue Jan 22 12:00:08 2008
    M  calling db_connect ...
    C  Parameter format dbs/oledb/packet_size is deprecated in release 6.20.  Please use format dbs/mss/<parameter>.  See note 28667.
    C  Parameter format dbs/oledb/pn_cache_size is deprecated in release 6.20.  Please use format dbs/mss/<parameter>.  See note 28667.
    C  Parameter format dbs/oledb/stats_on is deprecated in release 6.20.  Please use format dbs/mss/<parameter>.  See note 28667.
    C  Thread ID:1500
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'C:\usr\sap\PRD\D00\exe\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      87
    C    patchcomment MSSQL: UTAB/ATAB/Dynp-access via clientside cursor (1002914)
    C  Network connection used from SAPAPP10 to sapprdr3 using tcp:sapprdr3
    C  CopyLocalParameters: dbuser is 'dbo'
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: MARS property was not set.
    C  Provider Release:08.10.3959
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  Cache sizes: header 52 bytes, 32000 names (42752000 bytes), 500 dynamic statements (2724000 bytes), total 45476052 bytes
    C  Using shared procedure name cache SAPPRDR3_PRD_PRD_MEM initialized by another process.
    C  Connected to db server : [sapprdr3] server_used : [tcp:sapprdr3], dbname: PRD, dbuser: dbo
    C  pn_id:SAPPRDR3_PRD_PRD
    C  Not using MARS (on sql 8.0)
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost
    B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20080122 120008 SAPPRDR3
    C  The IRow interface is supported by this OLEDB provider
    M  db_connect o.k.
    M  ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif
    I
    I Tue Jan 22 12:00:17 2008
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF               (addr: 13710040, size: 36342000)
    M  SHM_ROLL_AREA          (addr: 91730040, size: 268435456)
    M  SHM_PAGING_AREA          (addr: 159C0040, size: 134217728)
    M  SHM_ROLL_ADM               (addr: 1D9D0040, size: 2678942)
    M  SHM_PAGING_ADM          (addr: 1DC60040, size: 525344)
    M  ThCreateNoBuffer          allocated 324144 bytes for 1000 entries at 1DCF0040
    M  ThCreateNoBuffer          index size: 3000 elems
    M  ThCreateVBAdm          allocated 7424 bytes (50 server) at 1DD40040
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation view
    X  ES initialized.
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 20, CON_ID = -1
    B  dbtbxbuf: Buffer TABL  (addr: 238700C8, size: 190000000, end: 2EDA2C48)
    B  dbtbxbuf: Buffer TABLP (addr: 2EDB00C8, size: 46080000, end: 319A20C8)
    B  dbexpbuf: Buffer EIBUF (addr: 319C00D0, size: 30720000, end: 3370C0D0)
    B  dbexpbuf: Buffer ESM   (addr: 337100D0, size: 4194304, end: 33B100D0)
    B  dbexpbuf: Buffer CUA   (addr: 33B200D0, size: 7680000, end: 342730D0)
    B  dbexpbuf: Buffer OTR   (addr: 342800D0, size: 4194304, end: 346800D0)
    N  SncInit(): Initializing Secure Network Communication (SNC)
    N        PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/32/32)
    N  SncInit():   found snc/data_protection/max=1, using 1 (Authentication Level)
    N  SncInit():   found snc/data_protection/min=1, using 1 (Authentication Level)
    N  SncInit():   found snc/data_protection/use=1, using 1 (Authentication Level)
    N  SncInit(): found  snc/gssapi_lib=c:\usr\sap\prd\d00\exe\gssapi32.dll
    N    File "c:\usr\sap\prd\d00\exe\gssapi32.dll" dynamically loaded as GSS-API v2 library.
    N    The internal Adapter for the loaded GSS-API mechanism identifies as:
    N    Internal SNC-Adapter (Rev 1.0) to SAP's GSS-API v2 over NTLM(SSPI) Adapter
    N  SncInit():   found snc/identity/as=p:GROUP001\prdadm
    N  SncInit(): Accepting  Credentials available, lifetime=Indefinite
    N  SncInit(): Initiating Credentials available, lifetime=Indefinite
    M  ***LOG R1Q=> 1& [thxxsnc.c    259]
    M  SNC (Secure Network Communication) enabled
    M  CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 109BC280
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  2 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 500
    S  hostspool list size = 5000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 3C640098
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 3C640530
    S    using messages for server info
    S  size of spec char cache entry: 165020 bytes (timeout 100 sec)
    S  size of open spool request entry: 1160 bytes
    S  immediate print option for implicitely closed spool requests is disabled
    A
    A  -PXA--
    A  PXA INITIALIZATION
    A  System page size: 4kb, total admin_size: 16772kb, dir_size: 16692kb.
    A  Attached to PXA (address A1760040, size 500000K)
    A
    A Tue Jan 22 12:00:18 2008
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--
    A
    A  ABAP ShmAdm initialized (addr=59F86000 leng=20955136 end=5B382000)
    A  >> Shm MMADM area (addr=5A2EE240 leng=134720 end=5A30F080)
    A  >> Shm MMDAT area (addr=5A310000 leng=17244160 end=5B382000)
    A  RFC Destination> destination sapapp10_PRD_00 host sapapp10 system PRD systnr 0 (sapapp10_PRD_00)
    B  table logging switched off for all clients
    A  RFC Options> H=sapapp10,S=00,d=1,
    A  RFC FRFC> fallback activ but this is not a central instance.
    A
    A  RFC rfc/signon_error_log = 1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 1
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    M  ThrCreateShObjects          allocated 20856 bytes at 3C820040

    Hi Mushy;
    500 Internal Server Error
    Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.First try to run autoconfig and retest issue. If you have still same error check log file for more details
    Also check:
    500 Internal Server Error Servlet error:
    500 Internal Server Error  Servlet error:
    R12 Startup Issue
    Regard
    Helios

  • Error installing Oracle 92021 on Windows 2003 Std 64x

    Bit of an Oracle newb here, so someone set me strait...
    I need to install a test instance of Oracle 92x, and I want to install it on my Windows Server 2003 R2 x64 system (AMD Athlon 64 X2 4400+, 4GB RAM, if it matters).
    I downloaded the Windows 2003 x64 release of Oracle 9 (92021), but I can't even run the setup executable. I get:
    "The image file setup.exe is valid, but is for a machine type other than the current machine."
    .. as if the build was for a completely different processor architecture. I will be trying a x32 build next, but I understand x32 apps are very slow in WOW64.
    What am I missing?

    Ok, checked out Certify... the only certified release for my processor / OS is 10gR2... so be it. Still scratching my head that 92021 says it is for 2003 x64... oh well.
    My next question is, where do I find patches? I have looked all over downloads and no luck. Certify notes that I can get "patch sets" 10.2.0.2 and 10.2.0.3.
    Can someone direct me to those?
    Certify output below, patch info on the very bottom
    Certify - Additional Info Oracle Database - Standard Edition Version 10gR2 64-bit On Microsoft Windows 2003 (AMD64/EM64T)
    Operating System: Microsoft Windows 2003 (AMD64/EM64T) Version 2003 R2
    Oracle Database - Standard Edition Version 10gR2 64-bit
    N/A Version N/A
    Status: Certified
    Product Version Note:
    None available for this product.
    Certification Note:
    Existing patch sets:
    10.2.0.2
    10.2.0.3

  • Import Basis Support Package 7.00 error

    Hi All,
    I wanted to apply Basis support package 9 for release 7.00 for our solution manager 4.0 system.
    When i started, it gave an error in the phase ADDON_CONFLICT? stage.. The message is as below:
    Phase ADDON_CONFLICTS_?: Explanation of Errors
    Conflicts were found between the Support Packages that you want to
    import and the Add-Ons installed in the system. To guarantee the
    consistency of your system, the import is interrupted until all Conflict
    Resolution Transports (CRTs) for the listed Support Packages are
    included in the queue.
    To include the CRTs in the queue, proceed as follows:
    - Write down the Support Packages and Add-Ons that have conflicts.
    - Leave this screen by choosing 'Cancel' (F12).
    - Load the CRTs for the Support Packages with conflicts from the SAP
      Service Marketplace or request them from your Add-On supplier.
    - Define the extended queue again in the Support Package Manager.
    - Import the queue. The Support Package Manager executes all steps from
      the beginning.
    If the problem involves an SAP Add-On, see SAP Note 53902, which tells
    you which CRTs resolve the conflicts. Otherwise contact the supplier of
    your Add-On for details on how to proceed.
    The following contains a table of Support Packages for each Add-On for
    which conflicts were detected. The column 'Information on the Conflict
    Resolution' specifies how you can resolve a conflict. For more
    information, select the corresponding 'Information for the Conflict
    Resolution'.
    Conflicts Between Add-On ST 400 and Support Packages
    Software Component   Release      Support Package        Information on
                                                             Conflict Resolution
    SAP_BASIS            700          SAPKB70009             Include CRT
    Can anyone guide me how to proceed.
    Thanks,
    Sailesh K

    Hi Shailesh,
    You are employing one or more Add-Ons in your system, apply patches regularly and want to know how the consistency of your Add-Ons is guaranteed. The list of Add-Ons installed in your system is stored in table AVERS.
    During patch application the SAP Patch Manager (SPAM) checks for conflicts between patches in the queue and the installed Add-Ons. A conflict occurs if an object delivered in a patch is also delivered in an Add-On. If conflicts are detected, SPAM stops processing at step ADDON_CONFLICTS_? and asks the user to load the corresponding CRTs into his system. The attributes of such CRTs match the Add-On id, Add-On release and patch predecessor (i.e. the patch in conflict).
    The patch application can only resume if all CRTs are selected in the patch queue. To resolve a conflict SPAM does not check if the conflicting object is contained in a CRT. It suffices that the corresponding CRT has been selected in the patch queue. All conflicts raised by its patch predecessor(s) are then resolved in one go.
    CRTs were introduced to protect the consistency of Add-Ons during the application of patches, such as Hot Packages and Legal Change Patches (LCP). There are two types of CRTs:
    1. Conflict Resolution Transports (CRT)
    A CRT resolves conflicts between one patch and one version of an Add-On including all previous versions. Example:
    Consider a system where Add-On IS-X is installed. During the application of patches P1 and P2 SPAM detected conflicts between the patches and the Add-On.
    To resolve these conflicts two separate CRTs are required, CRT1 and CRT2. A consistent patch queue looks like this:
        P1
        CRT1
        P2
        CRT2
    SPAM will only let you resume the patch application if you redefine the patch queue containing all four patches. You can see the name of the patch for which a CRT resolves a conflict in the "Predecessor" field in the patch queue dialog.
    2. Collective Conflict Resolution Transports (CCRT) are similar to CRTs but resolve conflicts between several patches and an Add-On. Example:
    Consider the previous example but this time the conflicts between patches P1, P2 and Add-On IS-X are resolved not by two CRTs but by one Collective CRT (CCRT) CCRT1. A consistent patch queue looks like this:
    P1
    P2
    CCRT1
    SPAM will only let you resume the patch application if you redefine the patch queue containing all three patches. The CCRT is added at the end of its highest predecessor, here P2. You can see the highest predecessor for a CCRT in field "Valid to patch#" when you scroll the patch queue dialog to the right.
    Keep in mind that a CCRT describes a range of patches for which conflicts are resolved, with the lower limit being the predecessor and higher limit the highest predecessor.
    Cheers,
    Shyam

  • DDIC_ACTIVATION ERROR WHILW APPLYING SUPPORT PACKAGES

    Hi all,
    While applying support package(KB62019),i got error(DDIC_Activation)..
    How to resolve it?
    Thanks in advance.

    Hi,
    Which support package are you applying ? Have a look at these notes: 782140 and 447925.
    Search for SAPKB62019 in this note and you will get a solution to that. The note refers to some more notes. Please follow the instuctions in the note carefully.
    Cheers,
    Sunil
    PS: Reward points for helpful answers.

  • Support Package Manger for EBP/CRM cannot confirm SP ???, 'Package unknown'

    I am installing CRM 5.0 SR1 (Windows 32bit/Oracle/NW04s).
    I have imported SAP_BASIS SP07 and SP08:
    'Queue SAPKB70007 - SAPKB70008 imported successfully according to Standard scen.: Confirm this',
    but I cannot confirm (Support Package - Confirm is grayed out). If I start Support Package Manager for EBP/CRM SPAM, I get a window: 'Package is unknown'; after continuing I get an exception 'PATCH_NOT_SPECIFIED'. The status window in SPAM shows:
    Software Component: ???
    SPAM Status:        yellow triangle
    Next Action:        Confirm
    Please help.

    I ran into this issue. Upgraded spam from 38 to 42. When I go to env-EBp/CRM, the SPAM Package is unknown error came up
    Resolution: go to support package -> import spam/saint update again. It tokk care of the issue. Contuniuing with upgrade.

Maybe you are looking for