cancel
Showing results for 
Search instead for 
Did you mean: 

Brspace error

vince_laurent
Active Participant
0 Kudos

I did a :

brspace -f tbreorg -a reorg -i psapods2i -m offline -n psapods2d -s psapodsd -t "*"

then a:

brspace -f tbreorg -a reorg -i psapodsi -m offline -n psapodsd -s psapods2d -t "*"

Now dataloads are failing. They are trying to create things in PSAPODS2I which does not exist any more. When I created the DDL for one of the failing loads I get the following. Notice the PSAPODS2I at the end? Where is that stored? I have looked ALL over SAP/Oracle..

Oracle 10.2.0.2 on HP-UX Itanium 64

BRSPACE is version 33.

Thanks-

Vince

CREATE UNIQUE INDEX "SAPR3"."/BIC/B0000282000~0" ON

"SAPR3"."/BIC/B0000282000"

("REQUEST", "DATAPAKID", "PARTNO", "RECORD")

LOCAL

(

PARTITION "/BIC/B00002820000000000002"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000003"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000004"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000005"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000006"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000008"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000010"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000011"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000012"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000013"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000014"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000015"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000016"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING,

PARTITION "/BIC/B00002820000000000017"

STORAGE (

INITIAL 16384

NEXT 65536

MAXEXTENTS UNLIMITED

PCTINCREASE 0

FREELISTS 1

FREELIST GROUPS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

TABLESPACE "PSAPODSI"

LOGGING

)

STORAGE (

INITIAL 2

NEXT 320

MAXEXTENTS 2147483645

PCTINCREASE 0

FREELISTS 1

)

PCTFREE 10

INITRANS 2

MAXTRANS 255

NOCOMPRESS

LOGGING

TABLESPACE "PSAPODS2I"

NOPARALLEL;

Edited by: Vince Laurent on May 6, 2008 11:27 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Can you check table RSTS for outdated TABARTs? Also table DDSTORAGE can be related...

Regards

Martin

vince_laurent
Active Participant
0 Kudos

how?

SQL> desc rsts;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 TRANSTRU                                  NOT NULL VARCHAR2(27)
 OBJVERS                                   NOT NULL VARCHAR2(1)
 OBJSTAT                                   NOT NULL VARCHAR2(3)
 ACTIVFL                                   NOT NULL VARCHAR2(1)
 TSMETHODE                                 NOT NULL VARCHAR2(1)
 ODSTYPE                                   NOT NULL VARCHAR2(1)
 ODSNAME                                   NOT NULL VARCHAR2(30)
 ODSVERSION                                NOT NULL VARCHAR2(3)
 TRANSTRU_APPL                             NOT NULL VARCHAR2(30)
 TRANSTRU_CHAR                             NOT NULL VARCHAR2(27)
 TRANSTRU_IDOC                             NOT NULL VARCHAR2(27)
 TRANSTRU_IDOC3                            NOT NULL VARCHAR2(10)
 OBJSTATOLTP                               NOT NULL VARCHAR2(3)
 PROGNAME                                  NOT NULL VARCHAR2(40)
 FORMNAME                                  NOT NULL VARCHAR2(30)
 GLBCODE                                   NOT NULL VARCHAR2(25)
 OWNER                                     NOT NULL VARCHAR2(12)
 TSTMPOLTP                                 NOT NULL NUMBER(15)
 TSTPNM                                    NOT NULL VARCHAR2(12)
 TIMESTMP                                  NOT NULL NUMBER(15)
 LOGSYS                                    NOT NULL VARCHAR2(10)
 CONTREL                                   NOT NULL VARCHAR2(6)
 CONTTIMESTMP                              NOT NULL NUMBER(15)
 STARTROUTINE                                       VARCHAR2(25)
 EDSFL                                              VARCHAR2(1)
 PSADATCLS                                          VARCHAR2(5)
 PSASIZCAT                                          VARCHAR2(2)

Former Member
0 Kudos

The column PSADATCLS has to be checked.

vince_laurent
Active Participant
0 Kudos

Only 2 of the 709 rows had anything...

select PSADATCLS 
from rsts
/

PSADA
-----
.
.
.
DODS


DODS
.
.
.

709 rows selected.

former_member204746
Active Contributor
0 Kudos

your problem is that the default location of new partition is still located on the alternate tablesapce.

do:

alter index sapr3."/BIC/B0000282000~0" modify default attributes tablespace PSAPOSDI;

I have not tested this command. do it at your own risks.

Former Member
0 Kudos

One other idea: Was SAP stopped during or after the reorganization? If not, the SAP system might still see the old TAORA / IAORA / TSORA entries as these tables are buffered on SAP side and BRSPACE is not able to invalidate them in the buffer. Using report RSDBBUFF you can invalidate these tables in the SAP buffer so that SAP is forced to read the current information from these tables.

vince_laurent
Active Participant
0 Kudos

>

> your problem is that the default location of new partition is still located on the alternate tablesapce.

>

> do:

>

> alter index sapr3."/BIC/B0000282000~0" modify default attributes tablespace PSAPOSDI;

Yes, I know that is the issuue.

Does this having a blank field mean there is an issue?

SQL> l
  1  select table_name, index_name, tablespace_name
  2  from dba_indexes
  3* where index_name like '%282%'
SQL> /

TABLE_NAME                     INDEX_NAME                     TABLESPACE_NAME
------------------------------ ------------------------------ ------------------------------
/BIC/B0000282000               /BIC/B0000282000~0

vince_laurent
Active Participant
0 Kudos

>

> One other idea: Was SAP stopped during or after the reorganization? If not, the SAP system might still see the old TAORA / IAORA / TSORA entries as these tables are buffered on SAP side and BRSPACE is not able to invalidate them in the buffer. Using report RSDBBUFF you can invalidate these tables in the SAP buffer so that SAP is forced to read the current information from these tables.

SAP was down the whole time. I was only having oracle up/down during this OFFLINE reorg process. SAP has since been bounced more than a few times since.

vince_laurent
Active Participant
0 Kudos

>

> your problem is that the default location of new partition is still located on the alternate tablesapce.

>

> do:

>

> alter index sapr3."/BIC/B0000282000~0" modify default attributes tablespace PSAPOSDI;

This solved it. Just for grins I did another export and recreated the scripts that would recreate the indexes:

CREATE UNIQUE INDEX "SAPR3"."/BIC/B0000282000~0" ON "/BIC/B0000282000"
("REQUEST" , "DATAPAKID" , "PARTNO" , "RECORD" ) PCTFREE 10 INITRANS 2
MAXTRANS 255 STORAGE(INITIAL 16384 NEXT 2621440 MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0 FREELISTS 4) TABLESPACE "PSAPODS2I" LOGGING
LOCAL(PARTITION "/BIC/B00002820000000000017" PCTFREE 10 INITRANS 2
MAXTRANS 255 STORAGE(INITIAL 16384 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT) TABLESPACE "PSAPODSI" LOGGING ) ;


CREATE UNIQUE INDEX "SAPR3"."/BIC/B0000433000~0" ON "/BIC/B0000433000"
("REQUEST" , "DATAPAKID" , "PARTNO" , "RECORD" ) PCTFREE 10 INITRANS 2
MAXTRANS 255 STORAGE(INITIAL 16384 NEXT 2621440 MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0 FREELISTS 4) TABLESPACE "PSAPODS2I" LOGGING

For some reason brspace didn't update these two indexes. I issued the commands:

alter index "/BIC/B0000282000~0" modify default attributes tablespace PSAPODSI;
alter index "/BIC/B0000433000~0" modify default attributes tablespace PSAPODSI;

And all is happy now.

Thanks!

Vince

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Vince

Could you please have a short check on your tables TAORA and IAORA. There might still be an entry for PSAPODS2I, in your case probably for TABART DODS.

Dictionary objects do have a TABART in their technical settings, each TABARTs has a data tablespace / index tablespace assigned.

Regards

Michael

vince_laurent
Active Participant
0 Kudos

Thanks for the reply, but no, it isn't there. In fact I looked at all the user tables and indexes for a TABSPACE or INDSPACE name of PSAPODS2I and found none. I have even checked TABART, TABKAT, TGORA, IGORA, TSORA, IAORA, DD09L, DDART and DARTT.

It HAS to be somewhere for when I pull the DDL teh database gets it's information from somewhere. I just don't know enough how DDL is created and where it is stored.

Vince

former_member204746
Active Contributor
0 Kudos

a few things to check:

consider adapting table RSDCUBE fields CUBEDATCLS, DIMEDATCLS, AGGRDATCLS and ADMIDATCLS

Also check ODS objects table RSDODSO, fields ODSADATCLS and ODSMDATCLS

vince_laurent
Active Participant
0 Kudos

Both pretty much empty. The '...' means MANY blank rows.

SQL> select CUBEDATCLS, DIMEDATCLS, AGGRDATCLS, ADIMDATCLS

2 from rsdcube

3 /

CUBED DIMED AGGRD ADIMD

-


-


-


-


.

.

.

895 rows selected.

SQL> select odsadatcls, odsmdatcls

2 from rsdodso;

ODSAD ODSMD

-


-


.

.

DODS DODS

.

.

APPL1 APPl1

.

.

DODS DODS

DODS DODS

.

.

478 rows selected