on 02-07-2014 12:42 PM
Dear upgrade-gurus
I'm upgrading a sandbox system from NW701 to NW73. But unfortunately the upgrade hangs in phase PREP_SPACECALC/EU_IMPSPC
Ther is no logfile written in /usr/sap/SID/SUM/abap/log. TOP shows SAPup running like hell, but nothing happens! I restarted upgrade process and repeated the phase, but nothing changed.
ls -ltr on /usr/sap/SID/SUM/abap/log shows:
-rw-r--r-- 1 bisadm sapsys 32648 Feb 6 19:43 TPSIZECALL.SAV
-rw-r--r-- 1 bisadm sapsys 72824 Feb 6 19:44 GDBSSHD.LOG
-rw-r--r-- 1 bisadm sapsys 422333 Feb 6 19:44 TABSPCP.LOG
-rw-r--r-- 1 bisadm sapsys 1717 Feb 6 19:44 SQLDBSCRIPT.SAV
-rw-r--r-- 1 bisadm sapsys 172722 Feb 6 19:44 PHASES.SAV
-rw-r--r-- 1 bisadm sapsys 3432 Feb 6 19:44 TPSQLSTD.OUT
-rw-r--r-- 1 bisadm sapsys 1942 Feb 6 19:44 PHASES.LOG
-rw-rw-r-- 1 bisadm sapsys 2112128 Feb 6 19:44 SQLDBSCRIPT.OUT
-rw-r--r-- 1 bisadm sapsys 936 Feb 6 19:44 DYNSPC.LOG
-rw-r--r-- 1 bisadm sapsys 2992 Feb 7 09:13 ENVDUMP.LOG
-rw-r--r-- 1 bisadm sapsys 3220 Feb 7 09:13 ENVDUMP.SAV
-rw-r--r-- 1 bisadm sapsys 156 Feb 7 09:13 SAPup.out
-rw-r--r-- 1 bisadm sapsys 4214 Feb 7 09:13 SAPupFeatures.SAV
-rw-r--r-- 1 bisadm sapsys 3604 Feb 7 09:13 SAPupStat.log
-rw-r--r-- 1 bisadm sapsys 1118 Feb 7 09:13 SAPupFeatures.log
-rw-r--r-- 1 bisadm sapsys 909 Feb 7 09:13 EUIMPSPC.SAV
-rw-rw-r-- 1 bisadm sapsys 16099 Feb 7 09:13 SLOG730
-rw-r--r-- 1 bisadm sapsys 29540 Feb 7 09:13 SAPup.ECO
-rw-rw-r-- 1 bisadm sapsys 96353 Feb 7 09:13 ULOG14_1
-rw-r--r-- 1 bisadm sapsys 656 Feb 7 09:13 EUIMPSPC.LOG
-rw-r--r-- 1 bisadm sapsys 103928 Feb 7 09:13 SAPup.log
-rw-r--r-- 1 bisadm sapsys 139269 Feb 7 09:13 SAPupConsole.log
-rw-rw-r-- 1 bisadm sapsys 49973 Feb 7 09:13 ALOG730
ALOG730: ========================================================================
2014020619232400198f
SAPKITLRE5 BIS.ALL o 0000 20140206192326 bisadm des00933 20140206192325001991
SAPKITLRE6 BIS.ALL o 0000 20140206192329 bisadm des00933 201402061923260019a0
SAPK-73002INSAPBSFND BIS.ALL o 0000 20140206192330 bisadm des00933 201402061923290019aa
SAPK-63402INFINBASIS BIS.ALL o 0000 20140206192330 bisadm des00933 201402061923300019ac
SAPK-63402INSEMBW BIS.ALL o 0000 20140206192332 bisadm des00933 201402061923300019ae
SAPKITLRE7 BIS.ALL o 0000 20140206192333 bisadm des00933 201402061923320019b0
SAPKITLRE8 BIS.ALL o 0000 20140206192334 bisadm des00933 201402061923330019b2
SAPK-73701INBICONT BIS.ALL o 0000 20140206192342 bisadm des00933 201402061923350019b4
SAPK-73702INBICONT BIS.ALL o 0000 20140206192348 bisadm des00933 201402061923420019cf
SAPK-73703INBICONT BIS.ALL o 0000 20140206192353 bisadm des00933 201402061923480019d1
SAPK-73704INBICONT BIS.ALL o 0000 20140206192359 bisadm des00933 201402061923530019e3
SAPK-73705INBICONT BIS.ALL o 0000 20140206192401 bisadm des00933 201402061924000019f8
SAPK-73706INBICONT BIS.ALL o 0000 20140206192415 bisadm des00933 201402061924010019fa
### Phase PREP_SPACECALC/TR_COLLTABS_PRP:
### Phase PREP_SPACECALC/TABSPC_PREP:
### Phase PREP_SPACECALC/RUN_GENOBJNUM:
### Phase PREP_SPACECALC/LIST_LOAD_SPC:
### Phase PREP_SPACECALC/DYNSPCADD:
### Phase PREP_SPACECALC/EU_IMPSPC:
### Phase PREP_SPACECALC/EU_IMPSPC:
SAPupConsole.log =================================================================
>> 2014/02/06 19:16:20 START OF PHASE PREP_SPACECALC/TR_GET_SPCREQ_DISC
<< 2014/02/06 19:24:22 END OF PHASE PREP_SPACECALC/TR_GET_SPCREQ_DISC
>> 2014/02/06 19:24:22 START OF PHASE PREP_SPACECALC/TR_COLLTABS_PRP
<< 2014/02/06 19:24:22 END OF PHASE PREP_SPACECALC/TR_COLLTABS_PRP
>> 2014/02/06 19:24:22 START OF PHASE PREP_SPACECALC/TABSPC_PREP
Determining index sizes via estimation factor 0.600000...
<< 2014/02/06 19:44:05 END OF PHASE PREP_SPACECALC/TABSPC_PREP
>> 2014/02/06 19:44:05 START OF PHASE PREP_SPACECALC/LIST_LOAD_SPC
<< 2014/02/06 19:44:07 END OF PHASE PREP_SPACECALC/LIST_LOAD_SPC
>> 2014/02/06 19:44:07 START OF PHASE PREP_SPACECALC/DYNSPCADD
<< 2014/02/06 19:44:09 END OF PHASE PREP_SPACECALC/DYNSPCADD
>> 2014/02/06 19:44:09 START OF PHASE PREP_SPACECALC/EU_IMPSPC
=================================================================================
System:
HP-UX IA64
Oracle 11203
Kernel 721_EXT Patchno. 100
Best regards
Willi eimler
Hello Willi
Can you check whether the logs are getting updated in the /usr/sap/SID/SUM/abap/tmp directory ?
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi RB,
nice to see you answering.
Nope, the files in SUM-abap-tmp don’t change. I made:
cd /usr/sap/SID/SUM
ls –ltrR | grep <today-date>
and the last changed files are the files in SUM-abap-log directory with date/time of the beginning of the phase. It looks like a freeze!
I’m updating the Kernel on the system and the SUM-abap-exe directory to 721_ext patch 201. I rebooted the system and now I restart the system and SUM.
Best regards
Willi Eimler
Morning Willi,
I believe the phase you are right now is about to start the clone size estimation.
I would check for any DB related errors at the alert log.
secondly I would update the kernel (at least the TP and R3TRANS) and see if that helps.
I see you are doing a kernel upgrade now. Let me know whether it helped.
Regards
RB
Morning RB,
I patched the Kernel to last STACK, booted the UNIX-Host, restarted SAP and SUM and checked the alert.log. No error messages. In the listener.log I found the messages:
---------------------------------------------------------------------------------------------------------------------------------
WARNING: Subscription for node down event still pending
10-FEB-2014 11:04:18 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=des00933)(USER=orabis))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296)) * status * 0
---------------------------------------------------------------------------------------------------------------------------------
I'm not sure if this is important. I'm searching for this message at marketplace and google.
And the upgrade still hangs. Do you know if in this phase the upgrade tries to connect to database or to sap?
Best regards
Willi Eimler
Hello Willi,
Check whether you are hitting the error mentioned in this SAP note.
If yes set the parameter _use_zero_copy_io=false and restart the database and see if that helps.
Regards
RB
Hi RB,
the Note is only for Windows systems. I read the Note before I started the upgrade and made the parameter _use_zero_copy_io = FALSE. I thought: "It's only for Windows but I don't want to be the first one who proves that UNIX is affected too"
79 rows selected.
SQL> show parameter _use_zero_copy_io
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
_use_zero_copy_io boolean FALSE
SQL>
Best regards
Willi Eimler.
Sorry RB,
I didn't read 1738989! I read
1635605 - CLIENT HANGS ON INSERT INTO TABLE WITH SECUREFILE
LOB
And this Note states only Windows is affected! But Note 1738989 refers to the bug described in Note 1635605.
Best regards
Willi Eimler
Hi RB,
the messagein the listener.log:
WARNING: Subscription for node down event still pending
10-FEB-2014 11:04:18 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=des00933)(USER=orabis))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647296)) * status * 0
appears even if SUM is stopped.
So I think it's not an issue of the upgrade.
Best regards
Willi Eimler
Hi RB,
I solved it! The problem was made by myself! The problem was a cyclic link.
I copied the Media DVDs to /usr/sap/BIS/SUM
After starting SUM and telling SUM where to find the DVDs the filesystem /usr/sap/BIS/SUM runs full. So I copied the Media DVDs to another filesystem and set a link to the new location.
But accidently I made a the following link:
In directory /usr/sap/BIS/SUM Media-> /usr/sap/BIS/SUM
So the link points to itself.
The SUM doesn't throw an error like: "Can't find resources I need". The SUM freezes.
I corrected the link and now it runs!
Best regards
Willi Eimler
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.