Forcing log switch every minute.

Hi,
I want to force a log switch every one minute how can i do it?
What should be the value of fast_start_mttr_target?
Does a checkpoint force a log switch?
Do i need to only reduce the size of redo log to a small size?
How can i make sure that a log switch will happen after a particular time period for ex. 1Minute,2 minute.
I want to force a log switch every minute because i want to send the archive redo log to standby database so that not more than 1 minute changes in database are lost. I am using 10g R2 on windows 2003 server.
I am unable to find a solution. Any help?

Hi,
I want to force a log switch every one minute how
can i do it? yes with archive_lag_target parameter
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#sthref934
What should be the value of fast_start_mttr_target?incremental or normal checkpoint "fast instance recovery/downtime concerned" introduced from oracle 8, this feature is enabled with the initialization parameter FAST_START_MTTR_TARGET in 9i.
fast_start_mttr_target to database writer tries to keep the number of dirty blocks in the buffer cache low enough to guarantee rapid recovery in the event of a crash. It frequently updates the file headers to reflect the fact that there are not dirty buffers older than a particular SCN.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtunin004.htm#sthref1110
Does a checkpoint force a log switch? log switch force to checkpoint ,checkpoint never force to log switch.
Do i need to only reduce the size of redo log to a
small size?depends yours SLA how far you can risk the data ,but it will effect yours database performance ,recommended to set the size of log which should imply the log swtich after filling to 20 mins,its a trade off risk vs perofrmance.
How can i make sure that a log switch will happen
after a particular time period for ex. 1Minute,2
minute.
want to force a log switch every minute because i
want to send the archive redo log to standby database
so that not more than 1 minute changes in database
are lost. I am using 10g R2 on windows 2003 server.
am unable to find a solution. Any help?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#sthref934Khurram

Similar Messages

  • 6 Log Files every minute

    I have a networked HP All In One Office Jet Pro L7500 running on Windows XP.
    I removed all HP Software except the drivers. I was constantly getting messages from HP Monitoring SW that my printer was connected, disconnected, connected and on and on and on.
    In addition, my temp folder would create 6 HP log files every minute. I hoped removing everything but the drivers would fix this - no.
    I checked to see if there were updated drivers and I seem to have the latest.
    How can this be fixed? My computer is freezing up if I do not delete these every few hours, also as it writes the files, my computer will slow down to a halt. The files are typically 1K but every 10 files or so will be around a 1MB.
    HELP!!
    Next step is removing the drivers and buying a better printer without this issue and trust me it will not be an HP if that is the case.

    This is worrying to me because
    A. nobody has answered yet
    B. I have the same issue with an HP Photosmart D7400
    I love the printer and the network caqpability, but it goes crazy with the log files to where it will eventually clog the hard drive on my Windows XP machine.
    HP should reconsider the banner across the top of this paqe saying "Join the Conversation" if the chance of people doing so are slim.

  • [WRT400N] Several security log entries - every minute

    I have several entries in the security log that I have no idea where they are coming from. They are all blank like this:
    Incorrect User login : Username is , Password is From 192.168.1.101=> Wed Mar 17 17:42:48 2010
    Incorrect User login : Username is , Password is From 192.168.1.101=> Wed Mar 17 17:43:48 2010
    Incorrect User login : Username is , Password is From 192.168.1.101=> Wed Mar 17 17:44:48 2010
     The only exception are a few on the first day these started appearing:
    ncorrect User login : Username is badcred, Password is himom
    From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is admin From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is 1234 From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is password From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is , Password is admin From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is , Password is From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is motorola From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is root, Password is From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is , Password is password From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is root, Password is !root From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is Admin, Password is Admin From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is Admin, Password is From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is junxion From 192.168.1.101=> Tue Mar 9 15:04:12 2010
    Incorrect User login : Username is admin, Password is cableroot From 192.168.1.101=> Tue Mar 9 15:04:12 2010
     SInce I am getting blank entries every minute, I'm curious what would be causing this. The first entries are obvious that someone was trying to access with various passwords.
    Solved!
    Go to Solution.

    Well, if it is your computer it looks as if you have some malware running on your computer which tries to hack into your router... Or did you try those passwords at any time?

  • Force log switch using dbmcli

    Hello!
    How do I force a log switch using dbmcli?
    For data protection purpose I would like to do this on daily basis.
    The system has autolog=on, and I run the backups using dbmcli via crontab on a linux box. MaxDB version is 7.6.01.12
    Regards,
    Fredrik
    Message was edited by:
            Fredrik  Rosengren
    Message was edited by:
            Fredrik  Rosengren

    Hi Fredrik,
    with Oracle Databases you use logswitches to get online redo logs copied to archive logs even when these online redo logs are not yet completely filled.
    Basically you just want to make sure to have the latest changes in your backup too.
    Well in MaxDB there is no "switch logfile" because there is no such thing as the logfiles. And there is also no limitation like the one of Oracle when backing up log data.
    If you want to backup each and all not yet backed up log entries: no problem!
    Deactivate the automatic log backup, perform a manual log backup and restart the automatic logbackup.
    The log segments in MaxDB are not like the online redo logfiles of oracle. They are just markers in the logarea that are used by the autolog features to know "oh, there had been some changes again - let's do a backup of that now".
    You may also want to have a look into this note:
    <a href="https://websmp206.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=869267&_NLANG=E">#869267 - FAQ: MaxDB LOG area</a>
    KR Lars

  • Log switch must occur every 15 to 30 minutes: good practice or myth?

    I often heard that it is recommended to size redo log files in a way that Oracle performs a log switch every 15 to 30 minutes.
    I would like to know if it is true or if it is a myth ?
    I would like to know the best way for sizing redo log files ?
    What happen exactly in the database when a log switch occurs ?
    Please help me to clarify these concepts.

    So we can say that a log switch induces a full checkpoint. That's correct ?Well, no :-) . Indeed with a log switch the checkpoint event is generated requesting DBWR to flush the buffers from the checkpoint-queue to the data files but this is not a full checkpoint and it would not update the datafile and control file headers. The Full Checkpoint happens with the alter system checkpoint ( as shown) , database being shutdown properly.
    Please see the below code which shows the same,
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
    7 rows selected.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         91   52428800          1 NO  CURRENT
          3507399 13-APR-10
             2          1         89   52428800          1 NO  INACTIVE
          3486253 13-APR-10
             3          1         90   52428800          1 NO  INACTIVE
          3486256 13-APR-10
    SQL> alter system switch logfile;
    System altered.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         91   52428800          1 NO  ACTIVE
          3507399 13-APR-10
             2          1         92   52428800          1 NO  CURRENT
          3507906 13-APR-10
             3          1         90   52428800          1 NO  INACTIVE
          3486256 13-APR-10
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
    7 rows selected.
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
    7 rows selected.
    SQL> alter system checkpoint;
    System altered.
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507936
               3507936
               3507936
               3507936
               3507936
               3507936
               3507936
    7 rows selected.
    SQL>HTH
    Aman....

  • Is there any Harm to switch the log file of production every minute

    Is there any Harm to switch the log file of production every minute as we r trying to build a replication process. We are plaining to swith the redologs everyminute and then FTP it and use it for replication to achive the relatime senario

    Is there a reason that you're not using DataGuard and/or Streams here? It would seem a lot easier to use the tools Oracle provides than to roll your own solution...
    Switching the log file every minute may have some negative performance implications in your environment.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Continiously log switching, one node unavailable

    We run 4-node RAC 9.2.0.4 on Solaris 9. Recently, one of nodes crashed due to hardware failure. After some time since this crash, i executed the command forcing log switching within the cluster: 'Alter system archive log current'. After this command, our redo logs started switching continuously - every 5-6 seconds. Generated archived logs where almost empty - they contained only a few blocks, often only one - header, i suppose. The problem was resolved only after the thread of the died node was disabled with command 'Alter database disable thread 4;'.
    I made a few experiments to investigate this problem. It seems that every command forcing redo log switch in a RAC leads to such excessive log switching, when one of nodes in cluster is unavailable. I tested 'Alter system archive log current', ARCHIVE_LAG_TARGET parameter, and the command 'Alter system switch logfile', executing from an Oracle job. In all these cases redo logs began switching continuously when the commands had beed executed or it was time to switch logs by ARCHIVE_LAG_TARGET parameter. Is there any possibility to force redo logs switch in all threads in a cluster without any problems, when one node is unavailable? We would like to switch logs every 10 minutes - to limit the amount of data that can be lost in case of whole cluster failure...
    Thanks in advance
    Alexey Sergeyev
    [email protected]

    Joel, thank you for replay. I tested forcing log switch with one node down on different ways - within a job or without one. The command 'Alter system archive log current' was executed without any job from SQL*Plus command line. This triggered continuously log switching on working nodes. The parameter ARCHIVE_LAG_TARGET does'nt produce any job - at least this job is'nt shown in DBA_JOBS. This parameter leads to continuously log switching on survived nodes, when one node goes down.
    I tried make a job, one per instance, with 'Execute immediate ''Alter system switch logfile''' command inside. Executing of such a job also triggered continuously log switching on working nodes...
    It seems that forcing log switching in a cluster works only when all is fine - all nodes are running. Is it Oracle bug? Or is it expected, but not documented behaviour?
    Alexey Sergeyev
    [email protected]

  • Frequent redo log switches

    Oracle 9.2.0.1 on W2k3 server. the redo log is switching every minute, even without any discernable database activity. It's in archive log mode and the redo logs are 100mb in size, so the archive logs are filling up my hard drive. I'm having a hard time figuring out why the redo logs are switching so often. there are 3 redo log groups. Thanks for any help you can give me.

    If the redo logs are defined at 100M in size and the archived redo logs are 100M in size then the online redo logs are being filled. As suggested log miner is one way to determine what is happening.
    Are the redo logs switching all the time or only during periods of peek activity? If the rapid log switches are only happening during certain time periods like 9:30 - 10:30 or the time correspond to the running of certain batch jobs then you should probably increase the size of your online redo logs.
    If the archived redo logs are small then obvious something is forcing log switches prior to their filling. I would check the spfile setting for log_checkpoint_interval, log_checkpoint_timeout, and fast_start_mttr_target to be sure no one had made a mistake changing one of the values prior to running the log miner.
    HTH -- Mark D Powell --

  • Redo log switching

    11gR2
    Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
    Wanted to know what would be negative side of large redo logs?

    >
    11gR2
    Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
    Wanted to know what would be negative side of large redo logs?
    >
    Patience, grasshopper!
    If it ain't broke, don't fix it. So first make sure it is broken, or about to break.
    Unless you have an emergency on your hands you don't want to implement a change like that without careful examination of your current log file usage and history.
    You need to provide more information such as typical size of your log files, number of log groups, number of members in each group, log archive policy, etc.
    1. How often do these 'peak periods' occur? Do they occur fewer than 5 or 6 times a day? Or dozens of times?
    2. How long do they last? A few minutes? Or a few hours?
    3. What is the typical, non-peak rate of switches? This is really your base-line that you need to compare things to.
    4. What has the switch pattern been over the last few weeks or months?
    5. What has the growth in DB activity benn over the last few weeks or months? What do expect over the next few months?
    6. What is your goal in reducing the frequency of log switches?
    Basic negative sides include longer time to archive each log file (the fewer logs in each group the more impact here) and the length of time to recover in the event you need to. With large log files there is more for Oracle to wade through to find the relevant data for restoring the DB to a given point in time.
    Your suggestion of every 20 - 30 minutes means 2 to 3 times per hour. If you currently switch 10 or 12 times per hour you are making a very big change.
    Although you don't want to 'tweak' the logs unnecessarily you also don't want to make such large changes.
    Everything in moderation. If your current switch rate is 10 or 12 times per hour you may want to first cut this to maybe 1/2 to 1/3: that is, to 4 or 5 time per hour. It all depends on the answers to questions like I ask above. If you post the answers to know if will be helpful to anyone trying to advise you.

  • Checkpoint and log switch

    I would like to know if when a redo log is filled, the new redo log can be written in parallel with the chekpoint.
    Or simply, what's the sequence for log switching:
    1 - redo log is filled -> checkpoint -> new log writes. or
    2 - redo log is filled -> checkpoint/new log writes (in parallel)
    Best Regards,
    Rogerio C. Schreiner
    null

    I'm tempted to say 'don't worry about it', because L_C_T has been deprecated since 9i: instead use FAST_START_MTTR_TARGET to control the rate of checkpointing.
    But that aside, L_C_T essentially says: "if a block was dirtied (changed) by a transaction whose redo was generated more that X seconds ago -where X is the number of seconds LCT is set to- then that block will be flushed to disk the next time DBWR wakes up on the '3 second rule'"
    L_C_INTERVAL means something similar: "If a block was dirtied by a transaction whose redo can be found in the redo log more than Y redo blocks away from the current checkpoint marker, where Y is the setting for LCI, flush it next time DBWR wakes up"
    A checkpoint does not always result in a log switch, but a log switch always results in a checkpoint.
    You can't really answer your third question, because the LCT parameter doesn't mean "Every 1800 seconds, flush everything to disk" (as it used to in version 8.0). But if a block was dirtied more than 1800 seconds ago, it will be a candidate for flushing to disk next time DBWR wakes up. But that doesn't tell us when a log switch will occur: that will only happen when the redo log fills up and we have to switch to the next log to keep going. I can't tell anything about the size of your logs or the rate at which they will fill up from the parameters you list.
    A parameter does exist which will force a log switch every so often. It's called ARCHIVE_LAG_TARGET, and it's set to a number of seconds. If that was set to 1800, I could say with confidence that you'd log switch every half hour. But that's not what you had in your question, of course!
    You might care to read this slightly more technical description of the parameters:
    http://www.jlcomp.demon.co.uk/faq/log_checkpoint.html
    (though I think Jonathan's timelines are wrong, because the change to the effect of the parameters came in with 8i).
    Message was edited by:
    howardjr

  • AFP session closing and logging in every 5 minutes.

    I have a new Macbook Pro and an Airport Extreme Dual Band that I seem to be having an issue with. I look at the logs in Airport Utility to check to make sure things are going well with my routers and I am continuously seeing this:
    Nov 01 05:04:43
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:04:43
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:12:29
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:12:29
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:14:47
    Severity:7
    Public address reported as 24.22.102.255 to 10.0.1.19:5353
    Nov 01 05:17:43
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:17:43
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:22:57
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:22:57
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:28:11
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:28:11
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:28:25
    Severity:5
    Associated with station 8c:58:77:30:dc:81
    Nov 01 05:28:25
    Severity:5
    Installed unicast CCMP key for supplicant 8c:58:77:30:dc:81
    Nov 01 05:29:48
    Severity:7
    Public address reported as 24.22.102.255 to 10.0.1.19:5353
    Nov 01 05:33:26
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:33:26
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:38:40
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:38:40
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    Nov 01 05:43:54
    Severity:5
    AFP session from <Guest>@10.0.1.5 closing.
    Nov 01 05:43:55
    Severity:5
    AFP login OK from <Guest>@10.0.1.5.
    10.0.1.5 is my Macbook Pro's IP address on my network and this log continues showing the session closing and logging in every 5 minutes or so. I don't know why it would be doing this. If I restart the router, all is fine for a day or so but it goes back to doing this again. Any suggestions?

    This issue can be caused by corrupted cookies.
    Clear the cache and the cookies from sites that cause problems.
    "Remove Cookies" from sites causing problems:
    * Tools > Options > Privacy > Cookies: "Show Cookies"
    Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
    *Don't make any changes on the Safe mode start window.
    *https://support.mozilla.com/kb/Safe+Mode

  • SQL Server log generating minidump files every minute

    Good afternoon.
    Our SQL server recently started generating minidump files almost every minute.
    I'm waiting on the final dbcc checkdb of the final database but all others have returned without error.
    I've run the dump files through the debugging utility and have the following stack dump which I'm not sure how to interpret.
    At this point, I'm not quite sure how to proceed, pending on the results from dbcc.
    There are no other obvious errors in the event or system logs to cross-reference.
    Thanks
    0:027> kC 1000
    Call Site
    KERNELBASE!RaiseException
    sqlservr!CDmpDump::Dump
    sqlservr!SQLDumperLibraryInvoke
    sqlservr!CImageHelper::DoMiniDump
    sqlservr!stackTrace
    sqlservr!stackTraceCallBack
    sqlservr!ex_raise2
    sqlservr!ex_raise
    sqlservr!RaiseInconsistencyError
    sqlservr!Page::DeleteRow
    sqlservr!PageRef::ExpungeGhostRow
    sqlservr!IndexPageRef::ExpungeGhost
    sqlservr!CleanVersionsOnBTreePage
    sqlservr!IndexDataSetSession::CleanupVersionsOnPage
    sqlservr!GhostExorciser::CleanupPage
    sqlservr!TaskGhostCleanup::ProcessTskPkt
    sqlservr!GhostRecordCleanupTask
    sqlservr!CGhostCleanupTask::ProcessTskPkt
    sqlservr!TaskReqPktTimer::ExecuteTask
    sqlservr!OnDemandTaskContext::ProcessTskPkt
    sqlservr!SystemTaskEntryPoint
    sqlservr!OnDemandTaskContext::FuncEntryPoint
    sqlservr!SOS_Task::Param::Execute
    sqlservr!SOS_Scheduler::RunTask
    sqlservr!SOS_Scheduler::ProcessTasks
    sqlservr!SchedulerManager::WorkerEntryPoint
    sqlservr!SystemThread::RunWorker
    sqlservr!SystemThreadDispatcher::ProcessWorker
    sqlservr!SchedulerManager::ThreadEntryPoint
    msvcr80!_callthreadstartex
    0x0
    0x0
    0x0

    i agree with Erland. Run DBCC CHECKDB on the database. Most likely there is corruption in database.
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • TNS-12537 - Service_died, Service_register events being logged every minute

    We have an 11.2.0.2 Grid Infrastructure listener that is configured with Oracle Restart. At this time, the listener is listening for connections to a 10.2.0.4 database. The following events are being logged every minute in the listener.log file. In the past, we have occasionally seen similar events logged in the 10.2.0.4 log file, but not every minute.
    21-MAR-2011 14:38:25 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=my.host.here)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=186647040)) * status * 0
    21-MAR-2011 14:38:25 * service_died * LsnrAgt * 12537
    21-MAR-2011 14:38:25 * version * 0
    Dynamic address is already listened on (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=my.host.here)(PORT=1521)))
    21-MAR-2011 14:38:25 * service_register * LsnrAgt * 0
    oerr tns 12537
    12537, 00000, "TNS:connection closed"
    // *Cause: "End of file" condition has been reached; partner has disconnected.
    // *Action: None needed; this is an information message.
    I am wondering if the LsnrAgt is part of the Oracle Restart configuration and is it really just informational when it is occurring every minute?
    Thanks for any help or pointers to docuements that may explain these events that are being logged every minute.
    Edited by: patriciaashe on Mar 21, 2011 3:08 PM
    Edited by: patriciaashe on Mar 21, 2011 3:09 PM

    This error seems to be directly tied to the auto restart configuration of the listener.
    If you remove the listener from the config, the problem goes away.
    ie.
    srvctl remove listener -l listener
    Also, if you want to leave the configuration, you can modify the check interval to alleviate the problems.
    Setting it to 0, prevents the service_died errors. Of course this has the impact of listener not automatically restarting in the event it crashes.
    crsctl modify resource ora.LISTENER.lsnr -attr CHECK_INTERVAL=0

  • My 2012 MBA on Mav 10.9.1 tries to log out every 10 to 12 minutes

    My 2012 MBA on Mav 10.9.1 is closing out programs in the background every 10-12 min. and then trying to log out.  When it get's to the one I'm working on,usually Xcode, I have to cancel the ''close", but other programs are closed out by then. Is Server 3.03 doing this? Preferences for screen saver and power mode at this point are set to "never",  If I get up to take a phone call or use the facilities I'll come back to the login screen.  At times it seems to be quicker than 10-12 minutes.  It can drive you nuts when you have a few versions of your app up on xcode and maybe some reference pages from the dev lib up on chrome or safari,  Email closes out also, so I don't realize, I just assume since I'm not getting notifications that I'm not getting mail.  I hear my phone get the notifications though so if I were to stop the log out and open mail it would download them right away.  Please help, it's driving me crazy.
    One thing, this computer does act as a server when connected, but 99% of the time I am logged into my main server.  Sorry its so long, I just couldn't quantify my question without the background information so that I can get a proper answer.  So the question agin is, is the Server software on Maverick's doing this since my preferences are set to never go to slepp or a screen saver.
    I have been working on an app for the last two months, doing everything with it as a one man show so the compter is used 20 hours a day.

    From the menu bar, select
     ▹ System Preferences... ▹ Security & Privacy ▹ Advanced...
    and uncheck the box marked
    Log out after … minutes of inactivity
    If there's a closed padlock icon in the lower left corner of the preference pane, you may need to click it to unlock the settings. Enter your login password when prompted.

  • Query runs every minute from B1 client - read B1 log file

    Hi all,
    We found this query has been run every minute from B1 client. It slows down the system, as we have over 100,000 records in table OCLG - activities. How do we stop this query to be run from B1 client. Also, anyone know what is the number for Duration in B1 log file, does the number mean CPU time? We got Duration=3581 for this query. but it takes about 10-15 seconds to run the same query from SQL 2005 management studio. Any idea?
    Thanks,
    David
    ============================================================================================
    16/02/2010  12:10:42:295830    SQLMessage    Note           ExecDirectInt     C:\Program Files\SAP\SAP Business One\SAP Business One.exe            PID=1972             TID=1920             Duration=3581  Fetched=0
                                                                                    Query     
    SELECT T0.[ClgCode], T0.[Action], T0.[Details], T1.[Name], T0.[Recontact], T0.[BeginTime], T0.[AttendUser] FROM  [dbo].[OCLG] T0   LEFT OUTER  JOIN [dbo].[OCLO] T1  ON  T1.[Code] = T0.[Location]   WHERE T0.[Reminder] = (N'Y' )  AND  T0.[RemSented] = (N'N' )  AND  (T0.[RemDate] < (CONVERT(DATETIME, '20100216', 112) )  OR  (T0.[RemDate] = (CONVERT(DATETIME, '20100216', 112) )  AND  T0.[RemTime] <= (1210 ) ))

    Thanks Paulo,
    I found another two queries that also run every minute on each B1 workstation. What is the measurement for the duration number in the log file, like  Duration=1391?
    David
    ============================================================================================
    17/02/2010  11:32:46:620527    SQLMessage    Note           ExecDirectInt     C:\Program Files\SAP\SAP Business One\SAP Business One.exe     PID=1868     TID=3236     Duration=1391     Fetched=21
                                  Query      SELECT T0.[ClgCode], T0.[AttendUser], T0.[Closed], T0.[Recontact], T0.[endDate], T0.[Action], T0.[BeginTime], T0.[ENDTime], T0.[Duration], T0.[DurType], T0.[Details], T0.[Notes], T0.[personal] FROM [dbo].[OCLG] T0 WHERE (T0.[Recontact] >= CONVERT(DATETIME, '20100215', 112)  AND T0.[Recontact] <= CONVERT(DATETIME, '20100221', 112)  )  AND  T0.[endDate] = T0.[Recontact]  AND  T0.[inactive] = (N'N' )  AND  T0.[BeginTime] IS NOT NULL   AND  T0.[ENDTime] IS NOT NULL   AND  (T0.[Action] = (N'C' )  OR  T0.[Action] = (N'M' )  OR  T0.[Action] = (N'N' ) ) AND  (T0.[AttendUser] = (612 ) )  ORDER BY T0.[Recontact],T0.[BeginTime]
    17/02/2010  11:32:54:917455    SQLMessage    Note           ExecDirectInt     C:\Program Files\SAP\SAP Business One\SAP Business One.exe     PID=1868     TID=3236     Duration=487     Fetched=0
                                  Query      SELECT T0.[ClgCode], T0.[AttendUser], T0.[Closed], T0.[Recontact], T0.[endDate], T0.[Action], T0.[BeginTime], T0.[ENDTime], T0.[Duration], T0.[DurType], T0.[Details], T0.[Notes], T0.[personal] FROM [dbo].[OCLG] T0 WHERE (((T0.[Recontact] >= CONVERT(DATETIME, '20100215', 112)  AND T0.[Recontact] <= CONVERT(DATETIME, '20100221', 112)  )  OR  (T0.[endDate] >= CONVERT(DATETIME, '20100215', 112)  AND T0.[endDate] <= CONVERT(DATETIME, '20100221', 112)  ) ) OR  (T0.[Recontact] < (CONVERT(DATETIME, '20100215', 112) )  AND  T0.[endDate] > (CONVERT(DATETIME, '20100221', 112) ) )) AND  T0.[endDate] <> T0.[Recontact]  AND  T0.[inactive] = (N'N' )  AND  T0.[BeginTime] IS NOT NULL   AND  T0.[ENDTime] IS NOT NULL   AND  (T0.[Action] = (N'C' )  OR  T0.[Action] = (N'M' )  OR  T0.[Action] = (N'N' ) ) AND  (T0.[AttendUser] = (612 ) )  ORDER BY T0.[Recontact],T0.[BeginTime]

Maybe you are looking for