Yet another sizing question: Solution Manager Install on Oracle and Redhat

[Former Member]

We are trying to install SM 7.0 and are encountering sizing errors. We have setup our sapdataX's as per note 972263:

SAP Solution Manager 4.0 SR3:

File System Name Space Requirement

/oracle/<DBSID>/sapdata1 18 GB

/oracle/<DBSID>/sapdata2 20 GB

/oracle/<DBSID>/sapdata3 9 GB

/oracle/<DBSID>/sapdata4 1 GB

SUM 48 GB

In actual fact we increased it to

sapdata1 - 20GB

sapdata2 - 22GB

sapdata3 - 11GB

sapdata4 - 6 GB

It is still giving us an error and sapdata2 and sapdata3 are at 100%

Is there a more accurate note that I can't seem to find? Or any advice? We can keep adding space but how much and where is an issue.

Thanks,

Lori

[Former Member]

did you have a look at this Sizing guide??

The "Sizing Guide SAP Solution Manager" is available on the SAP Service Marketplace under the following quick link: instguides (http://service.sap.com/instguides) -> SAP Components -> SAP Solution Manager <current release>Sizing Guide SAP Solution Manager 7.0 .

Also have a look at below SAP Note for more information.

Note 1088980 - Documentation: SAP Solution Manager

Hope this helps.

[Former Member]

Yes thanks, I did review the sizing guide. It does give a general sizing of 300GB for the small system landscape but does not give specifics as to what size each filesystem should be. This one was dated April 2008 and I found note 972263 which is dated May 2009 and has specifics in it. Unfortunately, the numbers are too low and we cannot find a more accurate list.

I also review the note you mentioned and all attached notes without finding anything regarding sizing and filesystems.

Any other advice? Has anyone else installed SM 7.0 on Linux with Oracle 10?

[former_member244874]

My Group completed an installation of SM 7 with Linux and Oracle 10.

My sizing is a lot larger then this, but the current used part of the sapdataX is as follows hope this helps

sapdata1 - 40GB

sapdata2 - 32GB

sapdata3 - 32GB

sapdata4 - 42GB

This might help you but i do not recommend setting the total size to these exact numbers you will run out of space !

Edited by: Sean Siegmund on Nov 4, 2010 1:02 AM

[Former Member]

Thanks for the input and assistance. I have increased all sapdataX's significantly and tried to continue the install. Still errors out. I am wondering if I missed something else and space is not the only issue. Here is the output of my REPSOSRC.log file:

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101102132702

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -ctf I /sapsol7/51033518_1/EXP1/DATA/REPOSRC.STR /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/DDLORA_LRG.TPL REPOSRC.TSK ORA -l REPOSRC.log

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

/usr/sap/SOL/SYS/exe/run/R3load: job completed

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101102132702

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101102132702

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

(DB) INFO: REPOSRC created #20101102132704

DbSl Trace: OCI-call 'OCILobWrite' failed with rc=1691

DbSl Trace: ORA-1691 occurred when writing to a LOB

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "REPOSRC"

(SQL error 1691)

error message returned by DbSl:

ORA-01691: unable to extend lob segment SAPSR3.SYS_LOB0000009771C00034$$ by 1024 in tablespace PSAPSR3700

(DB) INFO: disconnected from DB

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101102140953

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101102154018

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

(DB) INFO: REPOSRC deleted/truncated #20101102154024

DbSl Trace: OCI-call 'OCILobWrite' failed with rc=1653

DbSl Trace: ORA-1653 occurred when writing to a LOB

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "REPOSRC"

(SQL error 1653)

error message returned by DbSl:

ORA-01653: unable to extend table SAPSR3.REPOSRC by 1024 in tablespace PSAPSR3700

(DB) INFO: disconnected from DB

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101102154857

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101102155321

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

(DB) INFO: REPOSRC deleted/truncated #20101102155343

DbSl Trace: Error 1653 in stmt_execute() from oci_execute_stmt(), orpc=0

DbSl Trace: ORA-1653 occurred when executing SQL stmt (parse error offset=0)

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "REPOSRC"

(SQL error 1653)

error message returned by DbSl:

ORA-01653: unable to extend table SAPSR3.REPOSRC by 1024 in tablespace PSAPSR3700

(DB) INFO: disconnected from DB

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101102160947

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101104100321

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

(DB) INFO: REPOSRC deleted/truncated #20101104100336

DbSl Trace: OCI-call 'OCILobWrite' failed with rc=1653

DbSl Trace: ORA-1653 occurred when writing to a LOB

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "REPOSRC"

(SQL error 1653)

error message returned by DbSl:

ORA-01653: unable to extend table SAPSR3.REPOSRC by 1024 in tablespace PSAPSR3700

(DB) INFO: disconnected from DB

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101104100946

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101104162425

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101104162426

/usr/sap/SOL/SYS/exe/run/R3load: START OF LOG: 20101104162630

/usr/sap/SOL/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/SOL/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/SOL/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -stop_on_error

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541

DbSl Trace: CONNECT failed with sql error '12541'

(DB) ERROR: DbSlErrorMsg rc = 99

/usr/sap/SOL/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SOL/SYS/exe/run/R3load: END OF LOG: 20101104162630

This is the first error and I am not sure what to do:

DbSl Trace: ORA-1691 occurred when writing to a LOB

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 99, table "REPOSRC"

(SQL error 1691)

error message returned by DbSl:

ORA-01691: unable to extend lob segment SAPSR3.SYS_LOB0000009771C00034$$ by 1024 in tablespace PSAPSR3700

(DB) INFO: disconnected from DB

Any help would be welcomed.

Thanks,

Lori