on 06-04-2012 12:23 PM
Hi
I have upgraded the kernel under our ECC6 system from 7.00 to 7.20 EXT (not unicode; SAPEXE/DB patch 201 + DW patch 220 and ILETOOLS patch 220) according to note 1636252. All hað gone well.
If I try no to start to system I got a message that the sid doesn't match in the job-log (dspjoblog):
collectSystemInfo: check instance profile DEV_DVEBMGS00_LYSDEV.
readInstInfoFromProfile: examining profile
"/usr/sap/DEV/SYS/profile/DEV_DVEBMGS00_LYSDEV".
collectSystemInfo: sid retrieved from instance profile
"/usr/sap/DEV/SYS/profile/DEV_DVEBMGS00_LYSDEV" does not match sid .
RtvSidCfg: DEV system info status is not OK (2).
StartAllInstances: Starting all instances of system DEV is not possible.
System configuration can not be retrieved.
O4STRSTP: Starting all instances of system DEV failed.
I have checked the instance profile and it contain the following entries:
SAPSYSTEMNAME = DEV
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
Is there anyone who can imaging what parameter is wrong?
Curd
Hi Curd,
that is exactly, what I had last weekend as well ;-(
I restored the 201 ILE, then STARTSAP was OK again. When I did start sap, it worked and has shown me 201 only instead of 220.
Then I removed SAPEXE & SAPEXEDB from the directory and used APYSIDKRN with *ADD again ... then it really worked fine - I could not believe ... so, ILE 220 seems not to work with older kernels and APYSIDKRN has errors, so that it "forgets" sometimes newer DW patches ...
... already looking forward to your experiences ...
Regards
Volker Gueldenpfennig
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Volker
Thanks for the answer. I have tried to run APYSIDKRN again only with SAPEXE/DB and IGS in the folder but now the process stops with saying that parameter DIR_CT_RUN is missing in profile (what is not hte case).
End of SAPCAR messages
Patch Apply Process run from QRPLOBJ/SAPILEXDEV at Mon Jun 4 14:17:48 2012
Input argument 1: ---> APYSAP <---
Input argument 2: ---> APYSIDKRN <---
Input argument 3: ---> DEV <---
Input argument 4: ---> kernel/* <---
Input argument 5: ---> *NONE <---
Input argument 6: ---> /sapmnt/DEV/patches/log/apysidkrn1338819330.log <---
Input argument 7: ---> *NONE <---
Input argument 8: ---> *FULLY <---
Input argument 9: ---> *NO <---
Input argument 10: ---> *NO <---
Input argument 11: ---> /usr/sap/trans/config/infoapar.710 <---
Input argument 12: ---> *ENV <---
Input argument 13: ---> *ENV <---
Input argument 14: ---> 1 <---
Input argument 15: ---> *ASP <---
Input argument 16: ---> *NONE <---
Program delivered with ILE patch 201
ERROR: Parameter DIR_CT_RUN missing in profile '/sapmnt/DEV/profile/START_DVEBMGS00_LYSDEV'
SAP_TOOLS library is still with patch 220. That's the only availible on the Marketplaces.
Regards
Curd Abstoss
To anyone reading this note: 1702912 provides a workaround to this problem!
I hope this helps someone else...
Regards,
Yannick C.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAP's BC_OP_AS4 answer on this issue:
if you copy your kernel thru your landscape, then you must ensure to runeach of the involved systems in the same environment, especially with
same JVM.
Take note that i use a copy of an updated (lib_dbsl_189) kernel
librairy from my sandbox to do the APYSAP on my dev instance. Like
usualy i deploy from sandbox thru dev, QA and Prod.
My sandbox has been switched to SAP JVM 4 however all others not yet
they still use IBM's jdk 1.4
Kind regards,
Roger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ho Roger,
I was mislead by the title of this thread - so I looked for an error from a 720 EXT kernel.
In a 7.01 kernel, the error message only shows up if the instance profile cannot be read or does not contain the necessary data. You wrote "my DBU_DVEBMGS49_sapdbu instance that was suddenly missing all those parameters". Which parameters do you mean? Is it lines in the instance profile or environment parameters you see with WRKENVVAR aftwer logging on as DBUOFR/DBUADM?
Best regards
B. Wolf
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Bernhard,
"Which parameters do you mean?"
Those listed on my post @
Roger Arsenault Jun 8, 2012 10:26 PM
plus many more, i had to restore the old instance profile.
One thing that i suspect,
i installed the kernel patch on my sandbox then copied it's kernel librairy to another SAP instance.
Then i used this kernel librairy to be applyed (APYSAP)
Nothing particular so far.
Here's my suspicion: this source instance has been migrated to SAP JVM 4 not the target.
APYSAP changed the instance profile adding
# generated entry (apyr3fix):
SAPJVM_VERSION = 4.1.020
and removing many other entries.
I yet have to test it again, and in the affirmative i'll address it to BC_OP_AS4.
Best regards,
Roger
Thanks Bernhard,
but i'm not working on 7.20 EXT
i am upgrading a 701NUC kernel on iSeries from DW_183 dbsl_178 ILE_178 J2EE_1 to dbsl_189.
and the issue looks similar.
Best regards,
Roger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Roger,
please read SAP note 1728238 (currently being translated to English) and proceed accordingly.
Best regards,
B. Wolf
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello all,
i was able to restart my instance
i question myself on this strange state of my DBU_DVEBMGS49_sapdbu instance that was suddenly missing all those parameters:
SAPSYSTEMNAME = DBU
SAPSYSTEM = 49
INSTANCE_NAME = DVEBMGS49
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = /usr/sap/DBU/SYS/exe/run
SAPLOCALHOST = sapdbu
i think that i'll address this to BC_OP_AS4
Best regards,
Roger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello to all,
Volker quoted "... already looking forward to your experiences ..." so here's mine :
I have a similar issue on a different kernel.
i am upgrading a 701NUC kernel on iSeries from DW_183 dbsl_178 ILE_178 J2EE_1 to dbsl_189.
( lib_dbsl_189-10006284.sar ) only
i can't restart the instance since.
i get the following messages in START_DBU QPJOBLOG spool file:
Message . . . . : collectSystemInfo: sid retrieved from instance profile
"/usr/sap/DBU/SYS/profile/DBU_DVEBMGS49_sapdbu" does not match sid DBU.
RtvSidCfg: DBU system info status is not OK (2).
invalid system configuration.
Message . . . . : R3DBU400/R3INLPGM: Could not retrieve system environment
information for system DBU.
Best regards,
Roger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.