Checkpoint entries in my alert log - needhelp to decipher

hi guys,
I have the following in my alert log. Can someone please help decipher to let me know why Checkpoint is not being complete?
thanks
Beginning log switch checkpoint up to RBA [0x240.2.10], SCN: 0x0000.00255e4d
Thread 1 advanced to log sequence 576
Current log# 2 seq# 576 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 576 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Thread 1 cannot allocate new log, sequence 577
Checkpoint not complete
Current log# 2 seq# 576 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 576 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Tue Sep 2 16:22:39 2008
Completed checkpoint up to RBA [0x240.2.10], SCN: 0x0000.00255e4d
Tue Sep 2 16:22:39 2008
Beginning log switch checkpoint up to RBA [0x241.2.10], SCN: 0x0000.00255ed6
Thread 1 advanced to log sequence 577
Current log# 1 seq# 577 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.1a.log
Current log# 1 seq# 577 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.1b.log
Tue Sep 2 16:22:46 2008
Completed checkpoint up to RBA [0x241.2.10], SCN: 0x0000.00255ed6
Tue Sep 2 16:22:48 2008
Beginning log switch checkpoint up to RBA [0x242.2.10], SCN: 0x0000.00255f57
Thread 1 advanced to log sequence 578
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Thread 1 cannot allocate new log, sequence 579
Checkpoint not complete
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Tue Sep 2 16:22:51 2008
Completed checkpoint up to RBA [0x242.2.10], SCN: 0x0000.00255f57

Aman.... wrote:
Oracleguy,
You switched in 3 minutes only,
Tue Sep 2 16:22:48 2008*
Beginning log switch checkpoint up to RBA http://0x242.2.10, SCN: 0x0000.00255f57
Thread 1 advanced to log sequence 578
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Thread 1 cannot allocate new log, sequence 579
Checkpoint not complete
Current log# 2 seq# 578 mem# 0: /ora2/oradata/9.2.0.7/TESTDB/redoTESTDB.2a.log
Current log# 2 seq# 578 mem# 1: /ora3/oradata/9.2.0.7/TESTDB/redoTESTDB.2b.log
Tue Sep 2 16:22:51 2008+
Completed checkpoint up to RBA http://0x242.2.10, SCN: 0x0000.00255f57
Its pretty small time for log checkpoint to get complete. You need to make your log files bigger and add new members in them so that thereis sufficient time for checkpoint to get complete.
What's your current redo log configuration?
Aman....hi aman, did you mean 3 minutes, or 3 seconds?
I have two groups, and the log files are at 10M
thanks

Similar Messages

At what point oracle write "Checkpoint not complete" in alert log ?

DB version: 10.2.0.4/RHEL 5.8
During a batch run, we encountered lots of 'Checkpoint not complete' errors in alert log.
Later we discovered that ORLs were sized only 50mb and this DB had only 3 redo log group. Since this is the potential cause, we are going create at least 10 Redo log groups and increase Redo log size to 500MB.
But , I want to know what exactly causes oracle to write "Checkpoint not complete" in alert log ?
For the purpose of this discussion, I am assuming we have only 1 ORL per redo log group. Is my below assumption correct ?
ORL1
|----------------> ORL1 file got full, so, LGWR starts writing to ORL2 file. Checkpoint occurs at log switch
|                    DBWR writes modified blocks associated with the redo entries in ORL1 to datafiles
|
V
ORL2
|----------------> ORL2 file got full, LGWR wants to start writing to ORL3 file. Checkpoint is initiated at log switch.
|                    But checkpoint can't be finished due to unknowN reasons
|
V
ORL3
|---------------->

Your assumption is only partly right.
I would illustrate it like
ORL1
|
|----------------> ORL1 file got full, so, LGWR starts writing to ORL2 file. Checkpoint occurs at log switch
|                    DBWR starts writing modified blocks associated with the redo entries in ORL1 to datafiles
|
V
ORL2
|----------------> ORL2 file got full, LGWR starts writing to ORL3 file.
|                    Checkpoint for ORL2 is initiated at log switch.
|
V
ORL3
|
|----------------> ORL3 file (the last member) also got full very quickly . LGWR wants to start the 'new cycle' by
                    writing (Reusing) to ORL1. But the checkpoint intiated by the log switch of ORL1 from the previous cycle is
                    not complete yet !! .
Basically you get this error when LGWR attempts to reuse an online redo log file (ORL1 in the above example) and finds that it cannot.
This is because the remaining ORL files (ORL2 and ORL3) got fully written before DB writer finished checkpointing the modified blocks associated with ORL1 yet.
Until the checkpoint of ORL1 is complete, the DB effectively hangs and user sessions have to wait until LGWR can safely reuse ORL1
Yes a larger redo log size of 10 groups can help. But make sure the I/O subsytem where ORLs are stored has no latency issues.

Checkpoint not complete in alert log file Oracle 11gR2 RAC

Hi,
I found checkpoint not complete in alert log file, almost every 3 seconds .
In metalink i saw for this error, archive_lag_target=0, already this value was set to 0 in my database.
We have 7 redo log groups for each instance, each group is of two redo log files, each file size is 50m.
To avoid this error what i need to do..........
please help me..................

When you "checkpoint not complete" messages in your alert log this normally means your online redo logs are defined too small to handle the load and you have filled and need to switch to a new online redo log before the checkpoint triggered by the previous log switch has been completed.
Increasing your online redo log size is normally the fix for this.
HTH -- Mark D Powell --
PS - The following Oracle support document may also apply:
Checkpoint Not Complete In Alert.log Due To Setting Of Archive_lag_target [ID 435780.1]
Edited by: Mark D Powell on Nov 7, 2011 8:29 AM

"checkpoint not complete" in alert log file.

Hi, all.
I have got a message of "Checkpoint not complete" in alert log file.
Thread 2 advanced to log sequence 531
Current log# 7 seq# 531 mem# 0: \\.\REDO231
Current log# 7 seq# 531 mem# 1: \\.\REDO232
Thread 2 cannot allocate new log, sequence 532
Checkpoint not complete
Current log# 7 seq# 531 mem# 0: \\.\REDO231
Current log# 7 seq# 531 mem# 1: \\.\REDO232
I searched "Checkpoint not complete" issue in this forum.
As solutions,
1. add more redo log groups
2. increase the size of redo log
3. check I/O contention
4. set LOG_CHECKPOINT_INTERVAL, LOG_CHECKPOINT_TIMEOUT or
FAST_START_MTTR_TARGET
I think No.4 is the possible first approach in our environment.
I think No.1 and No2 are not the ploblems in our environment.
I ask the above issue oracle support center, but
I was told that "if you are not getting this message frequently, you do not need to worry about it" from an oracle engineer.
Is this true?? If I am not getting this message frequently, there is no problem
in terms of database integrity, consistency, and performance?
I will be waiting for your advice and experience in real life.
Thanks and Regards.

Redo Log Tuning Advisory and Automatic Checkpoint Tuning are new features introduced in Oracle 10G, if you are on 10g you may benefit from these features.
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance, however it must balanced out with the expected recovery time. Undersized log files increase checkpoint activity and increase CPU usage. As rule of thumb switching logs at most once every fifteen minutes.
Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files.
The redo logfile sizing advisory is specified by column optimal_logfile_size of v$instance_recovery. This feature require setting the parameter "fast_start_mttr_target" for the advisory to take effect and populate the column optimal_logfile_size.
Also you can obtain redo sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
To enable automatic checkpoint tuning, unset FAST_START_MTTR_TARGET or set it to a nonzero value(This is measured in seconds and by default, this feature is not enabled, because FAST_START_MTTR_TARGET has a default value of 0). If you set this parameter to zero this feature will be disabled. When you enable fast-start checkpointing, remove or disable(set to 0) the following initialization parameters:
- LOG_CHECKPOINT_INTERVAL
- LOG_CHECKPOINT_TIMEOUT
- FAST_START_IO_TARGET
Enabling fast-start checkpointing can be done statically using the initialization files or dynamically using -
SQL> alter system set FAST_START_MTTR_TARGET=10;
Best regards.

Checkpoint Not complete in alert log

Hello Gurus,
Alert log keeps displaying the following message:
Current log# 3 seq# 80148 mem# 0: /UBSUNDO/ghadb_redo03b.log
Current log# 3 seq# 80148 mem# 1: /UBSTEMP/ghadb_redo03a.log
Thu Dec 06 01:33:20 GMT 2012
Thread 1 advanced to log sequence 80149 (LGWR switch)
Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
Thu Dec 06 01:34:06 GMT 2012
Thread 1 cannot allocate new log, sequence 80150
Checkpoint not complete
Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
Thu Dec 06 01:34:14 GMT 2012
Thread 1 advanced to log sequence 80150 (LGWR switch)
Current log# 2 seq# 80150 mem# 0: /UBSUNDO/ghadb_redo02b.log
Current log# 2 seq# 80150 mem# 1: /UBSTEMP/ghadb_redo02a.log
Kindly advice on how to resolve this issue. Database is up for now but i donot want to bounce DB because of this archiving problem.
Thank you.

PVOWUSU wrote:
Hello Gurus,
Alert log keeps displaying the following message:
Current log# 3 seq# 80148 mem# 0: /UBSUNDO/ghadb_redo03b.log
Current log# 3 seq# 80148 mem# 1: /UBSTEMP/ghadb_redo03a.log
Thu Dec 06 01:33:20 GMT 2012
Thread 1 advanced to log sequence 80149 (LGWR switch)
Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
Thu Dec 06 01:34:06 GMT 2012
Thread 1 cannot allocate new log, sequence 80150
Checkpoint not complete
Current log# 1 seq# 80149 mem# 0: /UBSUNDO/ghadb_redo01b.log
Current log# 1 seq# 80149 mem# 1: /UBSTEMP/ghadb_redo01a.log
Thu Dec 06 01:34:14 GMT 2012
Thread 1 advanced to log sequence 80150 (LGWR switch)
Current log# 2 seq# 80150 mem# 0: /UBSUNDO/ghadb_redo02b.log
Current log# 2 seq# 80150 mem# 1: /UBSTEMP/ghadb_redo02a.log
Kindly advice on how to resolve this issue. Database is up for now but i donot want to bounce DB because of this archiving problem.
Thank you.Those lines are just informational.
no error exists

Most Recent Alert Log Entries - Error processing Alert Log

Hi..
Can someone help me?
When I want to check the log of alerts the following thing goes out for me:
"This shows the last 100,000 bytes of the alert log. The log is constantly growing, so select the browser's Refresh button to see the most recent log entries.
Number of Lines Displayed Error processing Alert Log"
Since I can solve it?

Number of Lines Displayed Error processing Alert Log"
check ur alert.log file content any data.
bcoz if ur alert.log file entries is null then above error is show. ( happen with me when i am purge alert.log file and try to view content of alert.log then above error received so may be problem is null contents ( empty alert.log file)).
HTH

How to initiating entry in alert.log?

Hallo,
i want initiate an entry in the alert.log by myself.
how can i do that?
thanks in advance

just make a archive log switch or shut down startup or any parameter changes which will effect alert.log file and there are many more

Removed standby but getting interesting alert log entry

So, we had multiple set ups of primary database in our local data center, standby in remote location.
We're in the process of shutting down our remote location and have shut down our standbys gracefully, i.e., shutdown managed standby mode, removed archive_log_dest, changed archive_log_dest_state, etc. However, in some primary databases, I'm seeing a weird entry in the alert log:
Changing destination 2 from remote to local during archival of log#: 2 sequence#: 48708 thread#: 1
If I check my local destination, the archive log is created fine. In the remote location, no archives are being created.
I've not found anything on Google, Metalink, anywhere! Has anyone else seen this before, and if so, do I need to worry about it?
Oracle version is 11.1.0.7

Hello;
Its just information. You can ignore it.
Went back to some 2010 alert logs and found :
network reconnect abandoned
Attempting destination LOG_ARCHIVE_DEST_2 network reconnect
Setting 'active' archival for destination LOG_ARCHIVE_DEST_2Not much chance of finding here as all old version of Oracle are gone and a SAN move makes old alert logs rare. Still it just information or Oracle would throw an error.
Best Regards
mseberg
Edited by: mseberg on Jul 31, 2012 11:32 AM
Later
Tried to recreate message using several combinations of the parameters you listed. Unable to recreate, but only have 11.2.0.3.0 to test on.
Edited by: mseberg on Jul 31, 2012 12:44 PM

Oracle troubleshooting when I have no info in the alert log

Hello everyone,
I'm running Oracle 10g on Solaris 10. I performed a restore yesterday, and my DB instance was running smoothly. This morning I discovered that Oracle died on me "silently", that is, nothing was recorded in the alert log - the last entry in the alert log was the end of the restore.
No Oracle processes were running anymore on the machine, trying to log in via sqlplus issued the expected
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
The instance is running again after rebooting the machine.
Can I find clues about the crash, as the alert log hasn't anything for me?
Thank you,
Adrian

Thank you all for your ideas.
I looked in the /var/adm/messages (there's also /var/log/sysmsg which might be of some help) and found out that the machine was rebooted. Apparently, the Oracle instance hasn't been started properly afterwards.
The alert log mentions (before the crash) that 'alter database open resetlogs' was performed successfully, and I ran some applications after restore that accessed the DB - the instance was indeed running.
There is no other alert log (my attempts to bring up the DB the next day are recorded in the same file).

Oracle 9i (SE) Solaris 9 (Alert.log file)

Hi Guys,
How do I clean up my alert.log file. Do I have to delete it completely or only delete the content of the file.
Thank you.

Laura Gaigala wrote:
Why You want to clean up it? Too large or some other reasons?
If You have some planned db restart, then during restart rename archive.log and upon startup it will be created automaticaly again.
If no restart is planned, then delete it's content, but before that make a copy of alert.log. Just in order You will need to find something.Actually, I've found that it is quite safe to rename the alert.log right out from under a running database. It will simply start a new one with the next message to be written. However, I agree it is much nicer to do this housekeeping while the db is down, so that the first entry in an alert log is the startup.
This renameing of the log against a running process does not work for the listener log. I've found that if I rename listener.log to listener.log.1, the listener will continue to log to the original file (now listener.log.1) until such time as it is restarted. THEN it will start a new listener.log.
This was all on unix. Windows may behave differently.

Control File Auto Backup Alert Log

Hello-
Is there a parameter in the 11g database that needs to be configured to write to the alert log when the controlfile is auto-backed up ?
I have this configured but there are no entries in the alert logs for 11g databases.
I do have them in my 10g alert logs.
Thanks-

No there is no such parameter.
It seems that Oracle 11g does not write anything to alert log when control file is auto backed up but instead writes to a trace file in diagnostic_dest directory tree:
Trace file /u01/app/oracle/diag/rdbms/db112/DB112/trace/DB112_ora_5837.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/EE
System name:    Linux
Node name:      lx01.localdomain
Release:        2.6.18-92.el5
Version:        #1 SMP Fri May 23 22:17:30 EDT 2008
Machine:        i686
Instance name: DB112
Redo thread mounted by this instance: 1
Oracle process number: 29
Unix process pid: 5837, image: [email protected] (TNS V1-V3)
*** 2011-04-18 19:21:39.223
*** SESSION ID:(17.34) 2011-04-18 19:21:39.223
*** CLIENT ID:() 2011-04-18 19:21:39.223
*** SERVICE NAME:(SYS$USERS) 2011-04-18 19:21:39.223
*** MODULE NAME:(backup full datafile) 2011-04-18 19:21:39.223
*** ACTION NAME:(0000023 STARTED111) 2011-04-18 19:21:39.223
Starting control autobackup
*** 2011-04-18 19:21:40.050
Control autobackup written to DISK device
        handle '/tmp/c-732354255-20110418-011'Edited by: P. Forstmann on 18 avr. 2011 19:25

TRIM alert log

Hi,
This is not a database specific question, instead a Unix generic one!
I have my database in HPUX environment and one of my alert log file is very huge!
I want to trim the old entries of my alert log files. For eg: the first 1000 lines.
Could you please help me with the command to do the same!
Thanks!

Nicolas,
What did you say about my "man tail?"
Sorry, I just had to respond to that post from the God of Comedy Setup Lines
John

Cjq process related entries in alert log

Hi,
I have recently set up 10g (10.2.0.4) database on solaris 10. In the alert log of the db , there are entries like this;
Mon May 25 02:31:56 2009+
Starting background process CJQ0+
CJQ0 started with pid=15, OS id=18484+
Mon May 25 03:12:47 2009+
Stopping background process CJQ0+
the database is up and it is running but in alert log several such messages are there...not sure why the CJQ processes should start and shut down. can you suggest regarding possible cause for it.
thanks
Edited by: orausern on May 25, 2009 7:22 AM
Edited by: orausern on May 25, 2009 7:22 AM

From the documentation you get the following:
This is the Oracle’s dynamic job queue coordinator. It periodically selects jobs that need to be run, scheduled by the Oracle job queue. The coordinator process dynamically spawns job queue slave processes (J000…J999) to run the jobs. These jobs could be PL/SQL statements or procedures on an Oracle instance. Please note that this is not a persistent process. It comes and goes.
Regards, Gerwin

New Archived log entry in alert log after cpu patch 19 applied

Has anyone applied October critical patch for 11.1.0.7? I applied the cpu Patch 19 (8892977) for 11.1.0.7 on several windows2008 servers and after the patch the alert log displays a new message everytime a redo log transfers. This only happens on servers that have archivelog on. It looks like there is some kind of trace set. Anyone know know what the message is?
Thanks,
Kathie
Archived Log entry 10937 added for thread 1 sequence 10938 ID 0xa96e3908 dest 10:

Hi Mark!
Yes, Oracle informed me that this message is normal and is only used for formational purposes. I should just ignore it.
Did you apply patch19? I have also found issues with a high amount of "waits" of type of "other". Some jobs are running slightly slower also. Also, if you check your "database health link" on dbconsole home page you will see consistant "non-critical" alerts. I don't have these alerts on servers not yet patched. This alerts appear to be caused by wait events of "other".
Kathie

Errors in alert log fileand application log file

Hi,
Oracle EBS version 12.1.1
RDBMS version 11.1.0.7.0
OS RHEL 5.4
All of a sudden I am not able to access my R12 system.It shows me 500 Internal server error.
I am not able to connect to database from client either.(SQLPLUS or any other tools hangs while trying to connect to DB)
Although I can connect to database from server.
Errors in DB alert log file is :
=================
Fatal NI connect error 12547, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:08:12
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (12562_47163992198336)
Sat Jul 30 14:10:12 2011
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:10:12
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (12599_47919733853376)
Sat Jul 30 14:11:43 2011
Incremental checkpoint up to RBA [0x137.8b97e.0], current log tail at RBA [0x137.8c0c4.0]
Sat Jul 30 14:11:52 2011
Fatal NI connect error 12547, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:11:52
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (12627_47439235198144)
Sat Jul 30 14:14:32 2011
Fatal NI connect error 12547, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:14:32
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (12890_47772667911360)
Sat Jul 30 14:15:08 2011
Beginning log switch checkpoint up to RBA [0x138.2.10], SCN: 10132185231186
Thread 1 advanced to log sequence 312 (LGWR switch)
Current log# 3 seq# 312 mem# 0: /u01/oracle/VIS/db/apps_st/data/log1.dbf
Sat Jul 30 14:15:52 2011
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:15:52
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (13156_47242339073216)
Sat Jul 30 14:20:15 2011
Completed checkpoint up to RBA [0x138.2.10], SCN: 10132185231186
Sat Jul 30 14:32:04 2011
Incremental checkpoint up to RBA [0x138.5646.0], current log tail at RBA [0x138.6444.0]
Sat Jul 30 14:40:33 2011
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:40:33
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (14536_47011734056128)
Sat Jul 30 14:45:33 2011
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
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: 30-JUL-2011 14:45:33
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (14688_47186744614080)
Sat Jul 30 14:47:13 2011
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: 30-JUL-2011 14:47:13
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: <unknown>
ORA-609 : opiodr aborting process unknown ospid (14684_46999375879360)
--Repeatedly getting this error.
Error in application log is:
================
11/07/30 14:45:53.449 html: Servlet error
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:75)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at java.nio.channels.Channels.write(Channels.java:60)
at java.nio.channels.Channels.access$000(Channels.java:47)
at java.nio.channels.Channels$1.write(Channels.java:134)
at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
11/07/30 14:49:53.591 html: Broken pipe
11/07/30 14:49:53.591 html: Broken pipe
11/07/30 14:49:53.592 html: Broken pipe
11/07/30 14:49:53.592.592 html: Broken pipe
11/07/30 14:49:53.592 html: Broken pipe
11/07/30 14:49:53.592.592 html: Broken pipe
11/07/30 14:49:53.593 html: Broken pipe
11/07/30 14:49:53.593 html: Broken pipe
11/07/30 14:49:53.594 html: Broken pipe
11/07/30 14:49:53.594 html: Servlet error
java.io.IOException: Broken pipe
11/07/30 14:49:53.594 html: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:75)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at java.nio.channels.Channels.write(Channels.java:60)
at java.nio.channels.Channels.access$000(Channels.java:47)
at java.nio.channels.Channels$1.write(Channels.java:134)
at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
11/07/30 14:49:53.594 html: Servlet error
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:75)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at java.nio.channels.Channels.write(Channels.java:60)
at java.nio.channels.Channels.access$000(Channels.java:47)
at java.nio.channels.Channels$1.write(Channels.java:134)
at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
11/07/30 14:49:57.630 html: Broken pipe
11/07/30 14:49:57.630 html: Broken pipe
11/07/30 14:49:57.630 html: Broken pipe
11/07/30 14:49:57.630 html: Broken pipe
11/07/30 14:49:57.630 html: Broken pipe
11/07/30 14:49:57.631 html: Servlet error
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:75)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at java.nio.channels.Channels.write(Channels.java:60)
at java.nio.channels.Channels.access$000(Channels.java:47)
at java.nio.channels.Channels$1.write(Channels.java:134)
at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
11/07/30 14:49:57.632 html: Broken pipe
11/07/30 14:49:57.632 html: Broken pipe
11/07/30 14:49:57.632 html: Broken pipe
11/07/30 14:49:57.633 html: Broken pipe
11/07/30 14:49:57.633 html: Broken pipe
11/07/30 14:49:57.633 html: Servlet error
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:75)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at java.nio.channels.Channels.write(Channels.java:60)
at java.nio.channels.Channels.access$000(Channels.java:47)
at java.nio.channels.Channels$1.write(Channels.java:134)
at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:619)
11/07/30 14:55:33.775 html: Broken pipe
11/07/30 14:55:33.775 html: Broken pipe
11/07/30 14:55:33.775 html: Broken pipe
11/07/30 14:55:33.776 html: Broken pipe
11/07/30 14:55:33.776 html: Broken pipe
11/07/30 14:55:33.776 html: Servlet error
java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
at sun.nio.ch.IOUtil.write(IOUtil.java:75)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
at java.nio.channels.Channels.write(Channels.java:60)
at java.nio.channels.Channels.access$000(Channels.java:47)
at java.nio.channels.Channels$1.write(Channels.java:134)
at com.evermind.server.http.AJPOutputStream.endRequest(AJPOutputStream.java:117)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:317)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:619)
I tried to bounce the system.
When I executed ./adstpall.sh it took a long time (about 15 mins) and exited with status 1.
You are running adstpall.sh version 120.10
adstpall.sh: Database connection could not be established. Either the database is down or the APPS credentials supplied are wrong.
USAGE: adstpall.sh <appsusername/appspassword>
adstpall.sh: exiting with status 1
But I check from server that the database is up and running.
Please help asap
Thanks,
Rushi

Oracle support has given me two docs
Note 550859.1 TROUBLESHOOTING GUIDE TNS - 12518 TNS listener could not hand off client connection
Note 340089.1 New Connections to the Database lead to ORA-12518 or TNS-12518
I do not any ORA-12518 or TNS-12518 errors in the log file entries you posted above. However, please see (ORA-00610 And/Or "unable to spawn jobq slave process " And/Or "Process(<>) creation failed" In The Alert Log And/Or TNS-12518/ TNS-12500 In Listener Log [ID 416244.1]).
Thanks,
Hussein

Checkpoint entries in my alert log - needhelp to decipher

Similar Messages

Maybe you are looking for