on 11-06-2008 1:45 PM
Hi All,
Iam applying basis patch 12 .
I have done this on other system with no problem, but on the
current one, it seems to hang on the "imp all" step (displayed
next to the spinning clock.
I opened another session I canceled spam transaction.
it is giving error.
Import_proper.
How to overcome this problem.
Regards
Siva
we are starting reinstallation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>we are starting reinstallation.
what do you mean of this? mean you are scrapping your existing installed R/3 and again going to reinstall again? do you think so you will not have the same error again?
keep in mind, you have to again apply DB patches, kernel upgrade steps has to be done.
cheers,
-Sunil
Check the logfiles in SPAM (in your second mode)
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Start import R3TRTABU/OSP/T_BM_CTX ...
Start import R3TRTABU/OSP/T_BM_RLV ...
Start import R3TRTABU/OSP/T_MDR_SETOP ...
Start import R3TRTABUAGR_TIMEB ...
AGR_TIMEB table class is 'C'. Entries are only imported to client '000'.
Start import R3TRTABUALLAZYMT2 ...
Start import R3TRTABUALMONISETS ...
sap_dext called with msgnr 1:
db call info
function: db_setget
fcode: RT_GET (0)
tabname: ALMONISETS
len (char): 28
key: MSSAP CCMS Monitor Templates
ok fetches: 0
last entry:
retcode: 1
SQL error 3106 accessing : ORA-03106: fatal two-task communication protocol e
Main import
End date and time : 20081103031720
Ended with return code: ===> 12 <===
######################################
Regards
Siva
you can download the patches from https://service.sap.com/swcenter-3pmain --> select database / OS
cheers,
-Sunil
Sunil,
I am getting errors.
SAPQUA:eqaadm> opatch lsinventory
Unrecognized option: -Xj9
JVMCI119: Error parsing IBM_JAVA_OPTIONS java options - rc=-6
Could not create JVM.
Usage: java.bin [-options] class [args...]
(to execute a class)
or java.bin -jar [-options] jarfile [args...]
(to execute a jar file)
where options include:
-cp -classpath <directories and zip/jar files separated by 😆
set search path for application classes and resources
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version
-showversion print product version and continue
-? -help print this help message
OPatch failed with error code 1
SAPQUA:eqaadm>
Regards
Siva
Hi,
SAPQUA:oraeqa> opatch lsinventory
Invoking OPatch 10.2.0.2.0
Oracle interim Patch Installer version 10.2.0.2.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home : /oracle/EQA/102_64
Central Inventory : /oracle/oraInventory
from : /oracle/EQA/102_64/oraInst.loc
OPatch version : 10.2.0.2.0
OUI version : 10.2.0.2.0
OUI location : /oracle/EQA/102_64/oui
Log file location : /oracle/EQA/102_64/cfgtoollogs/opatch/opatch-2008_Nov_06_11-
40-47-CST_Thu.log
Lsinventory Output file location : /oracle/EQA/102_64/cfgtoollogs/opatch/lsinv/l
sinventory-2008_Nov_06_11-40-47-CST_Thu.txt
-
Installed Top-level Products (2):
Oracle Database 10g 10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 1 10.2.0.2.0
There are 2 products installed in this Oracle Home.
There are no Interim patches installed in this Oracle Home.
-
OPatch succeeded.
SAPQUA:oraeqa>
Regards
Siva
Hi Markus & sunil,
I applied patch, But problem is same.
APQUA:oraeqa> /oracle/EQA/102_64/OPatch/opatch apply
Invoking OPatch 10.2.0.2.0
Oracle interim Patch Installer version 10.2.0.2.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home : /oracle/EQA/102_64
Central Inventory : /oracle/oraInventory
from : /oracle/EQA/102_64/oraInst.loc
OPatch version : 10.2.0.2.0
OUI version : 10.2.0.2.0
OUI location : /oracle/EQA/102_64/oui
Log file location : /oracle/EQA/102_64/cfgtoollogs/opatch/opatch-2008_Nov_06_13-
42-32-CST_Thu.log
ApplySession applying interim patch '5099990' to OH '/oracle/EQA/102_64'
Invoking fuser to check for active processes.
Invoking fuser on "/oracle/EQA/102_64/bin/oracle"
OPatch detected non-cluster Oracle Home from the inventory and will patch the lo
cal system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local sy
stem.
(Oracle Home = '/oracle/EQA/102_64')
Is the local system ready for patching?
Do you want to proceed? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '5099990' for restore. This might take a
while...
Backing up files affected by the patch '5099990' for rollback. This might take a
while...
Patching component oracle.rdbms, 10.2.0.2.0...
Updating archive file "/oracle/EQA/102_64/lib/libserver10.a" with "lib/libserve
r10.a/opiexe.o"
Updating archive file "/oracle/EQA/102_64/lib/libserver10.a" with "lib/libserve
r10.a/opitsk.o"
Updating archive file "/oracle/EQA/102_64/lib/libcommon10.a" with "lib/libcommo
n10.a/ttcclr.o"
Running make for target ioracle
ApplySession adding interim patch '5099990' to inventory
Verifying the update...
Inventory check OK: Patch ID 5099990 is registered in Oracle Home inventory with
proper meta-data.
Files check OK: Files from Patch ID 5099990 are present in Oracle Home.
The local system has been patched and can be restarted.
OPatch succeeded.
SAPQUA:oraeqa>
Regards
Siva
Shumar,
it´s not only that one patch - you have to apply all the patches of note 871096 - Oracle Database 10g: Patch sets/patches for 10.2.0 (yes, those are 50+ single patches).
Many of those patches have notes for them, sometimes you need to execute some scripts on the database, on some patches you have to set special parameters to activate the fixes.
That´s Oracle...
Markus
The reason for what?
If you use Oracle as database you have to/should make sure you have the latest recommended patches applied - just to avoid problems like you have now implementing support packages.
Oracle is a really complex and huge database, many features are used "behind the scenes" and all those features contain bugs. SAP has this note for the release 10.2.0.2 to make sure, you are able to avoid problems - not run into them (as you are doing) and then try to fix them.
If you want to run a stable system I can just recommend doing as described in that note - read it frequently, check it for updates and apply updates if you have a maintenance cycle - after you have checked that they work on a test system.
If you read installation and upgrade guides you will notice, that SAP always recommends to read the most current version of that note and apply all patches. Depending on the installation CD set you used to install the system you may e. g. run into problems at some point described in
Note 1136063 - Oracle Direct Path Load leads to block corruptions in ASSM
(just as example)
Those corruptions can´t be fixed easily - if they can be fixed at all. You may hit serious problems and run very risky when this occurs in production system.
Markus
Those are 50 single patches but
871096 - Oracle Database 10g: Patch sets/patches for 10.2.0
<...>
You must apply a relatively large number of patches for Oracle Release 10.2.0.2. Information about the patch installation using MOPatch, see Note 1027012.
<...>
All information is in the note and related notes.
Markus
Markus,
Is there any tp problem.
Notes on phase IMPORT_PROPER
In this phase repository objects and table entries are imported. This
phase can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called.
o TP_FAILURE: The program tp could not be executed. For more
information on this, see the SLOG or ALOG log file.
o TP_STEP_FAILURE: A tp step could not be executed. To find the cause
of the error, see the appropriate log, such as the import log.
If the cancelation message contains a tp step 6, N or S, the step in
question is independent of the transport request. You can find these
logs under the node Import steps not specific to transport request
in the log overview.
Alternatively, you can find these logs in the following files in the
log directory of your transport directory (usually:
/usr/sap/trans/log):
Give me any idea
Regards
Siva
Markus,
In SLOG File ,
START tp_getprots EQA P 20081103025302 KILARIS SAPQUA 20081103025237
STOP tp_getprots EQA P 20081103025707 KILARIS SAPQUA 20081103025237
STOP MOVE NAMETABS EQA 6 20081103025707 KILARIS SAPQUA 20081103025237
START MAIN IMPORT EQA I 20081103025707 KILARIS SAPQUA 20081103025237
ERROR SAPKB70012 EQA I 0012 20081103031720 SAPUSER KILARIS SAPQUA 20081103025237
STOP MAIN IMPORT EQA I 20081103031734 KILARIS SAPQUA 20081103025237
ERROR: stopping on error 12 during MAIN IMPORT
START INFORM SAP-SYSTEM OF EQA Q 20081103031734 KILARIS SAPQUA 20081103025237
START tp_getprots EQA Q 20081103031734 KILARIS SAPQUA 20081103025237
WARNING: System EQA. Warning. 20081103032139 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
Please check that the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
Regards
Siva
Markus,
This is the que status.
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: IMPORT_PROPER
- Reason for error: TP_BUFFER_INCONSISTENCY
- Return code: 0008
- Error message: Pkgs. in queue don"t exist in the tp buffer (e.g.
SAPKB70012)
Regards
Siva
The root cause of your problem is the fact, that the database shadow process of the tp/R3trans is crashing. This is happening most likely due to the fact, that you did not yet install all the necessary patches.
the TP error you see is caused by the patches no more being available in /usr/sap/trans/EPS/in.
So you should
- patch your database as suggested several times
- apply latest R3trans and tp patch
- restart the patch application
If you just try and get it through without fixing the root cause it won´t help you.
Markus
Hi Siva,
I agree with Markus. Oracle is a database of its kind and you need to manage it properly. You have to apply all the interim patches and generic patches for your OS which is easy to find in the marketplace before starting any troubleshooting.
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000673263&_SCENARIO=01100035870000000202&;
Cheers,
Rajeev
Hi skumar,
you can apply the interim patch 5117016 for 10.2.0.2.0 which is very important.
see below the details from lsinventory
-
Installed Top-level Products (2):
Oracle Database 10g 10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 1 10.2.0.2.0
There are 2 products installed in this Oracle Home.
Interim patches (1) :
Patch 5117016 : applied on Sun Aug 10 09:14:50 AST 2008
Created on 30 Mar 2006, 12:52:17 hrs US/Pacific
Bugs fixed:
5117016
have you checked the logs before termintating the session whether the support pack really hung or still running?
can you please paste the detailed log of error.
Cheers,
-Sunil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.