Problem in upgrade of Solution manager 3.2 to 4 - "general check failed"

[Former Member]

Problem facing in upgrade of Solution manager 3.2 to 4. The general check phase and optional phase not successed... the CHECKS.LOG shows following error-

#=======================================================================

1. Starting new execution of PREPARE modules

2. General checks

3. Optional checks for conversions

4. at 20070613162535.

#=======================================================================

#====================================================#

1. Requests and information for module General checks #

#====================================================#

-

---

INFO> The following values may be preliminary because of

free space consumption during productive operation and

additional free space requests derived in a later stage.

Conversions of modified tables can require additional space.

Please use the largest free space request printed,

which are the values at the very end of this file.

ERROR> Insufficient free space in the database as follows:

Create TABLESPACE PSAPSMP700 with 8301 MB

INFO> To adjust the size of your tablespaces, you may use the commands

in file 'E:\usr\sap\put\log\ORATBSXT.LST' using the 'brspace' utility.

Please copy the file before making changes, as it may be

overwritten in subsequent upgrade phases.

INFO> During the upgrade, the new SAP kernel

will be installed. All files and subdirectories

in directory E:\usr\sap\SMP\SYS\exe\run which are not used

in Release 700 will be removed.

The files from "dbclient.lst" in the kernel directory are kept.

Files and subdirectories can be protected from deletion

if they appear in a file "protect.lst" in the same directory

(each protected name in a separate line).

For security reasons, directory E:\usr\sap\SMP\SYS\exe\run

should be saved in a backup.

INFO> It is possible to upgrade the frontend software before

you start SAPup!

ERROR: The table TCPDB is empty. This would cause the upgrade

to stop in the EU_IMPORT phases. Please consult note

15023 for further information on how to insert the

correct codepage entries in table TCPDB.

#===========================================================#

1. PREPARE module General checks finished with status failed #

#===========================================================#

#=====================================================================#

1. Requests and information for module Optional checks for conversions #

#=====================================================================#

Information:

In file E:\usr\sap\put\log\TABCONV.LST you can see a list of tables

which will be converted in your SAP System during the upgrade.

The list of tables was determined at SAP and is not complete for

your system. Other tables might have to be converted due to your

modifications. The final list of tables can only be determined immediately

before the conversion during downtime. The list contains the names and

the size of the tables.

-

---

INFO> The following values may be preliminary because of

free space consumption during productive operation and

additional free space requests derived in a later stage.

Conversions of modified tables can require additional space.

Please use the largest free space request printed,

which are the values at the very end of this file.

ERROR> Insufficient free space in the database as follows:

Create TABLESPACE PSAPSMP700 with 8301 MB

INFO> To adjust the size of your tablespaces, you may use the commands

in file 'E:\usr\sap\put\log\ORATBSXT.LST' using the 'brspace' utility.

Please copy the file before making changes, as it may be

overwritten in subsequent upgrade phases.

#============================================================================#

1. PREPARE module Optional checks for conversions finished with status failed #

Using ORATBSXT.LST - which shows -

1. These are examples for brspace commands to extend/create the required

2. tablespaces. You can adapt them according to your own needs.

3. Add option '-c force' to call the commands in batch mode.

4. Change option '-autoextend' to 'yes' and set '-maxsize' and '-incrsize'

5. to create autoextensible segments.

brspace -function tscreate -tablespace PSAPSMP700 -owner SAPSMP -data both -size 8301 -autoextend no

... but same error comes up in General check . Please help.

Regards-

Sanjay Birari

[former_member204746 · Accepted solution]

create tablespace:

brspace -function tscreate -tablespace PSAPSMP700 -owner SAPSMP -data both -size 8301 -autoextend no

then:

Please consult note

15023 for further information on how to insert the

correct codepage entries in table TCPDB.

once you do those 2 things, run PREPARE again.

[Former Member · Accepted solution]

thanks ben... but i told you the system stops upgrade at dbchck phase. error i got is "Severe database inconsistancy".

Again rebuilding the whole system. thanks for all you help.

Regards-

Sanjay Birari

[former_member204746 · Accepted solution]

SAnjay, provide CHECKS.log again.

have you applied SAP note 15023?

[Former Member]

ERROR> Insufficient free space in the database as follows:

Create TABLESPACE PSAPSMP700 with 8301 MB

ERROR: The table TCPDB is empty. This would cause the upgrade

to stop in the EU_IMPORT phases. Please consult note

15023 for further information on how to insert the

correct codepage entries in table TCPDB.

[Former Member]

Hi,

Update brtools to latest patch level.

manually Create TABLESPACE PSAPSMP700 with 8301 MB

Regards

Ben

[Former Member]

Hi Ben,

Thanks for the solution but i already check the BRTOOLS version.

Is it ok to create the database manually bcause when i check in SAPBACKUP the particular PSAPSMP700.data1, data2, data3 already created. Does it affects my upgrade, because the previous experiance of mine is really bad .. w"Upgrade stops showing error "Datbase inconsistancy" upgrade terminate. Can you please guide , how to create the tablespace manually using BRTOOLS. And which version should i9 applied for BRTOOLS.

Regards-

sanjay