SAP Web Blog

Upgrade Doc

2008-09-03T11:06:00.000-07:00

SAP Solution Manager

2008-08-24T22:35:00.000-07:00

What Is The Use of Solution Manager
What is the use of solution manager, and what we can do with solution manager?

Now a days solution manager is mandatory.
1. it is used for generating keys and downloading support packages
2. it is used to document user requirments and preparing senarios what needs to to be adopted using solution manager, where the blue print is the part of solution manager
3. it is used for reporting, solution desk,to manage the change requests and use to monitor entire landcape Central message processing in the SAP Solution Manager:
- Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA)
- Assign processor
- Send messages to the creator and other processors
- Forward message to other processors or support units
- Create documents and URLs
- Attach documents
- Status assignment and monitoring
- Create a worklist with selection conditions *-- Shankar

I have a requirement to install SAP Solution Manager Solution Support Enablement Package (SEP) in our solution manager 4.0. This SEP contains, RBE, TDMS, ...etc.,

I checked for the software download at market place but couldn't find the software package, can anyone help me to download this SEP for windows/oracle.

Look at following:

http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> Installations and Upgrades -> SAP Technology Components -> SAP Support Enablement Package - >SAP Support Enabl. Package 1.0

How to configure the service desk on Solution Manger 4.0. I want to cofigure Solution Manger only for service desk I have install Solution Manger 4.0. What is the Step please explain.

Check: http://service.sap.com/rkt-solman

There are tutors, PDFs and powerpoints to guide you through the configuration process. *-- Markus

If you have 3 or 4 client systems, must you install SAP solution manager for each one of these systems and manage them independently -or- 2. Can you install One Solution manager, that will manage all 3 these systems in one solution manager -or- 3. Do you install 3 Solution managers for each of the systems, then another one linked to the 3 individual solution managers, which then in turn manages the 3 systems in one.

In any System landscape only one solution manager is installated in one system and it will communicate with the other system using the RFC and collect the report from each and every system through (SDCCN).

Step by Step Alert Configuration Doc Links in XI

2008-01-02T04:48:00.000-08:00

XI: Alerts - Step by step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2328

XI: Alerts - Troubleshooting guide
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2327

Alerts with variables from the messages payload (XI) - UPDATED
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1382

Simple Steps to Get Descriptive Alerts from BPM in XI
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4714

Docs for Unicode Conversion

2007-12-30T03:54:00.000-08:00

The SAP Unicode conversion Guides can be found at url http://service.sap.com/unicode@sap

----> Unicode Conversion Guides

Refer SAP OSS Note
# 548016 - Unicode Conversion (Master Note)
# 765475 - Unicode Conversion: Troubleshooting

Creating your first SAP Business Workflow by Ginger Gatling

2007-12-25T09:39:00.000-08:00

SAP Business Workflow has been around for a long time. It is a proven tool that is used by many of our customers. Normally new customers, or those who have not used workflow, want to see a demo on how it works. I still get lots of questions of how workflow works and how to get started.

Here is a demo on how to create your first workflow. It walks you through creating a workflow and linking the workflow to the ERP application. The result is a workflow starting whenever a material is created. The demo is 10 minutes and includes a voice explanation.

So, start by viewing the video. .

Then, if you want to build it on your own development or sandbox system, and you have never used workflow on your SAP system, do the following steps:

Go to transction code SWU3.
Select Perform Automatic Customizing. It is the red and white button normally called the 'generate' button.
Drill into Maintain Definition Environment. Select Maintain Prefix Numbers. Here you must enter a number range for workflow. When workflows get created, they are assigned WS and a unique number.
That's it, now you are ready to build your own workflow!! (Of course, in order to do this you also need security access and a development key may be required, so a sandbox is a good place to start!)

Happy workflowing!

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/7288

Phase List for the Upgrade to SAP ERP 2005 700

2007-12-13T00:57:00.000-08:00

PREPARE Modules:
Parameter input
Initialization
Import
Extension
Integration
Installation
General checks
Activation checks
Necessary checks for conversions
Optional checks for conversions
Modification support
Pre-processing

Upgrade Phase Groups:
Import and Modification Transfer
Shadow System Installation
Shadow System Operations: SPDD and Activation
Shadow Import
Downtime phases I: Switch tables and Kernel
Downtime phases II: Conversion, Main Import, XPRAs
Post Processing

Explanations

--------------------------------------------------------------------------------

PREPARE Modules
PREPARE Module: Parameter input (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
BEGIN_PRE < 10s Checks upgrade directory
KEY_CHK < 1% Prompts for keyword from SAP main upgrade note KEYCHK.LOG
Check for upgrade correction package and enter upgrade keyword
EXTRACTKRN_PRE < 10s Extracts kernel EXTRKRN.LOG
none
INITPUT_PRE dial Initializes R3up

DB2 UDB for z/OS and OS/390:
Tests JCL Submission
Enter parameters

DB2 UDB for z/OS and OS/390:
Test JCL Submission

DBCHK_PRE < 10s Determines database version and SAP release
CONFCHK_IMP < 10s Tests operating system and database version Upgrade operating system and database to the required version, if necessary
SOLMAN_CHK < 1% Prompts for keyword from solution manager SOLMANCHK.LOG
Enter keyword generated by solution manager
CHKSYSTYPE < 10s Determines if system is SAP or customer CHKSYSTYPE.LOG

TOOLVERSION_INI < 10s Determines and checks the tool version TOOLVERS.LOG
Upgrade tools if necessary
DBCONNCHK_INI < 10s Tests if new tools can connect to the database DBCONNCHK.LOG

J2EE_CHK < 10s As of start release 620:
Checks if J2EE is also running J2EECHK.LOG
info
REQ_J2EEUPG < 1% CBU: Requests j2ee prepare and upgrade
SETSYNC_PREP_STARTED dial events for sync with Jump
REQ_READNOTE < 1% CBU: Requests cbu specific parameters
INIT_CBU < 1% CBU: Requests cbu specific parameters
CHECKGROUP_END0 < 1% End of module
PREPARE Module: Initialization (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
INITCURENV < 10s Initializes internal administration information
DBCHK_INI < 10s Determines database version and SAP release
RFCCHK_INI < 10s Tests RFC connection RFCCHK_INI.LOG

VERSCHK_INI < 10s Checks SAP release Upgrade to a valid source release, if necessary
VALCHK_INI < 10s Tests target system: Is it a preliminary version? (Cannot upgrade the system) VALCHK.LOG

UNICODE_CHK_PRE < 10s Checks, if DB is UNICODE UNICPTCP.LOG
UNICHK.LOG

SETSYNC_INFO_FINISHED dial events for sync with Jump
UCMIG_DECISION < 10s For start release 46C to 46D:
Check for combined Upgrade and Unicode Conversion UCMIGDEC.LOG

CLNT_CHK_INI < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
CLNTOUT.LOG
Unlock clients for SAP system upgrade, if necessary
PATCH_CHK1 < 1% Finds unconfirmed Support Packages and displays the result PATCHOUT.LOG
EXECPT.LOG
Call transaction SPAM to confirm any unconfirmed Support Packages, if necessary
INTCHK_INI < 10s Checks whether the inactive nametab is empty
ADJ_CNTRANS 1% ( Resolves inconsistencies in TABART-TABSPACE mapping ADJCNTRANS.LOG
ADJCNTRANS.ELG

INIT_CNTRANS < 10s Initializes the container name translator SELTAIA.LOG
SELDBS.LOG
INICNT.LOG
Fix inconsistencies in TABART-TABSPACE mapping, if necessary. Additional informations are given in SAP Note 541542
CNTRANS_PRE < 10s Makes adjustments to scripts for MCOD systems CNTPRE.LOG

DMPSPC_INI < 10s Dumps database size DMPSPC_INI.LOG

CHK_DB6_REG_PRE dial DB2 UDB for UNIX and Windows:
Checks DB6 registry parameters
SPACECHK_INI < 10s Checks database free space DBFPREP.LOG
Extend the database, if necessary
KRNCHK_DEST < 10s For start release 30D to 31I:
Checks the SAP kernel version for the destination release KRNCHK.LOG
Import kernel for the destnation release, if necessary
DBPREP_CHK < 10s DB2 UDB for z/OS and OS/390:
Performs DB2/390-specific checks DB2 UDB for z/OS and OS/390:
Make preparations as described in SAP Note 400565
EXECCV < 10s As of start release 46C:
Reads cvers table EXECCV.LOG

EXECAV < 1% Finds add-ons EXECAV.LOG

COMPINFO_INI < 10s As of start release 46C:
Get the component information after the addon selection COMPINFOINI.LOG

ADDON_CHK dial Checks the current Add-on versions against the ranges in IS_RANGE.LST ADDONCHK.LOG

ADDON_INFO dial print add-on information ADDONINFO.LOG

ADDON_SPEC1 dial Requests add-on information ADDONSPEC1.LOG

ADDON_TREAS dial Special actions for treasury ADDONTREAS.LOG

ADDON_WFM dial As of start release 620:
Special actions for wfmretail ADDONWFM.LOG

ACE_CHK dial For start releases 620:
Special actions for CRM ACECHK.LOG

CRM_BILL dial For start release 610 to 620:
Requests note handling CRMBILL.LOG

PR_DBPAR dial ORACLE:
Checks Oracle parameters PRDBPAR.LOG

CHECKGROUP_END1 < 1% End of module
PREPARE Module: Import (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
REQIMPORT dial Displays question Confirm execution of Import module
READDATA 1% Reads data files from the upgrade CDs Mount each requested upgrade CD
READDATA_EXT < 1% Reads additional data files from the upgrade CDs Mount each requested upgrade CD
TOOLFIX_CHK < 1% Integrates the Upgrade Correction Package TOOLFIXCHK.LOG
Unpacks the fix archive again to patch files from READDATA_EXT.
CPYFIL0_CBU < 1% CBU: Copy files CBUCPY0.LOG

EXEC_CPYFIL1_CBU < 1% CBU: Copy cbu specific files CBUCPY1.LOG

FRP_CHK < 1% For start releases 640:
Unpacks the FRP to the kernel directory FRPCHECK.LOG

UNICODELIB_CHK1 < 10s Checks for missing UNICODE libs in kernel directory UCLIBCHK.LOG

CNV_CHK_IMP < 10s Finds outstanding conversions and restart logs of terminated conversions Make conversions (after discussion with SAP consultant), if necessary
ICNVCHK_IMP < 10s As of start release 40A:
Checks whether incremental conversion from previous upgrade has finished ICNVEX.LOG
ICNVLIST.LOG
ICNVCHK.LOG
Complete incremental conversion with transaction ICNV, if necessary
SCRIPT_CHK_TOOL3 < 10s For start releases up to 31I:
Avoids critical conversions in tool import CNVTST.LOG
CLCNVTAB.LOG
SCRIPTCHK.LOG

SCRIPT_CHK_TOOL4 < 10s As of start release 40A:
Avoids critical conversions in tool import CNVTST.LOG
CLCNVTAB.LOG
SCRIPTCHK.LOG

SCRIPT2_TST_RESTART < 10s Performs actions for restart handling UPGPARAM.LOG
REPTST.LOG
SCRTREST.LOG

TRBATCHK_IMP < 10s Checks whether table TRBAT is empty Perform any actions specified by R3up
CLNT_CHK_IMP < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
CLNTOUT.LOG
Unlock clients for SAP system upgrade, if necessary
INTCHK_IMP < 10s Checks whether the inactive nametab is empty
SPACECHK_IMP < 10s Checks database free space DBFPREP.LOG
Extend the database, if necessary
PATCH_CHK2 < 10s Finds unconfirmed Support Packages and displays the result PATCHOUT.LOG
EXECPT.LOG
Call transaction SPAM to confirm any unconfirmed Support Packages, if necessary
NTHISTCRE < 10s For start releases up to 40B:
Creates tables for nametab administration so that new tools have access NTABHIST.LOG

ALTER_TO < 1% Deletes tables that describe the delivery ALTER_TO.LOG

TOOLIMPD1 2% For start release 30D to 31I:
Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG

TOOLIMPD2 2% For start release 40A to 40B:
Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG

TOOLIMPD3 2% For start release 45A to 46D:
Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG

TOOLIMPD4 2% As of start release 610:
Prepares ABAP Dictionary for upgrade tools TOOLIMPD.ELG

MVNTAB_TOOL < 1% Activates nametabs for upgrade tools MVNTTOOL.ELG
MVNTTOOL.LOG

TOOLIMPI 1% Imports tools for the SAP system upgrade TOOLIMPI.ELG

TOOLIMPM < 1% Imports tools for the SAP system upgrade TOOLIMPM.ELG

TOOLIMP4_FIX < 1% For start releases up to 46D:
Imports tools for the SAP system upgrade TOOLFIX.ELG

TOOLIMP6_FIX < 1% As of start release 610:
Imports tools for the SAP system upgrade TOOLFIX.ELG

TOOLIMP4_UCMIG < 1% For start releases up to 46D:
Imports tools for the combined Upgrade and Unicode Conversion TOOLUCMIG.ELG

NPREPCRE0 3% Imports tables that describe the delivery from Upgrade CD1 PREPIMP.ELG

JOB_RSUVSAVE < 1% Saves old entries of table UVERS PSUVSAVE.ELG
PSUVSAVE.LOG

UVERS_PREIMP < 10s As of start release 46B:
Writes entry in table UVERS UVERSINI.LOG

UVERS_INIT < 10s As of start release 46B:
Writes entry in table UVERS UVERSINI.LOG

SQLDB_UVERS_INIT (var For start releases up to 46A:
Cleans tables for unicode conversion UVERSINS.LOG

UVERS_CHK_IMP < 10s Checks consistency of table UVERS UVERSCHK_IMP.LOG

BATCHCHK_IMP < 1% Tests whether the background server can access the upgrade directory BATCHCHK_IMP.LOG

UCMIG_STATUS_SET0 < 10s Set status for combined Upgrade and Unicode Conversion UCMIGSETSTAT0.LOG

JOB_RSCVINIT < 1% Initializes table CVERS PSCVINIT.ELG
PSCVINIT.LOG

RUN_RSPTBFIL_PREP < 1% Creates PUTTB and PUTTB_SHD tables RSPTBINI.ELG
RSPTBINI.LOG

READPUTTB_INI < 10s Reads table PUTTB and places it in the file system RDPUTTB.LOG

JOB_RDDGENRS < 1% Generates tool reports RDDGENRS.LOG

RUN_RDDITCUG < 1% For start release 30D to 31I:
Generates GUIs PDDITCUG.ELG
PDDITCUG.LOG

RUN_RSINCGEN_IMP < 1% Adapts ABAP include RSTABINC to the system PSINCGEN.ELG
PSINCGEN.LOG

TR_BUF2HEAP_INSTIMP < 10s Moves upgrade requests from the INSTIMP.BUF buffer to the R3up buffer TPSHBUF.LOG
TRB2H.LOG

TR_EXT2HEAP < 10s Moves additional upgrade requests to the R3up buffer TREXT2HEAP.LOG

TR_MODACT_IMP < 1% Calculates the amount of data from the upgrade requests TRMAIMP.LOG
TRMAIMP.ELG

SQLSCREXE_UPGPAR < 10s Makes parameter settings for the upgrade procedure PARAMSHD.LOG
UPGPAR.ELG
UPGPAR.LOG

SQLDB_PARAMCOMP < 10s Makes parameter settings for the component upgrade procedure PARAMCOMP.LOG

JOB_RDDPURI2 < 1% Does various cleanups PDDPURI2.ELG
PDDPURI2.LOG

CHECKGROUP_END2 < 1% End of module
PREPARE Module: Extension (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
RUN_RSTODIRM_CLEAN < 1% Check delivery catalog for inconsistencies RSTODIRM.ELG
RSTODIRM.LOG

MULTSPC_UC < 10s Adapts space requirements
ADDSPAREQ_0 < 10s Prepares space check on the database
EXECLANG < 1% Determines installed languages EXECLG.LOG

LANG_CHK < 10s Checks whether the new release supports the installed languages LANGOUT.LOG
Delay upgrade until next release, if necessary
LANG_SELECT 1% Copies data for the language import into the upgrade directory LANGSEL.LOG
LANGSEL.ELG

RUN_RSUPGSLI < 1% Configures the selective-language-import option RSUPGSLI.ELG
RSUPGSLI.LOG

SPAM_CHK_INI < 1% Checks SPAM version SPAMCHK.LOG

UPLOAD_REQUEST dial Prompts you to retrieve packages UPLOADREQ.LOG
Retrieve packages that are required, if necessary
JOB_CBUPIFCHK < 1% CBU: Checks PIF file CBUPIFCHK.ELG
CBUPIFCHK.LOG

NCVERS_READ < 10s Determines components contained in the delivery NCVERSOUT.LOG

COMPINFO_EXP < 10s Get the component information concerning export components COMPINFOEXP.LOG

IS_MV_CHK1 < 10s Checks version of IS_MOVES.LST file ISMVCHK1.LOG

NAVERS_READ < 10s Initializes NAVERS from delivered and customer addon components NAVERSOUT.LOG

IS_INIT < 10s Initialize for IS phases IS_INIT.LOG

IS_INST_BICONT < 10s For start releases up to 620:
Fake BI_CONT installation IS_INST_BICONT.LOG

IS_INST_LIST < 10s Fake addon Installations from list (if needed) IS_INST_LIST.LOG

IS_MOVEMENT < 10s Determine/decide Add-on movements IS_MOVEMENT.LOG

COMPINFO_ISMV < 10s Get the component information after the addon movements COMPINFOISMV.LOG

SFW_MOVEMENT < 10s SFW Addon Movements SFW_MOVEMENT.LOG

COMPINFO_SFWMV < 10s Get the component information after the sfw movements COMPINFOSFWMV.LOG

ADDONSPEC_OIL dial For start releases up to 640:
Special actions for IS_OIL ADDONSPEC_OIL.LOG

ADDONSPEC_ISPSCA dial For start releases up to 640:
Special actions for IS_PS-CA ADDONSPEC_ISPSCA.LOG

RUN_RSUPGSFW < 1% For start releases up to 640:
SFW only: Determines active BF(S) according to installed Addons RSUPGSFW.ELG
RSUPGSFW.LOG

IS_TABDMP < 1% Dump addon tables to file IS_DUMPTABLES1.LOG

IS_SELECT dial Decide about all Add-ons IS_SELECT.LOG
Decide what to do with the add-ons during the upgrade
COMPINFO_ADDON < 10s Get the component information after the addon selection COMPINFOADDON.LOG

ADDON_QCALC < 1% Calculates queue for selected add-ons ADDONQCALC.LOG
SPDA_ADDONQCALC.LOG
IS_MV_CHK2 < 10s Checks version of IS_MOVES.LST file ISMVCHK2.LOG

TR_EXPPKG2HEAP < 10s Moves export packages to the R3up buffer TREXPPKG2HEAP.LOG

PATCHK_EQUI < 10s Determines Support Package level for target release that corresponds to the level of the source release PATCHKEQUI.LOG

PATCH_CHK3 < 1% Find unconfirmed Support Packages and checks whether the source release contains Support Packages that are more recent than the version of the target release PATCHOUT.LOG
EXECPT.LOG
Call transaction SPAM to confirm any unconfirmed Support Packages
Call SAP Note 073510 to check whether you can upgrade the system or which Support Packages are equivalent to those in the target release.

EXEC_CPYFIL3_CBU < 1% CBU: Copys PIF files CBUCPY3.LOG

BIND_PATCH dial Includes Support Packages for the target release PATCHINT.LOG
SPDA_PATCHINT.LOG Include Support Packages in the upgrade, if necessary
COMPINFO_SPP < 10s Get the component information after the support package selection COMPINFOSPP.LOG

ADDON_LANGINC < 1% Include Add-on language packages ADDONLANGINC.LOG
SPDA_ADDONLANGINC.LOG
TR_CMDIMPORT_FDTASKS < 10s Imports command files for full and delta tasks PCMDIMPFD.ELG
PCMDIMPFD.LOG

IS_MERGE < 10s Adds Supplement Tasks (without AOS) to the TRStorage IS_MERGE.LOG

TR_QUEUE2HEAP < 10s Moves the upgrade requests of the queue to the R3up buffer TRQUEUE2HEAP.LOG

TR_CMDIMPORT_PREPARE < 1% Imports piece lists for included Support Packages PCMDIMP.ELG
PCMDIMP.LOG

JOB_RDDIT020 < 1% Merges transports for add-ons in NAVERS PDDIT020.ELG
PDDIT020.LOG

IS_SYNC_20 < 1% Synchronizes NAVERS in file system ISSYNC20.LOG

CONFLICT_CHECK < 1% Checks for conflicts according to transaction SPAM CONFLCHK.LOG
SPDA_CONFLCHK.LOG
ADJUSTPRP dial Prepares adjustment calculation: Imports command file flagged in other system, if necessary ADJUSTPRP.ELG
Select command file, if necessary
INTEG_PATCH < 1% Selects the Support Package integration file and imports the requests contained in it INTGPTCH.LOG

UCMIG_REQINC < 10s Ask for customer request for preparation of Unicode Conversion UCMIGREQINC.LOG

ICNVXRQ < 1% Checks prerequisites for ICNV DDICNV.LOG
ICNVXRQ.ELG
ICNVXRQ.LOG

CHECKGROUP_END3 < 1% End of module
PREPARE Module: Integration (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
IS_MERGE_I < 10s For start release 30D to 31I:
Adds Supplement Tasks (without AOS) to the TRStorage IS_MERGE.LOG

TR_CMDIMPORT_PREPARE_31I < 1% For start release 30D to 31I:
Imports piece lists for included Support Packages PCMDIMP.ELG
PCMDIMP.LOG

RUN_RSTODIRM_BIND < 1% Preparation of the delivery directory RSTODIRM.ELG
RSTODIRM.LOG

TR_TODIR_MERGE_PATCH < 1% Merges included Support Packages with the delivery directory
JOB_RDDIT021 < 1% Merges add-ons in the delivery list PDDIT021.ELG
PDDIT021.LOG

UVERS_UP_T < 1% Changes the status in table UVERS
TR_MODACT_ADD < 1% Calculates the amount of data in add-on and language requests TRADIMP.LOG
TRADIMP.ELG

TR_MODACT_DISC < 1% Calculates the amount of data in additional Support Package requests TRDIIMP.LOG
TRDIIMP.ELG

TR_COLLTABS_PREP < 1% Totals data TRCOLLTA.LOG
TRCOLLTA.ELG

TABSPC_PREP 2-10 Calculates which tables are part of import into old tables TABSPCP.LOG
TABSPCP.ELG

ADDSPAREQ_N < 10s Prepares space check on the database
ADDSPAREQ_S < 10s Prepares space check on the database
ADDSPAREQ_T < 10s Prepares space check on the database
CHECKGROUP_END10 < 1% End of module
PREPARE Module: Installation (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
INITSHD dial Prompts for shadow parameters Enter shadow parameters
SHDINST_CRE < 10s Creates directory structure for the shadow instance SHDINST_CRE.LOG

SHDINST_CPY < 10s Copies the profiles SHDINST_CPY.LOG

SHDINST_ADAPT < 10s Adapts the profiles to the shadow instance SHDINST_ADAPT.LOG

SHDINST_MOD < 10s Adapts the system settings ALPSHDIN.LOG
ALPSHDDF.LOG

SHDINST_REQ < 10s Checks ports for shadow instance SHDINST_REQ.LOG
Perform actions from CHECKS.LOG, if necessary
SHDINST_OS < 10s Performs operating system-specific actions SHDINST_OS.LOG
Perform actions from CHECKS.LOG , if necessary
SHDINST_SDB_CHK < 10s Checks database-specific settings MaxDB: Adjust the database parameters MAXLOCKS and MAXUSERTASKS, if necessary
SHDINST_DB_PREP < 1% Checks database-specific settings SHDUSREX.LOG
SHDUSRCRE.LOG
SHDDBPRP.LOG
Perform actions from CHECKS.LOG, if necessary
SHDINST_SWT_HOST < 10s Adjusts the profile of the shadow instance, if necessary SHDINST_SWT.LOG

SHDINST_PFPAR < 10s Checks with sappfpar the shadow instance profile SHDINST_PFPAR.LOG
Perform actions from CHECKS.LOG, if necessary
RUN_RSUPGRFC < 1% Creates RFC connection SAP_UPGRADE_SHADOW_SYSTEM PSUPGRFC.ELG
PSUPGRFC.LOG

CHECKGROUP_END11 < 1% End of module
PREPARE Module: General checks (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
CONFCHK < 1% Tests operating system and database version Upgrade operating system and database to the required version, if necessary
DB_ACTION_RUN_PRE < 1% DB2 UDB for UNIX and Windows:
Remove volatile flags DBACTRUN.LOG

CHK_DB6_PAR_PRE dial DB2 UDB for UNIX and Windows:
Checks DB6 parameters
SPACECHK_GEN < 1% Checks database free space DBFPLUSD.LOG
Extend the database, if necessary
TOOLVERSION_EXE < 10s Determines and checks the tool version of the new kernel TOOLVRSEXE.LOG
Upgrade $(PUTPATH)/exe if necessary
UNICODELIB_CHK2 < 10s Checks for missing UNICODE libs in kernel directory UCLIBCHK.LOG

FREECHK < 1% Checks disk space for logs and SAP kernel

Checks whether the SAP kernel can be overwritten Increase disk space, if necessary

Check SAP kernel write authorization, if necessary
LC_CHECK < 1% Checks Livecache LCCHECK.LOG
Checks Livecache
PROFSET < 10s For start releases up to 46C:
Sets DDIC autorizations PROFSET.LOG

DB_ACTION_PRE < 1% ORACLE:
Performs database-specific actions SELDBSL.LOG
ALTDBS.LOG
DBACTPRE.LOG

DB_ACTION_EXTMAN < 1% ORACLE:
Determines extent management on database Oracle EXTMAN.LOG
DBACTEMA.LOG

REPACHK < 1% Finds SAP objects locked in repairs or requests REPACHK.LOG
Release repairs and requests, if necessary
CNV_CHK_GEN < 1% Finds outstanding conversions and restart logs of terminated conversions Make conversions (after discussion with SAP consultant), if necessary
TRBATCHK_GEN < 1% Checks whether table TRBAT is empty Perform any actions specified by R3up
CLNT_CHK_GEN < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
CLNTOUT.LOG
Unlock clients for SAP system upgrade, if necessary
SCRIPT_TST_DDART < 1% Checks entries in table TA and IA CUSTTA.LOG
SCRPTDDA.LOG
If errors occur, see SAP Note 500252
JOB_RSAUCHK_DUP < 1% Checks for double F rules RSAUCHKD.ELG
RSAUCHKD.LOG
See SAP Note 431886
JOB_RSAODSACTIVATE_PRE < 1% Performs TADIR cleaning PSATADIR.ELG
PSATADIR.LOG

JOB_RSTLIBG < 1% Checks TADIR objects RSTLIBG.ELG
RSTLIBG.LOG

JOB_STRU_TADIR_GEN_1 < 1% Performs TADIR insert PSTRUGEN.ELG
PSTRUGEN.LOG

JOB_SDLINIT_TABLES_70 < 1% Performs SDLINIT preparations PSDLINIT.ELG
PSDLINIT.LOG

JOB_RSUPGRCHECK_PRE < 1% Checks consistency of generated repository PSUPGCHK.ELG
PSUPGCHK.LOG

JOB_RSMD_UPGR_PRE < 1% Performs component-specific checks PSMDCHK.ELG
PSMDCHK.LOG

JOB_RSODSO_GUID_CHK < 1% As of start release 610:
Performs component-specific checks PSODCHK.ELG
PSODCHK.LOG

JOB_CRM_UPGRADE50 < 1% For start release 610 to 620:
Removes duplicate table entries CRM_UPGRADE50.ELG
CRM_UPGRADE50.LOG

JOB_SDLINIT_TABLES_PRE < 1% As of start release 620:
Performs BW specific checks RSSM_SDLINIT.ELG
RSSM_SDLINIT.LOG

JOB_CHECK_RSMONICDP_PRE < 1% As of start release 610:
Performs BW specific checks RSSM_RSMONICDP.ELG
RSSM_RSMONICDP.LOG

JOB_DROP_TMPOBJ_PRE < 1% Deletes invalid nametab entries RSDR_NAMT_CL.ELG
RSDR_NAMT_CL.LOG

JOB_TS_UPG41 < 1% For start releases up to 620:
Performs index check TSUPG41.ELG
TSUPG41.LOG

NTACT_CHK 2% Checks the consistency of the nametab entries NTCHK.ELG
NTCHK.LOG
Perform any actions specified by R3up
INTCHK_GEN < 1% Checks whether the inactive nametab is empty
SINXCHK < 1% Checks the consistency of the indexes in the substitution tables SINXCHK.LOG
Delete indexes, if necessary
VIEWCHK < 1% Checks for conflicts between customer tables in the SAP name range and delivered views VIEWCHK.LOG
Delete tables, if necessary
ENVCHK_PRE < 10s Checks whether profiles of user adm can be modified Assign write authorization to the user profiles, if necessary
FRONTREQ_PRE < 10s Displays information about the upgrade of the front end software Upgrade the front end software, if necessary
UVERS_CHK_GEN < 10s Checks consistency of table UVERS UVERSCHK_GEN.LOG

BATCHCHK_GEN < 1% Tests whether background server can access the upgrade directory BATCHCHK_GEN.LOG

PROFCHK < 10s Checks whether the profile names specified in phase INITPUT correspond with the names used by the SAP system PROFCHK.LOG
Correct entries with R3up set stdpar, if necessary
JOB_RXPRECHK_PRE < 1% For start release 30D to 31I:
Performs preliminary checks for the XPRA RLXPRA40 PXPRECHK.ELG
PXPRECHK.LOG

JOB_RSVBCHCK_PRE < 1% Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
PSVBCHCK.LOG
Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
RUN_RSCHECKEXC < 1% For start release 610 to 6ZZ:
Find tables in exchange table space that are not exchanged ( SAP Note 674070) RSCHECKEXC.ELG
RSCHECKEXC.LOG

SCRIPT_TST_TCPDB < 1% Checks code page settings TCPDB.LOG
SCRTCPDB.LOG
See SAP Note 015023, if necessary
SCRIPT_TST_TCPDB_UC < 1% Checks code page settings TCPDB.LOG
SCRTCPDB.LOG
See SAP Note 015023, if necessary
REMEMBER_N410963 < 10s ORACLE, for start releases up to 46D:
Checks Oracle start release REMN410.LOG
See SAP Note 410963, if necessary
JOB_SRM_PRE_CHECKS_1 < 1% SRM specific checks PSRMPRE.ELG
PSRMPRE.LOG

JOB_J_3GJUPGCD < 1% As of start release 40B:
DIMP specific checks PJ_3GJUPGCD.ELG
PJ_3GJUPGCD.LOG

CHECKGROUP_END4 < 1% End of module
PREPARE Module: Activation checks (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
JOB_RADDRCHK < 1% For start releases up to 40B:
Prepares for renaming of data elements PADDRCHK.ELG
PADDRCHK.LOG
Correct naming conflicts as described in SAP Note 096905
ACTREF_CHK < 1% Checks whether activation errors might occur during the upgrade RSTODIRX.LOG
RSTODIRX.ELG
Remove references to SAP data elements and domains
RUN_RSUPGDEC_PRE < 1% Checks if current structure extensions collide with the DDIC enhancement category of the target release RSUPGDEC.ELG
RSUPGDEC.LOG
Adjust include or consider help from SAP SAP Note 493387
CHECKGROUP_END5 < 1% End of module
PREPARE Module: Necessary checks for conversions (Mandatory)
Phase Duration PREPARE Actions Log Files User Actions
CNV_AVOID < 1% For start release 30C to 31I:
Finds tables that can be reduced in size before the upgrade to speed up the conversion Reduce the size of the tables as described in SAP Note 076431
JOB_RSCNVADR < 1% For start releases up to 40B:
Prepares address data conversion PSCNVADR.ELG
PSCNVADR.LOG
Start the report for preparing the address data conversion as described in SAP Note 082167 and SAP Note 097032 as well as adaptions to number ranges as described in SAP Note 319986 and SAP Note 379769
REQ_APOUPG0 dial Prompts for checks for the LiveCache Save the live cache: follow the instructions given in the manual
JOB_MC01_CACL_CDP_PRE < 1% For start releases up to 610:
Performs consistence check CDPCON.ELG
CDPCON.LOG

CHECKGROUP_END6 < 1% End of module
PREPARE Module: Optional checks for conversions (Optional)
Phase Duration PREPARE Actions Log Files User Actions
CNV_LIST < 1% Finds tables that are converted during the upgrade (if known to SAP) and lists them in a file
ADDSPAREQ_AD < 10s Summarizes the results of all space checks
DYNSPCADD < 1% Checks the database space requirements dynamically:
Space needed temporarily for conversion
Space for new secondary indexes
DYNSPC.LOG

SPACECHK_OPT < 1% Checks database free space DBFPLUSD.LOG
Extend the database, if necessary
CHECKGROUP_END7 < 1% End of module
PREPARE Module: Modification support (Optional)
Phase Duration PREPARE Actions Log Files User Actions
SETPAR_PDIFFEXP_PRE < 1% Sets parameters for RDDIT006 SQLPDIFP.LOG
SETPDIFP.LOG
SETPDIFP.ELG

RUN_RDDIT006_PRE < 1% Finds conflicts with central SAP Web Application Server objects DIFFCALC.ELG
DIFFCALC.LOG
Contact SAP to get modifications to central SAP Web Application Server objects, if necessary
ADJUSTCHK_PRE < 1% Finds objects to be adjusted - preparation for transactions SPDD and SPAU ADJUSTCP.LOG
ADJUSTCP.ELG
Call transaction SPDD or SPAU to display modifications
CHECKGROUP_END8 < 1% End of module
PREPARE Module: Pre-processing (Optional)
Phase Duration PREPARE Actions Log Files User Actions
RUN_RSWBO230_PRE < 1% Deletes SAP requests from previous upgrades PSWBO230.ELG
PSWBO230.LOG

SAVE_VAR_CHK dial As of start release 40B:
Requests SAVE_VAR information SAVEVARCHK.LOG
Answer SAVE_VAR prompt
JOB_RASUVAR1 < 1% As of start release 40B:
save variants, see note 712297 PASUVAR1.ELG
PASUVAR1.LOG

CHECKGROUP_END9 < 1% End of module

--------------------------------------------------------------------------------

Upgrade Phase Groups
Upgrade Phase Group: Configuration and Initialization
Phase Duration Upgrade Actions Log Files User Actions
BEGIN < 10s Checks upgrade directory
INITPUT dial Initializes R3up

DB2 UDB for z/OS and OS/390:
Checks parameters and JCL submission service DB2 UDB for z/OS and OS/390:
Enter parameters
DBCHK < 1% Determines database version and SAP release
SETSYNC_UPGR_STARTED dial events for sync with Jump
SETSYNC_PREUP_STARTED dial events for sync with Jump
VERSCHK < 1% Checks SAP release Upgrade to a valid source release first, if necessary
UVERS_CHK < 1% Checks consistency of table UVERS UVERSCHK.LOG

BATCHCHK < 1% Tests whether background server can access the upgrade directory BATCHCHK.LOG

PATCH_CHK < 1% Finds unconfirmed Support Packages and displays the result PATCHOUT.LOG
EXECPT.LOG
Call transaction SPAM to confirm any unconfirmed Support Packages, if necessary
CLNT_CHK < 1% Checks whether clients are locked for SAP system upgrade EXECCT.LOG
CLNTOUT.LOG
Unlock clients for SAP system upgrade, if necessary
INTCHK < 1% Checks whether the inactive nametab is empty
TOOLVERSION_UPG < 1% Determines all tool version TOOLVERS.LOG
Upgrade tools if necessary
ADDON_SPEC2 dial Requests add-on information ADDONSPEC2.LOG

ADDONKEY_CHK < 1% Prompts for keyword for industry solution, if necessary
ADDONKEY.LOG
Enter keyword for industry solution, if necessary

JDKCHK_UPG < 1% Checks availability of JDK JDKCHK.LOG
Install JDK, if necessary
SHDINST_CHK1 < 1% Checks the shadow instance SHDINST_CHK1.LOG

INITSUBST < 1% Initializes for System Switch Upgrade Enter parameters
FRONTREQ < 1% Informs users that they must import a new version of the SAP GUI Confirm
CONFCHK_X < 1% Tests operating system and database version Upgrade operating system and database to the required version, if necessary
VIEWCHK1 < 1% Finds conflicts between delivered views and customer tables in the SAP name range VIEWCHK1.LOG
Delete tables, if necessary
REPACHK1 < 1% Finds SAP objects locked in repairs or requests REPACHK1.LOG

UCMIG_STATUS_CHK1 < 10s Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT1.LOG

JOB_RSVBCHCK2 < 1% Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
PSVBCHCK.LOG
Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
RUN_RSWBO230 0-2% Deletes SAP requests from previous upgrades PSWBO230.ELG
PSWBO230.LOG

JOB_RXPRECHK < 1% For start release 30D to 31I:
Makes preliminary checks for the XPRA RLXPRA40 PXPRECHK.ELG
PXPRECHK.LOG

JOB_RS_OLTPSOURCE < 1% Performs OLTP source cleaning PSOLTPSC.ELG
PSOLTPSC.LOG

JOB_RSAODSACTIVATE < 1% Performs TADIR cleaning PSATADIR.ELG
PSATADIR.LOG

TABSPC_UPG < 1% Checks database version if it was too low during PREPARE TABSPCU.LOG
TABSPCU.ELG

CHK_DB6_REG_UPG dial DB2 UDB for UNIX and Windows:
Checks DB6 registry parameters
DB_ACTION_RUNSTATS 1% DB2 UDB for UNIX and Windows:
Remove volatile flags DBACTRUN.LOG

CHK_DB6_PAR_UPG dial DB2 UDB for UNIX and Windows:
Checks DB6 parameters
SPACECHK_ALL < 1% Checks free space on the database DBFPLUSD.LOG
Extend the database, if necessary
FREECHK_X < 1% Checks free space in the file system Confirm

Enlarge the file system, if necessary

DMPSPC_X < 1% Provides information on freespace in the database DMPSPC_X.LOG

JOB_BTCTRNS0 < 1% As of start release 45A, strategy Resource-minimized:
Deschedules background jobs BTCTRNS1.ELG
BTCTRNS1.LOG

UCMIG_STATUS_CHK21 < 10s Strategy Resource-minimized:
Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT2.LOG

SETPAR_PDIFFEXP < 1% Sets parameters for RDDIT006 SQLPDIFU.LOG
SETPDIFU.LOG
SETPDIFU.ELG

RUN_RSPTBFIL_INIT 1% Enters source release information in table PUTTB_SHD RSPTBINI.ELG
RSPTBINI.LOG

READPUTTB_UPG < 1% Reads table PUTTB and places it in the file system RDPUTTB.LOG

SQLDB_SWITCH_DOCU < 1% enabling of shadow import for docu objects PUTTBDOKTL.LOG

LOCKEU_PRE < 1% Strategy downtime-minimized: Prompts for time from when ABAP Workbench is locked LOCKEUPR.LOG
Strategy downtime-minimized: Respond to prompt for lock time
CHECKCDMOUNTS < 1% Checks whether all required CDs for the EU_IMPORT phases are available If a CD is missing, change the mount directories or, if you do not use mount directories, ignore the prompt
Upgrade Phase Group: Import and Modification Transfer
Phase Duration Upgrade Actions Log Files User Actions
DB_ACTION_UPG < 1% Performs database-specific actions SELDBSU.LOG
ALTDBS.LOG
DBACTUPG.LOG

CNTRANS_TPL < 10s MCOD only: Adapts container names in R3load CNTTPL.LOG

SQLSCREXE_UPGEU1 < 1% Performs actions for restart handling PARAMEU1.LOG
UPGPAREU.ELG
UPGPAREU.LOG

JOB_MC01_CACL_CDP_POST1 < 1% For start releases up to 610, strategy Resource-minimized:
Performs consistence check CDPCON1.ELG
CDPCON1.LOG

REQSTOP_APO1 dial Strategy Resource-minimized:
Prompts, if system may be stopped Confirm, that the system may be stopped
LOCKSYS_APO1 < 1% Strategy Resource-minimized:
Locks SAP system for user access LOCKSYSAPO.LOG

STOPSAP_LCD1 < 1% Strategy Resource-minimized:
Stops SAP system Isolate the central instance and stop all application servers
STARTSAP_LCD1 < 1% Strategy Resource-minimized:
Starts SAP system
REQ_APOUPG1 dial Strategy Resource-minimized:
Prompts to save the live cache Save the live cache: follow the instructions given in the manual
SETSYNC_PREUP_FINI_R1 dial Strategy Resource-minimized:
events for sync with Jump
GETSYNC_PREUP_FINI_R1 dial Strategy Resource-minimized:
events for sync with Jump
SETSYNC_DOWN_START_R1 dial Strategy Resource-minimized:
events for sync with Jump
SETSYNC_EULCK_START_R1 dial Strategy Resource-minimized:
events for sync with Jump
JOB_GN_BEF_UPG_CRM40_1 < 1% Strategy Resource-minimized, as of start release 610:
Performs consistence check MWCRM1.ELG
MWCRM1.LOG

EU_IMPORT1 1-2% Copies substitution set from Upgrade CD to the shadow tables EU_IMP1.ELG
EU_IMP1.LOG
Mount requested Upgrade CD, if necessary
NTACT_NODBPOS < 1% Cleans up nametab NTSHDNDB.ELG
NTSHDNDB.LOG

NTACT_CONV_UC < 1% Generates nametabs of shadow tables in shadow nametab conv_uc NTSHDCUC.ELG
NTSHDCUC.LOG

SHADOW_NTACT_CP < 1% Generates nametabs of shadow tables in the shadow nametab NTSHDCP.ELG
NTSHDCP.LOG

SQLDB_SHDI_DOC31I_ON1 < 1% For start releases up to 31I:
enabling of shadow import for docu objects, special handling startrelease 3.1I SHDI_DOC31I.LOG

EU_IMPORT2 5-8% Copies substitution set from Upgrade CD to the shadow tables EU_IMP2.ELG
EU_IMP2.LOG
Mount requested Upgrade CD, if necessary
EU_IMPORT3 2-5% Copies substitution set from Upgrade CD to the shadow tables EU_IMP3.ELG
EU_IMP3.LOG
Mount requested Upgrade CD, if necessary
READDATA_EU4 < 1% Copies substitution set from Upgrade CD to the shadow tables, if necessary Mount requested upgrade CD, if necessary
EU_IMPORT4 6-10 Copies substitution set from Upgrade CD to the shadow tables EU_IMP4.ELG
EU_IMP4.LOG
Mount requested Upgrade CD, if necessary
EU_IMPORT5 15-2 Copies substitution set from Upgrade CD to the shadow tables EU_IMP5.ELG
EU_IMP5.LOG
Mount requested Upgrade CD, if necessary
EU_IMPORT6 < 10s Copies substitution set from Upgrade CD to the shadow tables EU_IMP6.ELG
EU_IMP6.LOG
Mount requested Upgrade CD, if necessary
EU_IMPORT7 < 10s Copies substitution set from Upgrade CD to the shadow tables EU_IMP7.ELG
EU_IMP7.LOG
Mount requested Upgrade CD, if necessary
EUVIEWIMP < 1% Imports views for shadow tables ALTER34V.LOG

INDQUE_CHK < 1% SAP DB:
Checks for indexes INDQUECHK.LOG

TR_APPENDBUF_UPG1 < 10s Moves upgrade requests from the R3up buffer to the hyperbuffer TRAPPB.LOG

SHADOW_IMPORT_UPG1 1-6% Imports upgrade and language data into the shadow tables (no new tables) SHDUPGIMP1.ELG

STARTSAP_IMP < 1% Starts SAP system if it was stopped during phase EU_IMPORT1
REPACHK2 < 1% Finds SAP objects locked in repairs or requests REPACHK2.LOG
Confirm locks for ABAP Workbench if not yet done in phase LOCKEU_PRE
SETSYNC_EULCK_START_D1 dial Strategy Downtime-minimized:
events for sync with Jump
SETSYNC_EULCK_START_R2 dial Strategy Resource-minimized:
events for sync with Jump
UVERS_UP_U < 1% Changes the status in table UVERS
CNV_CHK_XT < 1% Finds outstanding conversions and restart logs for conversions that have not been completed Make conversions (after discussion with SAP consultant), if necessary
TRBATCHK_XT < 1% Checks whether table TRBAT is empty Perform any actions specified by R3up, if necessary
LIST_LOAD < 1% Generates list of programs that need to be generated LISTLOAD.LOG

JOB_RDDTAXIT < 1% Selects generated objects SYSPREP.ELG
SYSPREP.LOG

JOB_STRU_TADIR_GEN_2 < 1% Performs TADIR insert PSTRUGEN.ELG
PSTRUGEN.LOG

JOB_RSGENYTT < 1% Copies nametabs to table DDYTT/F PSGENYTT.ELG
PSGENYTT.LOG

SUBSTNT_INS < 1% Creates nametab entries for the new substitution tables STBNTINS.LOG

RUN_RSINCGEN < 1% Generates include program for accessing substitution tables PSINCGEN.ELG
PSINCGEN.LOG

JOB_SRM_PRE_CHECKS_2 < 1% SRM specific checks PSRMPRE.ELG
PSRMPRE.LOG

RUN_RDDIT006 1-3% Determines deviations of the current system from the future standard SAP system (objects and modifications that need to be copied) DIFFCALC.ELG
DIFFCALC.LOG

ADJUSTCHK < 1% Determines ABAP Dictionary objects that need to be adjusted ADJUSTCK.LOG
ADJUSTCK.ELG
Confirm R3up message, if necessary
JOB_RSPUSCAD < 1% Exports documentation created or modified by customer PSPUSCA4.ELG
PSPUSCA4.LOG

DB_ACTION_LOWQ1 < 1% Performs switch for DIFFEXP phases LOWERQ.LOG
DBACTLQ1.LOG

DIFFEXPADDE (var Exports content of add-on objects not stored in shadow tables DIFFEXPA.ELG
DIFFEXPA.LOG

SQLDB_LOCKFLAG_CCI (var Perform database correction after export LOCKFLAGRESET_CCI.LOG

DIFFEXPADD (var Copies Dictionary part for add-on objects to the shadow tables DIFFEXPA.ELG
DIFFEXPA.LOG

DIFFEXPPKGE (var Exports content of support package ects not stored in shadow tables DIFFEXPP.ELG
DIFFEXPP.LOG

SQLDB_LOCKFLAG_CCP (var Perform database correction after export LOCKFLAGRESET_CCP.LOG

DIFFEXPPKG (var Copies Dictionary part for support package objects to the shadow tables DIFFEXPP.ELG
DIFFEXPP.LOG

DIFFEXPLAN (var Exports language content of support packages not stored in shadow tables DIFFEXPL.ELG
DIFFEXPL.LOG

SQLDB_LOCKFLAG_CCL (var Perform database correction after export LOCKFLAGRESET_CCL.LOG

DIFFEXPGEN 2% Copies Dictionary part of generated objects to the shadow tables DIFFEXPG.ELG
DIFFEXPG.LOG

DIFFEXPMOD < 1% Copies unsent modified objects to the shadow tables DIFFEXPR.ELG
DIFFEXPR.LOG

DIFFEXPCUSTE (var Export content of customer developments not stored in shadow tables DIFFEXPC.ELG
DIFFEXPC.LOG

SQLDB_LOCKFLAG_CCC (var Perform database correction after export LOCKFLAGRESET_CCC.LOG

DIFFEXPCUST (var Copies Dictionary part of customer developments to the shadow tables DIFFEXPC.ELG
DIFFEXPC.LOG

DIFFEXPDDIV < 1% Exports inactive ABAP Dictionary versions DIFFEXPD.ELG
DIFFEXPD.LOG

DIFFEXPDOCU < 1% Exports customer extensions to SAP object documentation DIFFEXPO.ELG
DIFFEXPO.LOG

DIFFEXPCDOC < 1% Exports documentation for customer objects DIFFEXCO.ELG
DIFFEXCO.LOG

DIFFEXPTSAP < 1% Exports local private objects and test objects in the SAP name range DIFFEXPT.ELG
DIFFEXPT.LOG

DB_ACTION_UPQ1 < 1% Performs switch for DIFFEXP phases UPPERQ.LOG
DBACTUQ1.LOG

JOB_RDDSAVTE < 1% Copies technical settings in the ABAP Dictionary PDDSAVTE.ELG
PDDSAVTE.LOG

RUN_RDDCP4TB < 1% Copies non-delivered TADIR entries to the shadow tables PDDCP4TB.ELG
PDDCP4TB.LOG

RUN_RDDDL4TB < 1% Deletes entries for deleted objects from the shadow table TADIR PDDDL4TB.ELG
PDDDL4TB.LOG

RUN_RSTRESNC < 1% Copies namespace reservations to the shadow tables PSTRESNC.ELG
PSTRESNC.LOG

JOB_RDDINDPR < 1% Finds all secondary indexes INXPREP.ELG
INXPREP.LOG

Upgrade Phase Group: Shadow System Installation
Phase Duration Upgrade Actions Log Files User Actions
ALTEXT_MAXALL < 1% ORACLE:
Sets tablespace extents as unlimited SELALTAB.LOG
DBACTGRA.LOG
DBACTGRA.ELG

SQLSCREXE_MLI4 < 10s For start releases up to 46D:
Creates the license for the shadow instance CPMLICHK.LOG
SQLEXEML.ELG
SQLEXEML.LOG

SQLSCREXE_MLI6 < 10s As of start release 610:
Creates the license for the shadow instance CPMLICHK.LOG
SQLEXEML.ELG
SQLEXEML.LOG

SQLDB_CPUSR < 10s Initializes authorizations SQLEXUS.LOG

PSCRGEN_ALIAS < 10s Generates scripts for aliases/views/synonyms SQLGENAL.ELG
SQLGENAL.LOG

SCRGEN_ALI_ORG < 10s Generates scripts for shadow instance SGALORG.ELG
SGALORG.LOG

DB_ACTION_GRANT < 1% SAP DB:
Generates grant scripts SELTAB.LOG
DBACTGRA.LOG

SQLSCREXE_GRANT < 1% SAP DB:
Grants privileges PTBALIGR.LOG
SQLEXEGR.ELG
SQLEXEGR.LOG

SCEXEC_GRANT 1% Except SAP DB:
Grants privileges SQLEXEGR.LOG

SCEXEC_ALIAS 1% Creates aliases/views/synonyms SQLEXEAL.LOG

SQLSCREXE_GRA_ORG < 1% Executes scripts for shadow instance ALORGR.LOG
SEGRORG.ELG
SEGRORG.LOG

SQLSCREXE_ALI_ORG < 1% Executes scripts for shadow instance ALORDC.LOG
SEDCORG.ELG
SEDCORG.LOG

SQLSCREXE_SEQ < 10s Creates sequence SEQUE.LOG
SQLEXESE.ELG
SQLEXESE.LOG

VIEWIMP_BAS < 1% Creates views for the SAP Web Application Server VIEWIMP.ELG
VIEWIMP.LOG

TR_TRK2HEAP_INIT < 10s Copies requests to the R3up buffer TRSHDIN.LOG

TP_ACTION_CP2SINI < 1% Copies a small number of control entries to shadow tables CP2SHDI.ELG
CP2SHDI.LOG

SHADOW_NTACT_DEL < 1% Deletes nametabs of shadow tables in the shadow nametab NTSHDDEL.ELG
NTSHDDEL.LOG

SQLDB_SHDI_DOC31I_OFF1 < 1% For start releases up to 31I:
enabling of shadow import for docu objects, special handling startrelease 3.1I SHDI_DOC31I.LOG

EXEC_SMOFF_SHD < 10s Switches off the Session Manager for the upgrade EXECSMF.LOG

JOB_GN_BEF_UPG_CRM40_2 < 1% Strategy Resource-minimized, as of start release 610:
Performs consistence check MWCRM2.ELG
MWCRM2.LOG

JOB_MC01_CACL_CDP_POST2 < 1% For start releases up to 610, strategy Resource-minimized:
Performs consistence check CDPCON2.ELG
CDPCON2.LOG

REQSTOPPROD < 1% Strategy Resource-minimized:
Stops production operation Confirm R3up prompt
JOB_BTCTRNS2 < 1% As of start release 45A, strategy Resource-minimized:
Deschedules background jobs BTCTRNS1.ELG
BTCTRNS1.LOG

UCMIG_STATUS_CHK22 < 10s Strategy Resource-minimized:
Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT2.LOG

UCMIG_STATUS_CHK23 < 10s Strategy Downtime-minimized:
Check status of Unicode Conversion Preparations on the start release UCMIGCHKSTAT2.LOG

REQSTOP_APO2 dial Strategy Resource-minimized:
Prompts, if system may be stopped Confirm, that the system may be stopped
LOCKSYS_APO2 < 1% Strategy Resource-minimized:
Locks SAP system for user access LOCKSYSAPO.LOG

STOPSAP_LCD2 < 1% Strategy Resource-minimized:
Stops SAP system Isolate the central instance and stop all application servers
STARTSAP_LCD2 < 1% Strategy Resource-minimized:
Starts SAP system
REQ_APOUPG2 dial Strategy Resource-minimized:
Prompts to save the live cache Save the live cache: follow the instructions given in the manual
JOB_DROP_TMPOBJ_UPG1 < 1% Strategy Resource-minimized:
Deletes temporary BW objects RSDR_NAMT_CL.ELG
RSDR_NAMT_CL.LOG

JOB_SDLINIT_TABLES_UPG1 < 1% Strategy Resource-minimized, as of start release 620:
Deletes invalid nametab entries RSSM_SDLINIT.ELG
RSSM_SDLINIT.LOG

JOB_RDDPURIF_R < 1% Strategy Resource-minimized:
Deletes inconsistent values from tables PDDPURIF.ELG
PDDPURIF.LOG

JOB_KEYIDX1_R < 1% Strategy Resource-minimized, MSSQL, for start releases up to 45B:
Component-specific actions RKEYIDX1.ELG
RKEYIDX1.LOG

JOB_RSVBCHCK_R < 1% Strategy Resource-minimized:
Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
PSVBCHCK.LOG
Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
INTCHK_SW < 1% Checks whether the inactive nametab is empty
SETSYNC_PREUP_FINI_R2 dial Strategy Resource-minimized:
events for sync with Jump
GETSYNC_PREUP_FINI_R2 dial Strategy Resource-minimized:
events for sync with Jump
SETSYNC_DOWN_START_R2 dial Strategy Resource-minimized:
events for sync with Jump
STOPSAP_PROD < 1% Strategy Resource-minimized:
Stops the production system
Upgrade Phase Group: Shadow System Operations: SPDD and Activation
Phase Duration Upgrade Actions Log Files User Actions
CONFCHK_BAS < 1% Tests operating system and database version
SHD_FIX_IMP < 1% Imports repair requests for shadow system SHD_FIX.ELG

PORT_IMP_SHD < 1% Transports add-on-specific imports into the shadow system PORT_SHD.ELG

SHDINST_CHK2 < 1% Checks the shadow instance SHDINST_CHK2.LOG

START_SHDI_FIRST < 1% Starts the shadow system DEVTRACE.LOG
STARTSFI.LOG

STOP_SHDI_SW1 < 1% Stops shadow instance STOPSHDI.LOG

SETSYNC_PREUP_FINI_SW dial events for sync with Jump
GETSYNC_PREUP_FINI_SW dial events for sync with Jump
SETSYNC_DOWN_START_SW dial events for sync with Jump
SETSYNC_EULCK_START_SW dial events for sync with Jump
STARTSAP_SW2 < 1% Starts SAP system
JOB_BTCTRNSSW < 1% As of start release 45A:
Deschedules background jobs BTCTRNS1.ELG
BTCTRNS1.LOG

JOB_GN_BEF_UPG_CRM40_S2 < 1% As of start release 610:
Performs consistence check MWCRMSW.ELG
MWCRMSW.LOG

JOB_MC01_CACL_CDP_POSTT < 1% For start releases up to 610:
Performs consistence check CDPCONSW.ELG
CDPCONSW.LOG

REQ_APOUPGSW dial Prompts to save the live cache Save the live cache: follow the instructions given in the manual
JOB_DROP_TMPOBJ_UPG2 < 1% Deletes temporary BW objects RSDR_NAMT_CL.ELG
RSDR_NAMT_CL.LOG

JOB_SDLINIT_TABLES_UPG2 < 1% As of start release 620:
Deletes invalid nametab entries RSSM_SDLINIT.ELG
RSSM_SDLINIT.LOG

JOB_RDDPURIF_R_SW < 1% Deletes inconsistent values from tables PDDPURIF.ELG
PDDPURIF.LOG

JOB_KEYIDX1_R_SW < 1% MSSQL, for start releases up to 45B:
Component-specific actions RKEYIDX1.ELG
RKEYIDX1.LOG

JOB_RSVBCHCK_R_SW < 1% Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
PSVBCHCK.LOG
Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
STOPSAP_SW1 < 1% Stops the production system
START_SHDI_SECOND < 1% Starts the shadow system DEVTRACE.LOG
STARTSFI.LOG

JOB_MSSSPEXE_SHD < 1% MSSQL:
Performs specific actions PMSSSPEX.ELG
PMSSSPEX.LOG

ALTNTAB_FILL 2% Creates alternative nametab DDMTT/DDMTF for distributor ALTNTFI.LOG
ALTNTFI.ELG

RUNASYN_RSGENLOAD < 1% Genrates ABAP Loads on Shadow System on advance RSGENLOAD.LOG

JOB_RSUPGBAD < 1% Disables all application BAdIs RSUPGBAD.ELG
RSUPGBAD.LOG

JOB_RSUPDTEC < 1% Adapts technical settings for the MCOD system PSUPDTEC.ELG
PSUPDTEC.LOG

JOB_RDDNEWPP_SHD < 1% Reschedules RDDIMPDP RDDNEWPP.ELG
RDDNEWPP.LOG

RUN_RDDNT5MD < 1% Adjusts structure changes to the source release PDDNT4MD.ELG
PDDNT4MD.LOG

TABUIMP_CNV < 1% Imports (a small number of) table entries needed to start the system with the new SAP Kernel TABUCNV.ELG

TR_BUF2HEAP_DIFF < 10s Copies requests from DIFFEXP buffer to request buffer TPSHBUF.LOG
TRB2H.LOG

TR_APPENDBUF_UPG < 10s Moves upgrade requests from the R3up buffer to the hyperbuffer TRAPPB.LOG

DDIC_700 (var Imports results from transaction SPDD from a development system, if necessary DDICUPG.ELG

JOB_RSWBOUP1_SHD < 1% Initializes and adjusts tables for the Workbench Organizer PSWBOUP1.ELG
PSWBOUP1.LOG

RUN_RSINCGEN_SHD1 < 1% Generates include program for accessing original tables PSINCGEN.ELG
PSINCGEN.LOG

JOB_RSUMOD03 < 1% Initializes new management of customer modifications RSUMOD03.ELG
RSUMOD03.LOG

JOB_RDDMCMRG < 1% Automatically adjusts matchcodes PDDMCMRG.ELG
PDDMCMRG.LOG

ADDTOBUF_MCM < 1% Flags matchcodes for activation ADDMCM.ELG
ADDMCM.LOG

ADDTOBUF_MCM1 < 1% Flags matchcodes for activation ADDMCM.ELG
ADDMCM.LOG

RUN_DREXE_SHD < 1% For start releases up to 40B:
Renames data elements with conflicting names in the customer name range PADDREX1.ELG
PADDREX1.LOG

JOB_RUTTYREP < 1% For start releases up to 40B:
Checks, and repairs if necessary, entries in the DDTYPES table PUTTYREP.ELG
PUTTYREP.LOG

JOB_DL4TA_UPG < 1% Deletes TADIR entries for objects generated temporarily PDDDL4TA.ELG
PDDDL4TA.LOG

NTACT_DELPRE < 1% Deletes inactive nametabs from non-database objects with a delete request NTDELPRE.ELG
NTDELPRE.LOG

JOB_SFW_UPG < 1% Configures the SFW settings and creates the object list for activation SFW_UPG.ELG
SFW_UPG.LOG

ADDTOBUF_SFW < 1% Adds SFW object list for activation ADDSFW.ELG
ADDSFW.LOG

JOB_UMOD20_UPG < 1% Brings the structure of tables into line with the database PSUMOD20.ELG
PSUMOD20.LOG

RUN_RADTBUCACT < 1% UNICODE only: Adjusts ABAP Dictionary entries PADTBUC.ELG
PADTBUC.LOG

ACT_700 (var Activates ABAP Dictionary customer objects ACTUPG.ELG
If necessary, adjust ABAP Dictionary objects using transaction SPDD
RUN_RSPTBFIL_DEST < 1% Enters target release information in table PUTTB_SHD RSPTBDST.ELG
RSPTBDST.LOG

JOB_RDDPRHS < 1% saves spdd informations PRDDPRHS.ELG
PRDDPRHS.LOG

JOB_RUTTTYPSET < 1% Runs only in UNICODE to update DD40L PUTTTYPSET.ELG
PUTTTYPSET.LOG

JOB_RSSTORPA < 1% Saves memory parameters for distributor PSSTORPA.ELG
PSSTORPA.LOG

RUN_INDC_UPG < 1% Checks secondary indexes INDEXCHK.ELG
INDEXCHK.LOG

PARDIST_SHD 2% Starts distributor PARDSHD.ELG
PARDSHD.LOG

JOB_RSNTICNV < 1% Strategy Downtime-minimized:
Calculates candidates for ICNV PSNTICNV.ELG
PSNTICNV.LOG

RUN_RSPTBFIL_PDIST < 1% Enters distributor results in table PUTTB_SHD RSPTBDST.ELG
RSPTBDST.LOG

RUN_RSUPG_DDXTT_TABLSIZE < 1% Preparations for parallel DDL execution RSUPG_DDXTT_TABLSIZE.ELG
RSUPG_DDXTT_TABLSIZE.LOG

RUN_RSPTBFIL_TRINIT_S < 1% Generates trigger names and creates transports RSPTBTRI.ELG
RSPTBTRI.LOG

RUN_RSINCGEN_SHD2 < 1% Regenerates include program for standard operation PSINCGEN.ELG
PSINCGEN.LOG

JOB_UM4_COPY_RESULTS < 1% Takes over unicode conversion data UM4_COPY_RESULTS.ELG
UM4_COPY_RESULTS.LOG

SQLDB_DDNTT_CONV_UC_UCM (var Cleans tables for unicode conversion DDNTT_CONV_UC.LOG

RUN_RADCUCNT_ALL < 1% Generates the Unicode NTs from the inactive shadow NT RADCUCNTALL.ELG
RADCUCNTALL.LOG

SHMD_STAT_SSIL < 1% Dumps shared memory usage of shadow system SHMD_SSIL.LOG

STOP_SHDI_LAST < 1% Stops shadow instance STOPSHDI.LOG

Upgrade Phase Group: Shadow Import
Phase Duration Upgrade Actions Log Files User Actions
DMPSPC_LAST < 1% Provides information on freespace in the database DMPSPC_LAST.LOG

VIEW_DEL_SHD < 1% Deletes views in the shadow system VIEWDEL.LOG

SCEXEC_DEL_ALI 1% Deletes aliases/views/synonyms SQLEXEAL.LOG

DB_ACTION_REVOKE < 1% SAP DB:
Generates revoke scripts SELTAB.LOG
DBACTGRA.LOG

SQLSCREXE_DEL_GRA 1% SAP DB:
Deletes grants PTBALIRE.LOG
SQLEXEGR.ELG
SQLEXEGR.LOG

SCEXEC_DEL_GRA 1% Except SAP DB:
Deletes grants SQLEXEGR.LOG

SQLSCREXE_DEL_ALIORG < 1% Deletes additional aliases/views/synonyms ALORDR.LOG
SEDEORG.ELG
SEDEORG.LOG

SQLSCREXE_DEL_GRAORG < 1% Deletes grants ALORRE.LOG
SEREORG.ELG
SEREORG.LOG

PSCRGEN_DROP_SHD_TABLE 3-5% Generates scripts for deleting shadow tables and executes them SQLDRSHD.ELG
SQLDRSHD.LOG

ICNVINIT < 1% Strategy Downtime-minimized:
Checks the volumes of the candidates and initializes successful candidates DDICNV.LOG
ICNVINIT.ELG
ICNVINIT.LOG

ICNVREQ < 1% Strategy Downtime-minimized:
Prompts you to start transaction ICNV if there are candidates for the ICNV, but ICNV has not yet been started DDICNV.LOG
ICNVCAND.LOG
ICNVREQP.ELG
ICNVREQP.LOG
Call transaction ICNV, if necessary
RUNASYN_RSINDCRE < 1% Strategy Downtime-minimized:
Starts index pre-creation for some database systems RSINDCRE.LOG

NTACT_PREMV < 1% Copies nametabs to the shadow tables NTMOVPRE.ELG
NTMOVPRE.LOG

PARMVNT_SHD 1-2% Activates nametab entries MVNTSHD.ELG
MVNTSHD.LOG

SHADOW_NTACT_RECP < 1% Generates nametabs for shadow tables NTSHDCP.ELG
NTSHDCP.LOG

SQLDB_SHDI_DOC31I_ON2 < 1% For start releases up to 31I:
Enables shadow import for docu objects, special handling startrelease 3.1I SHDI_DOC31I.LOG

PSCRGEN_TRIG < 1% Generates scripts for creating and deleting triggers SQLGENTR.ELG
SQLGENTR.LOG

OPTEXE_TRIG < 1% Creates triggers PTTRCT.LOG
SQLEXETR.ELG
SQLEXETR.LOG

DMPSPC_TRG < 1% Provides information on freespace in the database DMPSPC_TRG.LOG

TR_TRK2HEAP_CP2S < 10s Copies requests to the R3up buffer TRSHDINT.LOG

TR_TRK2HEAP_CPFROM < 10s Copies requests to the R3up buffer TRSHDINF.LOG

DB_ACTION_LOWQ2 < 1% Performs switch for DIFFEXP phases LOWERQ.LOG
DBACTLQ2.LOG

DIFFEXPADDI (var Main import for add-on objects to shadow tables DIFFEXPAI.ELG
DIFFEXPAI.LOG

DIFFEXPPKGI (var Main import for support package objects to the shadow tables DIFFEXPPI.ELG
DIFFEXPPI.LOG

DIFFEXPGENI 2% Main import of generated objects to shadow tables DIFFEXPGI.ELG
DIFFEXPGI.LOG

DIFFEXPMODI < 1% Main import of modified objects to the shadow tables DIFFEXPRI.ELG
DIFFEXPRI.LOG

DIFFEXPCUSTI (var Main import of customer developments to shadow tables DIFFEXPCI.ELG
DIFFEXPCI.LOG

DB_ACTION_UPQ2 < 1% Performs switch for DIFFEXP phases UPPERQ.LOG
DBACTUQ2.LOG

TP_ACTION_CP2STAB < 1% Copies tables for shadow import CP2SHDT.ELG
CP2SHDT.LOG

TR_BUF2HEAP_TABUIMP < 10s Moves basis upgrade requests from the TABUIMP.BUF buffer to the R3up buffer TPSHBUF.LOG
TRB2H.LOG

TR_APPENDBUF_BAS < 10s Moves upgrade requests from the R3up buffer to the hyperbuffer TRAPPB.LOG

SHADOW_IMPORT_BAS 2% Imports (a small number of) table entries needed to start the system with the new SAP kernel SHDBASIMP.ELG

HYPAPPBUF_SHDUPG2 < 10s Merges buffer for SHADOW_IMPORT_UPG2 phase HYPAPPBUF.LOG

APPENDBUF_SHDUPG < 10s Merges buffer for SHADOW_IMPORT_UPG2 phase
SHADOW_IMPORT_UPG2 6% Imports upgrade and language data into the new tables SHDUPGIMP2.ELG

SHADOW_IMPORT_INC 6% Imports included Add-on and Support Packages into the shadow tables and the new tables SHDALLIMP.ELG

APPENDBUF_TRIGIM < 10s Merges buffer for SHADOW_IMPORT_TRIG phase
APPENDBUF_TABIM < 10s Merges buffer for TABIM_UPG phase
SCRGEN_DROP_TABLE_LAST < 1% Generates scripts for deleting remaining shadow tables SQLDRSHD.ELG
SQLDRSHD.LOG

VIEWCHK2 < 1% Finds conflicts between delivered views and customer tables in the SAP name range VIEWCHK2.LOG

SCRGEN_XCNV < 10s Generates scripts for external conversion SCRGENXC.ELG
SCRGENXC.LOG

SCRGEN_SWITCH < 10s Generates scripts for substitution tables SCRGENSW.ELG
SCRGENSW.LOG

SQLSCREXE_SELNEW < 1% List all new tables LISTNEW.LOG
SELNEW.ELG
SELNEW.LOG

DB_ACTION_STATNEW < 1% Update statistics for new tables STATNEW.LOG
LISTNEW.LOG
DBSTATNEW.LOG

SQLSCREXE_SELSHD < 1% List all new tables LISTSHD.LOG
SELSHD.ELG
SELSHD.LOG

DB_ACTION_STATSHD < 1% Update statistics for shadow tables STATSHD.LOG
LISTSHD.LOG
DBSTATSHD.LOG

DMPSPC_MPT < 1% Provides information on freespace in the database DMPSPC_MPT.LOG

Upgrade Phase Group: Downtime phases I: Switch tables and Kernel
Phase Duration Upgrade Actions Log Files User Actions
JOB_GN_BEF_UPG_CRM40_3 < 1% Strategy Downtime-minimized, as of start release 610:
Performs consistence check MWCRM3.ELG
MWCRM3.LOG

JOB_MC01_CACL_CDP_POST3 < 1% For start releases up to 610, strategy Downtime-minimized:
Performs consistence check CDPCON3.ELG
CDPCON3.LOG

REQSTOP_APO3 dial Strategy Downtime-minimized:
Prompts, if system may be stopped Confirm, that the system may be stopped
LOCKSYS_APO3 < 1% Strategy Downtime-minimized:
Locks SAP system for user access LOCKSYSAPO.LOG

STOPSAP_LCD3 < 1% Strategy Downtime-minimized:
Stops SAP system Isolate the central instance and stop all application servers
STARTSAP_LCD3 < 1% Strategy Downtime-minimized:
Starts SAP system
REQ_APOUPG3 dial Strategy Downtime-minimized:
Prompts to save the live cache Save the live cache: follow the instructions given in the manual
SETSYNC_PREUP_FINI_D dial Strategy Downtime-minimized:
events for sync with Jump
GETSYNC_PREUP_FINI_D dial Strategy Downtime-minimized:
events for sync with Jump
MODDEF_APP < 1% Appends Java parameters to the ALP files MODDEFAPP.LOG

MODPROF_TRANS < 1% Stops SAP system and changes profiles ALPXPOOL.LOG
ALPXDEF.LOG
Strategy downtime-minimized: Isolate the central instance and stop all application servers
SETSYNC_PROFILES_CHANGED dial events for sync with Jump
SETSYNC_DOWN_START_D dial Strategy Downtime-minimized:
events for sync with Jump
MOD_PFPAR_TRANS < 1% Calls sappfpar for checking modified profile MODPFPAR.LOG
if the next start fails, we remember ...
ALTEXT_MAXALL_DT < 1% ORACLE:
Sets tablespace extents as unlimited SELALTAB.LOG
DBACTGRA.LOG
DBACTGRA.ELG

STARTSAP_TRANS < 1% Starts SAP system
JOB_CUST_CND_TO_INDX < 1% For start releases up to 610:
Performs consistence check CNDTOINDX.ELG
CNDTOINDX.LOG

JOB_BTCTRNS1 < 1% As of start release 45A, strategy Downtime-minimized:
Deschedules background jobs BTCTRNS1.ELG
BTCTRNS1.LOG

JOB_RSINDSTP < 1% Strategy Downtime-minimized:
Stops index pre-creation RSINDSTP.ELG
RSINDSTP.LOG

SQLSCREXE_UPGMPT < 1% Performs actions for restart handling PARAMMPT.LOG
UPGPAMPT.ELG
UPGPAMPT.LOG

EXEC_TRIG_DEL < 1% Deletes triggers SQLEXETD.LOG

DB_ACTION_GENTRUNC < 1% Strategy Downtime-minimized:
Generates truncate table script. SELTRIG.LOG
TRUNCTAB.LOG
GENTRUNC.LOG

SQLSCREXE_TRUNCSHD < 1% Strategy Downtime-minimized:
Truncate shadow tables where the original table has been updated to speed up the phase TP_ACTION_CP2STRIG. (db dependant) TRUNCTAB.LOG
TRUNCSHD.ELG
TRUNSHD.LOG

RUN_RSPTBFIL_TRICHK < 1% Strategy Downtime-minimized:
Enters trigger analysis in table PUTTB_SHD RSPTBTRC.ELG
RSPTBTRC.LOG

RUN_RSPTBFIL_TRICHK_S < 1% Enters trigger analysis in table PUTTB_SHD RSPTBTRC.ELG
RSPTBTRC.LOG

JOB_DROP_TMPOBJ_UPG3 < 1% Strategy Downtime-minimized:
Deletes temporary BW objects RSDR_NAMT_CL.ELG
RSDR_NAMT_CL.LOG

JOB_SDLINIT_TABLES_UPG3 < 1% Strategy Downtime-minimized, as of start release 620:
Deletes invalid nametab entries RSSM_SDLINIT.ELG
RSSM_SDLINIT.LOG

JOB_RDDPURIF_D < 1% Strategy Downtime-minimized:
Deletes inconsistent values from tables PDDPURIF.ELG
PDDPURIF.LOG

JOB_RSVBCHCK_D < 1% Strategy Downtime-minimized:
Checks whether outstanding updates tasks and queued RFCs exist PSVBCHCK.ELG
PSVBCHCK.LOG
Check outstanding update tasks with transaction SM13 and queued RFCs with transaction SMQ1
TP_ACTION_CP2STRIG < 1% Copies tables with trigger for shadow import CP2SHDR.ELG
CP2SHDR.LOG

NTACT_HIST < 1% For start release 40A to 46D:
Copies history nametab data NTHISTCP.ELG
NTHISTCP.LOG

UVERS_UP_B < 1% Changes the status in table UVERS
JOB_KEYIDX1_D < 1% Strategy Downtime-minimized, MSSQL, for start releases up to 45B:
Component-specific actions RKEYIDX1.ELG
RKEYIDX1.LOG

STOPSAP_XCNV < 1% Stops SAP system
XCNV_DUMP 1% Writes the contents of tables for external conversion to the file system XCNVDU.ELG
XCNVDU.LOG

XCNV_DEL < 1% Deletes from the system the contents of tables that have been written to the file system XCNVDE.ELG
XCNVDE.LOG

PARMVNT_XCNV < 1% Activates nametab entries for external conversions MVNTXCNV.ELG
MVNTXCNV.LOG

SHADOW_NTACT_REDEL < 1% Deletes shadow table nametabs NTSHDDEL.ELG
NTSHDDEL.LOG

SQLDB_SHDI_DOC31I_OFF2 < 1% For start releases up to 31I:
enabling of shadow import for docu objects, special handling startrelease 3.1I SHDI_DOC31I.LOG

VIEW_TABDEL < 1% Deletes tables that become views in new release TABDEL.LOG

EU_SWITCH 1% Switches to new Repository EUSWITCH.LOG

XCNV_LOAD < 1% Converts tables externally and writes the contents back to the system XCNVLO.ELG
XCNVLO.LOG

LOADCRE_TMP < 1% Creates temporary load tables LOADCRT.ELG
LOADCRT.LOG

PMVNTAB_VIEW < 1% Creates SAP Web Application Server views MVNTVIEW.ELG
MVNTVIEW.LOG

NTACT_RWR < 1% Adapts switched nametab entries for database objects to the target system NTRWR40.ELG
NTRWR40.LOG

UVERS_UP_S < 1% Changes the status in table UVERS
ALTER_D4V < 1% Deletes views for the shadow tables ALTERD4V.LOG

EXEC_SMOFF < 1% Switches off the Session Manager for the upgrade EXECSMF.LOG

MODPROF_BAS < 1% Stops SAP system and changes profiles ALPX.LOG
ALPXDP.LOG

MOD_PFPAR_BAS < 1% Calls sappfpar for checking modified profile MODPFPAR.LOG
if the next start fails, we remember ...
ENVCHK < 1% Tests and switches environment of the operating system user of the SAP system
EXEC_CPDEFTPP < 1% CBU: Copys new DEFAULT.TP0 CPDEFTPP.LOG

KX_SWITCH < 1% Switches SAP kernel KX_SW.LOG

SETSYNC_KX_FINI dial events for sync with Jump
SQLDB_BAS_TCP < 10s Mark some codepage tables for import in the next phase SQLDB_BAS_TCP.LOG

TABUIMP_BAS 2% Imports (a small number of) table entries needed to start the system with the new SAP kernel TABUIMP.ELG

PORT_IM1 < 1% Imports requests for porting-specific modifications PORT_IM1.ELG

SQLSCREXE_DBSTA < 1% DB2 UDB for UNIX and Windows:
Updates DBSTATC UPDDBSTA.LOG
SSEDBSTA.ELG
SSEDBSTA.LOG

SQLSCREXE_DBST2 < 1% DB2 UDB for UNIX and Windows:
Updates DBSTATC UPDDBST2.LOG
SSEDBST2.ELG
SSEDBST2.LOG

AREA_SET < 1% Adjusts language environment LANGAREA.LOG

DMPSPC_SET < 1% Provides information on free space in the database DMPSPC_SET.LOG

Upgrade Phase Group: Downtime phases II: Conversion, Main Import, XPRAs
Phase Duration Upgrade Actions Log Files User Actions
STARTSAP_NBAS < 1% Starts SAP system
JOB_RSWBOUP1 < 1% Initializes and adjusts tables for the Workbench Organizer PSWBOUP1.ELG
PSWBOUP1.LOG

JOB_RSUPGAO1 < 1% Deletes old CVERS_REF entries for upgraded add-ons RSUPGAO1.ELG
RSUPGAO1.LOG

RUN_RSUPGBADACT < 1% Re-activates non-basis BAdI objects that have been deactivated in phase JOB_RSUPGBAD RSUPGBADACT.ELG
RSUPGBADACT.LOG

JOB_RDDNEWPP < 1% Reschedules RDDIMPDP RDDNEWPP.ELG
RDDNEWPP.LOG

JOB_MSSSPEXE < 1% MSSQL:
Performs specific actions PMSSSPEX.ELG
PMSSSPEX.LOG

ALTER_RSCPFROM < 1% Generates statistics for tables in transport management RSCPFERR.LOG

RUN_RSCPFROM 2% Copies entries from shadow tables to original tables PSCPFROM.ELG
PSCPFROM.LOG

PORT_IM2 < 1% Imports requests for porting-specific modifications PORT_IM2.ELG

SVERSCHK_UPG < 10s Checks table SVERS to see whether the new SAP release was created successfully
ALTER_VID < 10s For start releases up to 31I:
Deletes inconsistent views ALTERVID.LOG

JOB_RSINDCHK < 1% Strategy Downtime-minimized:
Check, if index pre-creation was succesful RSINDCHK.ELG
RSINDCHK.LOG

JOB_RSTABXTT < 1% Generates control entries for parallel conversion PSTABXTT.ELG
PSTABXTT.LOG

JOB_RSSWICNV < 1% Strategy Downtime-minimized:
Analyzes and deletes table entries PSSWICNV.ELG
PSSWICNV.LOG

JOB_RSXMB_DDCNVEXIT < 1% Creates entries for table DDCNVEXIT PSXMBDDCNV.ELG
PSXMBDDCNV.LOG

PARMVNT_DROPVIEW < 1% Drop views before PARCONV MVNTDROPVIEW.ELG
MVNTDROPVIEW.LOG

DB_ACTION_DROP_VIEW < 1% SAP DB:
Drop views before PARCONV. DBDROPV.LOG

PARCONV_UPG 5% Converts application tables and activates their nametab entries PARCONV.ELG
PARCONV.LOG

SHMD_STAT_PCON < 1% Determines shared memory usage SHMD_PCON.LOG

STOPSAP_IUPG < 1% Stops SAP system
PMVNTAB_UPG 1% Converts application views and activates remaining nametab entries PMVNTUPG.ELG
PMVNTUPG.LOG

SCRIPT_TST_XTT < 1% Checks whether the inactive nametab is empty CNTXTT.LOG
SCRCHKXTT.LOG

ALTER_XTF < 1% Deletes and recreates table DDXTF ALTERXTF.LOG

LOADCRE < 1% Creates new ABAP load tables LOADCRE.ELG
LOADCRE.LOG

STARTSAP_NLUPG < 1% Starts SAP system
JOB_DBDIF_UPG < 1% Cleans up table DBDIFF in the database PADDBDIF.ELG
PADDBDIF.LOG

RUN_DREXE_UPG < 1% For start releases up to 40B:
Renames data elements with conflicting names in the customer name range PADDREX2.ELG
PADDREX2.LOG

SQLDB_SHDI_TRIG < 10s Mark all table where trigger fired to be imported again SHADOW_IMPORT_TRIG.LOG

STOPSAP_TABIM < 1% Stop SAP system to speed up import
TABIM_UPG 5% Imports entries into control tables TABIMUPG.ELG

ALTER_TABIMUPD < 1% Updates statistics for certain tables TABIMERR.LOG

FS_ACTION_IMPSUB < 1% Get list of tables to update statistics for LISTSHD.LOG
FSACTSUB.LOG

DB_ACTION_STATIMP < 1% Update statistics for tables STATIMP.LOG
DBSTATIMP.LOG

STARTSAP_TBUPG < 1% Starts SAP system
TABIM_POST 1% Import of additional transport requests TABUPOST.ELG

DMPSPC_TAB < 1% Provides information on free space in the database DMPSPC_TAB.LOG

JOB_RSWBOUP2 < 1% Initializes and adjusts tables for the Workbench Organizer PSWBOUP2.ELG
PSWBOUP2.LOG

JOB_KEYIDX2 < 1% MSSQL, for start releases up to 45B:
Component-specific actions RKEYIDX1.ELG
RKEYIDX1.LOG

RUN_RSUPGDEC_UPG < 1% Checks if current structure extensions collide with the DDIC enhancement category of the target release RSUPGDEC.ELG
RSUPGDEC.LOG
Adjust include or consider help from SAP, see SAP Note 493387
JOB_BATCHCHECK_XPRA 0% Starts the batchjob execution checker RSUPGBWD.ELG
RSUPGBWD.LOG

SQLDB_LOCKFLAG_SET (var Switch on flag for XPRA execution LOCKFLAGSET_XPRA.LOG

TR_SETSYNC < 1% Sets required syncmarks SETSYNC.ELG
SETSYNC.LOG

RUN_XPRA_SKIP < 1% CBU: Skips XPRAs, if requested CBUXPRAS.ELG
CBUXPRAS.LOG

XPRAS_UPG 8% Executes XPRAs

If errors occur, repeats phase automatically
XPRASUPG.ELG

RUN_XPRA_ACT < 1% CBU: Activates XPRAs, if requested CBUXPRAA.ELG
CBUXPRAA.LOG

DMPSPC_XPR < 1% Provides information on free space in the database DMPSPC_XPR.LOG

SHMD_STAT_XPRA < 1% Determines shared memory usage SHMD_XPRA.LOG

SQLSCREXE_DROP_LAST < 1% Deletes remaining shadow tables DROPLADR.LOG
EXEDRLST.ELG
EXEDRLST.LOG

UEXP_UPG < 1% Exports any adjusted ABAP Dictionary objects, if necessary UEXPUPG.ELG

STARTSAP_UPG < 1% Starts SAP system
JOB_RDDIT022 < 1% Updates CVERS and AVERS tables RDDIT022.ELG
RDDIT022.LOG

EXECDCV < 1% For start releases up to 610:
deletes SAP-APO from CVERS EXECDCV.LOG

JOB_RSTLANUPG < 1% Sets the status of the installed languages RSTLANUPG.ELG
RSTLANUPG.LOG

OCS_ADDON_STATUS_UPGRADE < 1% Updates status information for included addons ADDONSYNC.LOG

TR_PATCH_STATUS_UPGRADE < 1% Updates status information for imported Support Packages PATCHSYNC.LOG

RUN_RUTTYREP1 < 1% For start releases up to 40B:
Checks, and repairs if necessary, entries in the DDTYPES table PUTTYREP1.ELG
PUTTYREP1.LOG

JOB_RADCREMNT < 1% For start releases up to 46D:
Changes the maintenance flag for tables and initializes the flag for views PADCREMNT.ELG
PADCREMNT.LOG

JOB_DBPROD_UPG < 1% Performs database-specific operations before restarting production operation of the system PSDBPROD.ELG
PSDBPROD.LOG

Upgrade Phase Group: Post Processing
Phase Duration Upgrade Actions Log Files User Actions
PRODCHK_UPG < 10s Checks prerequisites for production operation
JOB_RSMODACU < 1% Activates CMOD enhancements RSMODACU.ELG
RSMODACU.LOG

DBCLEAN_UPG < 1% Cleans up database DBCLEANUPG.LOG

JOB_RSDLDSEQ < 1% Cleans up screen sequence control PSDLDSEQ.ELG
PSDLDSEQ.LOG

JOB_RDDNTPUR < 1% Cleans up nametab PDDNTPUR.ELG
PDDNTPUR.LOG

REQ_LCUPG < 1%
EXEC_SMON < 1% Switches the Session Manager back on EXECSMN.LOG

STOPSAP_DUAL < 1% Phase for dual stack
IGS_INST < 1% Unpacks the IGS to the kernel directory IGSINST.LOG

FRP_INST < 1% For start releases 640:
Unpacks the FRP to the kernel directory FRPINST.LOG

SETSYNC_MODPROF_STARTED dial events for sync with Jump
GETSYNC_MODPROF_FINI dial events for sync with Jump
MODPROFP_UPG < 1% Stops SAP system and resets profiles

MaxDB: If archiving is deactivated, prompts you to create database backup
ALPXP.LOG
ALPXDEFP.LOG
Confirm

MaxDB: If archiving is deactivated, back up database and confirm

MOD_PFPAR_UPG < 1% Calls sappfpar for checking modified profile MODPFPAR.LOG
if the next start fails, we remember ...
SETSYNC_POSTUP_START dial events for sync with Jump
SETSYNC_LOCK_FINI dial events for sync with Jump
STARTSAP_PUPG < 1% Starts SAP system
SETSYNC_DOWN_FINI dial events for sync with Jump
GETSYNC_DOWN_FINI dial events for sync with Jump
REQJOBRES < 1% As of start release 45A:
Prompts you to schedule background jobs Reschedule background jobs, if necessary
EWIMPORT_UPG < 1% Imports authorizations into client 066 (EarlyWatch) EWTCH066.ELG

JOB_RASUVAR2 < 1% As of start release 40B:
Restore saved variants PASUVAR2.ELG
PASUVAR2.LOG

REQ_BBPCRM dial Prompts for post upgrade activities Prompts for post upgrade activities
SQLSCREXE_UPGDEL < 1% Performs actions for restart handling PARAMDEL.LOG
UPGPADEL.ELG
UPGPADEL.LOG

SQLDB_DDXTT_CONV_UC (var Cleans tables for unicode conversion DDXTT_CONV_UC.LOG

SQLDB_DDNTT_CONV_UC (var Cleans tables for unicode conversion DDNTT_CONV_UC.LOG

DMPSPC_END < 1% Saves database size after the upgrade DMPSPC_END.LOG

END < 10s No actions
ENDCHK < 10s Tests target version
UVERS_UP_END < 1% Changes the status in table UVERS
JOB_RDDDBSTA < 1% Updates database table statistics PDDDBSTA.ELG
PDDDBSTA.LOG

JOB_DRDOC_UPG < 1% For start releases up to 40B:
Adjusts documentation for the renamed data elements (executes report RADDRDOC) PADDRDOC.ELG
PADDRDOC.LOG

REQSTARTSRV dial For start releases up to 640:
Refers to note for installation of SAP start server Confirm
REQGENLD dial Prompts you to start transaction SGEN Confirm
REQ_SECU_MS dial Prompts to read note 821875 Confirm
JOB_CBUEPI < 1% CBU: Status update (support packages, addons CBUEPI.ELG
CBUEPI.LOG

REQFINCBU dial Prompts you to import additional CBU transports Confirm
JOB_UM4_FILL_RLOAD < 1% UCCNV: Fills TRDIR-RLOAD UM4_FILL_RLOAD.ELG
UM4_FILL_RLOAD.LOG

JOB_RSUCUPGR < 1% UCCNV: Cleans up UM4 objects RSUCUPGR.ELG
RSUCUPGR.LOG

CHK_POSTUP < 1% Displays P errors LONGPOST.LOG Correct P errors before you start production operation
SPAUINFO < 1% Displays information on adjusting objects with transaction SPAU Confirm
UEXPSPAU < 1% Exports any objects adjusted with transaction SPAU UEXPSPAU.ELG

RUN_RADCUCNT_NEW < 1% Generates the Unicode NTs from the inactive shadow NT RADCUCNTNEW.ELG
RADCUCNTNEW.LOG

REQ_UCCNV_OBL < 1% Info: Unicode Conversion needed (obligatory)
REQ_UCCNV_OPT < 1% Info: Unicode Conversion possible (optional)
JOB_UPGDELPROG < 1% Cleans up upgrade reports UPGDELPROG.ELG
UPGDELPROG.LOG

EVAL_STATS_EUIMP < 10s produce statistics from EUIMPORT phases EUIMPSTAT.LOG

SAVELOGS dial Copies upgrade logs to /usr/sap/trans/upgrade SAVELOGS.LOG
Choose between:
normal (important logs only)
all
none
EXITINFO dial Displays SAP Notes for post-upgrade activities Confirm
SAVEPRO < 1% Copies control files to /usr/sap/put/save SAVEPRO.LOG

UCMIG_STATUS_SET4 < 10s Set status for combined Upgrade and Unicode Conversion UCMIGSETSTAT4.LOG

SETSYNC_POSTUP_FINI dial events for sync with Jump
CREATE_UPGSTATS < 1% Stores the upgrade evaluation in the database for reference
STORE_UPGEVAL < 1% Stores the upgrade evaluation in the database for reference
SEND_UPGEVAL < 1% Prompts the user to send the upgrade evaluation
EXIT < 1% Ends SAP upgrade. Extracts statistical data.

--------------------------------------------------------------------------------

Explanations:

Phase restrictions:
Source release restrictions: As the phase list is component-independent, source release denominators always refer to the underlying technology component release, not to the specific component denominator you are upgrading.
This means that source release denominators 4.x to 6.x refer to the underlying component SAP Basis / SAP Web Application Server 4.x to 6.x.
Source release denominator 3.x refers to the release number of the component SAP R/3.
Component restrictions: The phase list is product-independent. There may be phases on the list that are not valid for the component you are upgrading.
Database restrictions: Some phases only run on certain databases. The following database name abbreviations apply:
DB2 NT/UNIX for IBM DB2 UDB for UNIX and Windows,
DB2/390 for IBM DB2 UDB for OS/390 and z/OS
...
Strategy restrictions: Some phases are upgrade-strategy-dependent.
Phases printed on gray backgroud are executed on the shadow instance.
Upgrade Phase Groups:
Strategy downtime minimized: System downtime ranges from group Downtime phases I to Downtime phases II (phase STARTR3_PUPG) only.
Strategy resource minimized: System downtime ranges from group Import and Modification Transfer (Phase EU_IMPORT1) to Downtime phases II (phase STARTR3_PUPG).

--------------------------------------------------------------------------------

Phase List generated on 2007/12/11 15:52:21
by SAPup version 7.00/1, build 23.054

How to Activate Session Trace.

2007-12-07T02:20:00.000-08:00

To Activate the Session trace, click on the highlighted button.

The results appear in the activity tab

How To enable STATTRACE in Java Stack

2007-12-07T02:10:00.000-08:00

Difference between STATTRACE and DSR
DSR will give time spent for the complete job, while STATTRACE will in a very detailed with detailed time spent in each of activity. So generally first a basic function is monitored using DSR. When something is noticed which has to be drilled down in detail, then STATTRACE is used to monitor in detail.

To enable STATTRACE in Java Stack, go to Visual Administrator and then go to the tab
Runtime -> Trace Config. Here activate the traces

Then go to the tab Application Tracing and restart the node to be traced in the “Maintenance Mode”.

The results can be viewed in the ABAP Stack in the tx Code ST03G

And the detailed result can be viewed in the Tx Code STATTRACE.

How to activate and evaluate SQL TRACE

2007-12-07T01:46:00.000-08:00

SQLTRACE

SQL Trace can be activated from the url ahttp://hostname:javaport/sqltrace.
In this page activate the sql trace for any node then stop the trace and evaluate.

To show the statistical data from JAVA stack in ABAP Stack (Tx ST03G)

2007-12-07T01:21:00.001-08:00

Distributed Statistical Records
Similar in the ABAP Stack it is called Work Load Analyzer (ST03 / ST03G)
To show the statistical data from JAVA stack in ABAP Stack (Tx ST03G)
The First Requirement is that
The Agent SAPCCMSR must be running
The Seconnd
The job SAP JOB FOR NONR3_STACK Job is running

(tips : All the jobs would be defined in the table TCOLL)

How to register CCMS Agent (SAPCCMSR) on JAVA stack for it to be monitored in the ABAP STACK?

2007-12-07T00:22:00.001-08:00

How to connect SAP Java to CEN system on the ABAP Stack
Where Java Stacks ends the data to ABAP Stack to be monitored in the CEN CCMS system, while in NWA data from ABAP Stack and goes to the Java Stack, it is there in the NW2004s (NW7.0). The SAPCCMSR are installed and registered in the JAVA Stack, this agents pushes the data to the CEN or into the Solution Manager. This program reads the data from shared memory of the JAVA Stack, where the data is populated by the J2EE engine. It is similar to the program SAPCCM4X in ABAP Stack.

Tx Code RZ21
1. Creating CSMREG User

2. Creating start file for CSMCONF Agent

3. Register the Username and Password in Visual Administrator
For Dispatcher -> Services -> Monitoring

4. Then Click on the register button.

5. If Visual Administrator fails to register the gent, the manually do it by using command at the bottom of the below picture.

6. Then check in the ABAP Stack, Tx. Code RZ21 (J2ee -> Engines) the node will appear.

Setting Up of Development Life Cycle in SAP Java Stack

2007-12-06T20:30:00.000-08:00

One of most important phase of Project Management in SAP Implementation project of late is implementation of Development LifeCycle.

http://help.sap.com/saphelp_nw04s/helpdata/en/25/4b84582fd041109e93a8028959e4b2/frameset.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/62ce5264-0e01-0010-a884-99c9d48c35f5#section10

SAP Java requires 4 Systems Landscape Architecture while ABAP requires 3 Systems Landscape Architecture, Why ?

2007-12-05T05:04:00.000-08:00

ABAP Stack require 3 System Landscape
ABAP requires 3 systems Landscape because ABAP modifies programs and moves them as a program to the consolidation for Testing. Since ABAP has both have Client Dependent and Client Independent data(s) and programs (cross client data consists of Programs and Data Dictionary), modification to such programs cannot be tested reliably in the same (development) system, which anyway would work correctly. So to simulate a production environment the changes need to be tested in Quality System. So an ABAP system would require 3 and not 2 systems landscape.

JAVA Stack require 4 System Landscape
In a Java stack the program are not moved alone, they are moved along with its other dependencies as a Software Component (jar, ear files). In the development system a user can copy the program and modify it and but would require a consolidation system for consolidating and building the application (Software Component). So a program is transported from Development System to Consolidation System. The Consolidation system will build the application. Once the software components are built they would be moved to Test System for Testing and finally to delivery System (Production System). Thus a Java Stack would require a 4 system landscape for a development Infrastructure.

In addition to these 4 Servers, there would be one more system which will host the Netweaver Development Infrastructure Application (NW + NWDI)

Development System -> Consolidation System -> Test System -> Productions System

Development : will have the modified Sources
Consolidation : Will consolidate the modified program from Development system and will be built as a Software component (jar File)
Testing : Software Component will tested here
Production : Productions System

Product -> Software Component -> Development Component -> Program

SAP NW 2004s Development Infrastructure
http://help.sap.com/saphelp_nw04s/helpdata/en/71/0369404c65587ee10000000a155106/frameset.htm

How to Patch SAP JAVA Applications ?

2007-12-05T02:45:00.001-08:00

This is deployed using the tools SDM. (/usr/sap/SID/instance/program/RemoteGui.sh) The default password for the SDM tool is “sdm”. In Offline Deployment, the Java instance has to be stopped before SDM is started while in online deployment it can be deployed online.

Sometimes the files come with the extension filename.sca.zip just rename the file as filename.sca (or sda) and then deploy.

JAVA Application Server sometimes requires SAPINST tool to apply the patches, Then
1. Stop all instances of SAP except the CI
2. Deactivate all server process except one (server0 should alone be active)
3. Make the instance in SAFE mode from Config Tool.
4. Start Patching using the sapinst tool, possibly by keeping the instance in SAFE Mode.
5. Start Patching the Java application in CI.
6. Start Patching applications for other server nodes.

How to Patch SAP J2ee Stack ?

2007-12-04T23:43:00.000-08:00

1. Read the release notes of packages and do the home work (very Important)
2. Download the Support Packs from the SAP Market Place
2.a. CTRLSAPDBnn_0-20000nnn.SAR
2.b. J2EERTnn_0-20000nnn.SAR
2.c. J2EERTOSnn_0-20000nnn.SAR
2.d. SAPINSTnn_0-20000nnn.SAR
2.e. SAPCAR (optional, but necessary because what you have might not be the latest)
3. Create a Temporary File System, and
4. Extract SAPINST* and CTRL* SAR Files
5. Extract OS Independent (J2EERTnn_0-20000nnn.SAR) and apply First and then extract the OS Dependent Files and apply. The Order is important.
6. J2ee Engine patching would either be required to be done by sapinst or by SDM or JSPM tools. The details will be mentioned in the release notes.
7. First patch the Central Instance, when you run the sapinst
a. The patching should be done first for the Central Instance
i. The Option “Import Support Package nn”, when you run the sapinst.

b. Only then patch the Dialog instance
1. Choose the option “Support Package nn – Dialog Instance Update”

6 Restart the j2ee engine.
7 Check the status from the URL http://hostname:javaport/ -> “System Information”

Important UME logs and Locations

2007-12-04T22:40:00.001-08:00

Files at Operating System Level:
- Security Logging : Contain important security events (like failed user logon attempts, changes to users and authorizations, etc.)

Storage Locations : /usr/sap/SID/j2ee/cluster/serverX/log/security.log

- Trace Files
The file contains trace information for the entire server, UME libraries and the UME provider. The information in the file is very detailed and contains exceptions, warnings and debugging information.

/usr/sap/SID/j2ee/cluster/serverX/log/defaultTrace.#.trc

Log Configuration Services in the Visual Administrator can be used to increase severity of the traces for further debugging.
Visual Administrator -> Cluster -> Server -> Services -> Log Configurator
Select Security logging or Tracing Settings

How to add a new Server Process to a Java Instance ?

2007-12-04T21:59:00.000-08:00

A server process is added to scale up your Java Instance. In an ABAP+JAVA stack combined (java add-on to ABAP stack) installation, it is not possible to install java stack (individually, without ABAP stack) in any instance or in any host. So any additional instance of Java Stack can only be installed as an add-on to a fresh ABAP stack .i.e. both have to be installed together. For scaling up java stack a further server process can be added, BUT ABAP stack alone, without JAVA Add-on, can be installed.

Start the SAP‘s “Config Tool”
Identify the instance where you have to add Current Instance -> Select the Option “Server” -> “Add”

How to Activating emergency user (Super Administrator User (sap*)) in JAVA Stack

2007-12-04T21:25:00.001-08:00

Go to Config Tool -> click on the button “Switch to configuration edit mode”
Expand the tree :-
“Cluster_data -> Server -> cfg -> Services -> Propertysheet com.sap.security.core.ume.service”

When the “Super Administrator” parameter is activated to true and the password being reset, all other users will locked.
Set the parameters
ume.superadmin.activated = true
ume.superadmin.password = a new password

Restart the Java Cluster...

Logon as sap* and new password, correct the problem. then revert the change made to the parameter ume.superadmin.activated to false and Restart the Java Cluster.

SAP JAVA Add-on Installation Error

2007-12-04T05:10:00.000-08:00

Problem:
During Installation of SAP Java Add-on in an ABAP+JAVA SAP Installation on a Windows Platform, the below error is quite common.
Error:
ERROR 2007-12-04 12:09:34
FSL-02107 Path component contains reserved character ('"'): "G:

ERROR 2007-12-04 12:09:34
FSL-02106 Path contains reserved character ('"'):
"G:\usr\sap\SID\

Solution :
Run REGEDIT from
1. Check for the entry “G:\usr\sap\SID\” in the REGEDIT and remove the ‘”’ (quotes).
2. Expand the Tree (My Computer -> HKEY_LOCAL_MACHINE -> ControlSet001 -> Services -> SAPSID_nn (SID = System ID, nn=Instance Number)
3. Change the values “G:\usr ...” by removing the ‘”’ Quotes.
4. restart the Installation.

Basic SAP NetWeaver Installation Steps (NW 640)

2007-12-03T23:01:00.000-08:00

1. Before that download the installation guide from the http://service.sap.com/instguides and read it properly before the installation is started.
2. Prepare the OS as described in the installation Guide.
3. Install ABAP Central Instance (CI)
4. Install Database (chose the number of parallel process at an optimal level (which can be maximum up to 8, default is 3). It depends on the system resources (processors and memory in the Server).
5. Install additional Dialog Instances ABAP
6. Client Creation (using Tx Code SCC4) (UID/Password : sap* / pass)
7. Client Copy from 000 to a new client. (There will only be 2 clients initially after a fresh installation. 066 and 000).
8. Install an Add-on Java to Central Instance (CI) to the newly created client (java has no client concept in JAVA Stack), here it will install the Central Service (CS) instance (MS, ES) and also will install Dispatcher, Server process and SDM.
9. Install Add-on Java to other ABAP Dialog Instance (It will install only Dispatcher and Server process) also note that only one Server process (server0) will created when the instance is initially installed, for scaling up a new server process (server1) can be added separately after installation.
10. Decide on the Option of User Management, it could be either centrally or distributed.
Central – can be handled in the ABAP stack. (using Tx Code SU01 / PFCG) and distributed would use Java’s User Management Stack (UME) for user management.
11. Changes to JVM parameters to the Java Stack (dispatcher, server process(es)) are made after installation. The first step in the post installation steps is to run the template Configurator. It will set the SAP recommended JVM parameters setting for Java Stack.

Template Configurator is found in the path :
(/usr/sap/SID/SYS?global/TemplateConfig/cfgtemplategui.bat) or http://hostname:javaport/nwa -> Deploy and Change.
It is done individually for each of the instances immediately after the ABAP installation.

Is it possible to add a Java Stack alone, without ABAP in a ABAP+JAVA installation scenario. ?
In an ABAP+JAVA stack combined (java add-on to ABAP stack) installation, it is not possible to install java stack (individually, without ABAP stack) in any instance or in any host. So any additional instance of Java Stack can only be installed as an add-on to a fresh ABAP stack .i.e. both have to be installed together. For scaling up java stack a further server process can be added, BUT ABAP stack alone, without JAVA Add-on, can be installed.
A new Server process can be added by Logging into “ConfigTool” "Current Instance" -> Select the Option “Server” -> “Add”

Difference in 6.40 and 7.00 installation steps.
In 7.0 we have to choose a particular installable component during initial steps based on the Client requirement (installation scenario). ie. If the client’s requirement is of installing EP, the nEP alone will be selected for installation. Since EP requires only NW Java Stack, it will install only Java Stack with EP component. Further it will combine CI and DB installation in one step, while 6.40 had two separate steps for CI and DB installation. In ABAP+JAVA Stack installation, In NW 7.0 it will automatically create three clients 000, 066 and 001 and java stack will be automatically added to 001 client. While in 6.40 ABAP will be installed first then a fresh client has to be created and then JAVA stack is installed as an add-on to the fresh client.

Kindly note that In 7.0 after installation if the Client to which Java Stack is added as an add-on, has to be changed, then it is possible by making a few changes. The changes can be made by using Visual Administrator to change the Client Number.

SAP Startup Process

2007-12-03T04:52:00.000-08:00

In ABAP stack Startup sequence.
The Startup script will start the sapstart binary which will read the start profiles (/usr/sap/SID/SYS/profiles/START_INSTANCE_HOSTNAME) and get all the information like Hostname, System Name (SID), instance number.
Once the information are available the script will start the dispatcher which in turn will read the install profile and starts the server like, Database, Message Service, Enqueue Service, Dispatcher Service. The dispatcher in turn will start all the Work Process Services.

Java Startup process. (JCONTROL and JLAUNCH :- JControl starts JLaunch)
Sequence
1. Database is Started : Database must be operational before SAP is started.
2. Central Services is Started : Java Central services which includes the message service, enqueue service are started.
3. Central Instance is started : Now the Java Central Instance which includes the services like Dispatcher, Server process and SDM is started by “Start and Control Framework”

The Start procedure in the Startup and Control Framework
3.1 JControl is started by the startup script.
3.2 JControl creates a connection to the message server (on the CS).
3.3 JControl starts a Java Instance bootstrap process with parameters that are defined in the file bootstrap.properties (/usr/sap/SID/instance/j2ee/cluster/bootstrap). The bootstrap process synchronize all required binaries for the Java Nodes from the database with the file system. This is necessary, since the Class Loading is performed using the file system in the Java environment. The database always contains the current (deployed) binaries and properties and distributes these to every java node when starting.
3.4 The java instance bootstrap process reads the instance description from the java schema of the database.
3.5 The java instance bootstrap process stores a file instance.properties, containing the instance description, at operating system level.
3.6 JControl start the instance description from the file system.
3.7 JControl starts the specified bootstrap processes for java nodes. Then JControl starts all java nodes such as dispatchers and servers as JLaunch processes and, when doing so, loads a JVM in the JLaunch process.

--->>> If an ABAP instance is started with an additional Java Instance, the ABAP dispatcher uses a signal from the ABAP dispatcher process to run a start command on the Startup and control Framework.

Every time Java instance is started it will create a instance.properties file ( /usr/sap/SID/instance_name/j2ee/cluster/instance.properties ), which is used for synchronizing the information with the database. The instance profile contains A service called Jcontrol will start initially which in turn will start Jlaunch process. There would be as many as jlaunch processes as many there are server process like dispatcher process, Server process, SDM. For each instance it will start one jcontrol and atleast 2 jlaunch process (dispatcher and Server process).

Central services (Message Service and Enqueue Service) are not started by jcontrol process. Java’s instance profile is not used for any configuration, here the configurations are done in services which are modified by either tool called “Configtool” or “Visual Administrator”.

4. Java Additional Dialog instances are Started : Other Dialog instance is started here.

SAP's Lock Concept

2007-12-03T04:50:00.001-08:00

In an Update request the data is changed for an entire SAP LUW (Logical Unit of Work), which are either carried out in full or not al all. An LUW can consist of multiple Transaction screens. So LUW can modify and update data consisting in multiple database objects (rows and tables), i.e. SAP’s LUW can result changes in many database objects. Sometimes only a few fields might be affected, so it might be required to lock only those affected fields, while rest of the fields can be used by other users. So therefore SAP has come out with its own Lock Concepts which can lock an object. An object in turn can lock a series of Database objects spread over many row and tables in the database level. Eg. When a User Master data is modified the data may affect more then one table in the Database Level, but Database can lock only at record level or a table level on one table. But SAP Locks will lock the entire object which could be spread over rows in all the affecting (here two) tables. The database lock exists only for the duration of the database LUW, in which the changes made in the SAP system are actually updated. And the SAP Lock is released once the LUW is commited or rolled back when the LUW is cancelled.

Why two different Enqueue Services for Java and ABAP.
Since SAP uses two separate schemas at the database, one each for ABAP and Java Stack. Data is saved is separately for ABAP and Java Stack. So enqueue process (locked objects) for Java would not interfere with the enqueue process (locked Objects) of ABAP stack.

SAP WEB Dispatcher

2007-11-30T03:14:00.000-08:00

The SAP Web dispatcher is used for ‘Load Balancing” and as a “Software Web Switch”, in a SAP system with several SAP NetWeaver Application Servers for Web applications. It lies between the Internet and SAP system in the DMZ. It is the entry point for HTTP(S) requests into the SAP system, which consists of one or more Web application servers. As a "software Web switch", the SAP Web dispatcher can reject or accept HTTP connections. When it accepts a connection, it balances the load to ensure an even distribution across the servers.

Planning : Sizing a SAP WEB Dispatcher
Memory usage for internal tables
-> Server tables
->> Holding information about connected servers
->> Usually very small (90 kBdefault, few MB for very large system)
-> Connection tables
->> Holding information about the open connections
->> concurrent_conn= (users * req_per_dialog_step*conn_keepalive_sec)/ (thinktime_per_diastep_sec)
->> mpi/total_size_mb= (concurrent_conn* mpi_buffer_size)/(1024* 1024)
->>> Default: mpi_buffer_size= 32kB
->>> Default: mpi/total_size_mb= 500
->End to End SSL table
->>1.8 MB for 10.000 entries

Installation Steps
Media for the web dispatcher is provided with the J2EE kernel:
"/usr/sap/SID/Central-Instance/exe/sapwebdisp"
"/usr/sap/SID/Central-Instance/exe/icmadmin.SAR"

1.Download kernel files from SAP service market place

2.Extract kernel using
$ mkdir /tmp/sapwebdisp
$ cp dw_??_########.SAR /tmp/sapwebdisp
$ cd /tmp/sapwebdisp
$ sapcar –xvf dw_??_########.SAR (disp+work Package)

3.Copy the sapwebdisp and icmadmin.SAR files to a directory on what is to be the Web Dispatcher host.
$ mkdir /usr/sap/sapwebdisp
$ cp /tmp/sapwebdisp/sapwebdisp /usr/sap/sapwebdisp/.
$ cp /tmp/sapwebdisp/icmadmin.SAR /usr/sap/sapwebdisp/.

4.Extract the icmadmin.SAR file into that directory using the command
$ sapcar –xvf icmadmin.SAR

5.Generate an initial profile for the Web Dispatcher by running the command
$ ./sapwebdisp –bootstrap

6.Start the web dispatcher with
$ cd /usr/sap/sapwebdisp
$ ./sapwebdisp pf=sapwebdisp.pfl –auto_restart

Profile Parameters
These are the most basic profile parameters

->SAPSYSTEM
->>Must be unique on the host and must be in the range between 0 –98
->>Used to distinguish shared memory segments of different SAP WebDispatchers on the same host
->rdisp/mshost
->>Hostname of the host where the message server is running (in case of double stack installation the ABAP MS has to be used)
->ms/http_port
->>Port of the message server
->wdisp/auto_refresh
->>Time to refresh internal routing tables
->icm/server_port_0
->>protocol and port where the dispatcher is listening for incoming requests
->icm/http_admin_0
->>Configuration of admin access

link :
http://help.sap.com/saphelp_nw70/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm

Sending faxes from SAP

2007-11-29T20:57:00.000-08:00

In continuation to my blog on Bar Code Printing from SAPGui. I 'm forwarding similar setup on sending faxes from SAP, written by a fellow SAP Basis Blogger, here is the link.... For a simple setup
http://sap4basis.blogspot.com/search/label/Sending%20faxes%20from%20SAP

Please also take note that the E-Mail communication (my blog on SMTP configuration) can be used to send faxes as well using SMTP. It requires no other configuration except that the fax numbers have to saved in a particular pattern. Pl refer the URL..
http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm

CONFIGURATION SENDING MAILS FROM SAP

2007-11-26T22:29:00.001-08:00

The Details that are required before configuration.
1. SMTP Mail Server Domain Name
2. SMTP Port Number (usually 25).
It is required to configure SAPconnect settings for every client that is used for send processes (E-mails, Faxes, SMS).

Step No 1
 Go To Tx Code SCOT
1. Enter the Value for Default Domain
Under Settings -> Default Domain, define the domain of the SAP system
client. This allows for the following to take place:
1.1* The SMTP plug-in logs on to the mail server using the domain as ID.
1.2* The message ID of the outbound e-mails is assembled with this domain.
1.3* If an SAP user who does not have an Internet mail address sends an e-mail, a sender address consisting of the SAP user name and this domain is generated.

 Choose the Menu Option
Views -> Nodes -> in the subsequent screen, expand INT -> double click on SMTP

Step No 2 In the Subsequent Screen… enter the following informations.
 How often the Mail should be sent. (mostly every 5 minutes)
 Check the “checkbox” “Node in use”
 Enter the “SMTP Mail Server Host Name”
 Enter the SMTP Port Number (usually 25).
 Click on the button “Set”.

Step No 3 In the Subsequent Screen… enter the following informations.
Address Areas :- To which all address (domains) the mails can be sent.
“*” means emails can go to any E-Mail Addreses, while *hcl.in
means the mails can go to only to users in the hcl.in domain

Step No 4
 Go to the menu option
View -> Jobs
In the subsequent Screen, Click on the Create Button

Step 5
In the subsequent screen, enter some job name.

Step 6 In the subsequent screen, Click once on the “SAP&CONNECTALL” and double click on the button “Schedule Job”.

Step 7 In the subsequent screen
 Click on the Button “Schedule Periodically” and select how often the Background job should run (mostly every 5 minutes)
 Click on create button

A new node will appear in the Jobs screen.
In Tx Code SM37, check whether the New Job, is scheduled or not.

Split Mirror Backup in SAP

2007-11-25T01:29:00.000-08:00

For large global organizations spanning operations in many countries, a robust Information Technology Infrastructure supporting 24x7 365 days a year has become absolutely necessarily. Non-availability of Information Systems for however short time would cause these organization losses in Millions. The loss of Data due to system failures would even result in closure of these organizations. In such a scenario it is become absolutely necessary to not only have a mechanism to efficiently take Backup of the systems but also to be able to do it without any downtime and performance degradation.

The Split-Mirror technology helps in achieving High Availability of Database, by letting a system quickly take backup, typically in seconds, and it also helps in eliminating the use of System Resources of the Database Server for backing up the database, thus efficiently avoids System degradation (often experienced) while Backups are running.

The Split-Mirror, as the name suggests, is achieved by splitting the Mirror at the Storage (SAN) Subsystem level. Typically this is possible if RAID 10 is configured for storing Data of the Database Server. The tape Backup can be initiated from secondary disks by an agent running in a separate Backup Server. The mirrored disks are resynchronized after the Backup is completed.

In the split mirror configuration, the disks of the production database host are mirrored, that is, synchronized. BRBACKUP runs on a backup database host, where the backup is performed after the mirror disks have been split and mounted. On the production host, this saves processing power otherwise required for the backup, so that the production SAP System is unaffected by the backup.

BRBACKUP can be used to control the splitting and later synchronization of the disks. If you want to open the database on the backup host and use it as a "reporting server" you can perform the synchronization yourself later. The actual splitting and later synchronization of disks is executed by a script or program supplied and supported by the manufacturer of the operating system, disk subsystem, or backup software.

If the split disks do not have to be resynchronized immediately after the backup you can use the backup server along with the mirror disks to operate an independent SAP system on the backup server. For this you must install the entire Oracle server software on the backup server.

Typically the steps are like.

Backup Steps:
1: BRBACKUP connects to the production database on the R/3-Server to set the tablespaces to backup mode (ALTER TABLESPACE ... BEGIN BACKUP). Thus the database is only consistent with the offline redo log files which were created during the begin backup – end backup period.

2: BRBACKUP invokes a script to split the mirrored disks identified by the split_cmd parameter.

3: The split-script includes all actions necessary to access the disks (secondary volumes) with read/write-option set on the Backup-Server (e.g. file system check and mount).

4: BRBACKUP connects to the production database on the R/3-Server to take the tablespaces out of backup mode (ALTER TABLESPACE ... END BACKUP).

5: BRBACKUP does the backup of the tablespaces/data files defined by the parameter
backup_mode (e.g. backup_mode=all for a full database backup) directly on the Backup-Server.

6: Optionally, BRBACKUP invokes a script to resynchronize the mirrored disks identified by the resync_cmd parameter

Please refer,
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
http://help.sap.com/saphelp_nw2004s/helpdata/en/68/b72d86db13c642bb6e17b83b75f598/content.htm

Shell Script for Checking whether SAP is Up or not

2007-11-23T01:51:00.001-08:00

Wonder how would you check whether the SAP is up or not from Unix Shell Script. Here is a small shell script which uses the Enviornment variables and some files to check whether the SAP is runnig or not from the Operating System.

It can be automated and the output message can be used for sending as an Alert. It could be modified to suit any Landscape. In this case the command for running the script is "$/usr/bin/checksap.sh SID"

#!/bin/ksh
################################################################################
#
# /usr/bin/checksap.sh
# UNIX Shell Script for Checking
# 1. Whether SAP Has Started or not
# is found by checking whether kill.sap file exists or not
# and if it exists, whether the PID recorded in the file is live or not
# 2. Whether DB has started or notA
# is found using the Command R3trans -d
# 3. Whether SAP is able to detect the Message Server or not
# (important for Applicateion Server Test
# Creation Dated : 23/11/2006
# Authored by : Biju Kumar
#
################################################################################
__time=`date` ;
__date=`echo $__time | awk '{ printf "%s",$3$2$6"/"$4 ; }' ;`;
__variable='';
__variable1='';
SAPSYSTEMNAME=$1 #### 'D20';

LOCAL_FILE_NAME=`echo /usr/sap/${SAPSYSTEMNAME}/D*/work/kill.sap`;
my_SID_USERNAME=`echo ${SAPSYSTEMNAME}adm | tr '[A-Z]' '[a-z]'`
APPLICATION_SERVER="true" # Notes whether the SAP System has Application Servers or not ?

MY_PROC_LIST="";
MY_SAP_RUNNING='';
if [ -f $LOCAL_FILE_NAME ];
then
MY_PROC_LIST=`cat $LOCAL_FILE_NAME | awk '{printf $3}'`;
MY_SAP_RUNNING=`ps -p $MY_PROC_LIST | grep 'sapstart' | awk '{printf $4}'`;
fi;

MY_DBSERVER='true';

MY_DB_STR="";
if [ $MY_DBSERVER == "true" ] ;
then
MY_DB_STR=`su - $my_SID_USERNAME -c "R3trans -d" | grep "R3trans finished"| awk '{printf $3}'`;
fi;

__variable1='';
if [ $MY_DB_STR == "(0000)." ];
then
__variable1="$__time DB Inst Running";
else
__variable1="$__time DB Inst Not Running";
fi;
__variable=$__variable" "$__variable1;

MY_ARGUMENT=`ps -ef | grep dw.sap | awk '{if (NR==1) printf $9}'`

if [ $APPLICATION_SERVER == "true" ];
then

my_var=`su - $my_SID_USERNAME -c "lgtst $MY_ARGUMENT" | grep "list of reachable "`;

if [ -z $my_var ];
then
__variable=$__variable", CI Not Running ";
else
__variable=$__variable", CI is Running ";
fi;
fi;

__variable1="";

if [ -f $LOCAL_FILE_NAME ]; #### -a [ $MY_SAP_RUNNING == "sapstart" ];
then
if [ $MY_SAP_RUNNING == "sapstart" ];
then
my_start_time=`ls -lt $LOCAL_FILE_NAME | awk '{ printf "%s",$7"-"$6"-2006 "$8 ; }' ;`;
__variable1="SAP Inst has started at $my_start_time /$__date";
fi;
else
__variable1="SAP Inst has not started /$__date";
fi;

__variable=$__variable", "$__variable1;
echo $__variable ;
##### It can be added to crontab, and scheduled to run maybe every 5 minutes. #####

SAP not starting because of database Error

2007-11-21T02:55:00.001-08:00

Problem: SAP was not starting, because the dispatcher work process was unable to connect to the database.

Observations:1. Found in the dispatcher log (disp_dev) that all the Work Process were getting killed.
2. Ran R3trans –d and found that the log showed the error

4 ETW000 [dev trc ,00000] Logon as OPS$-user to get SAPSID's password 68 0.066880
4 ETW000 [dev trc ,00000] Connecting as /@SID on connection 0 ... 28 0.066908
4 ETW000 [dev trc ,00000] Allocating service context handle 30 0.066938
4 ETW000 [dev trc ,00000] Allocating server context handle 25 0.066963
4 ETW000 [dev trc ,00000] Attaching to DB Server SID (con_hdl=0,svchp=025EA574,svrhp=025EB17C)
4 ETW000 70 0.067033
4 ETW000 [dev trc ,00000] Assigning server context 025EB17C to service context 025EA574
4 ETW000 40583 0.107616
4 ETW000 [dev trc ,00000] Allocating user session handle 56 0.107672
4 ETW000 [dev trc ,00000] Wed Nov 21 12:19:55 2007 227 0.107899
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=025EA574,srvhp=025EB17C,usrhp=025F3948)
4 ETW000 39 0.107938
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 7285 0.115223
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 34 0.115257
4 ETW000 [dev trc ,00000] Try to connect with default password 95 0.115352
4 ETW000 [dev trc ,00000] Connecting as SAPSID/@SID on connection 0 ...
4 ETW000 29 0.115381
4 ETW000 [dev trc ,00000] Assigning username to user session 025F3948 20 0.115401
4 ETW000 [dev trc ,00000] Assigning password to user session 025F3948 29 0.115430
4 ETW000 [dev trc ,00000] Starting user session (con_hdl=0,svchp=025EA574,srvhp=025EB17C,usrhp=025F3948)
4 ETW000 35 0.115465
4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000 8428 0.123893
4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000 32 0.123925
4 ETW000 [dblink ,00419] ***LOG BY2=>sql error 1017 performing CON [dblink#1 @ 419]
4 ETW000 145 0.124070
4 ETW000 [dblink ,00419] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#1 @ 419]
4 ETW000 29 0.124099
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'SID'"

3. When tried to logging into sqlplus “ / as sysdba” from command prompt using the userid (adm), it gave the following error “Insufficient Privileges”

4. Found that the parameter
SQLNET.AUTHENTICATION_SERVICES = was having the value “(NONE)” in file “sqlnet.ora” Parameter file.

5. Changed the parameter to SQLNET.AUTHENTICATION_SERVICES = (NTS), since then it started working

Steps to Configure Bar Code Printing from SAP for SAP Basis Consultants

2007-11-20T22:10:00.001-08:00

1. Download barcode.dll file from website http://www.e-bizco.com

2. Install the barcode.dll file in the system, by either running the Setup program or copying the barcode.dll file in the directory where saplpd.exe (SAP Printer Daemon) File exists or in the Windows directory (c:\windows or c:\windows\system32).

3. Check whether the SAP Printer Daemon (SAPLpd) is sensing barcode.dll file or not by starting the SAP Printer Daemon. It will show in the log.

4. Configure Front End printer using the Transaction Code : SPAD
a. with Device Type “SWIN” or a copy “ZSWIN”

b. Access Method “F: Printing on Front End Computer” or “S: Print Using SAP Protocol”

6. Test the printer by printing the Bar Code, whether it works or not ?

7. If you get some Extra text "bC=PSN9,B=65,H=3,A=0,D=" in the printout in place of the Barcode.

Then the reason is because some R/3 releases have a broken device type SWIN. Please copy SWIN to ZSWIN and change the print control SBS01: The text field shall be empty. Atributes "Extended" and "Converted" are OK.

8. Other Errors, please refer the URL
http://www.e-bizco.com/english/support.phtml

JCOProxy Error: and the Solution

2007-11-18T22:27:00.001-08:00

Problem:
When we tried to connect SAP R/3 System (Ver. 4.7) from xMII server, we were getting the error “Fatal Error: JCOProxy error: User not authorized. Session terminated”. The error continued to happen despite entering the correct user name and Password. The user ID, which was used to connect, was having the profiles “sap_all” and “sap_new”.

Screenshot of the Error.

Reason:
The SAP backend system (SAP R/3 4.7) is a Web Application Server (WAS) of version 6.20, and it converts the password into UPPERCASE. Therefore all passwords in lowercase were failing in RFC, which got resolved by changing the Password to UPPERCASE.

Resolution:
The issue was resolved by entering the password to UPPERCASE.

How to Solve Oracle Error ora-1114 in SAP Instance using brtools

2007-11-18T06:45:00.000-08:00

Steps would be like
1. Log into each of the SAP DB Servers thru Telnet
2. login as ora
3. goto all the /oracle/SID/sapdata? FS
4. Check whether these FS have Temp Data files created in these Directory
5. check the Free Space left in the FS using the command
5.1 $ cd /oracle/SID/sapdata??
5.2 $ bdf . in Unix
5.3 $ df -k . in Unix & linux

6. Check the Size allocated to the Temp files
6.1 $ ls -lt ./temp_?/* replace ? with the actual number.

the value will be in bytes and not in KiloBytes. so divide this value (8589934592) by 1024 to convert the value into Kilobytes.

7. Check the space currently used by the Temp Files.
7.1 $ du -sk ./temp_2/*

8. So the temp data file can maximum grow, as in this example, to the size 3,817,552+324,960 KB
but the datafile created is sized (8589934592 / 1024) KB = 8,388,608 KB

9. if the Temp Data file size in the FS is more than free space left.
i.e.
if 8,388,608 KB > (3,817,552 + 324,960 - 317,440) KB
then resize the Temp date File to 3,817,552 + 324,960 - 317,440
where the 3,817,552 is the current used by the Temp File
324,960 is the free space left in the mount point
317,440 Min Free space required in the Mount Point for OS.

so resize the the Temp file to 3735 MB (3825072 KB / 1024 => 3735 MB)

10. Check whether the Temp Table Space is being used or not
$brtools
2 - Space management ->
7 - Additional space functions ->
1 = Show tablespaces ->
5 ~ Database tabelspace (tablespace) . [PSAPTEMP]
press "c - cont" -> "c - cont"
The space in the Temp table Space must not have been used.

11. Resizing the Data File, please use brtools
$brtools
-> 2 - Space management
-> 5 - Alter data file
-> 3 ~ Alter data file action (action) . [resize]
-> 4 ~ Tablespace names (tablespace) ... [PSAPTEMP]
-> 5 ~ Data file names (file) .......... [/oracle/AEM/sapdata10/temp_2/temp.data2]
press "c - cont" -> "c - cont"
-> 7 ? New data file size in MB (size) ......... [3735]
press "c - cont" -> "c - cont"

to confirm the corrections, do the same checkes which are listed in steps from 5-9

12. Add a new Temporary Data File in a separate file system of a reasonable Size.

Daily SAP Server Monitoring Transaction Codes

2007-11-18T05:06:00.000-08:00

SM50 All WP should be either in Waiting or Running condition
OS01 _______ number of presentation server
_______ number of Application Servers

SICK Look for No errors (If any rectify)
ST06 CPU User Utilization _____
System Utilization _____
CPU Idle _____
User + System CPU Utilization should not exceed 65%

Load Average ___ Number of waiting for CPU should be <= 3
Pages in/second ___ Should be less(<=) 5%

Physical Memory Available _______
Physical Memory Free _______ Should be >20% of Physical
Memory
Check that the Disk Queue Length does not exceed 5 by performing the following:
Click the ‘Detail Analysis Menu’ button.
Previous Hours
Disk Review the Queue Length
Page file Ensure PageFile Utilization < 10%

ST03 Click ‘This Application Server’ -> Last Minute Load
Enter ’120 minutes’.
Avg Response Time (<100000 ms Bkg, 2,000ms Dia/Upd)
Bgd:_____ Dialog: _____ Upd: _____
Avg Wait Time (<5% Response Time, waiting on WP)
Bgd:_____ Dialog: _____ Upd: _____
Avg Load Time <5% response Time)
Bgd:_____ Dialog: _____ Upd: _____
Avg Roll Time (<10% Response Time)
Bgd:_____ Dialog: _____ Upd: _____
Avg DB Request Time (<50% Response time)
Bgd:_____ Dialog: _____ Upd: _____
Avg CPU Time (<30% response time, 60% bkg OK)
Bgd:_____ Dialog: _____ Upd: _____

AL16 (or Via ST06)
OS Alerts: _______
Worst Queue Length: _______
Error/Collisions: _______

ST07: Number of Users – Logged in : _______
Active: _______
In a Work Process: _______
SM12 Look for any ‘old’ locks
(Clear ‘user name’.’no lock entries found’ desired, other list here. _________
SM37 Ensure no jobs have been cancelled/abended
(clear ‘user name’ ands ‘job name’, then insert * in each of these, and in ‘Job Status’ tab, select only ‘Canceled’)
SP01 Ensure that no print jobs is waiting for more thab an hour (* in ‘Created by’):
ST04 Data cache % Quality Hit ratio >96%
Procedure cache % Quality Hit ratio >96%
ST02 In the SWAPS Column, ensure nothing is displayed in ‘red’,
or note : ______
DB02 Size (Total) of Database :
Used :
Should be less than 85%
Otherwise increase TableSpace