Quantcast
Channel: SCN: Message List - SAP ERP 6.0 Upgrade
Viewing all 4288 articles
Browse latest View live
↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 12:20 am
$
0
0

Hi Rahul,

 

Operating System HPUX11.31

Database ORACLE 11.2.0.4

RAM is 16GB,SWAP Size is 40GB.

 

I have updated my shadow instance Kernel 742 release to 200 and also updated the tp to level 211 of SAP KERNEL 7.42 64BIT UNICODESAP KERNEL 7.42 64BIT UNICODE.

The parameters added are OK.Please guide further.


Santosh

↧
Search

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 12:30 am
$
0
0

Hi Anand,

 

As per the thread:

 

1. Space is enough
2. No tablesapce is running out of space

3. tp is connecting well

any other suggestions?

 

Santosh

 

↧
↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 12:38 am
$
0
0

Stop and start the shadow instance manually & check the memory/CPU utilization while both the instance are running(main & shadow instance).Also check the below KBA:

172747 SAP on HPUX:OS kernel parameter recommendations

 

BR,

Rahul

 

↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 12:40 am
↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 1:33 am
$
0
0

Almost all memory is in use and total is close to 100%: ============================================================== [1.3] SYSTEM PAGING SPACE (swapinfo -tm)                       Mb          Mb          Mb  PCT    START/          Mb       TYPE          AVAIL        USED        FREE  USED      LIMIT    RESERVE  PRI  NAME       dev          16384        4343        12041  27%          0          -    1  /dev/vg00/lvol2       reserve          -      12041      -12041       memory        7786        7469          317  96%       total        24170      23853          317  99%      -          0    - =============================================================== Please find the attached memlimits -v output: [1]memlimits -v off SAP R/3 address space configuration test tool V3.2 (98/01/14) ========================================================================= Verbose mode off Check the maximum data size per process (malloc) Check the available swap space (malloc in several processes) Process 22702 allocating Check the available swap space (malloc in several processes)           ... Size =  476MB  Total:  476MB Check the maximum size of mapped file (mmap anonymous,dev/zero) Check protection operations on this area (protect) Maximum mapped file size: 472MB Maximum mprotect size:    472MB Check the maximum address space per process usable both by process local memory and mapped file Maximum address space ( mmap(472 MB)+ malloc(4MB) ): 476MB +-------------------------------------------------------+ |                        Result                        | +-------------------------------------------------------+ Maximum heap size per process........:  476 MB     this value is probably limited by swap space Maximum mapped file size (mmap)......:  472 MB     this value is probably limited by swap space Maximum protectable size (mprotect)..:  472 MB     em/initial_size_MB > 472 MB will not work Maximum address space per process....:  476 MB     this value is probably limited by swap space Total available swap space...........:  476 MB     *** ERROR =>  swap space too small, expect problems     main memory size x 3 recommended , minimum 1 GB Please help to solve the same. Regards, Santosh.

↧
↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 1:56 am
$
0
0


As per the logs sent ,Your Swap Memory is not enough to run the both instance simultaneously.

As a work around, Have you tried to stop the main instance and then run only the shadow instance?

Also ask your OS team to increase the page size.In the log its clear that Page size should be main memory x 3. Know me what are the results.

 

BR,

Rahul

↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 2:32 am
$
0
0

I have stopped the main R3 instance, Now only the shadow instance is Up and running.

I have started the upgrade from the point it stopped, I see its running quite fine now, and It has gone by far the time it usually gives the memory dump. I am constantly monitoring the space and memory and till now I don't see much utilization.

 

Regards,

Santosh

↧

Re: Memory Error in pre-processing phase MAIN_SHDRUN/ACT_UPG

July 31, 2015, 2:48 am
$
0
0

Great!!!

 

For a fair solution,you should now increase your swap size.

 

BR,

Rahul

↧
Search

SAP EHP7 Upgrade

August 3, 2015, 6:53 pm
$
0
0

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,

↧
↧

Re: Print problem with SAPSprint in Window 7

August 3, 2015, 8:01 pm
$
0
0

I have same problem in Windows2008 R2 with SAPSprint version 730 or 740, 32bit or 64bit.

SAP support give such information:

Chinese character can only be substition with fonts which include code page 936.

↧

Re: Heterogenous system Copy ERP 6.0

August 4, 2015, 6:08 am
$
0
0

Ciao Abert

 

I see completely your point.

 

If you are the real decision maker, just go for Linux and both your users and you will be happy

 

If you are not in a position to decide but you want to support the decision with a fair compare, why don't you subscribe to Gartner? I'm sure they have done a lot of research in this field

 

Let me know how it goes

cheers

a

↧

Re: Error in SUBMOD_FDC_PREP/RUN_FDC4UPG_PREPROC in module MAIN_SHDRUN

August 5, 2015, 9:10 am
$
0
0

Checked following entries:

SAPLOCALHOST in Windows System Properties

Shadow Instance Profile --- RZ10 SAPLOCAL HOST Entry

Shadow Instance ---  SM51 Hostname entry

------

Note:  All 3 Parameters have to match up word for word and upper/lower case entries.

↧

Re: SAP EHP7 Upgrade

August 6, 2015, 6:54 am
$
0
0

Suganthi AN wrote:

 

Hi, We are upgrading our ECC EHP7 to latest version, current SAP version is SAP ECC EHP5 SP 9.

 

You are upgrading your EHP7. And current version EHP5.

Confused? Please clarify to get better answers.

 

Regards,

Serhat

↧
↧

Re: SAP EHP7 Upgrade

August 6, 2015, 7:50 am
$
0
0

Hi, We are in SAP ECC6 EHP5 SP9, planning to upgrade to SAP ECC6 EHP7 Latest SP Please advise

↧

Re: SAP EHP7 Upgrade

August 6, 2015, 10:53 am
$
0
0

Hi Suganthi,

 

The best way to go about in my view would be to first patch EHP5 SP9 to EHP5 SP11 and then upgrade SQL, this will not take long and can be done on a weekend.

Then you have a week for users to test and then you can upgrade it to EHP7 latest.

 

Going from EHP5 to EHP7 will take time whereas SP9 to SP11 will finish quite early. your option 1 will however take a lot of downtime initially.

 

You can also save a lot of time by doing the initial preparations before the upgrade. Refer the SUM guide for this.

 

You can start SUM and run the pre processes until Execution one week before your planned downtime.

 

Hope this helps

 

AC

↧
Search

Re: Heterogenous system Copy ERP 6.0

August 6, 2015, 11:08 am
$
0
0

Hi Albert,

 

I am in total agreement with Andrea, you need to consider lot of factors like integration to non SAP system, stability, OS and DB compatibility, Endian byte order etc.

 

Personally I would be more comfortable Going from any type of Unix environment like HP-UX or AIX to Linux rather than Windows. Both have Big endian byte order and administration is easier.

 

Windows have its own advantages as the troubleshooting is easier.

 

Choose wisely

 

AC

↧

Re: SAP EHP7 Upgrade

August 7, 2015, 1:36 am
$
0
0

Hello Suganthi,

 

If SQL upgrade and SAP upgrade depend to each other; then you must fulfill the requirements step by step.

You can not upgrade your ECC system to EHP7 at the beginning, because of your SQL version is not suitable yet.

 

Therefore:

 

1-Execute support package patching from EHP5 SP9 --> to EHP5 SP11. Now you are allowed to upgrade your SQL.

     *Make functional tests.

 

2-Upgrade your SQL server to 2012 version. Then you can start with SAP upgrade.

     *Make functional tests.

 

3-Upgrade your SAP system from EHP5 SP11 --> to EHP7 latest SP level.

     *Make functional tests.

 

I would go in that order (your option 2?) .

Remember that advancing safe and following guides are more important than early finishing.

 

Good luck!

Serhat

↧
↧

Re: ./SAPup reset prepare & -nr

August 7, 2015, 6:55 pm
$
0
0

Hello Evgeniy,

 

Can you to solve the error?

 

I have the same error.

 

Thanks in advanced!

↧

Insufficient free space in the database during ERP6 upgrade in checks phase

August 8, 2015, 11:01 am
$
0
0

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

↧

Re: Insufficient free space in the database during ERP6 upgrade in checks phase

August 9, 2015, 12:49 am
$
0
0

Issue resolved after creating containers manually for the mentioned tablespaces with specified sizes.


Thanks,

Vinay

↧
Viewing all 4288 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>