Safari consuming 80% + CPU

On our PowerBook G4 - we've noticed that Safari seems to be consuming more and more CPU lately. Restarting Safari if it's been running for more than a few days, or even rebooting the PowerBook helped in the past when we had this issue, but not anymore. Even from a fresh reboot, with no other applications running, launching Safari (which opens Apple's welcome page) consumes 90% or more CPU.
I've tried the following:
- removed the ~/Library/Caches/Safari folder
- removed the ~/Library/Safari/Icons folder
- removed the comp.apple.Safari.plist file from ~/Library/Preferences folder
- resetting Safari
No effect. This machine is still running Safari 2.0.4.
It's interesting to note that if I switch to another user, their CPU usage is fine when running Safari... which makes it an issue in the User folder, instead of a further system corruption or issue. But I'm at a loss for what else to do to the "affected" user's folder to clean this up. Running FireFox is fine.
I thought maybe it was the Internet-Plugins, so I moved them to the desktop and launched Safari, same issue...
Any ideas?
Thanks in advance,
Sean

I have found the issue...
After trying a fresh install on an external drive and migrating the user accounts - the issue was still there, meaning it was definitely a User account issue.
I created a user called "test" and copied the folders from the affected User's Library folder one by one, restarting Safari each time to check CPU usage. Once I copied over the "Syndication" folder and started Safari, the issue was reproduced.
Returning to my affected user account, I moved this folder to t he desktop - fired up Safari and after a brief blip of CPU usage the CPU usage settled right down and stays there. A new "Syndication" folder was created in it's place and now Safari behaves.
In the Syndication folder that I moved, the following were the contents:
- Damaged Database
- Damaged Database #2
- Database3
- DotMacSyncCache
I had seen these before and assumed (wrongly) that the creation of a new file might mean that the damaged ones were no longer in the picture. The new folder created 1 file so far, called "Database 3", apparently it knows some history from somewhere.
I think I can delete these, but I'll do some research on that before I do, but thought I'd update this in case my findings help someone else. If you know more details on what these do - feel free to update this thread further.
Thanks everyone for your suggestions. This was a new one for me for sure.
Sean

Similar Messages

Safari Consuming All CPU Power

I just recently noticed that Safari seems to be taking a lot more processing power while browsing.
When I click on a link, the fans start spinning faster, the little colored wheel cursor appears and I can see in Activity Monitor that the CPU usage for Safari goes to 100%.
This happens every time I click on a link. It even happens if I hit the back button. It happened while I was typing in the post, since My Yahoo web page automatically refreshed on another tab.
As you can see, I have a dual Power Mac G5 2.5 GHz with 4.5 MBytes of memory.
This just started happening yesterday. I've never seen this before. From my previous PC days, I would say that I picked up a virus or some kind of Spyware.

Over the last several weeks, I too have been noticing Safari taking up more system resources than it had in the past. I upgraded to Tiger the day it came out (from 10.2) and only began noticing this problem in early August. Not only have I seen an increase in CPU usage when running Safari, but I've also seen an increase over time of RAM usage. When I restart, RAM usage is under 30% with iCal, Address Book, iTunes, Mail, NetNewsWire, and a weather app running. Later that day after having browsed and done many other actions with only those basic apps running, RAM usage stays at or slightly above 50%. It often pegs out at 65% and again after restarting and re-opening those apps back up with the exception of Safari, RAM usage remains far below 50%. With my meager 800mhz processor, and all the memory leaking and CPU hogging going on, the fan is running much more frequently than it should.

Firefox 18.0.1 consuming excessive CPU--both in Standard and Safe Mode--when accessing Gmail

Firefox 18.0.1 consumes excessive CPU--both in Standard and Safe Modes--when accessing Gmail (in Standard Mode). CPU consumption averages around 56% on my dual-CPU, Windows 7 desktop.
The only way to stop this from happening it to open Gmail in "HTML" mode. When I open Gmail in Standard mode, a "Loading..." status shows at the top of the page. After about 30 seconds, a error window pops-up within the Gmail page saying that there is a performance problem and provides the option to load Gmail in a limited, "HTML" mode. Clicking the HTML Mode link solves the issue. I've been using Firefox for years and have never seen this issue until now.

try this link
*https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

How to find out the JVM thread that is consuming high CPU

I am using WL 10.3, JRockit JVM on Linux. I have taken thread dumps. How to find out the JVM thread that is consuming high CPU?
I know how to map it Sun JVM on Solaris. I haven't done in on JRockit so far. Please advise.

Check out some of Marcus Hirt's blog entries for details about how to use JRockit Mission Control. It's a very nice tool that should provide a lot of insight:
http://blogs.oracle.com/hirt/

Dbwr consuming high CPU after enabling DirectIO

Hi,
DBWR is consuming high CPU. After enabling DirectIO on Solaris SPARC 10, dbwr is eating away almost 1 CPU on a v440 machine i.e. 19% throughout the day. Neither of "buffer busy waits" or "write complete waits" or "free buffer waits" are in the top 5 wait events, which, to me, means that there is no buffer contention.
What I understand is that after enabling DirectIO, it takes longer for the IO to complete because pre-DirectIO it would return from the file system cache whereas now it has to return from the disk (and I do see at the OS level that IO has become slow), but should that result in dbwr consuming more CPU?
Infact after enabling DirectIO, IO has become very slow which is another problem and as a result log file writes have also become slow which is a 3rd problem. btw, I am aware that if there were many FTS, then DirectIO can make the system slow but there are no FTS in my case. Also, that SGA should be increased after enabling DirectIO, which has also been done.
Thanks

user12022918 wrote:
DBWR is consuming high CPU. After enabling DirectIO on Solaris SPARC 10, dbwr is eating away almost 1 CPU on a v440 machine i.e. 19% throughout the day. 19% is less than 1/5th of a CPU. Or are you referring to a 100% being all 4 CPUs?
What I understand is that after enabling DirectIO, it takes longer for the IO to complete because pre-DirectIO it would return from the file system cache whereas now it has to return from the disk Incorrect. See directio for details.
Yes, removing the file system cache from the I/O layer for a device can reduce I/O performance if the caller does not perform its own caching. However, direct I/O will eliminate the system cache overheads (and associated CPU resources needed) from a caller (like Oracle) that implements its own sophisticated buffer cache.
Direct I/O should therefore increase Oracle I/O performance and decrease resource footprint as it eliminates the need for the kernel to maintain a cache for that device.
Infact after enabling DirectIO, IO has become very slow which is another problem and as a result log file writes have also become slow which is a 3rd problem. Direct I/O, as per the Sun docs, is an advisory call. It may not place that device in direct I/O modes. It may result in partial direct I/O. So you need to make sure exactly what happens and how successful (partial or complete) this setting was.
btw, I am aware that if there were many FTS, then DirectIO can make the system slow but there are no FTS in my case. FTS (multi block reads/large sequential reads) is slower? This is contrary to Sun's docs that state:
Large sequential I/O generally performs best with DIRECTIO_ON, except when a file is sparse or is being extended and is opened with O_SYNC or O_DSYNC.

Oracle.exe consuming 100% CPU on windows and database hang

Hi all,
every time my oracle database is hanging when the application run, the problem is the oracle.exe consum 100% CPU but not memory and the server hang and the dabase is going to inaccessible, we need to restart oracle instance service or server to bring the databas eback to normal but it's not permanent because the problem occurs once the application turn on.
Checking the log file i found the below error every time:
My database version is 9.2.0.7.0
OS: Windows 2003 Server Standard Edition Service Pack 2
RAM: 3,5Gb
CPU: Inte Xeon 3.20 GHz
ORA-00600: internal error code, arguments: [kghuclientasp_03], [0xBFEADCE0], [0], [0], [0], [], [], []
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04050: error while attempting to allocate 163500 bytes of memory
ORA-06512: at "SYS.ORACLE_LOADER", line 14
ORA-06512: at line 1
Fri Mar 05 05:35:15 2010
Errors in file e:\oracle\admin\optprod\udump\optprod_ora_5876.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-04030: out of process memory when trying to allocate 8389132 bytes (pga heap,redo read buffer)
ORA-04030: out of process memory when trying to allocate 8389132 bytes (pga heap,redo read buffer)
ORA-04030: out of process memory when trying to allocate 8180 bytes (callheap,kcbtmal allocation)
Thank you
Lucienot.

Is this a new application on this database?
Has it run well in the past?
I have had this happen before on a 32bit Windows server. Our problem was a poorly written procedure that kept pegging the cpu to 100%. You should be able to figure out what SQL is being used that is causing this problem, it will be the Top Working SQL most likely.
I also had this problem on a Logical Standby server which was trying to apply SQL to the SYS.AUD$ table. As soon as SQL Apply was started, the CPU went to 100%. Once I truncated that table, the cpu usage went back to normal. Not sure what you are using to monitor your database but if you can, try to find out what SQL is running when your CPU goes to 100%.

Query to find out which process consuming more cpu?

Hi All,
some one please tell me the query to find out which process is consuming more
cpu resources?
Thanks and Regards
Srikanth

Use V$SESSTAT to determine which sessions are using most CPU, and investigate what SQL these users/sessions are executing:
SQL> select ss.sid, se.command, ss.value CPU, se.username, se.program
from v$sesstat ss, v$session se
where ss.statistic# in
(select statistic#
from v$statname
where name = 'CPU used by this session')
and se.sid=ss.sid
order by ss.value desc;

How to find top 10 SQL statments which are consuming more cpu time.

hi all,
Is there any command or script to monitor the top 10 sql statments which are consuming more cpu time.
I know by using AWR REPORT we can find it, i want the command or script to find the top cpu utilization sql statments.
Regards
Subhash.

Subhash,
A quick and dirty Google search could have get you started with the following:
Thread: how to get top CPU consuming sql oracle 10g
Re: how to get top CPU consuming sql oracle 10g
Oracle SQL top sessions
http://www.dba-oracle.com/oracle10g_tuning/t_sql_top_sessions.htm
"How to Find top 10 expensive sql's", version 9.2.0
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:73325450402303
HTH,
Thierry

Reader 9.0 consumes 25% CPU and freezes...open Reader first?

I was having problems double clicking on a document and scrolling through it. After a few page down clicks, it would consume 25% CPU and lock up. This is on a quad core with 6gb memory running 64 bit Vista. What I discovered was if I instead opened up Reader first, chose Open and browsed to the document, it worked fine. Does anyone know why this might occur? I'm assuming it has to do with how Reader is launched.
I understand how file type associations and things worked under XP, but I'm having difficulty finding the same thing in Vista to see if there are different parameters being used.
The same document worked fine on my 4 year old XP machine with Reader 7.

. Uninstalling Reader version 9
2. Installing Reader version 8.1 from the abobe.com website
3. I then had to uninstall via control panel add remove programs the adobe.com program, and I also uninstalled the Adobe AIR program.
4. I then checked in my Add Remove programs list and Adobe Reader 9 is still listed, I uninstall it again (why I don't know).
5. I then view a PDF file outside of Internet Explorer and I have to accept the license agreement in a popup window to get Reader 8 working properly.
6. I then go to a web page that links to a PDF file and finally I can view PDfs in the browser again.
We have around 30 PCs in our department with Adobe Reader 9 and some of them work in a browser and some of them do not, so there appears to be a conflict of some sort.
For info, I have Acrobat Professional 8.1 on my PC also.

FNDOPP process consumes 200% CPU even though request count is less

Hi Guys,
We have problem with FNDOPP services in R12.1.3 with database version 11.2.0.3
Its a multinode environment with RAC database and shared Appl_top with PCP.
The problem is that FNDOPP process at OS level is consuming 200% CPU
we have defined 4 threads for OPP in our production environment. with server having 24 CPU on each application node.
Also Post processing action Concurrent Request takes long to process with OPP.
Please suggest what areas to look into bring down load on OPP and hence CPU consumption through OPP process.
Your help is appreciated.
Regards,
Milan

Please see the following docs.
R12: Troubleshooting Known XML Publisher and E-Business Suite (EBS) Integration Issues [ID 1410160.1]
EBS - Technology Area - Webcast Recording 'BI Publisher / XML Publisher Overview & Best Practices - Webinar' [video] [ID 1513592.1]
Poor Performance /High Buffer Gets In FND_CONC_TEMPLATES [ID 1085293.1]
Performance Issue - PDF Generated With BI Publisher [ID 956902.1]
Overview of Available Patches for Oracle XML Publisher embedded in the Oracle E-Business Suite [ID 1138602.1]
Tuning Output Post Processor (OPP) to Improve Performance [ID 1399454.1]
Thanks,
Hussein

How to identify TOP 5 SQL consuming more CPU time without using statspack

How to identify the TOP 5 SQL queries which are consuming more CPU time during the timespan of 24 hours for entire database. There are N number of users who have issued sql queries, out of which few users have disconnected and few user are still connected to the database(I need to consider all sessions). My database version is 9.0.1. I don't want to use statspack. Is there any way to identify TOP 5 SQL consuming more CPU time without affecting the performance of the database. Can any one help me on this? Its urgent!!.

My database version is 9.0.1. I don't want
to use statspack. Is there any way to identify TOP 5
SQL consuming more CPU time without affecting the
performance of the database. Can any one help me on
this? Its urgent!!.I cant understand why you dont want to use statspack. As it is very easy to use and very quick to identify bottlenecks. Try using statspack. Its really wonderful.
Particularly in your case statspack is the best.
Regards,
Sanju.

After starting up the listener the server consuming 100% CPU

Hi,
when i startup the database tier (EBS 12.1.3 and DB 11.2.0.2) its stared well and the CPU usage is normal.But when i start the listener the server (RHEL 5.8) start consuming 100% CPU.
alert.log details
in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j000_7601.trc:
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
ORA-06512: at line 1
Wed Dec 12 10:11:33 2012
Sweep [inc][480592]: completed
Wed Dec 12 10:13:17 2012
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc (incident=480612):
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc:
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
ORA-06512: at line 1
Wed Dec 12 10:13:18 2012
Sweep [inc][480612]: completed
Wed Dec 12 10:14:18 2012
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_ora_7814.trc (incident=481092):
ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/incident/incdir_481092/UAT_ora_7814_i481092.trc
Wed Dec 12 10:14:23 2012
Dumping diagnostic data in directory=[cdmp_20121212101423], requested by (instance=1, osid=7814), summary=[incident=481092].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Dec 12 10:14:24 2012
Sweep [inc][481092]: completed
Sweep [inc2][481092]: completed
Wed Dec 12 10:16:50 2012
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc (incident=481492):
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc:
ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
ORA-06512: at line 1
Wed Dec 12 10:19:04 2012
Incremental checkpoint up to RBA [0xf.ac257.0], current log tail at RBA [0xf.c3691.0]
Wed Dec 12 10:20:56 2012
Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of ASHSIZE to a sufficiently large value. Currently, ASH size is 2097152 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:
select total_size,awr_flush_emergency_count from v$ash_info;
Wed Dec 12 10:21:26 2012
Sweep [inc][481492]: completed

Please see these docs.
ORA-600/ORA-7445/ORA-700 Error Look-up Tool [ID 153788.1]
ORA-600 [13011] "Problem occurred when trying to delete a row" [ID 28184.1]
Workflow Control Queue Clean Up Program Fails With ORA-25226 [ID 334237.1]
Thanks,
Hussein

Data Base 11G is consuming all cpu

i have installed a oracle database 11g and Apex in a vitual machine, I start the virtual machine and also database services start, but after three minuts the consume of CPU for oracle.exe process it grow much until cosume the 100% of CPU
i don´t know what happen, wich is the cause?

user11095479 wrote:
i have installed a oracle database 11g and Apex in a vitual machine, I start the virtual machine and also database services start, but after three minuts the consume of CPU for oracle.exe process it grow much until cosume the 100% of CPU
i don´t know what happen, wich is the cause?
>i have installed a oracle database 11g and Apex in a vitual machine, I start the virtual machine and also database services start, but after three minuts the consume of CPU for oracle.exe process it grow much until cosume the 100% of CPU
i don´t know what happen, wich is the cause?
COPY & PASTE results from following SQL
SELECT * FROM V$VERSION;

Syslogd Consuming more CPU utilization in Solaris 10

Hi All,
The Syslogd process consuming more CPU utilization in Solaris 10. Kindly help how to reduce this cpu utilization.
Regards
Siva

Hi Robert,
Both are same architecture. x86
The following is the prstat o/p from the affected server. Pls note that one of the mount point in this server is in ZFS.
prstat -l
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/LWPID
26092 root 3933M 3930M cpu1 60 0 29:00:43 22% syslogd/56
26092 root 3933M 3930M run 30 0 289:47:33 12% syslogd/18
26092 root 3933M 3930M run 40 0 272:31:05 11% syslogd/22
26092 root 3933M 3930M run 22 0 14:47:16 9.7% syslogd/65
26092 root 3933M 3930M run 42 0 14:43:46 9.7% syslogd/63
26092 root 3933M 3930M run 31 0 14:40:42 9.6% syslogd/66
26092 root 3933M 3930M sleep 40 0 152:45:42 5.9% syslogd/21
26092 root 3933M 3930M cpu0 53 0 6:41:58 4.1% syslogd/58
26092 root 3933M 3930M run 52 0 6:23:13 4.0% syslogd/57
26092 root 3933M 3930M sleep 43 0 6:29:21 3.9% syslogd/59
26092 root 3933M 3930M sleep 52 0 5:55:14 3.6% syslogd/71
More over we are continuously receiving the below error message in the /var/adm/messages, we don't know, from where the error arises from the syslog server.
syslogd: malloc failed: dropping message from remote: Not enough space
PRIVILEGE :[4] 'NONE'
Edited by: Siva_Systems on Mar 29, 2010 5:06 AM
Edited by: Siva_Systems on Mar 29, 2010 8:18 AM

Why process 'timestenrepd' on the standby database keep consuming 600% CPU?

Hi all, I have just created a empty active standby pair where there are 14 regular AWT cache groups.
After call of ttRepStart on the standby database, it takes 600% CPU(24 cores CPU) all the time.
There is no data in the cache groups and I found the error logs in the tterrors.log file:
14:01:28.32 Warn: : 27703: 27710/0xf83c50: Recovery started
14:01:31.62 Warn: : 27703: 27710/(nil): Another checkpoint is in progress. The final checkpoint will continue when the other checkpoint finishes.
14:01:44.96 Warn: REP: 25580: [139865850070784, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'FAILOVER' (context 0x7f2f580008c0) starting
14:01:44.97 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'REPLISTENER' (context 0x7f2f600008c0) starting
14:01:44.97 Warn: REP: 25580: [139865846920960, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'XLA_PARENT' (context 0x7f2f680008c0) starting
14:01:44.97 Warn: REP: 25580: [139865853220608, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'REPHOLD' (context 0x7f35040008c0) starting
14:01:45.04 Warn: REP: 25580: [139865840621312, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'LOGFORCE' (context 0x7f3500000c50) starting
14:01:45.04 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(M)' (context 0x7f2f540008c0) starting
14:01:45.04 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 0 got repSlave object 0x5406d9a0
14:01:45.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(M)' (context 0x7f2f500008c0) starting
14:01:45.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 0 got repSlave object 0x5006d9a0
14:01:45.05 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:45.12 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:45.13 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f480008c0) starting
14:01:45.13 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f400008c0) starting
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 1 got repSlave object 0x5406d9a0
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f3c0008c0) starting
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 2 got repSlave object 0x5406d9a0
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:46.15 Err : REP: 25580: [139841666549504, 0, noAwt] EPPDB:meta.c(3134): TT16999: receiver slot alloc: 16289484001462337649 15530743840010091109
14:01:46.15 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:46.46 Warn: : 27703: 25580/0x7f2f400008c0: XXX:1st CTN for track 1 was 1354600888.2 with prev as 4294967295 hdr.firstCTN 1354600888.2expectedCTN=1354600888.2
14:01:46.46 Warn: : 27703: 25580/0x7f2f400008c0: XXX:1st CTN for track 1 was 1354600894.2 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:46.83 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:46.83 Warn: REP: 25580: [139841526023936, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f340008c0) starting
14:01:46.83 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:47.04 Warn: : 27703: 25580/0x7f2f540008c0: XXX:1st CTN for track 0 was 1354600888.3 with prev as 0 hdr.firstCTN 1354600888.2expectedCTN=1354600888.2
14:01:47.05 Warn: : 27703: 25580/0x7f2f540008c0: XXX:1st CTN for track 0 was 1354600894.0 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:47.43 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:47.43 Warn: REP: 25580: [139840591431424, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f200008c0) starting
14:01:47.43 Warn: REP: 25580: [139841522874112, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:48.46 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 0) set to 1
14:01:48.46 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. select() timed out isAwt (false) parallelism (3) trackId (0) socket (17)
14:01:48.46 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 0) set to 1
14:01:48.66 Warn: REP: 25580: [139840591431424, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 1) set to 1
14:01:48.66 Warn: REP: 25580: [139840591431424, 1, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. TimesTen replication receivers are stopping isAwt (false) parallelism (3) trackId (1) socket (19)
14:01:48.66 Warn: REP: 25580: [139840591431424, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 1) set to 1
14:01:48.66 Err : REP: 25580: [139841522874112, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139841522874112, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139840591431424, 1, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841526023936, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 2) set to 1
14:01:48.66 Warn: REP: 25580: [139841526023936, 2, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. TimesTen replication receivers are stopping isAwt (false) parallelism (3) trackId (2) socket (23)
14:01:48.66 Warn: REP: 25580: [139841526023936, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 2) set to 1
14:01:48.66 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(1870): TT16999: stopRcvrThreads (track 0) set to 0
14:01:48.66 Err : REP: 25580: [139840594581248, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Err : REP: 25580: [139841663399680, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841526023936, 2, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:49.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:49.05 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:49.05 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f480008c0) starting
14:01:49.06 Warn: REP: 25580: [139841526023936, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context 0x7f2f00000000) starting
14:01:49.22 Warn: : 27703: 25580/0x7f2f3c0008c0: XXX:1st CTN for track 2 was 1354600894.11 with prev as 4294967295 hdr.firstCTN 1354600894.11expectedCTN=1354600894.0
14:01:50.17 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:53.54 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:53.54 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f440008c0) starting
14:01:53.54 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f200008c0) starting
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 2 got repSlave object 0x5006d9a0
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:54.20 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:54.20 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f180008c0) starting
14:01:54.20 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 1 got repSlave object 0x5006d9a0
14:01:54.20 Warn: REP: 25580: [139841533159168, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f080008c0) starting
14:01:54.20 Warn: REP: 25580: [139841533159168, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #4 started
14:01:54.20 Warn: REP: 25580: [139841405417216, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2ef40008c0) starting
14:01:54.20 Warn: REP: 25580: [139841405417216, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #1 started
14:01:54.21 Warn: REP: 25580: [139841530009344, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2efc0008c0) starting
14:01:54.21 Warn: REP: 25580: [139841530009344, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #3 started
14:01:54.21 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:54.21 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:54.21 Warn: REP: 25580: [139841402267392, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2ef80008c0) starting
14:01:54.21 Warn: REP: 25580: [139841402267392, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #0 started
14:01:54.21 Warn: REP: 25580: [139841536308992, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f040008c0) starting
14:01:54.21 Warn: REP: 25580: [139841536308992, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #5 started
14:01:54.21 Warn: REP: 25580: [139841539458816, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_SORTER' (context 0x7f2f0c0008c0) starting
14:01:54.21 Warn: REP: 25580: [139841539458816, 0, Awt] EPPDB:awt.c(144): TT16999: Parallel AWT Sorter started
14:01:54.21 Warn: REP: 25580: [139841399117568, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2eec0008c0) starting
14:01:54.22 Warn: REP: 25580: [139841392817920, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.22 Warn: REP: 25580: [139841395967744, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ef00008c0) starting
14:01:54.22 Warn: REP: 25580: [139841389668096, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.22 Warn: REP: 25580: [139841408567040, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f000008c0) starting
14:01:54.22 Warn: REP: 25580: [139841408567040, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #2 started
14:01:55.87 Warn: REP: 25580: [139841663399680, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:56.54 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:56.55 Warn: REP: 25580: [139841182365440, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ed80008c0) starting
14:01:56.55 Warn: REP: 25580: [139841179215616, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600759.70 with prev as 63 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600888.2 with prev as 4294967295 hdr.firstCTN 1354600888.1expectedCTN=1354600888.0
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600894.2 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:57.26 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:57.27 Warn: REP: 25580: [139841176065792, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ecc0008c0) starting
14:01:57.27 Warn: REP: 25580: [139841172915968, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:57.90 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600759.71 with prev as 68 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600759.69 with prev as 64 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600888.1 with prev as 4294967295 hdr.firstCTN 1354600888.1expectedCTN=1354600888.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600894.11 with prev as 4294967295 hdr.firstCTN 1354600894.11expectedCTN=1354600894.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600888.0 with prev as 4294967295 hdr.firstCTN 1354600888.0expectedCTN=1354600888.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600894.0 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
Please note that this is a newly active standby pair where there is no data or workload while the problem occurs, it makes me very depressed.

Ok, Chirs, here are my steps to set up the active stnadby pair:
1.steps on the active database:
% ttIsql eppdb;
command> @init_user_grant.sql
% ttIsql "DSN=eppdb;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
command> call ttCacheUidPwdSet('cacheuser','oracle');
command> call ttGridCreate('myGrid');
command> call ttGridNameSet('myGrid');
command> call ttCacheStart;
command> @create_all_cache_groups.sql
command>
CREATE ACTIVE STANDBY PAIR eppdb ON "baal", eppdb ON "diablo"
RETURN TWOSAFE
STORE eppdb ON "baal" DISABLE RETURN ALL 5 RESUME RETURN 20
STORE eppdb ON "diablo" DISABLE RETURN ALL 5 RESUME RETURN 20;
command>call ttRepStart;
command>call ttRepStateSet('active');
command>@load_cache_groups.sql
command>exit
2.steps on the standby database:
% ttRepAdmin -duplicate -from eppdb -host "baal" -uid cacheuser -pwd timesten -cacheuid cacheuser -cachepwd oracle -keepCG eppdb
% ttIsql "DSN=eppdb;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
Command> CALL ttCacheUidPwdSet('cacheuser','oracle');
Command> CALL ttCacheStart;
Command> CALL ttRepStart;
After the replication agent is started on the standby database, issuing a 'top' command in the bash on the standby database server,
I can see the process 'timestenrepd' consumes 600%+ CPU all the time except for stopping the replication agent.

Safari consuming 80% + CPU

Similar Messages

Maybe you are looking for