on 03-03-2011 10:35 AM
Hi friends,
I dont know whether this is the right thread i am posting or not. But technical people can definately help me.
Recently we have upgraded patch from SP 22 to SP 25 for BI 7.0. From that time onwards i am facing issues like anything.
Here is the impact.
1. Data loads not triggering for process Chains as per schedules. we are running emegency chains manually. We have raised an issue to SAP, waiting for reply.
Short Dumps:
b)
DBIF_REPO_SQL_ERROR
Short text
SQL error 3114 occurred when accessing program "SAPLRS_EXCEPTION " part "LOAD".
What happened?
The system is no longer linked to an ORACLE instance.
No further operations can be performed on the database.
Error analysis
The system attempted to access an ORACLE instance to which
it is no longer linked.
This situation may arise because the ORACLE instance
has been stopped due to an error or an external operation.
How to correct the error
Database error text........: "ORA-03114: not connected to ORACLE"
Triggering SQL statement...: "SAPLRS_EXCEPTION "
The current status of the ORACLE instance cannot be determined.
It may be still inactive or the database administrator may have
restarted it.
In any case, all systems that have accessed the ORACLE instance
must be restarted after the ORACLE instance has been restarted.
If you were working on a central system, inform
your system administrator.
If you were working on an external local system, inform
the person responsible for this system.
If you were working on your own local system, restart
the system yourself.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_REPO_SQL_ERROR" " "
"SAPLRRMS" or "LRRMSU14"
"RRMS_EXCEPTION_HANDLING"
c)
DBIF_RSQL_SQL_ERROR
CX_SY_OPEN_SQL_DB
How to correct the error
Database error text........: "ORA-03135: connection lost contact"
Internal call code.........: "[RSQL/RDUP/TADIR ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPLSDI0" or "LSDI0U01"
"TRINT_TADIR_UPDATE"
2. Especially ODS activation (through process chains) failing in every process Chain. if you run maual activation , then its ok.
All Batch are got struck when accessing table TADIR. Dump C which is mensioned above impact is very high on the system.
Anyone know about to resolve the above dumps, Please help me.
If you want to analyze more detailed level, please let me know
Thanks in Advance.
Venkat
Hi,
I moved the thread to the Oracle Forum, as this is the Microsoft SQL Server forum.
Best regards
Clas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This issue doesn't seem related to SP upgrade. Was DB upgraded or Oracle patch applied or any parameter was changed during SP installation?
Manual activation works probably because you're activating from DB server and the failures occur probably when run from application servers.
Probable causes:
1) Oracle client incompatiblity
2) Network issues
3) Application servers were added recently
See if R3trans -d returns zero from all application servers. if not, there is some kind of connectivity issue between app server and DB server. When were application servers bounced?
Bala
Hi Bala..
Sorry for late reply..
Your thread really help to found the issue. We have raised an issue to SAP. We sent all log files as per their request.
They found some inconsistency between kernel patch in dev_disp and dev_ms log, one is on 254 and other is on 251.
So they suggested us to upgrade latest patch 290.
WE are planning on kernal patch.
I am assigneing full points to all ..
Keep rocking Guys
Venkat.
Hi,
Whats the database release..??
and also can you paste the sqlnet.ora file here.
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Please gothrough below details.
################
Filename......: sqlnet.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10 # Name..........:
Date..........:
@(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#4 $ ################
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
NAMES.DEFAULT_DOMAIN = WORLD
NAME.DEFAULT_ZONE = WORLD
SQLNET.EXPIRE_TIME = 0
TCP.NODELAY=YES
TADIR file got struck during this stament:
-
Last SQL statement
SELECT
/*+
FIRST_ROWS (1)
*/
*
FROM
"TADIR"
WHERE
"PGMID" = :A0 AND "OBJECT" = :A1 AND "OBJ_NAME" = :A2
FOR UPDATE
-
Database Number Time (usec) Recs.
Direct Read 1,017 172,733 232
Sequential Read 1,815 471729 10,454
Insert 20 31,223 306
Update 25 9,621 17
Delete 25 115,827 291
Sources 3,069,427 (Bytes)
RSQL 2,265,032 (Bytes)
Commit 0
DB Procedure Calls 0 0
-
Thanks and reagards
Venkat
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.