Upgrade from 40B to 4.7 on Windows Oracle block co...

Hi All,

We are performing an upgrade from 40B to 4.7 SR1, Prepare has been successful,

but now while performing actual upgrade we are getting error at EU_IMPORT5 phase and refered logs are mentioned below.

It says about Oracle block corruption we have taken restart of server too but still error is same , also SAP is running fine at other end.I am unable to perform checkdb as there is some problem with sapdba.Oracle 9.2.0.6 Windows platform is current platform.

But errors are as below , could anybody let me know how i can perform repair and continue with upgrade

K:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

K:\usr\sap\put\exe\R3load.exe: version R6.40/V1.4

K:\usr\sap\put\exe\R3load.exe -i K:\usr\sap\put\exchange\compack\EX000022.COD -p K:\usr\sap\put\log\EX000022.DPR -s K:\usr\sap\put\log\EX000022.DST -datacodepage 1100 -dbcodepage auto -nametab DDNTT~ DDNTF~ -t 288

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1017

DbSl Trace: CONNECT failed with sql error '1017'

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(DB) ERROR: DDL statement failed

(DROP INDEX "SMAPTNODER~REF")

DbSlExecute: rc = 103

(SQL error 1418)

error message returned by DbSl:

ORA-01418: specified index does not exist

(IMP) INFO: a failed DROP attempt is not necessarily a problem

DbSl Trace: ORA-1578 occured when executing SQL statement (parse error offset = 34)

(DB) ERROR: DDL statement failed

(CREATE INDEX "SMAPTNODER~REF" ON "SMAPTNODER" ( "REF_TYPE" , "REF_OBJECT" ) TABLESPACE PSAPSTABI STORAGE (INITIAL 3862118 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )

DbSlExecute: rc = 99

(SQL error 1578)

error message returned by DbSl:

ORA-01578: ORACLE data block corrupted (file # 53, block # 67970)

ORA-01110: data file 53: 'D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA2'

(DB) INFO: disconnected from DB

K:\usr\sap\put\exe\R3load.exe: job finished with 1 error(s)

K:\usr\sap\put\exe\R3load.exe: END OF LOG: 20070929141109

Best Regards,

AjitR

SAP Managed Tags:
Oracle Database

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

you are lucky, this corruption is probably on an index.

refer to these notes:

365481- Block corruptions

10537 - ORA-1578/ORA-600 [3339] corrupted block on device

basically, go in SE14, choose your index SMAPTNODER~REF, delete it and re-create it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

But when i go to SE14 and check table SMAPTNODER it says

Table SMAPTNODER exists in database but not in the ABAP data dictionary

what should be the way out ?

Eric,

logs for EU_IMP5 phase are as below

EU_IMP5.ELG:

>>EU_IMPORT ERROR:, log file "EX000021.DPR": only 0 times "R3load.exe: job completed" found.

Analyze the log file EX000021.DPR for error messages or program abort.

>>EU_IMPORT ERROR:, log file "EX000022.DPR": only 0 times "R3load.exe: job completed" found.

Analyze the log file EX000022.DPR for error messages or program abort.

EX000021.DPR:

K:\usr\sap\put\exe\R3load.exe: START OF LOG: 20070929140222

K:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

K:\usr\sap\put\exe\R3load.exe: version R6.40/V1.4

K:\usr\sap\put\exe\R3load.exe -i K:\usr\sap\put\exchange\compack\EX000021.COD -p K:\usr\sap\put\log\EX000021.DPR -s K:\usr\sap\put\log\EX000021.DST -datacodepage 1100 -dbcodepage auto -nametab DDNTT~ DDNTF~ -t 228

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1017

DbSl Trace: CONNECT failed with sql error '1017'

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(DB) ERROR: DDL statement failed

(DROP INDEX "BMTNODE01T~NO1")

DbSlExecute: rc = 103

(SQL error 1418)

error message returned by DbSl:

ORA-01418: specified index does not exist

(IMP) INFO: a failed DROP attempt is not necessarily a problem

DbSl Trace: ORA-1578 occured when executing SQL statement (parse error offset = 34)

(DB) ERROR: DDL statement failed

(CREATE INDEX "BMTNODE01T~NO1" ON "BMTNODE01T" ( "NODE_ID" , "EXT_KEY" ) TABLESPACE PSAPSTABI STORAGE (INITIAL 2672947 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )

DbSlExecute: rc = 99

(SQL error 1578)

error message returned by DbSl:

ORA-01578: ORACLE data block corrupted (file # 53, block # 12679)

ORA-01110: data file 53: 'D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA2'

(DB) ERROR: DDL statement failed

(DROP INDEX "BMTNODE01T~NOD")

DbSlExecute: rc = 103

(SQL error 1418)

error message returned by DbSl:

ORA-01418: specified index does not exist

(IMP) INFO: a failed DROP attempt is not necessarily a problem

DbSl Trace: ORA-1578 occured when executing SQL statement (parse error offset = 34)

(DB) ERROR: DDL statement failed

(CREATE INDEX "BMTNODE01T~NOD" ON "BMTNODE01T" ( "SPRAS" , "NODE_ID" , "EXT_KEY" ) TABLESPACE PSAPSTABI STORAGE (INITIAL 2784768 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )

DbSlExecute: rc = 99

(SQL error 1578)

error message returned by DbSl:

ORA-01578: ORACLE data block corrupted (file # 53, block # 12679)

ORA-01110: data file 53: 'D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA2'

(DB) INFO: disconnected from DB

K:\usr\sap\put\exe\R3load.exe: job finished with 2 error(s)

K:\usr\sap\put\exe\R3load.exe: END OF LOG: 20070929140612

EX000022.DPR :

K:\usr\sap\put\exe\R3load.exe: START OF LOG: 20070929140619

K:\usr\sap\put\exe\R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP

K:\usr\sap\put\exe\R3load.exe: version R6.40/V1.4

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1017

DbSl Trace: CONNECT failed with sql error '1017'

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(DB) ERROR: DDL statement failed

(DROP INDEX "SMAPTNODER~REF")

DbSlExecute: rc = 103

(SQL error 1418)

error message returned by DbSl:

ORA-01418: specified index does not exist

(IMP) INFO: a failed DROP attempt is not necessarily a problem

DbSl Trace: ORA-1578 occured when executing SQL statement (parse error offset = 34)

(DB) ERROR: DDL statement failed

DbSlExecute: rc = 99

(SQL error 1578)

error message returned by DbSl:

ORA-01578: ORACLE data block corrupted (file # 53, block # 67970)

ORA-01110: data file 53: 'D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA2'

(DB) INFO: disconnected from DB

K:\usr\sap\put\exe\R3load.exe: job finished with 1 error(s)

K:\usr\sap\put\exe\R3load.exe: END OF LOG: 20070929141109

When i go to SE14 and give table names for both like BMTNODE01T or SMAPTNODER both gives error as

Table SMAPTNODER exists in database but not in the ABAP/4 data dictionary

What could be the problem.

Best Regards,

AjitR

you got multiple bad oracle blocks. this is not normal and you should find out why this happened.

at this point, I would do one of the following:

1. reorg table PSAPSTABI (check SAP note 646681)

2. restart db loads from scratch.

I can't believe the bizarre error you are getting!

Eric ,

One more thing i would like to share with you ,

when i go to transaction DB02 and check --> database and abap dictionary -->

check -->

i get these indexes under

Unknown objects in ABAP Dictionary

DB tables

But this same operation on PRD system doesnt show anything ,

but my system is copy of PRD only.

Are you still advice to reorg the tablespace.

My advice remains. either reorg or restart DB load.

your system is not completely setup, so, do not rely on DB02 settings just yet.

Message was edited by:

Eric Brunelle

Eric,

I will Reorg tablespace through SAPDBA , do i need to backup anything.

users are already locked ?

I have offline backup before and after Prepare.

Eric ,

could you please let me know while doing reorganisation through SAPDBA

which out od 2 options i should choose :

. Reorganise Tablespace

. Reorganise Tablespace and data files

Best Regards,

AjitR

I have selected 2nd option Reorganise Tablespace and data files

and below are the logs

*******************************************************************************

SAPDBA - SAP Database Administration for ORACLE *****

*******************************************************************************

SAPDBA V6.20 Reorg. tablespace incl. datafiles

SAPDBA release: 6.20

Patch level : 113

Patch date : 2003-08-08

ORACLE_SID : TST

ORACLE_HOME : D:\oracle\TST\920

ORACLE VERSION: 9.2.0.5.0

Database state: 'open'

SAPR3 : 40B

SAPDBA DB USER: system (standard)

OS real user : tstadm

OS eff. user : tstadm

Command line : sapdba

HOST NAME : SAPTEST

OS SYSTEM : Windows NT

OS RELEASE : 5.0 (Build 2195) Service Pack 4

PROCESSOR : Intel

NO. PROCs : 1

Log file : 'G:\oracle\TST\sapreorg\0710020258.rtd'

Log start date: '2007-10-02'

Log start time: '02.58.31'

*******************************************************************************

###############################################################################

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Program options:

Reorganize tablespace by dropping and

recreating incl. data file(s)

- SAPDBA checks and requires SAP name conventions

- ORACLE-SID: TST

- ORACLE-HOME: D:\oracle\TST\920

- Working directory: G:\oracle\TST\sapreorg

- Dump destination: G:\oracle\TST\sapreorg 2572 M

- Dump method: ORACLE export, check, no compress, no chop

- Export/import buffer size: 3000000

- Commit during import: yes

- Exp./imp. parallel degree: 1

- Direct path export: yes

- Compress extents: yes

- Reduce object size: no

- Use ABAP dict. for NEXT: no

- Use ABAP dict. for tsp.: no

- Change storage manually: no

- Check space: for all extents

- Parallel index degree: 1

- Hide tables during reorg.: no

- Select condition is:

"WHERE TABLESPACE_NAME='PSAPSTABI'"

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Working (checking temporary tablespace)

(2007-10-02 02.58.31) ...

SAPDBA: Working subdirectory created:

'G:\oracle\TST\sapreorg\0710020258'.

Working (selecting segments)

(2007-10-02 02.58.31) ...

SAPDBA: No. of selected segments: 8898

SAPDBA: Using same constraint definitions as

selected during the last reorganization!

Working (selecting indexes)

(2007-10-02 02.58.41) ...

SAPDBA: No. of selected indexes: 8898

Working (selecting left IOT parameters)

(2007-10-02 02.59.28) ...

Working (selecting partitions)

(2007-10-02 02.59.28) ...

SAPDBA: No. of selected main segments: 15279

Working (selecting left table partitions)

(2007-10-02 02.59.28) ...

Working (selecting left index partitions)

(2007-10-02 02.59.28) ...

Working (selecting left table subpartitions)

(2007-10-02 02.59.29) ...

Working (selecting left index subpartitions)

(2007-10-02 02.59.29) ...

Working (selecting table partition defaults)

(2007-10-02 02.59.29) ...

Working (selecting index partition defaults)

(2007-10-02 02.59.29) ...

Working (checking locked tables)

(2007-10-02 02.59.30) ...

SAPDBA: Lock check for 0 tables to be reorganized

and for 6381 only referenced tables.

No database tables locked at all.

Working (writing tables to analyze.lst)

(2007-10-02 02.59.30) ...

Working (writing indexes to analyze.lst)

(2007-10-02 02.59.30) ...

SAPDBA: No export dump necessary!

Working (selecting data/temp files of PSAPSTABI)

(2007-10-02 02.59.42) ...

SAPDBA: File 'd:\oracle\tst\sapdata1\stabi_1\stabi.data2'

does not follow SAP conventions:

Different numbers of file name and last subdirectory!

SAPDBA: Reorganization terminated with error!

Process aborted because of errors

while creating SQL- and shell scripts.

No database data have been changed.

Warning! Scripts (if created)

may be not complete or may include errors!

A restart with these scripts is not supported!

SAPDBA: End of log file 'reorganization of tablespace and data files'

###############################################################################

*******************************************************************************

Log file : 'G:\oracle\TST\sapreorg\0710020258.rtd'

Log end date : '2007-10-02'

Log end time : '03.00.25'

Database state: 'open'

*******************************************************************************

END OF SAPDBA LOG FILE *****

*******************************************************************************

how this datafile 2 is not following SAP convention ?

hi,

not sure about your question.

The error is clear:

SAPDBA: File 'd:\oracle\tst\sapdata1\stabi_1\stabi.data2'

does not follow SAP conventions:

Different numbers of file name and last subdirectory!

That file was not added with SAPDBA or it was done with a version that has/had a bug.

You should rename the file in order to follow SAP standards.

Before you ask, there is a thread indicating how to do it.

You are right , i got information from my DBA due to some problem with SAPDBA tool they added the same through Oracle commands on urgent basis.

alter tablespace add datafile

but file name seems to same

File which was by default in SAP is first one

D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA1

and one we have added through command line is

D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA2

i dont find anydifference between them could you tell me how to go ahead or thread at least ?

OHHH i got the problem ,

I think it should be

D:\ORACLE\TST\SAPDATA1\STABI_2\STABI.DATA2

and not D:\ORACLE\TST\SAPDATA1\STABI_1\STABI.DATA2

can you provide me the thread to rename the same.

Hi all,

I have renamed the datafile and reorganised the tablepspace now it contains only one datafile as original.I am running upgrade again.

Upgrade continued with the phase and now at phase SHADOW_IMPORT_UPG1

i got below error:

Phase SHADOW_IMPORT_UPG1:

Deleting file K:\usr\sap\put\log\CONNECT.LOG

R3up> Starting subprocess tp.exe with id 3028 at 20071002055202

EXECUTING K:\usr\sap\put\exe\tp.exe pf=K:\usr\sap\put\bin\SHDUPGIMP1.TPP put TST

Environment: dbs_ora_schema=SAPR3

Environment: dbs_ora_tnsname=TST

Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC

Environment: ORACLE_HOME=D:\oracle\TST\920

Environment: ORACLE_SID=TST

This is K:\usr\sap\put\exe\tp.exe version 340.07 (release 640)

This is K:\usr\sap\put\exe\R3trans.exe version 6.09 (release 640 - 28.04.04 - 16:14:00).

2EETW000 sap_dext called with msgnr "1":

2EETW000 -

db call info -

2EETW000 function: db_xrtab

2EETW000 fcode: RT_MI_LOAD

2EETW000 tabname: E071K~

2EETW000 len: 282

2EETW000 key: SAPK620MK02 R3TRTABUEDSAPPL 000079TDATEDISEGMENT E1UPSPRE *

2EETW000 retcode: 1

2EETW125 SQL error "1632" during "" access: "ORA-01632: max # extents (100) reached in index SAPR3.E071K^0"

K:\usr\sap\put\exe\R3trans.exe finished (0012).

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBCONFPATH is no longer used.

stopping on error 12 during SHADOW IMPORT

tp returncode summary:

TOOLS: Highest return code of single steps was: 12

WARNS: Highest tp internal warning was: 0118

tp finished with return code: 12

I can make increase the extent but how to find out for which tablespace it is present ?

what are exact steps ...

Hi all,

Can anybody please let me know for which tablespace i should increase the Extent or for which table Max Extent reached . How should i solve this problem ??

Any help is really appreciated.

go into SE14

select table

click on STORAGE PARAMETERS

press F5

change value from 100 to 505

change next extent size to a bigger value

on long term, you should consider migrating tablespace to locally managed.

also, I hate begging for points (and this is not what I am doing now), but you should reward good/helpful answers with points...

especially on the topic " System copy for ABAP+JAVA system using SAPINST method". Markus gave you tremendous help and you have not rewarded him with any points. this is your way of saying "thanks".

Eric,

I apologize for the same , but the thread is still open and i didnt find the solution even from OSS guys because it was BW system copy which has some other prerequisites.

But Markus always been helpfull to the MAX , could you please let me know how to reward points and what is standard , is there any thread where i get this info.

I even have same opinion as yours and myself never asked for points to others.

But i want to learn how to reward ,

Also i am trying the changes suggested by you and will get back to you shortly

thanks once again

Best Regards,

AjitR

if you started the topic, you will see a list of options on the left of each reply you get (all except yours!)

options are:

o Unassign

o Solved problem (10)

o Very helpful answer (6)

o Helpful answer (2)

just choose the level you want. you can change your idea later. obviously, if your problem is not still resolved, do not flag an answer with "solved problem". Note that you are not obligated to provide points, but it rewards people who help others. more about this at https://www.sdn.sap.com/irj/sdn/crphelp#posted

anyways, back to topic. supply results of using SE14 and tell me if this works.

have a good day.

Sorry Eric ,

But i am not able to get steps you mentioned ,

i went to SE14 and gave tablename .... E071K then i click on storage parameter

Src InitExt NextExt MinE MaxE Tablespace name FG Fr Pf Pu

DBS 5536 20480 1 300 PSAPSTABD 1 1 10 40

CMP 16 10240 1 300 PSAPSTABD 1 1 10 40

USR

Now where should i put values you mentioned.

Under USR empty row or some other row ??

Please let me know where to put next Extent value

Eric,

I have done required changes for particular tabel as well as index through sapdba and made maxentent = unlimited ,

But now error remanins the same and it came for some other index

I have also done the same but now it is showing error for 3rd some other index ,

how can i make all indexes of table change extent value ... at a same time ?

I forgot that you are still running on r/3 4.0b. the SE14 screen is completely different.

go in DB13 and run job NextExtent, then fix your new index that failed and try again.

the NextExtent job will recalc the next_extent size to a better value.

but I repeat, a long-term solution is converting tablespaces to locally-managed.

Eric,

I am really sorry but because of 40B even my DB13 jobs are not working even after successful execution of oradbusr.sql ,

Is there any other way to schedule Adapt next extent job which we schedule from DB13 from sapdba menu.

Hi all,

I have executed the job through Brtools and now the same phase is finished

Now i am getting error at phase JOB_RSPUSCAD and logs says

Batchjob RSPUSCA4 failed

SEVERE error : batchjob RSPUSCA4 aborted.

In sm37 jobs is continuously getting cancelled with logs below;;;;

03.10.2007 03:26:06 00 516 Job started

03.10.2007 03:26:06 00 550 Step 001 started (program RSPUSCA4, variant , user name DDIC)

03.10.2007 03:26:15 00 671 ABAP/4 processor: DBIF_RSQL_SQL_ERROR03.10.2007 03:26:15 00 518 Job cancelled

There is no space problem and i have triied to restart this process many times but error is still the same.

Can anybody suggess something on the same.

Appreciate help regarding batch job RSPUSCA4 failure .

check ABAP dump created in ST22.

Eric,

Rewarded points to you and Mark.

Problem solve after analysing the dump but now there is problem at ACT_620 phase.

we are getting error at ACT_620

phase.

During this phase there was a message for performing modification

adjustments through

SPDD and we have done neccessary changes and restarted the upgrade but

it did result into error

as below

ACTUPG.ELG:

**************************************************

LIST OF ERRORS AND RETURN CODES *******

**************************************************

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~DDIC ACTIVATION ERRORS and RETURN CODE in SAPAAAA620.TST

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1EEDO519X"Lock object" "E_BAMMAPNG" could not be activated

1EEDO519 "Lock object" "E_BAMUIBT" could not be activated

1EEDO519 "Table" "AFRU" could not be activated

1 ETP111 exit code : "8"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCC620.TST

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 ETP111 exit code : "8"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCG620.TST

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 ETP111 exit code : "8"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~DDIC ACTIVATION ERRORS and RETURN CODE in SAPAD62023.TST

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 ETP111 exit code : "8"

We loged into shadow instance with user DDIC but we were not able to

loginto the same

with any other user ( as we did before for SPDD changes ) it was giving

message 'upgrade is

still runnign no logon posible '. But at the same time we were able to

We stopped the upgrade and taken restart of SAP system and database.

After restart we are now able to loginto original instance , but we are

not able to login

to shadow instance.We tried to start the upgrade and ACT_620 phase is

continued but it has been running from almost 12 Hrs now and progress

bar is showing 100 % completed but it is not moving

to next phase.

we cant start manually shadow instance.

K:\usr\sap>cd put

K:\usr\sap\put> cd bin

K:\usr\sap\put\bin>R3up startshd

'R3up' is not recognized as an internal or external command,

operable program or batch file.

Upgrade has been running from more than 14 hrs but not going to next phase

SLOG620 logs as below

ERROR: Please check trace file dev_evt.