ORA-3136 error in alert log file(EBS R12)

I have found ora-3136 alert log error in ebs r12 instance Can any one help on this error. Alert log continuously write this error. Below is the error i found.
Fatal NI connect error 12170.
VERSION INFORMATION:
        TNS for Linux: Version 11.1.0.7.0 - Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
Time: 07-NOV-2013 18:33:49
Tracing not turned on.
Tns error struct:
    ns main err code: 12535
TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=172.17.100.108)(PORT=60495))
WARNING: inbound connection timed out (ORA-3136)

Does this affect the functionality of the application?
Do you get any errors when opening forms or self-service pages?
Please see:
ORA-01403 and FRM-40735 error occur while opening any forms (Doc ID 1358117.1)
Troubleshooting ORA-3135/ORA-3136 Connection Timeouts Errors - Database Diagnostics (Doc ID 730066.1)
ORA-3136/TNS-12535 or Hang Reported for Connections Across Firewall (Doc ID 974783.1)
Thanks,
Hussein

Similar Messages

ORA.00600 Error in alert log file

Hi all,
I'm using Enterprise Linux Red hat 5 OS and Oracle version 10.2.0.1.0
I checked alert log file, yesterday i got this error,
* Errors in file /opt/oracle/admin/ssharp/udump/ssharp_ora_11162.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0xB7F8F6B4], [], [], [], [], [], []
Fri Mar 11 19:44:51 2011
Memory Notification: Library Cache Object loaded into SGA
Heap size 3784K exceeds notification threshold (2048K) *
how to solve this issue?
thanks in advance

Hello,
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0xB7F8F6B4], [], [], [], [], [], []For this kind of error you should open a Service Request to My Oracle Support and, send them all the information you can (Alert log, trace files, ...).
More over, as you are in *10.2.0.1*, you may apply the latest patchset to the Database (10.2.0.4 / 10.2.0.5). Sometime, ORA-00600 may be due to a Bug. So, perhaps, by chance, applying a Patch set can help to solve this kind of issue.
Anyway, first of all, contact the Support.
Hope this help.
Best regards,
Jean-Valentin

How to check particular error in alert log file

Hi all,
How to check particular error in alert log file,for supose if i get error in batabase yesterday 4 pm & today i want to check alert log file to get basic idea..it might be a big file so how to check that particular error..
Thanks & regards,
Eswar..

What's your oracle version?
If you are in 11g you can use adrci tool
1- set homes diag/rdbms/orawiss/ORAWISS/ : the rdbms home
2- show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term : to find all the ORA-% errors in the alert file
3- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term : to find all the ORA-% errors in the alert file during the last 51 days,
4- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-1/24 " -term : to find all the ORA-% errors in the alert file during the last hour,
5- show alert -P "MESSAGE_TEXT LIKE '%ORA-12012%' and originating_timestamp > systimestamp-1/24 " -term : to find the particular ORA-12012 error in the alert file during the last hour,
Example:
[oracle@wissem wissem]$ adrci
ADRCI: Release 11.2.0.1.0 - Production on Wed May 4 10:24:54 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/home/oracle/app/oracle"
adrci> set homes diag/rdbms/orawiss/ORAWISS/
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2010-12-11 19:45:41.289000 +01:00
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf'
ORA-1547 signalled during: ALTER DATABASE RECOVER database until time '2011-01-21:10:48:00' ...
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2011-03-15 10:19:45.316000 +01:00
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j006_5536.trc:
ORA-12012: error on auto execute of job 26
ORA-01435: user does not exist
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>

RMAN success, but errors in alert.log file

My RMAN backup script runs well, but generates errors in alert.log file.
Here is the trace file contents:
/usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_3990.trc
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
ORACLE_HOME = /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
System name: Linux
Node name: plockton
Release: 2.6.18-128.2.1.el5
Version: #1 SMP Wed Jul 8 11:54:54 EDT 2009
Machine: i686
Instance name: XE
Redo thread mounted by this instance: 1
Oracle process number: 26
Unix process pid: 3990, image: oracle@plockton (TNS V1-V3)
*** 2009-07-23 23:05:01.835
*** ACTION NAME:(0000025 STARTED111) 2009-07-23 23:05:01.823
*** MODULE NAME:(backup full datafile) 2009-07-23 23:05:01.823
*** SERVICE NAME:(SYS$USERS) 2009-07-23 23:05:01.823
*** SESSION ID:(33.154) 2009-07-23 23:05:01.823
*** 2009-07-23 23:05:18.689
*** ACTION NAME:(0000045 STARTED111) 2009-07-23 23:05:18.689
*** MODULE NAME:(backup archivelog) 2009-07-23 23:05:18.689
Does anyone know why? Thanks.
Richard

I'm not sure if this will answer your question or not, but I believe these messages can likely be ignored.
I'm currently running 10.2.0.1.0 Enterprise Edition in pre-production (yes, I know I should apply the latest patchset and I plan to do so as soon as I get a development box allocated to me and can test it's impact). I see the same types of messages that you've reported with each of my regularly-scheduled backups:
a) The alert_<$SID>.log reports that there are errors in trace files:
Mon Aug 10 04:33:49 2009
Starting control autobackup
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Control autobackup written to DISK device
handle '/backup/physical/BLAH/RMAN/cf_c-2740124895-20090810-00'
b) The .trc files, when you look at them contain no errors - only these "informational" messages:
*** 2009-08-10 04:33:50.781
*** ACTION NAME:(0000105 STARTED111) 2009-08-10 04:33:50.754
*** MODULE NAME:(backup archivelog) 2009-08-10 04:33:50.754
*** SERVICE NAME:(SYS$USERS) 2009-08-10 04:33:50.754
*** SESSION ID:(126.28030) 2009-08-10 04:33:50.754
c) I've verified that LOG_ARCHIVE_TRACE is set to 0:
SQL*Plus> show parameter log_archive_trace
NAME TYPE VALUE
log_archive_trace integer 0
As best I can discern from my own experience, these should just be ignored and I trust (read: "hope") they will simply go away once the latest patchset is applied. As for you running Oracle XE, a patchset is not an option, unfortunately.
V/R
-Eric

Configure Email through OEM when there is a error in alert log file

Hi,
I am using 10.2.0.4 on O/S RHEL5.0
I want to configure email facility through OEM so that whenever there is a error in alert log file i should receive an email.
Thanks and Regards
Amith

http://www.dba-oracle.com/oracle10g_tuning/t_oem_tuning.htm
Please read above link.
Regards
Girish Sharma

Create database fails with error ORA-01505: error in adding log files

hi all,
hope someone can help me out, I'm trying to create a database using a SQL script, the content of the script is:
create database testora
user sys identified by oracle
user system identified by oracle
logfile group 1 ('/u01/app/oracle/oradata/testora/redo01a.log', '/u02/app/oracle/oradata/testora/redo01b.log') size 100m blocksize 512 reuse,
     group 2 ('/u01/app/oracle/oradata/testora/redo02a.log', '/u02/app/oracle/oradata/testora/redo02b.log') size 100m blocksize 512 reuse,
     group 3 ('/u01/app/oracle/oradata/testora/redo03a.log', '/u02/app/oracle/oradata/testora/redo03b.log') size 100m blocksize 512 reuse,
maxlogfiles 5
maxlogmembers 5
maxdatafiles 100
character set US7ASCII
national character set AL16UTF16
extent management local
datafile '/u01/app/oracle/oradata/testora/system01.dbf' size 400m reuse
sysaux datafile '/u01/app/oracle/oradata/testora/sysaux01.dbf' size 400m reuse
default tablespace users
     datafile '/u02/app/oracle/oradata/testora/users01.dbf' size 500m reuse autoextend on maxsize unlimited
default temporary tablespace tempts1
     tempfile '/u01/app/oracle/oradata/testora/temp01.dbf' size 20m reuse autoextend on maxsize 4g
undo tablespace undotbs1
     datafile '/u01/app/oracle/oradata/testora/undotbs01.dbf' size 200m reuse autoextend on maxsize unlimited
It fails in creating the database with the following output:
SQL> @/home/oracle/Oracle_Scripts/testora_db_script.sql
create database testora
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-01501: CREATE DATABASE failed
ORA-01505: error in adding log files
ORA-01184: logfile group 1 already exists
Process ID: 3486
Session ID: 1 Serial number: 3

sorry to revive this thread but i have one more issue with this. I created a database with DBCA insetead of CREATE DATABASE command and selected option for Fast Recovery Area space. This automatically set initialization parameter db_recovery_file_dest and db_recovery_file_dest_size, but did not create a OMF redo log group, but instead created three redo log groups with 1 member each.
select * from v$logfile returns:
1          ONLINE     /u01/app/oracle/oradata/testdb2/redo01.log     NO
2          ONLINE     /u01/app/oracle/oradata/testdb2/redo02.log     NO
3          ONLINE     /u01/app/oracle/oradata/testdb2/redo03.log     NO
Any idea why if creating a database with create database command and specifying db_recovery_file_dest creates an OMF redo log group and with DBCA it doesn't?

ORA- errors in alert log file

I wanted to know when the ORA- errors are reported into the alert.log file?
And which tye of errors are reported into it?
And if i wanted to log all the ORA-errors in the alert log then is there any setting for that?

You can find the type of errors reported in the link above.
Also, you maynot like to log ORA-00942: table or view does not exist, ORA-00904: : invalid identifier type of errors in alert.log - right? You may want to research at setting up events for generating trace files on specific error numbers you are looking at. That might resolve your problem - hth.

Receiving Alerts on ORA- error in Alert Log File

Hi,
I am using 10.2.0.5 OEM grid control and same versioned agent on my database servers. I have configured the alert email notification if there is any ORA- error message in my alert log file. The metric i selcted for this is "Generic Alert Log Error Status". In notification email, i see only the message that there is generic error message in the alert log file. Is there any way to set this notification so that i receive the exact ORA- error message in my alert notification email if there is any kind of ORA- error found in my alert log file?
Thanks
Salman

Please look into the Metalink Note: 458605.1
Subject: Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric

ORA-16009 Error in Alert Log

Hi DBAs,
I saw the error ORA-16009 in alert log file. The database version is 10.2.0.3 configured with Physical standby on AIX 6.1 . The error is coming in alert log for a long time , I beleive after a swithover to Standby and switch back to Primary.
But I see the log from Primary to Standby are being applied and MRP is working fine on Standby Site.
I am posting the error message from alert log and trace file.
-------- Message in alert.log --------------
--Connected User is Valid
RFS[61129]: Assigned to RFS process 1511478
RFS[61129]: Database mount ID mismatch [0x8afdb574:0x8afd830b]
RFS[61129]: Client instance is standby database instead of primary
RFS[61129]: Not using real application clusters
Fri May 8 22:32:57 2009
Errors in file /oracle/admin/DBSID/udump/DBSID_rfs_1511478.trc:
ORA-16009: remote archive log destination must be a STANDBY database/oracle/admin/DBSID/bdump
HOST [DBSID]-> May 8 22:33:52 hostname daemon:err|error ltid[933986]: Remote scan failed on host HOST, drive IBMULTRIUM-TD25, Host is not the scan host for this shared drive (304)
----------------- Trace File with complete detail of the Error -----------------------------------
/oracle/admin/DBSID/udump/DBSID_rfs_1511478.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning and Data Mining options
ORACLE_HOME = /oracle/product/10.2.0/db_1
System name: AIX
Node name: hostname
Release: 3
Version: 5
Machine: XXXXXXX
Instance name: DBSID
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 1491066, image: oracleDBSID@hostname*** SERVICE NAME:(DBSID.DOMAIN.COM) 2009-05-08 22:31:57.314
*** SESSION ID:(1094.21412) 2009-05-08 22:31:57.314
Detected dead process 1491030; subsuming V$MANAGED_STANDBY slot
*** 2009-05-08 22:31:57.318 61287 kcrr.c
RFS[61128]: Database mount ID mismatch [0x8afdb574:0x8afd830b]
*** 2009-05-08 22:31:57.318 61287 kcrr.c
RFS[61128]: Client instance is standby database instead of primary
*** 2009-05-08 22:31:57.318 61287 kcrr.c
RFS[61128]: Not using real application clusters
ORA-16009: remote archive log destination must be a STANDBY database
Please advise and suggest,
Thanks
-Samar-

I have the follow setting for log_archive_dest_2 on Primary and standby which seems to be OK but above mention note which is for Oracle 9i server suggesting to disable the remote archiving on the standby database. Also I am using ASYNC option for log transport.
At Primary:
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=STDBY LGWR ASYNC REOPEN=60 DB_UNIQUE_NAME=STDBY
At standby:
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=PRI LGWR ASYNC REOPEN=60 DB_UNIQUE_NAME=PRI
Thanks
-Samar-

Errors in Alert log file

Hi,
I have encountered following errors in alrt log file, its strange to see FAST_START_MTTR_TARGET is out of valid and aksing to use another value and that value is changing every second, it should be in increasing order or it should be consistent. I think i have a serious problem, so anyone could help me out on this. I am getting this "FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead" error regurarly.
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead.
Wed Jan 16 23:40:34 2008
Completed checkpoint up to RBA [0x2aadb.2.10], SCN: 5473742880
Wed Jan 16 23:45:51 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24017 instead.
Wed Jan 16 23:46:21 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23647 instead.
Wed Jan 16 23:46:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23298 instead.
Wed Jan 16 23:47:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22906 instead.
Wed Jan 16 23:47:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22507 instead.
Wed Jan 16 23:48:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22133 instead.
Wed Jan 16 23:48:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21786 instead.
Wed Jan 16 23:49:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21443 instead.
Wed Jan 16 23:49:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21062 instead.
Wed Jan 16 23:50:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 20698 instead.
Wed Jan 16 23:53:53 2008
Incremental checkpoint up to RBA [0x2aadb.31b4.0], current log tail at RBA [0x2aadb.3e38.0]
Thu Jan 17 00:00:54 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 19582 instead.
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 16287 instead.
Thu Jan 17 00:34:01 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 15902 instead.
Thu Jan 17 00:34:31 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 14638 instead.
Thu Jan 17 00:35:01 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 13600 instead.
Thu Jan 17 00:35:31 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12773 instead.
Thu Jan 17 00:36:02 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12460 instead.
Thu Jan 17 00:36:32 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12338 instead.
Thu Jan 17 00:37:01 2008
Process P187 died, see its trace file
Thu Jan 17 00:37:02 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12248 instead.
Thu Jan 17 00:37:02 2008
Process P188 died, see its trace file
Thu Jan 17 00:37:03 2008
Process P189 died, see its trace file
Thu Jan 17 00:37:04 2008
Process P190 died, see its trace file
Thu Jan 17 00:37:16 2008
Process J000 died, see its trace file
Thu Jan 17 00:37:16 2008
kkjcre1p: unable to spawn jobq slave process
Thu Jan 17 00:37:16 2008
Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
Process J000 died, see its trace file
Thu Jan 17 00:37:22 2008
kkjcre1p: unable to spawn jobq slave process
Thu Jan 17 00:37:22 2008
Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
Thanks
Jafar

This parameter, FAST_START_MTTR_TARGET ranges from 0 to 3600 seconds. It is important to specify your oracle version, since a similar issue is reported for the 10gR1 release.
The solution for it would be to increase the value to the suggested one in the alert.log file, but it could be completely out of range from the valid values, so set it to zero and let the oracle instance calculate the value. You can check the output at the V$INSTANCE_RECOVERY view at the columns TARGET_MTTR, and ESTIMATED_MTTR prior to proceeding with modificaiton.
On the other hand, I suggest you to read this metalink note
Kkjcre1p: Unable To Spawn Jobq Slave Process, Error 1089
Doc ID: Note:344275.1
for the Kkjcre1p error message.
~ Madrid

Error in alert log files

Hi,
I am working on oracle10.2.0.4 and o/s is HP-UX .
In alert log ifle of database i found follwoing messages.
ksvcreate: Process(m000) creation failed
Wed Sep 1 09:09:02 2010
Process m000 died, see its trace file
Wed Sep 1 09:09:02 2010
ksvcreate: Process(m000) creation failed
By using TOP command checked that load on database server was very high...
383 processes: 347 sleeping, 35 running, 1 zombie
Cpu states:
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 1.67 *97.2%* 0.0% 6.8% 0.0% 0.0% 0.0% 0.0% 0.0%
1 1.68 *96.6%* 0.0% 10.4% 0.0% 0.0% 0.0% 0.0% 0.0%
avg 1.67 *97.4%* 0.0% 8.6% 0.0% 0.0% 0.0% 0.0% 0.0%
Memory: 11087320K (6724692K) real, 12604944K (7680860K) virtual, 924024K free Page# 1/19
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
1 ? 16530 oracle10 235 20 8969M 5180K run 0:52 27.80 27.75 oraclePROD2
0 ? 16536 oracle10 241 20 8969M 5116K run 2:55 20.57 20.53 oraclePROD2
1 ? 16523 oracle10 234 20 8969M 5116K run 0:27 20.18 20.15 oraclePROD2
This time application was down .....and we restarted applicaiton ...
IS this issue is realted to database .... ?
How to reolve this ...?
Edited by: oradba11 on Sep 1, 2010 1:00 PM
Edited by: oradba11 on Sep 1, 2010 1:00 PM

Yes , database was up and running ...
but in alert log file i got messages ...
and load on server was very high .. i put out put of top command ...
is this is realted to database ...?

Database generating a large number of ORA-1403 errors in Alert Log & trace

Hi,
Many ORA-1403: no data found messages appear in the alert log, but users are not seeing this error on their screens. The errors are only generated in the alert log along with an associated trace file.
We have not set the "set events 1403 trace" for either system or session level.
I confirmed this with the initialization file.
The database is generating huge trace files..
Database version: 10.1.0.4.2
Errors in Trace:
ksedmp: internal or fatal error
ORA-01403: no data found
Regards,
Chandan

Hi,
Check Note:271490.1. Try to issue
alter system set events '1403 trace name errorstack off'; as recommended in that Note.
If this not help then check other possible cases of this on Metalink or address this problem to Oracle support directly.
Best Regards,
Alex

ORA 600 Errors - in Alert log

Hi,
The last 2-3 days I am seeing the following messages in my alert log :
Sun Mar 29 19:28:09 2009
Errors in file /db01/oracle/TAP/dump/udump/ora_13542.trc:
ORA-00600: internal error code, arguments: [13013], [5001], [1], [134636630], [35], [134636630], [], []
Dump file /db01/oracle/TAP/dump/udump/ora_13542.trc
Oracle7 Server Release 7.3.2.1.0 - Production Release
With the distributed and parallel query options
PL/SQL Release 2.3.2.0.0 - Production
ORACLE_HOME = /usr/oracle/server7.3
System name:    AIX
Node name: rs1
Release: 2
Version:        4
Machine: 000001276600
Instance name: TAP
Redo thread mounted by this instance: 1
Oracle process number: 47
Unix process pid: 13542, image:
Sun Mar 29 19:28:08 2009
*** SESSION ID:(54.498) 2009.03.29.19.28.08.000
updexe: Table 0 Code 1 Cannot get stable set - last failed row is: 08066456.23
This happens at a time when I believe there is no user activity. There is a job which runs on midnights ; but the time the errors show up there isnt supposed to be any user activity.
I am not sure if Oracle is gonna support this version even if I did log in a SR.
In Metalink I came across this note : Doc ID:      40673.1 ; could this be related ?
Else what options do I have in getting this resolved.
Thanks.

It is possible that you could also be facing an issue as described in ML note 28185.1.
The current option you have is to apply the patch 7.3.4.x and check if this resolves the problem; else consider upgrade to supported versions itself.
Of course, if this error is only occurring at off-peak times and not affecting any of the users, then you could probably ignore that but it would be better to find a fix in first place.

Error in alert log file

Hi all,
DB Version: 10.2.0
OS Version: Windows 2003 Server
When i check alertlog file there i get following error
ORA-00942: table or view does not exist
I don't know exactly for which table i am getting this error

Vikas Kohli wrote:
Hi all,
DB Version: 10.2.0
OS Version: Windows 2003 Server
When i check alertlog file there i get following error
ORA-00942: table or view does not exist
I don't know exactly for which table i am getting this errorNot sure why you would be getting this error in your alert log.
You could try creating an 'after servererror on database' trigger. The below asktom thread is for ORA-1555 which you would need to change to ORA-942 for your situation.
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:40115659055475

ORA-00316 in the alert log file

Thu Aug 21 17:23:05 2008
Errors in file /ora_dump/CONCILIA/bdump/concilia_arc1_205172.trc:
ORA-00316: log 3 of thread 1, type 0 in header is not log file
ORA-00312: online log 3 thread 1: '/ora_data04/CONCILIA/redo01.log'
Thu Aug 21 17:23:05 2008
Errors in file /ora_dump/CONCILIA/bdump/concilia_arc1_205172.trc:
ORA-00316: log 3 of thread 1, type 0 in header is not log file
ORA-00312: online log 3 thread 1: '/ora_data04/CONCILIA/redo01.log'
$

It looks like your redo log might be corrupted.
Check the content of trc file and work with Oracle support.
00316, 00000, "log %s of thread %s, type %s in header is not log file"
// *Cause: The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.

ORA-3136 error in alert log file(EBS R12)

Similar Messages

Maybe you are looking for