R3 Homogeneous System Copy

[Former Member]

Hello to all,

I'm doing a Homogeneous System Copy from 46C SR2 and when I run the fhase DBR3LOADEXEC_NT_ORA, I'd encountered an error ( 1 out of 16). The error was :

#Trying to create primary key "SRRELROLES~0"

DbSl Trace: ORA-1630 occured; SQL statement is ==>

(IMP) ERROR: CREATE statement failed for object "SRRELROLES"

(CREATE UNIQUE INDEX "SRRELROLES~0" ON "SRRELROLES" (

"CLIENT", "OBJKEY", "OBJTYPE", "LOGSYS", "ROLETYPE"

) TABLESPACE PSAPBTABI STORAGE (INITIAL 0000000016K

NEXT 0000000160K MINEXTENTS 0001 MAXEXTENTS 0300 PCTINCREASE

0000 ))

DbSlExecute: rc = 99

(SQL error 1630)

error message returned by DbSl:

ORA-01630: max # extents (300) reached in temp segment in tablespace PSAPBTABI

Appreciated the help for this error.

Regards,

Desiree

[david_malinconici2 · Accepted solution]

It's a problem related to the extents number, so you must increase it.

Open the file DDLORA.TPL, go to section "# index storage parameters" and in the sub section "sto:" change the value of the last column to 2147483645.

Then restart the process.

Hope this helps.

David

[Former Member · Accepted solution]

Hi David.

I'm change the file DDLORA.TPL in the section index storage parameters, but the error is the same.

The information of the file DDLORA.TPL is the following:

prikey: AFTER_LOAD ORDER_BY_PKEY

seckey: AFTER_LOAD

cretab: CREATE TABLE &tab_name

( /{ &fld_name &fld_desc /-, /} )

TABLESPACE &location

STORAGE (INITIAL &init

NEXT &next

MINEXTENTS &minext

MAXEXTENTS &maxext

PCTINCREASE &pctinc )

crepky: CREATE UNIQUE INDEX &pri_key

ON &tab_name

( &key_fld /-, )

TABLESPACE &location

STORAGE (INITIAL &init

NEXT &next

MINEXTENTS &minext

MAXEXTENTS &maxext

PCTINCREASE &pctinc )

creind: CREATE &unique INDEX &ind_name

ON &tab_name

( /{ &fld_name /-, /} )

TABLESPACE &location

STORAGE (INITIAL &init

NEXT &next

MINEXTENTS &minext

MAXEXTENTS &maxext

PCTINCREASE &pctinc )

negtab: LICHECK MLICHECK

negind: LICHECK_{0 MLICHECK}0 LICHECK^{0 MLICHECK}0

negvie:

1. table storage parameters

loc: APPL0 PSAPSTABD 0000

APPL1 PSAPBTABD 0000

APPL2 PSAPPOOLD 0000

CLUST PSAPCLUD 0000

POOL PSAPPOOLD 0000

SDIC PSAPDDICD 0000

SDOCU PSAPDOCUD 0000

SLDEF PSAPEL46BD 0000

SLEXC PSAPEL46BD 0000

SLOAD PSAPLOADD 0000

SPROT PSAPPROTD 0000

SSDEF PSAPES46BD 0000

SSEXC PSAPES46BD 0000

SSRC PSAPSOURCED 0000

TEMP PSAPPROTD 0000

USER PSAPUSER1D 0000

USER1 PSAPUSER1D 0000

sto: 0 0000000016K 0000000040K 0001 0300

1 0000000016K 0000000160K 0001 0600

10 0000000016K 0001310720K 0001 0150

11 0000000016K 0002621440K 0001 0150

12 0000000016K 0005242880K 0001 0150

13 0000000016K 0010485760K 0001 0150

14 0000000016K 0020971520K 0001 0150

2 0000000016K 0000000640K 0001 0300

3 0000000016K 0000002560K 0001 0300

4 0000000016K 0000010240K 0001 0300

5 0000000016K 0000020480K 0001 0300

6 0000000016K 0000040960K 0001 0300

7 0000000016K 0000081920K 0001 0300

8 0000000016K 0000163840K 0001 0300

9 0000000016K 0000327680K 0001 0300

1. index storage parameters

loc: APPL0 PSAPSTABI 0000

APPL1 PSAPBTABI 0000

APPL2 PSAPPOOLI 0000

CLUST PSAPCLUI 0000

POOL PSAPPOOLI 0000

SDIC PSAPDDICI 0000

SDOCU PSAPDOCUI 0000

SLDEF PSAPEL46BI 0000

SLEXC PSAPEL46BI 0000

SLOAD PSAPLOADI 0000

SPROT PSAPPROTI 0000

SSDEF PSAPES46BI 0000

SSEXC PSAPES46BI 0000

SSRC PSAPSOURCEI 0000

TEMP PSAPPROTI 0000

USER PSAPUSER1I 0000

USER1 PSAPUSER1I 0000

sto: 0 0000000016K 0000000040K 0001 0300

1 0000000016K 2147483645K 0001 0300

10 0000000016K 0000327680K 0001 0150

11 0000000016K 0000655360K 0001 0150

12 0000000016K 0001310720K 0001 0150

13 0000000016K 0002621440K 0001 0150

14 0000000016K 0005242880K 0001 0150

2 0000000016K 0000000160K 0001 0300

3 0000000016K 0000000640K 0001 0300

4 0000000016K 0000002560K 0001 0300

5 0000000016K 0000005120K 0001 0300

6 0000000016K 0000010240K 0001 0300

7 0000000016K 0000020480K 0001 0300

8 0000000016K 0000040960K 0001 0300

9 0000000016K 0000081920K 0001 0300

Thanks for the help

Desiree

[david_malinconici2 · Accepted solution]

Maybe you changed the wrong value.

You have to change the section sto: under # index storage parameters as follows:

sto: 0 0000000016K 0000000040K 0001 2147483645

1 0000000016K 0000000160K 0001 2147483645

10 0000000016K 0000327680K 0001 2147483645

11 0000000016K 0000655360K 0001 2147483645

12 0000000016K 0001310720K 0001 2147483645

13 0000000016K 0002621440K 0001 2147483645

14 0000000016K 0005242880K 0001 2147483645

2 0000000016K 0000000160K 0001 2147483645

3 0000000016K 0000000640K 0001 2147483645

4 0000000016K 0000002560K 0001 2147483645

5 0000000016K 0000005120K 0001 2147483645

6 0000000016K 0000010240K 0001 2147483645

7 0000000016K 0000020480K 0001 2147483645

8 0000000016K 0000040960K 0001 2147483645

9 0000000016K 0000081920K 0001 2147483645

[Former Member · Accepted solution]

Hello David.

The process I correctly execute without errors changing the file DDLORA.TPL.

Thank for help me.

It wanted to know like the value to change in the file DDLORA.TPL ???

Desiree

[david_malinconici2 · Accepted solution]

You got the error because you reached the max number of extents, which is obtained from DDLORA.TPL and used in the sql statement.

By increasing the value you can avoid similar problems.

Cheers,

David

[Former Member · Accepted solution]

Hi all

I am doing heterogen copy (change OS from solaris to win)

and i have this problem too.

I change last column in section sto: under #index storage parameters to 2147483645, and restart process, but the problem was not closed

please help

Message was edited by:

Kirill Pomerantsev

[Former Member · Accepted solution]

Hello Kirill

Excuse not to help. I do not know the process of heterogeneous System Copy under Solaris.

Desiré

[Former Member · Accepted solution]

Hi Dcardena

I am doing import on Windows system.

On Solaris I make export data dir, and this phase is ok.

[Former Member]

Hi Andreas

I'm enlarge the tablespaces PSAPBTABI vía SAPDBA - Tablespace Administration - Alter tablespace add data file.

I restart the Import but the error is the same.

Desiré

[andreas_herzog]

tablespace PSAPBTABI has reached the max extents barrier..enlarge it using sapdba/brtools and restart the copy...

GreetZ, AH

[Former Member]

Hi Andreas

I'm enlarge the tablespaces PSAPBTABI vía SAPDBA - Tablespace Administration - Alter tablespace add data file.

I restart the Import but the error is the same.

Desiré