• During EHP7 upgrade going on production system whether we will be able to move the transport request into production? 

• As when we did the EHP7 upgrade testing during that time Initialization, Extraction, Configuration, Checks and Preprocessing taken 21days how we can reduce this as we have chosen standard installation and not advanced installation. As we don’t want to have business impact for performance during EHP7 upgrade going that’s why we have chosen standard installation so that it will utilize minimum resources. And also whether business will function as normal during EHP7 upgrade going during pre-processing phase?

• As we are taking daily production backups whether we will still be able to take the production backup during EHP7 upgrade is going on? If yes, then whether it will be possible we can restore this backup just in case if we have any problem during pre-processing going on. And we don’t want to have business data to be in risky situation without backups.

• And also we have DR for our production system whether we can still continue replicating the logs files on DR server during EHP7 upgrade going on? Or we will have to stop the DR during EHP7 upgrade started? Or we can stop DR only during actual downtime or execution phase when shadow instance will overwrite the actual system.

• And also just in case if something goes wrong during upgrade going as it is creating shadow instance and all the changes are in shadow instance is it possible to remove the shadow instance or undo the EHP7 upgrade?

• And also after upgrading our test system to EHP7 after running SGEN we got syntax error for 421 objects. Do we will have to fix this before we can release the system for functional team testing?

• And also we have 4 application servers configured for our ECC6.0 production system with MaxDB as database and we will like to run EHP7 upgrade only on CI system and not on application server. So whether there will be any problem if we don’t use application server during EHP7 upgrade going?

Hi,

We have a "problem/doubt" with the spau, we have "reset to original" one obsolete note and we have added this step to an order.

The problem is  this note is not implemented in the next system (integration), but we have added the "reset to original" step to an order.

The question is if this order will be problematic in the transport to the integration system because the note is not implemented in that system, only in the development system.

Thanks in advance.

Hi all,

We are experiencing a serious problem in our SAP Combined Upgrade and Unicode Conversion.

We are upgrading SAP R/3 4.7 systems to ECC6 EHP7 SPS07.

And in the meantime, we convert the database in UNICODE.

- The UNICODE preparation steps are all OK (SPUMG and so on).

- The upgrades steps are all ok (shadow and offline upgrade steps).

But when we export/import the database to convert it in UNICODE, we get duplicate keys in EKPO table at import step, which make the SWPM unable to create the primary index.

The fact is that EKPO table does not seem to get any problems in the source system.

We tried SAP Notes 2007272 and 2144285 without any result.

Any ideas please ?

Best regards,

Stéphan

Source system:

OS: Microsoft Windows 2003 Server 64 bit

DB: MSSQL 2005 64 bit

SAP: ECC6 SR2 dual stack

Kernel SAP: 700_REL UC 64bit

SAP_BASIS - 700 - 0026

SAP_ABA - 700 - 0026

PI_BASIS - 2005_1_700 - 0018

SAP_APPL - 603 - 0005

Target system:

OS: Microsoft Windows 2003 Server 64 bit

DB MSSQL 2008 64 bit

SAP: ECC6 SR2 dual stack

Kernel SAP: 700_REL UC 64bit

Same support package level

In order to perform a system upgrade, i've chosen to execute an homogeneous system copy as first step that leads me from MSSQL 2005 to MSSQL 2008 without changing the Windows platform neither the SAP kernel (these steps will be executed later).

As MSSQL 2008 is supported (PAM document clearly explain that), i've chosen to perform an homogeneus system copy instead of a MSSQL upgrade.

I'm using an old sapinst version, the same used to execute the export and the installation of the system, as the sap system still runs on 700_REL pl 353 unicode version 64bit kernel. Following the SAPinst version used:

SAPinst GUI

Version: 701.06.3

On a Windows 2003 server 64bit, i've correctly installed MSSQL 2008 R2 64bit taken from VBS script provided on disks 51044827 from the Marketplace.

During the import process, i'm facing a message from sapinst, which defenitely stops the process due to incompatibility version of MSSQL. Following the message received:

The MS SQL Server version 10 is not supported for the installation of this product. Use appropriate MS SQL Server version.

As i've checked the PAM before starting the import phase, i'm wondering why the MSSQL version is wrong. And if it's not a MSSQL version problem, what's the component that is raising an incompatibility issue?

Does anyone help me suggesting the right direction?
Kind regards
Massimo Solleretto

Hi,

We are planning to update ECC 6.0 SP25 to EHP7 SP7.

While generating stack file for EHP7 upgrade in solution manager 7.1 SP10 maintenance optimizer, system automatically selects only "Central application" Group.

We have query about this component selection during stack file generation.( Please see attached image)

1. Should we go with default selection of  "Central application", Or we should select all components in the list (big list)?

2. If we don't select other componets, will system upgrade all existing installed ECC components while EHP7 upgrade?

So please suggest on this option selection.

Regards

Santosh

Hi,

Facing Package interface elements and dialog text issue while doing SPAU process.

After adjustment, still the objects are display in red colors,

Is there any step which we have to follow with respect to these objects.

Please provide steps to make object status green.

Regards,

Praveer.

Hi Team,

Currently we have completed splitting of SAP BI 7.01 dual stack system.Now we are in processof upgrading and migrating BI-Abap to Hana (SAP NW 7.4).

How can we upgrade BI-Java stack system to SAP NW 7.4 while abap-stack upgrade still in process ?

Kindly advise on same.

Thanks & Regards,

Bakul

Hi,

  We have an SAP ILM V3 installed on an ERP 6 EHP6 SPS 11 stack.

  Component version: EHP6 for ERP 6.0 SPS 11

  Operating system: Linux, x86_64

  Database system: Oracle 11.2.0.3( to be upgraded to version 11.2.0.4 shortly)

  SAP kernel 720 PL 401(to be upgraded to version 721 PL 500 shortly)

We are planning to upgrade to SPS 14 .

I have already consulted SAP KB: http://service.sap.com/sap/support/notes/1566412

http://service.sap.com/sap/support/notes/1496212

However I am unable to find much consolidated information in them for SPS upgrade.

What we need in this regard is:

1) Pre-requisites for the SPS upgrade.

3) Known defects of SPS 14 and their remediation/workaround.

I am very new to using SAP ERP application(just working on it past 1 month) , and hence require guidance on the step by step process which I would need to follow for planning and executing the upgrade of the application SPS.

Regards

Sagarika

Hi Experts,

I am using SAP ECC6.0 vesion.

SAP users multilogon paramete is disabled but it  is working as multiple users at a time.

Long running work processes cant be killed in SAP ecc6.0 sm66

HI Exports,

Need Very urgent help, upgrade is in process and we are in Preprocessing Phase - MAIN_SHDIMP/SUBOD_SHD2_RUN/STOP_SHDI_SHD2 step.

normally this step should take more then 1 mins to shutdown Shadow instance but from past 12 hours the step is not completed.

When checked in SUM/Abap/log last log was generated 9 hours but there is no error reported in log of SUM tool.

Logs of  STOPSHD1.LOG

tail -100 STOPSHDI.LOG

1 ETQ201 Entering upgrade-phase "MAIN_SHDIMP/SUBMOD_SHD2_RUN/STOP_SHDI_SHD2" ("20150721213615")

1 ETQ399 Removing function description 'SUBST_START_BATCHJOB' from RFC cache.

1 ETQ399 Removing function description 'SUBST_CHECK_BATCHJOB' from RFC cache.

1 ETQ399 Removing function description 'SUBST_START_REPORT_IN_BATCH' from RFC cache.

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_ora_schema=SAPR3

1 ETQ200 Executing actual phase 'MAIN_SHDIMP/SUBMOD_SHD2_RUN/STOP_SHDI_SHD2'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'STOP_SERVICE'

1 ETQ399 SYSTEM MANAGER: Initializing.

1 ETQ399 SYSTEM MANAGER: STOPSAP on UNIX.

1 ETQ399 SYSTEM MANAGER: STOPSAP with SAPCONTROL.

1 ETQ399 SYSTEM MANAGER: SAPControl tries to control all instances.

1 ETQ399 SYSTEM MANAGER: Calling getInstances.

1 ETQ399 SYSTEM MANAGER: found instance for action STOP : Instance Number: 02

1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTOL action STOP for instance 02.

1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 02 on host sapehx01.

2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 2 for used ports on host 'sapehx01'.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3202 appears to be used.

1 ETQ399 SYSTEM HEALTH MANAGER: call test rfc.

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '02', GwService = 'sapgw02' Client = '000'

1 ETQ359 RFC Login to: System="EHX", AsHost="sapehx01" Nr="02", GwHost="sapehx01", GwService="sapgw02"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20150721213615

1 ETQ233 Calling function module "UPG_IS_SHADOW_SYSTEM" by RFC

2 ETQ373 parameter "IV_R3UP" = "X"

1 ETQ234 Call of function module "UPG_IS_SHADOW_SYSTEM" by RFC succeeded

4 ETQ010 Date & Time: 20150721213615

2 ETQ373 parameter "EV_SHADOW" = "X"

1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist.

1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: sapehx01 and instance: 02

3 ETQ120 20150721213616: PID 10813590 execute '/usr/sap/EHP7/SUM/abap/exe/sapcontrol -format script -prot NI_HTTP -host sapehx01 -nr 02 -function GetProcessList', output written to '/usr/sap/EHP7/SUM/abap/log/SAPup.ECO'.

3 ETQ122 20150721213616: PID 10813590 exited with status 3 (time: 0.000/0.060/0.112 real/usr/sys)

1 ETQ399 SYSTEM HEALTH MANAGER: System up and running, go on with stop action

1 ETQ399 SAPCONTROL MANAGER: stopWait with host: sapehx01 and instance: 02

3 ETQ120 20150721213616: PID 10813592 execute '/usr/sap/EHP7/SUM/abap/exe/sapcontrol -prot NI_HTTP -host sapehx01 -nr 02 -function StopWait 300 10', output written to '/usr/sap/EHP7/SUM/abap/log/SAPup.ECO'.

LOG of SAPup.ECO:

EXECUTING /usr/sap/EHP7/SUM/abap/exe/sapcontrol -format script -prot NI_HTTP -host sapeht01 -nr 02 -function GetProcessList

21.07.2015 21:36:16

GetProcessList

OK

0 name: msg_server

0 description: MessageServer

0 dispstatus: GREEN

0 textstatus: Running

0 starttime: 2015 07 21 15:16:43

0 elapsedtime: 6:19:33

0 pid: 7143444

1 name: enserver

1 description: EnqueueServer

1 dispstatus: GREEN

1 textstatus: Running

1 starttime: 2015 07 21 15:16:43

1 elapsedtime: 6:19:33

1 pid: 10748044

2 name: disp+work

2 description: Dispatcher

2 dispstatus: GREEN

2 textstatus: Running

2 starttime: 2015 07 21 15:16:43

2 elapsedtime: 6:19:33

2 pid: 15335606

3 name: gwrd

3 description: Gateway

3 dispstatus: GREEN

3 textstatus: Running

3 starttime: 2015 07 21 15:16:44

3 elapsedtime: 6:19:32

3 pid: 14287024

SAPup> Process with PID 10813590 terminated with status 3 at 20150721213616!

SAPup> Starting subprocess with PID 10813592 in phase 'STOP_SHDI_SHD2' at 20150721213616

    ENV: DIR_LIBRARY=/usr/sap/EHP7/SUM/abap/exe

    ENV: JAVA_HOME=/usr/java14_64

    ENV: LIBPATH=/usr/sap/EHP7/SUM/abap/exe:/usr/sap/EHP7/SUM/jvm/jre/lib/ppc64/server:/usr/sap/EHP7/SUM/jvm/jre/lib/ppc64:/usr/sap/EHP7/SUM/jvm/jre/../lib/ppc64:/usr/sap/EHP7/SUM/jvm/jre/lib/ppc64/jli:/usr/sap/EHP7/SUM/jvm/jre/../lib/ppc64/jli:/usr/lib:/lib:/usr/sap/EHT/SYS/exe/run:/oracle/client/11x_64/instantclient

    ENV: NLS_LANG=AMERICAN_AMERICA.WE8DEC

    ENV: ORACLE_BASE=/oracle

    ENV: ORACLE_SID=EHT

    ENV: PATH=/usr/sap/EHP7/SUM/abap/exe:/usr/java14_64/bin:.:/export/home/ehtadm:/usr/sap/EHT/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java5/jre/bin:/usr/java5/bin

    ENV: SAPDATA_HOME=/oracle/EHT

    ENV: SAPSYSTEMNAME=EHT

    ENV: dbms_type=ORA

    ENV: dbs_ora_schema=SAPR3

    ENV: dbs_ora_tnsname=EHT

    PWD: /usr/sap/EHP7/SUM/abap/tmp

EXECUTING /usr/sap/EHP7/SUM/abap/exe/sapcontrol -prot NI_HTTP -host sapeht01 -nr 02 -function StopWait 300 10

....................................................................................................................................................................................

So that where its hanging and not going forward and it also not erroring in out.

Any valuable suggession would be great as we need reach deadline.

Thanks

Dear All,

Need an help regarding the SPAU_ENH.

I searched for lot of documents in the net. But could not get a correct response and solution.

Actually, I need to use SPAU_ENH for few enhancements.

In the case of Grey Color, I am not suppose to do any changes as I need to keep the existing version intact.

I mean, the SAP changes should not be carried forward. Hence, can you please help me as to how to handle this scenario where we need to keep the same version as it is without going ahead with the changes.

To explain it simpler, I need to just keep the changes as it is and activate the Enhancement.

Any documentations with screenshots are most welcome.

Thank You.

Regards,

Anand

Hello,

We have upgraded  from ECC 6.0 Ehp3 to Ehp6. Net weaver portal 7.0 to net weaver portal 7.4.

after upgraded I activated fin_travel_1, fin_travel_2, fin_travel_3, fin_travel_4

however EP is on java packages BP_ERP5ESS,  BP_ERP5MSS. all ESS MSS -personal information, benefits and payments work on web dynpro java.

But travel works only on webdynpro abap hence my display request form, display expense form, display ,edit, change travel request buttons are not working in portal. Please suggest a workaround for this issue.

Regards,

Yashika Thakur

Hi :

I need to virtualize my SAP ERP environment.

I want to perform an heterogeous system copy from HP-UX / Oracle to Oracle in another operating system.

I have doubts to migrate to Windows or Linux.

I have another SAP Systems installed on Windows 2008 Server and we have no significant problems .

Now the question is , for the ERP over HPUX is better to migrate to a Linux distribution  (in order to keep the SAP / Oracle directories structure ) ?

Is there anyone that performed this migration before ?

Thanks for the replies !

Albert

Hi Experts

We have two different clients QAS and DEV in same SAP system. We need to upgrade sap_hr support pack in DEV client.

How we can apply support pack in only in DEV client.

Thanks in advance !

Hello Guys,

I am trying to implement Solution manager 7.1 SP8 patches to SPS 13 using SUM 1.0 SP 13 patch 4.

SUM looks stuck in phase PREP_IMPORT/TOOLIMPD from almost 5 hours.

Is it usually take that long to pass this phase?

There is no activity on log file from almost 3 hours. The only log file updated recently is <sum directory>/abap/tmp/dev_evt: below are the the lines i se in there:

Wed Jul 29 14:58:29 2015

Trace File of External Event Raiser (Level=0, Append=0)

******* Complete Call: *******

E:\usr\sap\<SID>\DVEBMGS00\exe\sapevt.exe

SAP_TRIGGER_RDDIMPDP

name=<SID>

nr=00

pf=\\<host name>\sapmnt\<SID>\SYS\profile\DEFAULT.PFL

******* End of Call *******

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: <host name>

SAP message server service (new): 3901

SAP message server service (old): sapms<SID>

Event sent to server <host name>_<SID>_00

Should i wait? how long i should wait?

i don't see any error though?

Thanks

Mani

Hi, We are upgrading our ECC EHP7 to latest version, current SAP version is SAP ECC EHP5 SP 9. To goto the latest version we need to upgrade SQL server into 2012, in order to do sql upgrade we need to be in SAP ECC EHP5 SP 11. SQL upgrade depends on ECC patch, ECC upgrade depends on SQL upgrade. Now we have two approaches 1. Upgrade SAP ECC EHP7 SP5 (minimum requirement for SQL 2012) - SQL upgrade - patch SAP ECC EHP7 to latest 2. Patch ECC EHP5 SP9 to latest version or SP11 - SQL upgrade - Upgrade SAP ECC EHP7 latest version May I know which approach we can execute in shortest duration? In either approaches we have two options Option 1 (a) SAP Upgrade / patch, user test for 1 week, if no issue, proceed with (b) (b) Upgrade SQL 2012, user verify for 1 week, if no issue, proceed with (c) (c) SAP Patch / upgrade, user test Option 2 Big Bang approach - SAP Upgrade / patch, Upgrade SQL server 2012 and SAP patch / upgrade SAP followed by user test. Difference between Option 1 and Option 2, Option 1 provides user test between each steps. May I know which option is recommended by SAP / SAP Best Practice? thanks and regards,

Hi,

Facing Package interface elements and dialog text issue while doing SPAU process.

After adjustment, still the objects are display in red colors,

Is there any step which we have to follow with respect to these objects.

Please provide steps to make object status green.

Regards,

Praveer.

Dear Experts,

We are upgrading R/3 4.7 system to ECC6.0 EHP7, stuck with an error at the CHECKS phase. OS is AIX 6.1 & DAtabase is DB2 9.7 FP10. Got below error message in Checks phase.

ERROR: Insufficient free space in the database as follows. Please refer to file /usr/sap/OS2/SUM/abap/log/DBFPLUSD.RES for more details and additional information about the results of the free space check.

ERROR: Extend file systems containing/db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

ERROR: to fulfil the following free space requirements:

ERROR: OP2#BTABD : 0 (MB)

ERROR: OP2#BTABI : 2510 (MB)

ERROR: OP2#CLUD : 0 (MB)

ERROR: OP2#CLUI : 0 (MB)

ERROR: OP2#DDICD : 3250 (MB)

ERROR: OP2#DDICI : 1450 (MB)

ERROR: OP2#DOCUD : 50 (MB)

ERROR: OP2#DOCUI : 30 (MB)

ERROR: OP2#EL740D : 0 (MB)

ERROR: OP2#EL740I : 0 (MB)

ERROR: OP2#ES740D : 0 (MB)

ERROR: OP2#ES740I : 0 (MB)

ERROR: OP2#LOADD : 70 (MB)

ERROR: OP2#LOADI : 0 (MB)

ERROR: OP2#POOLD : 4700 (MB)

ERROR: OP2#POOLI : 3090 (MB)

ERROR: OP2#PROTD : 0 (MB)

ERROR: OP2#PROTI : 0 (MB)

ERROR: OP2#SOURCED : 2700 (MB)

ERROR: OP2#SOURCEI : 230 (MB)

ERROR: OP2#STABD : 4890 (MB)

ERROR: OP2#STABI : 4900 (MB)

ERROR: OP2#USER1D : 1500 (MB)

ERROR: OP2#USER1I : 1510 (MB)

ERROR: SYSCATSPACE : 5300 (MB)

ERROR: the minimum extension size for the listed file systems can in general not be determined exactly.

ERROR: the following maximum extensions fulfil the requirements but may include large overhead:

ERROR: MAX: extend file system containing /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 by 10835 MB

ERROR: MAX: extend file system containing /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 by 14320 MB

ERROR: MAX: extend file system containing /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 by 7966 MB

You must fulfill these requirements first before you continue with the procedure!

We have enough space in the respective file systems. We ran the script /usr/sap/OS2/SUM/abap/log/DB6TBSXT.CLt as mentioned in the log /usr/sap/OS2/SUM/abap/log/DBFPLUSD.RES

Filesystem    GB blocks      Free %Used    Iused %Iused Mounted on

/dev/OS2_sapdata1_lv    100.00     32.41   68%       29     1% /db2/OS2/sapdata1

/dev/OS2_sapdata2_lv     70.00     12.21   83%       32     1% /db2/OS2/sapdata2

/dev/OS2_sapdata3_lv     70.00     11.45   84%       24     1% /db2/OS2/sapdata3

/dev/OS2_sapdata4_lv     60.00     19.59   68%       52     1% /db2/OS2/sapdata4

/dev/OS2_sapdata5_lv     60.00     20.19   67%       47     1% /db2/OS2/sapdata5

Here is the log DBFPLUSD.RES

*************************************************************************

*

* DB2 UDB for Unix, Windows (DB6)

* Comparing Free Space Requirements of SAPup

* with Free Space on Database

*

* THIS FILE CONTAINS INFO- AND ERROR-MESSAGES ONLY!

* TABLESPACES OR FILE SYSTEMS WITH ENOUGH FREE SPACE ARE NOT LISTED HERE!

*

* Messages and actions listed in this file can be assigned

* to the following categories:

*

* 1. Non-existing tablespaces &

*    tablespaces with insufficient free space of type 'DMS without autoresize':

*

*    ERROR: messages are listed here.

*    To solve all problems of this type marked with 'ERROR:'

*    file /usr/sap/OS2/SUM/abap/log/DB6TBSXT.CLP was created by SAPup as a template

*    DB2 CLP script containing the SQL-statements to create new tablespaces

*    and/or to enlarge the tablespaces with insufficient free space.

*

* 2. Tablespaces with insufficient free space of type 'DMS with automatic storage':

*

*    These kind of tablespaces can grow until all storage paths defined for the

*    database are full. If all storage paths defined for the database together have

*    insufficient free space, an 'ERROR:' message is listed here.

*

* 3. Tablespaces with insufficient free space of type 'SMS' &

*    tablespaces with insufficient free space of type 'DMS with autoresize':

*

*    These kinds of tablespaces can grow until the filesystems containing them are full.

*    If the filesystems containing one or more tablespaces have insufficient free space,

*    an 'ERROR:' message is listed here.

*    Depending on the database layout it is not always possible to determine if the

*    free space on file system level meets the space requirements of SAPup.

*    In these cases a detailed 'INFO:' message is generated. Please make sure manually

*    that enough free space on file system level is provided to meet

*    the space requirements of SAPup.

*

*************************************************************************

*

* all INFO: and/or ERROR: messages for autostorage or auto-resize enabled

* tablespaces listed below are based of the following information:

* (if no INFO: or ERROR: message is listed sufficient free space exists)

*

* TABLESPACE_NAME            FREE_MB     MB_NEEDED   IN_MOUNT_CONTAINING_FILE

* =============================================================================

* OP2#BTABI                       33193        2510  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

*                                 12505              /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001

*                                 11720              /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

*                                 20064              /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

*                                 20678              /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#DDICD                       33193        3250  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

*                                 12505              /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001

*                                 11720              /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

*                                 20064              /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

* OP2#DDICI                       20064        1450  /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

* OP2#DOCUD                       20678          50  /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#DOCUI                       20678          30  /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#LOADD                       20678          70  /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#POOLD                       33193        4700  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

*                                 12505              /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001

*                                 11720              /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

*                                 20064              /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

*                                 20678              /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#POOLI                       33193        3090  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

*                                 12505              /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001

*                                 11720              /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

*                                 20064              /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

*                                 20678              /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#SOURCED                     11720        2700  /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

* OP2#SOURCEI                     20064         230  /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

* OP2#STABD                       33193        4890  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

*                                 12505              /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001

*                                 11720              /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

*                                 20064              /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

*                                 20678              /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#STABI                       33193        4900  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

*                                 12505              /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001

*                                 11720              /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002

*                                 20064              /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

*                                 20678              /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004

* OP2#USER1D                      20064        1500  /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

* OP2#USER1I                      20064        1510  /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

* SYSCATSPACE                     33193        5300  /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000

* =============================================================================

*

*******************************************************************************

INSUFFICIENT FREE SPACE: ERROR: Extend file systems containing/db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/O

S2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE00

00/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.conta

iner003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/s

apdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/O

P2#BTABD.container003 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container

004 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapda

ta2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#B

TABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003

/db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/

NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD

.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2

/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE

0000/OP2#BTABD.container003 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.con

tainer002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000/OP2#BTABD.container004 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.container000 /db2/OS2

/sapdata2/NODE0000/OP2#BTABD.container001 /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata5/NODE0000

/OP2#BTABD.container004 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 /db2/OS2/sapdata1/NODE0000/OP2#BTABD.contain

er000

INSUFFICIENT FREE SPACE: ERROR:        to fulfil the following free space requirements:

INSUFFICIENT FREE SPACE: ERROR:        OP2#BTABD                : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#BTABI                : 2510 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#CLUD                 : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#CLUI                 : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#DDICD                : 3250 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#DDICI                : 1450 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#DOCUD                : 50 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#DOCUI                : 30 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#EL740D               : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#EL740I               : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#ES740D               : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#ES740I               : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#LOADD                : 70 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#LOADI                : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#POOLD                : 4700 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#POOLI                : 3090 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#PROTD                : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#PROTI                : 0 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#SOURCED              : 2700 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#SOURCEI              : 230 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#STABD                : 4890 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#STABI                : 4900 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#USER1D               : 1500 (MB)

INSUFFICIENT FREE SPACE: ERROR:        OP2#USER1I               : 1510 (MB)

INSUFFICIENT FREE SPACE: ERROR:        SYSCATSPACE              : 5300 (MB)

INSUFFICIENT FREE SPACE: ERROR:        the minimum extension size for the listed file systems can in general not be determined exactly.

INSUFFICIENT FREE SPACE: ERROR:        the following maximum extensions fulfil the requirements but may include large overhead:

INSUFFICIENT FREE SPACE: ERROR:        MAX: extend file system containing /db2/OS2/sapdata2/NODE0000/OP2#BTABD.container001 by 10835 MB

INSUFFICIENT FREE SPACE: ERROR:        MAX: extend file system containing /db2/OS2/sapdata3/NODE0000/OP2#BTABD.container002 by 14320 MB

INSUFFICIENT FREE SPACE: ERROR:        MAX: extend file system containing /db2/OS2/sapdata4/NODE0000/OP2#BTABD.container003 by 7966 MB

Can someone please help to resolve the issue?

Thanks,

Vinay

Hi,

Facing Package interface elements and dialog text issue while doing SPAU process.

After adjustment, still the objects are display in red colors,

Is there any step which we have to follow with respect to these objects.

Please provide steps to make object status green.

Regards,

Praveer.

Dear All,

We are upgrading our SAP R/3 4.7 to ECC 6 EHP7. O/S is AIX 6.1 and database is Db2 9.1 FP10.

We are getting following error during upgrade pre-processing .

Severe error(s) occurred in phase MAIN_SHDPREPUT/START_SHDI_PREPUT!

Last error code set: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': Process /usr/sap/OS2/SUM/abap/exe/sapcontrol exited with 2, see '/usr/sap/OS2/SUM/abap/log/SAPup.ECO' for details

Belog is the log from /usr/sap/OS2/SUM/abap/log/DEVTRACE.LOG

*** ERROR in DbSlConnectDB6[/bas/741_REL/src/dbs/db6/dbsldb6.c, 1317] CON = 0 (BEGIN)

C  &+    DbSlConnectDB6: DB2DB6EKEY not found in environment or password file

C  &+

C  &+

C  &+

C  *** ERROR in DbSlConnectDB6[/bas/741_REL/src/dbs/db6/dbsldb6.c, 1317] (END)

M  ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 71]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c  2323]

Environment variable DB2DB6EKEY  is already set to OS2ri3pa043.

output of the command setenv

I have stopped SUM, sap on primary, shadow instances & regenerated the password file by using below command.

dscdb6up -create <connect_user password> <sidadm password>

Replaced the Kernel present in /usr/sap/OS2/SUM/abap/exe with the latest target release kernel available from service market place.

I tried to restart SUM but no luck.

I tried to start shadow instance manually, but failed with below error

ri3pa043:os2adm 10> cd /usr/sap/OS2/SUM/abap/bin

ri3pa043:os2adm 11> ./SAPup startshd

Starting shadow system ...

Starting service ...

FATAL ERROR: Process /usr/sap/OS2/SUM/abap/exe/sapcontrol exited with 2, see '/usr/sap/OS2/SUM/abap/log/SAPup.ECO' for details

I am attaching  DEVTRACE.LOG, STARTSSC.LOG from /usr/sap/OS2/SUM/abap/log & dev_w0 from /usr/sap/OS2/SUM/abap/system/OS2/DVEBMGS02/work.

Can someone please check the logs & help me.

Thanks,

Vinay