The event log file is full

Hi All
In Message monitoring(RWB) in  adapter engine i am getting the following error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> The event log file is full
Can any one suggest me what might be the problem
Thanks
Jayaraman
Edited by: Jayaraman P on May 20, 2010 4:27 PM
Edited by: Jayaraman P on May 20, 2010 4:28 PM

>
Jayaraman P wrote:
> SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> The event log file is full
this is because of a problem at the WS server (it might mostly be a windows server).
You can request the WS team to have a look into this issue. it is not a PI problem.

Similar Messages

  • "The event log file is full" error - SAP LVS Report Viewer 1.0

    Hi Experts,
    I'm getting an error when trying to generate a report in SAP LVS.
    Error:
    The event log file is full
    How do I resolve this? Anyone encountered this error?
    Thanks in advance,
    Cyrous

    Hi,
    It seems that the audit log mechanism is activated, at your system. But, if you didn't set the parameter DIR_AUDIT, audit log will be created under "/usr/sap/<SID>/<instance>/log", not "data" folder. You can check its default value on RZ11. Revise the parameters, below;
    DIR_AUDIT = <path>
    FN_AUDIT = audit_++++++++.AUD
    rsau/enable = 1
    rsau/max_diskspace/local = <SizeOfFile>
    Best regards,
    Orkun Gedik

  • Unable to delete records as the transaction log file is full

    My disk is running out of space and as a result I decided to free some space by deleting old data. I tried to delete 100,000 by 100,000 as there are 240 million records to be deleted. But I am unable to delete them at once and shrinking the database doesn't
    free much space. This is the error im getting at times.
    The transaction log for database 'TEST_ARCHIVE' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
     How can I overcome this situation and delete all the old records? Please advice.
    mayooran99

    In order to delete the SQL Server need to write the information in the log file, and you do not have the place for those rows in the log file. You might succeeded to delete less in each time -> next backup the log file each time -> next shrink the
    log file... but this is not the way that I would chose.
    Best option is probably to add another disc (a simple disk do not cost a lot), move the log file there permanently. It will increase the database work as well (it is highly recommend not to put the log file on the same disk as the data file in most cases).
    If you can't add new disk permanently then add one temporary. Then add file to the database in this disk -> create new table in this disk -> move all the data that you do
    not want to delete to the new table -> truncate the current table -> bring back the data om the new table -> drop the new table and the new file to release the temporary disk.
    Are you using full mode or simple recovery mode ?
    * in full mode you have to backup the log file if you want to shrink it
      Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]

  • File history stopped working after a warning message in the event log

    I have encountered this twice that File history stopped working, the event log says:
    Unusual condition was encountered during finalization of a backup cycle for configuration C:\Users\xxxx\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config
    If I re-run it, it consumes the backup disk space but still failed to backup.
    I have to manually delete all backup, turn off File History and re-configure it again to make it work.
    This happened twice already, so all my file history lost after re-config.
    Anyone encounter the same situation?

    MICROSOFT is plagued by idiots!!!!
    - Just turn it off
    - then click  "select drive"
    - and when it asks you the retarded question... just click >>>>>"NO"<<<<<<<    -_-
    Seriously... this is the answer.... frigging retards at microsoft... to think it takes an army of programmers and billions of dollars to create such idiocy!
    http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/cannot-change-drive-in-file-history-windows-8/6dbeca54-d05e-4f93-9262-45a56d6a82d1?page=2&msgId=f1792c5e-c5d0-4163-b449-c7165d72f88d&tab=question&status=AllReplies&status=AllReplies%2CAllReplies
    I cant believe these morons put everyone through such hell and then don't even bother to follow up with the correct solution.
    To top it of the moron moderator marks this as an answer??!!!
    What a pathetic joke - I hope everyone reads this message before being punished by the miles of bullcrap in this thread -_-
    Microsoft = ridiculous
    Thanks! I guess the TL;DR version is "to change your file history drive you need to discard the current temp files."
    Exactly :)
    It's the bad wording in the messages.
    the first message (which I can only vaguely remember so can't quote exactly) that gives you the impression you can continue
    something but doesn't make clear that to so will need the "old drive" configured the way the "old drive" was.
    Then the next message is just confusing:
    “we can't copy files to this location.  Your current File History drive is disconnected.  Reconnect the drive and try again” 
    sounds like 
    “we can't copy files to this location. [because there's a problem with the new location]
    Your current File History drive is disconnected. [the new location is disconnected]
    Reconnect the drive and try again [reconnect your new location and try again]” 
    When it should be reworded to say something along the lines of (in more formal language):
    "You asked us to continue...give us the drive you were previously using...or if it's no longer available, click here to start from scratch"
    (I know that's all the opposite of tldr but I'm trying again to put into words what I think was happening).

  • The Data Access service is either not running or not yet initialized. Check the event log for more information

    Hi,
    I have SCSM with remote SQL and the SCSM Management server give below error
    Message: Failed to connect to server ‘Name of Server’
    Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized. Check the event log for more information. —> System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://ServerName:5724/DispatcherService.
    The connection attempt lasted for a time span of 00:00:04.0070932. TCP error code 10061: No connection could be made because the target machine actively refused it IPAddress:5724.  —> System.Net.Sockets.SocketException: No connection could be made
    because the target machine actively refused it IPAddress:5724
    I had try to restart SQL & MS with same error,
    Also i had try the following
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/c670d54d-3a92-481f-8dc9-55c475ad196f/problems-with-data-access-service-after-rebooting
    https://social.technet.microsoft.com/Forums/systemcenter/en-US/26dc1d5c-fa82-403f-8949-3073f3b82a60/the-data-access-service-is-either-not-running-or-not-yet-initialized
    Not help meRegards

    I had same error before 
    below steps to solve it
    Make sure SQL Server Running & ServiceManager Database not full
    Stop All SCSM Services,
               System Center Management Configuration
       Microsoft System Center Data Access Service.
       Microsoft Monitoring Agent
    Rename Health Service State to Health Service State_old --- @ "C:\Program Files\Microsoft System Center 2012 R2\Service Manager"
    Start SCSM Services
        Microsoft Monitoring Agent
               System Center Management Configuration
       Microsoft System Center Data Access Service.
    Wait 2 min...
    check Event Viewer... 
    hope this help you.
    Regards, Ibrahim Hamdy

  • Microsoft sql server extended event log file

    Dears
    Sorry for my below questions if it is very beginner level.
    In my implementation I have cluster SQL 2012 on Windows 2012; I am using MountPoints since I have many Clustered Disks.
    My MountPoint Size is only 3 GB; My Extended event log are growing fast and it is storing in the MountPoint Drive directly (Path: F:\MSSQL11.MSSQLSERVER\MSSQL\Log).
    What is the best practice to work with it? (is it to keep all Extended events? or recirculate? or to shrink? or to store in DB?)
    Is there any relation between SQL truncate and limiting the size of Extended event logs?
    How can I recirculate this Extended Events?
    How can I change the default path?
    How can I stop it?
    and in case I stop it, does this means to stop storing SQL event in Windows event Viewer?
    Thank you

    After a lot of checking, I have found below:
    My Case:
    I am having SQL Failover Cluster Instances "FCI" and I am using Mount-Points to store my Instances.
    I am having 2 Passive Copies for each FCI.
    In my configuration I choose to store the Root Instance which include the logs on Mount-Point.
    My Mount Point is 2 GB Only, which became full after few days of deployment.
    Light Technical Information:
    The Extended Event Logs files are generated Coz I have FCI, in single SQL Installation you will not find this files.
    The File Maximum size will be 100 MB.
    The Files start circulating after it become 10 Full Files.
    If you have the FCI installed as 1 Active 2 Passive, and you are doing failover between the nodes, then you will expect to see around 14 - 30 copy of this file.
    Based on above information you will need to have around 100 MB * 10 Files Per Instance copy * 3 Since in my case I have 1 Active and 2 passive instances which will = 3000 MB
    So in my case My Mount-Point was 2 GB, which become full coz of this SQLDIAG Logs.
    Solution:
    I extended my mount point by 3 GB coz I am storing this logs on it.
    In case you will need to change SQLDIAG Extended Logs Size to 50 MB for example and place to F:\Logs, then you will need below commands:
    ALTER SERVER CONFIGURATION SET DIAGNOSTICS LOG OFF;
    ALTER SERVER CONFIGURATION
    SET DIAGNOSTICS LOG MAX_SIZE = 50 MB;
    ALTER SERVER CONFIGURATION
    SET DIAGNOSTICS LOG PATH = 'F:\logs';
    ALTER SERVER CONFIGURATION SET DIAGNOSTICS LOG ON;
    After that you will need to restart the FCI from SQL Server Configuration Manager or Failover Cluster Manager.
    I wish you will find this information helpful if it is your case.
    Regards

  • WebLogic 10.3.2.0 hanging at startup after "The server log file is opened."

    Hi,
    A WebLogic 10.3.2.0 server is hanging at startup. There are no error messages. The last command in the startup window is:
    "The server log file <log file dest> is opened. All server side log events will be written to this file."
    I think the next line should be:
    "Security initializing using security realm realm."
    Any ideas on what could be the issue? For instance what resources should be accessed at that point of time? There is sufficient space left on the (virtual machine) disk. The VM configured with 8GB memory. Could it be performance related still?
    Following is written to the log file:
    ####<12.aug.2010 kl 09.47 CEST> <Info> <WebLogicServer> <oim> <> <Main Thread> <> <> <> <1281599254656> <BEA-000214> <WebLogic Server "AdminServer" version:
    WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.> ####<12.aug.2010 kl 09.47 CEST> <Notice> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255312> <BEA-170019> <The server log file ....logs\AdminServer.log is opened. All server side log events will be written to this file.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255390> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Diagnostics> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599255671> <BEA-320001> <The ServerDebug service initialized successfully.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Store> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599256515> <BEA-280050> <Persistent store "WLS_DIAGNOSTICS" opened: directory="....s\domains\oim\servers\AdminServer\data\store\diagnostics" writePolicy="Disabled" blockSize=512 directIO=false driver="wlfileio2"> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3s" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "http" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "https" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "iiop" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "iiops" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldap" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldaps" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "cluster" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "clusters" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "snmp" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "admin" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002624> <The administration protocol is "t3s" and is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <RJVM> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257468> <BEA-000570> <Network Configuration for Channel "AdminServer"
    Listen Address          :7001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257687> <BEA-002609> <Channel Service initialized.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258000> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
    ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000436> <Allocating 3 reader threads.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000446> <Native IO Enabled.> ####<12.aug.2010 kl 09.47 CEST> <Info> <IIOP> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599259500> <BEA-002014> <IIOP subsystem enabled.>
    Thanks!!

    tried both of these, still having same error as below:
    <Sep 8, 2010 1:32:37 PM IST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
    <Sep 8, 2010 1:32:37 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic2 javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic2 denied
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:250)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    Truncated. see log file for complete stacktrace
    >
    <Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Sep 8, 2010 1:32:37 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Pls help me out ASAP...

  • Server shutdown with the following log file -?

    JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=128m
    WLS Start Mode=Production
    CLASSPATH=:/home3/bea9/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home3/bea9/jdk150_07/lib/tools.jar:/home3/bea9/weblogic92/server/lib/weblogic_sp.jar:/home3/bea9/weblogic92/server/lib/weblogic.jar:/home3/bea9/weblogic92/server/lib/webservices.jar::/home3/bea9/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/home3/bea9/weblogic92/server/lib/xqrl.jar::
    PATH=/home3/bea9/weblogic92/server/bin:/home3/bea9/jdk150_07/jre/bin:/home3/bea9/jdk150_07/bin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/opt/nettladm/bin:/opt/fc/bin:/opt/fcms/bin:/opt/upgrade/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/hparray/bin:/opt/langtools/bin:/opt/imake/bin:/opt/perf/bin:/opt/ignite/bin:/opt/OV/bin/OpC:/opt/hpnp//bin:/opt/resmon/bin:/usr/sbin/diag/contrib:/opt/pred/bin:/opt/sec_mgmt/spc/bin:/opt/graphics/common/bin:/opt/OV/bin:/opt/ssh/bin:/opt/sec_mgmt/bastille/bin:.
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.5.0.07"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.07-_20_mar_2007_05_31)
    Java HotSpot(TM) Server VM (build 1.5.0.07 jinteg:03.20.07-04:39 PA2.0 (aCC_AP), mixed mode)
    Starting WLS with line:
    /home3/bea9/jdk150_07/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -da -Dplatform.home=/home3/bea9/weblogic92 -Dwls.home=/home3/bea9/weblogic92/server -Dwli.home=/home3/bea9/weblogic92/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home3/bea9/patch_weblogic922/profiles/default/sysext_manifest_classpath -Dweblogic.Name=Admin -Djava.security.policy=/home3/bea9/weblogic92/server/lib/weblogic.policy weblogic.Server
    <May 13, 2009 10:36:22 AM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /home3/bea9/weblogic92/platform/lib/p13n/p13n-schemas.jar:/home3/bea9/weblogic92/platform/lib/p13n/p13n_common.jar:/home3/bea9/weblogic92/platform/lib/p13n/p13n_system.jar:/home3/bea9/weblogic92/platform/lib/wlp/netuix_common.jar:/home3/bea9/weblogic92/platform/lib/wlp/netuix_schemas.jar:/home3/bea9/weblogic92/platform/lib/wlp/netuix_system.jar:/home3/bea9/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <May 13, 2009 10:36:24 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0.07 jinteg:03.20.07-04:39 PA2.0 (aCC_AP) from Hewlett-Packard Company>
    <May 13, 2009 10:36:29 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP2 Mon Jun 25 01:32:01 EDT 2007 952826 >
    <May 13, 2009 10:37:03 AM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /home3/bea9/license.bea>
    <May 13, 2009 10:37:03 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <May 13, 2009 10:37:03 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <May 13, 2009 10:37:04 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /home3/bea9/user_projects/domains/Production/servers/Admin/logs/Admin.log is opened. All server side log events will be written to this file.>
    <May 13, 2009 10:37:08 AM EDT> <Alert> <Socket> <BEA-000414> <Could not initialize POSIX Performance Pack.>
    <May 13, 2009 10:37:08 AM EDT> <Warning> <Socket> <BEA-000444> <Could not load the performance pack that can take advantage of /dev/(e)poll device due to:
         weblogic.utils.NestedError: Could not initialize /dev/poll Performance Pack. Ensure that /dev/poll device exists and is initialized..
    Will attempt to use the performance pack that does not depend on /dev/(e)poll device.>
    <May 13, 2009 10:37:18 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <May 13, 2009 10:37:35 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <May 13, 2009 10:37:35 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <May 13, 2009 10:37:52 AM EDT> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
    <May 13, 2009 10:37:53 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <May 13, 2009 10:37:53 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <May 13, 2009 10:37:54 AM EDT> <Warning> <Server> <BEA-002611> <Hostname "ncsci015", maps to multiple IP addresses: 10.45.8.61, 127.0.0.1>
    <May 13, 2009 10:37:54 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:9001 for protocols iiop, t3, ldap, http.>
    <May 13, 2009 10:37:54 AM EDT> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 10.45.8.61, 127.0.0.1>
    <May 13, 2009 10:37:54 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.45.8.61:9001 for protocols iiop, t3, ldap, http.>
    <May 13, 2009 10:37:54 AM EDT> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "Admin" for domain "Production" running in Production Mode>
    <May 13, 2009 10:37:54 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <May 13, 2009 10:37:54 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <May 13, 2009 10:39:55 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 13, 2009 10:43:47 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
    <May 13, 2009 10:44:08 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Dtcr%2CType%3DAppDeployment%22%29.>
    <May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 13, 2009 10:44:12 AM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 13, 2009 12:34:44 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 13, 2009 12:43:36 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 13, 2009 1:12:29 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 14, 2009 12:27:16 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 14, 2009 12:27:29 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
    <May 14, 2009 12:29:21 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 14, 2009 12:29:30 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
    <May 14, 2009 12:29:44 PM EDT> <Error> <netuix> <BEA-423405> <An exception [Broken pipe (errno:32)] was thrown while rendering the content at [jsp/contentheader/ContentMenu.jsp].
    java.net.SocketException: Broken pipe (errno:32)
         at java.net.SocketOutputStream.socketWrite0(Native Method)
         at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:97)
         at java.net.SocketOutputStream.write(SocketOutputStream.java:141)
         at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:525)
         at weblogic.servlet.internal.ChunkOutput.writeChunks(ChunkOutput.java:504)
         Truncated. see log file for complete stacktrace
    >
    <May 14, 2009 1:47:36 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 14, 2009 1:47:48 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
    <May 14, 2009 1:57:17 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 14, 2009 1:57:27 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3DTCSE%2CType%3DServer%22%29.>
    <May 15, 2009 9:15:48 AM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 15, 2009 12:07:05 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 15, 2009 12:07:14 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WebAppApplicationOverviewPage&WebAppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3Dtcr%2CType%3DAppDeployment%22%29.>
    <May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 15, 2009 12:07:15 PM EDT> <Warning> <J2EE Deployment SPI> <BEA-260128> <Changes not allowed to DTD based descriptors. The attempt to modify property 'ServletName' in WEB-INF/weblogic.xml for module 'tcr.war' will be vetoed if possible. The change will not be persisted in either case.>
    <May 19, 2009 2:29:26 PM EDT> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
    <May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    <May 31, 2009 10:27:32 PM EDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    <May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
    <May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <May 31, 2009 10:27:32 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <May 31, 2009 10:27:32 PM EDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 10.45.8.61:9001 was shutdown.>
    <May 31, 2009 10:27:32 PM EDT> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on 127.0.0.1:9001 was shutdown.>
    The server shutdown with the above output in the log file, can you please let me know why this happened and any solution for it?
    Thanks.

    Have you see that in your posted log:
    <May 13, 2009 10:37:08 AM EDT> <Alert> <Socket> <BEA-000414> <Could not initialize POSIX Performance Pack.>
    <May 13, 2009 10:37:08 AM EDT> <Warning> <Socket> <BEA-000444> <Could not load the performance pack that can take advantage of /dev/(e)poll device due to:
    weblogic.utils.NestedError: Could not initialize /dev/poll Performance Pack. Ensure that /dev/poll device exists and is initialized
    Will attempt to use the performance pack that does not depend on /dev/(e)poll device.>
    it seems to be a trouble with server performance pack. Try to DISABLE performance pack on your server and restart (unckeck "Native IO Enabled" on your domain"). You can also found some suggestions on http://edocs.bea.com/wls/docs92/messages/Socket.html (check for "BEA-000414" message).
    Regards
    Nat.

  • How to recover the database when some of the archive log file get deleted.

    I am facing a problem with Oracle database, which is related to archivelogs.
    Our development database is running in archivelog mode, but we don't have backups scheduled and have no recovery catalog.
    When the database was in running condition, disk got full, so some archivelogs were deleted manually.
    After this they restarted the DB, and now DB is not coming up. Errors are as follows:
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1444383504 bytes
    Fixed Size 731920 bytes
    Variable Size 486539264 bytes
    Database Buffers 956301312 bytes
    Redo Buffers 811008 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    SQL> recover datafile '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 215548705 generated at 09/02/2008 17:06:10 needed for thread
    1
    ORA-00289: suggestion :
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00280: change 215548705 for thread 1 is in sequence #1107
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00308: cannot open archived log
    '/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL>
    1. How to recover the database and bring it online
    Any help will be highly appreciated.
    With Regards
    Hemant Joshi
    Edited by: hem_Kec on Sep 7, 2008 9:07 AM

    Hi,
    Archive log files are the copies of redolog files.As redo log files are circularly overwritten,oracle generates archive log file of the corresponding redo logfiles being overwritten.So if you have a backup that dates back to 10 am in the morning and if your database creashed at 3 pm,you cannot use the redo log files alone as they have incomplete information.To completely recover the database upto 3 pm,you need archive log files generated between 10 am to 3 pm. In your case since you are missing one archive log file,you cannot perform complete recovery and hence would suffer data loss.

  • SCOM 2012 R2 Exchange Correlation Service , we receive almost at every day in the Event log Application the Event720

    HI
    Since the SCOM was Upgrade to R2 
    Almost at every Day, we receive in the Event log application the Event 720 from the correlation service Source MSExchangeMonitoring Correlation
    This arrives always around 7:20AM, someday is at 7:19, other at 7:21. It is always approximately at the same hour, but we never have any problem during weekend
    The description of the Event
    Exceeded maximum time (15 minutes) to wait for completion of all CorrelateBatchTask threads.
    After that the correlation stop to work. At the Same time if we tried to open the SCOM Console on that server we was unable to open it. Also we was not able to open the SCOM PowerShell
    And also we cannot from that server to get which server is the RMS if we run get-SCOMRMSEmulator .  (This the RMS Server)
    When this arrive, the only thing we found, it to reboot the server or restart de SCOM service, after the Reboot the Correlation begin to work
    We got also many Event 714 Critical and after this Event 711 Warning
    Thank

    Have a look at: https://social.technet.microsoft.com/Forums/systemcenter/en-US/e75e84d9-0c9e-4d83-b3da-45a143757f85/exchange-2010-monitoring-with-scom-2012-correlation-service-issue
    One user reported an issue with the exchange correlation engine after upgrade and said that:
    I had issues with the corellation engine after upgrading scom 2012 to R2.
    The MomBidLdr.dll version changed in the SCOM directories, and needs to be updated in the:
    C:\Program Files\Microsoft\Exchange Server\v14\Bin directory.
    That seemed to stop the errors for me.
    Some troubleshooting steps listed here also:
    https://technet.microsoft.com/en-us/library/ff360495(v=exchg.140).aspx
    Cheers,
    Martin
    Blog:
    http://sustaslog.wordpress.com 
    LinkedIn:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • BOXI 4 SP2 Patch 11 - Constant awt.dll crashes in the Event Log

    Hi All,
    Since implementing BOXI 4 SP2 Patch 11 I have noticed very frequent awt.dll crash error messages triggered by SAP JVM throughout the event log.
    Does anyone know what is causing this and how to resolve?
    =================================================================
    Faulting application name: java.exe, version: 6.0.170.4, time stamp: 0x4c3bb897
    Faulting module name: awt.dll, version: 6.0.170.4, time stamp: 0x4c3bfa5f
    Exception code: 0xc0000005
    Fault offset: 0x00000000000d2210
    Faulting process id: 0x1c80
    Faulting application start time: 0x01ccefaba2a15b7a
    Faulting application path: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin\java.exe
    Faulting module path: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\jre\bin\awt.dll
    Report Id: a6ef5e00-5ba2-11e1-a8c2-da6052897efd
    ====================================================================
    Also notice this error immediately afterwards reporting Transaction Deadlocks in our repository and auditing databases on SQL Server :-
    =====================================================================
    Database access error. Reason [Microsoft][SQL Server Native Client 10.0][SQL Server]Transaction (Process ID 63) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction..
    =====================================================================
    SQL Server version is 2008 Release 2.
    Have deployed BOXI 4 using Tomcat 6/Java platform.
    O/S in Windows Server 2008 Release 2.
    This should be a supported configuration so need ideas on why this is happening?
    Cheers,
    Gary

    Hi All,
    SAP Support finally came through for us on this.
    The issue is due to the version of the SAP JVM that comes bundled with BOXI 4 SP2 Patches 11 and 12.
    If you download the latest version of the SAP JVM from the SAP support portal and install this instead then the problems are resolved.
    Thanks,
    Gary

  • Audit/Log GPO changes and Logging of new addition of Domain Controllers in the Event Log

    Hi all, 
    We am trying to log the following items in the event log for Windows 2012. This applies to a domain controller. 
    1) Audit any changes made to the Group Policy
    2) Log the addition of new domain controllers added to the system.
    We need the windows event log to record the above events for security purposes. Can anyone advise if this is doable? If yes what are the steps. 
    Thank you

    Hi,
    >>1) Audit any changes made to the Group Policy
    We can enable audit for directory service object access and configure specific SACL for group policy files to do this.
    Regarding how to step-to-step guide for auditing changes of group policy, the following two blogs can be referred to for more information.
    Monitoring Group Policy Changes with Windows Auditing
    http://blogs.msdn.com/b/ericfitz/archive/2005/08/04/447951.aspx
    Auditing Group Policy changes
    http://blogs.msdn.com/b/canberrapfe/archive/2012/05/02/auditing-group-policy-changes.aspx
    >>2) Log the addition of new domain controllers added to the system.
    Based on my knowledge, when a server is successfully promoted to be domain controller, event ID 29223 will be logged in the System log.
    Regarding this point, the following thread can be referred to for more information.
    Is an Event ID for a completed Domain Controller promotion logged on the PDC?
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/11b18816-7db0-49e2-9a65-3de0e7a9645e/is-an-event-id-for-a-completed-domain-controller-promotion-logged-on-the-pdc?forum=winserverDS
    Best regards,
    Frank Shen

  • Wait Events "log file parallel write" / "log file sync" during CREATE INDEX

    Hello guys,
    at my current project i am performing some performance tests for oracle data guard. The question is "How does a LGWR SYNC transfer influences the system performance?"
    To get some performance values, that i can compare i just built up a normal oracle database in the first step.
    Now i am performing different tests like creating "large" indexes, massive parallel inserts/commits, etc. to get the bench mark.
    My database is an oracle 10.2.0.4 with multiplexed redo log files on AIX.
    I am creating an index on a "normal" table .. i execute "dbms_workload_repository.create_snapshot()" before and after the CREATE INDEX to get an equivalent timeframe for the AWR report.
    After the index is built up (round about 9 GB) i perform an awrrpt.sql to get the AWR report.
    And now take a look at these values from the AWR
                                                                       Avg
                                                 %Time  Total Wait    wait     Waits
    Event                                 Waits  -outs    Time (s)    (ms)      /txn
    log file parallel write              10,019     .0         132      13      33.5
    log file sync                           293     .7           4      15       1.0
    ......How can this be possible?
    Regarding to the documentation
    -> log file sync: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3120
    Wait Time: The wait time includes the writing of the log buffer and the post.-> log file parallel write: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3104
    Wait Time: Time it takes for the I/Os to complete. Even though redo records are written in parallel, the parallel write is not complete until the last I/O is on disk.This was also my understanding .. the "log file sync" wait time should be higher than the "log file parallel write" wait time, because of it includes the I/O and the response time to the user session.
    I could accept it, if the values are close to each other (maybe round about 1 second in total) .. but the different between 132 seconds and 4 seconds is too noticeable.
    Is the behavior of the log file sync/write different when performing a DDL like CREATE INDEX (maybe async .. like you can influence it with the initialization parameter COMMIT_WRITE??)?
    Do you have any idea how these values come about?
    Any thoughts/ideas are welcome.
    Thanks and Regards

    Surachart Opun (HunterX) wrote:
    Thank you for Nice Idea.
    In this case, How can we reduce "log file parallel write" and "log file sync" waited time?
    CREATE INDEX with NOLOGGINGA NOLOGGING can help, can't it?Yes - if you create index nologging then you wouldn't be generating that 10GB of redo log, so the waits would disappear.
    Two points on nologging, though:
    <ul>
    it's "only" an index, so you could always rebuild it in the event of media corruption, but if you had lots of indexes created nologging this might cause an unreasonable delay before the system was usable again - so you should decide on a fallback option, such as taking a new backup of the tablespace as soon as all the nologging operatons had completed.
    If the database, or that tablespace, is in +"force logging"+ mode, the nologging will not work.
    </ul>
    Don't get too alarmed by the waits, though. My guess is that the +"log file sync"+ waits are mostly from other sessions, and since there aren't many of them the other sessions are probably not seeing a performance issue. The +"log file parallel write"+ waits are caused by your create index, but they are happeninng to lgwr in the background which is running concurrently with your session - so your session is not (directly) affected by them, so may not be seeing a performance issue.
    The other sessions are seeing relatively high sync times because their log file syncs have to wait for one of the large writes that you have triggered to complete, and then the logwriter includes their (little) writes with your next (large) write.
    There may be a performance impact, though, from the pure volume of I/O. Apart from the I/O to write the index you have LGWR writting (N copies) of the redo for the index and ARCH is reading and writing the completed log files caused by the index build. So the 9GB of index could easily be responsible for vastly more I/O than the initial 9GB.
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
    "Science is more than a body of knowledge; it is a way of thinking"
    Carl Sagan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Cannot shrink log file 2 because the logical log file located at the end of the file is in use ?

    HI,
    I am getting this error frequently.. any recomendations :
    Executed as user: DB0\sqlservices. Processing database: dbin [SQLSTATE 01000] (Message 0) 
    Cannot shrink log file 2 (DB_log) because the logical log file located at the end of the file is in use. [SQLSTATE 01000] (Message 9008) 
    Processing database: DB_ [SQLSTATE 01000] (Message 0)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528) 
    Cannot shrink log file 2 (DB_log) because the logical log file located at the end of the file is in use. [SQLSTATE 01000] (Message 9008) 
    Processing database: DB [SQLSTATE 01000] (Message 0) 
    DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528) 
    Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed. [SQLSTATE 42000] (Error 3023) 
    Processing database: DB_AC [SQLSTATE 01000] (Error 0)  
    [SQLSTATE 01000] (Error 0)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Error 2528). 
    The step failed.
    Please give any receomendations to avoid this error in future :
    Yangamuni Prasad M

     
    Hi Yangamuni,
    Are there any progress?
    Please have a look on the below threads with the similar issues as yours:
    http://www.sqlservercentral.com/Forums/Topic652579-146-1.aspx
    http://social.msdn.microsoft.com/forums/en-US/sqldatabaseengine/thread/ae4db890-c15e-44de-a2af-e85c04260331
    The solution is change the recovery mode to SIMPLE, shrink log files and then change to the FULL recovery mode.
    Thanks,
    Weilin Qiao
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

  • Bottleneck when switching the redo log files.

    Hello All,
    I am using Oracle 11.2.0.3.
    The application team reported that they are facing slowness at certain time.
    I monitored the database and I found that at some switching of the redo log files (not always) I am facing a slowness at the application level.
    I have 2 threads since my database is RAC, each thread have 3 redo log groups multiplexed to the FRA, with size 300 MB each.
    Is there any way to optimize the switch of redo log files? knowing that my database is running in ARCHIVELOG mode.
    Regards,

    Hello Nikolay,
    Thanks for your input I am sharing with you the below information. I have 2 instances so I will provide the info from each instance
    Instance 1:
    Load Profile              Per Second    Per Transaction   Per Exec   Per Call
    ~~~~~~~~~~~~         ---------------    --------------- ---------- ----------
          DB Time(s):                4.9                0.0       0.00       0.00
           DB CPU(s):                1.1                0.0       0.00       0.00
           Redo size:        3,014,876.2            3,660.4
       Logical reads:           32,619.3               39.6
       Block changes:            7,969.0                9.7
      Physical reads:                0.2                0.0
    Physical writes:              164.0                0.2
          User calls:            7,955.4                9.7
              Parses:              288.9                0.4
         Hard parses:               96.0                0.1
    W/A MB processed:                0.2                0.0
              Logons:                0.9                0.0
            Executes:            2,909.4                3.5
           Rollbacks:                0.0                0.0            
    Instance 2:
    Load Profile              Per Second    Per Transaction   Per Exec   Per Call
    ~~~~~~~~~~~~         ---------------    --------------- ---------- ----------
          DB Time(s):                5.5                0.0       0.00       0.00
           DB CPU(s):                1.4                0.0       0.00       0.00
           Redo size:        3,527,737.9            3,705.7
       Logical reads:           29,916.5               31.4
       Block changes:            8,893.7                9.3
      Physical reads:                0.2                0.0
    Physical writes:              194.0                0.2
          User calls:            7,742.8                8.1
              Parses:              262.7                0.3
         Hard parses:               99.5                0.1
    W/A MB processed:                0.4                0.0
              Logons:                1.0                0.0
            Executes:            2,822.5                3.0
           Rollbacks:                0.0                0.0
        Transactions:              952.0
    Instance 1:
    Top 5 Timed Foreground Events
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                               Avg
                                                              wait   % DB
    Event                                 Waits     Time(s)   (ms)   time Wait Class
    DB CPU                                            1,043          21.5
    log file sync                       815,334         915      1   18.9 Commit
    gc buffer busy acquire              323,759         600      2   12.4 Cluster
    gc current block busy               215,132         585      3   12.1 Cluster
    enq: TX - row lock contention        23,284         264     11    5.5 Applicatio
    Instance 2:
    Top 5 Timed Foreground Events
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                               Avg
                                                              wait   % DB
    Event                                 Waits     Time(s)   (ms)   time Wait Class
    DB CPU                                            1,340          24.9
    log file sync                       942,962       1,125      1   20.9 Commit
    gc buffer busy acquire              377,812         594      2   11.0 Cluster
    gc current block busy               211,270         488      2    9.1 Cluster
    enq: TX - row lock contention        30,094         299     10    5.5 Applicatio
    Instance 1:
    Operating System Statistics        Snaps: 1016-1017
    -> *TIME statistic values are diffed.
       All others display actual values.  End Value is displayed if different
    -> ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
    Statistic                                  Value        End Value
    AVG_BUSY_TIME                             17,451
    AVG_IDLE_TIME                             81,268
    AVG_IOWAIT_TIME                                1
    AVG_SYS_TIME                               6,854
    AVG_USER_TIME                             10,548
    BUSY_TIME                                420,031
    IDLE_TIME                              1,951,741
    IOWAIT_TIME                                  288
    SYS_TIME                                 165,709
    USER_TIME                                254,322
    LOAD                                           3                6
    OS_CPU_WAIT_TIME                         523,000
    RSRC_MGR_CPU_WAIT_TIME                         0
    VM_IN_BYTES                              311,280
    VM_OUT_BYTES                          75,862,008
    PHYSICAL_MEMORY_BYTES             62,813,896,704
    NUM_CPUS                                      24
    NUM_CPU_CORES                                  6
    NUM_LCPUS                                     24
    NUM_VCPUS                                      6
    GLOBAL_RECEIVE_SIZE_MAX                4,194,304
    GLOBAL_SEND_SIZE_MAX                   4,194,304
    TCP_RECEIVE_SIZE_DEFAULT                  16,384
    TCP_RECEIVE_SIZE_MAX      9.2233720368547758E+18
    TCP_RECEIVE_SIZE_MIN                       4,096
    TCP_SEND_SIZE_DEFAULT                     16,384
    TCP_SEND_SIZE_MAX         9.2233720368547758E+18
    TCP_SEND_SIZE_MIN                          4,096
    Operating System Statistics - Detail  Snaps: 1016-101
    Snap Time           Load    %busy    %user     %sys    %idle  %iowait
    22-Aug 11:33:55      2.7      N/A      N/A      N/A      N/A      N/A
    22-Aug 11:50:23      6.2     17.7     10.7      7.0     82.3      0.0
    Instance 2:
    Operating System Statistics         Snaps: 1016-1017
    -> *TIME statistic values are diffed.
       All others display actual values.  End Value is displayed if different
    -> ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
    Statistic                                  Value        End Value
    AVG_BUSY_TIME                             11,823
    AVG_IDLE_TIME                             86,923
    AVG_IOWAIT_TIME                                0
    AVG_SYS_TIME                               4,791
    AVG_USER_TIME                              6,991
    BUSY_TIME                                475,210
    IDLE_TIME                              3,479,382
    IOWAIT_TIME                                  410
    SYS_TIME                                 193,602
    USER_TIME                                281,608
    LOAD                                           3                6
    OS_CPU_WAIT_TIME                         615,400
    RSRC_MGR_CPU_WAIT_TIME                         0
    VM_IN_BYTES                               16,360
    VM_OUT_BYTES                          72,699,920
    PHYSICAL_MEMORY_BYTES             62,813,896,704
    NUM_CPUS                                      40
    NUM_CPU_CORES                                 10
    NUM_LCPUS                                     40
    NUM_VCPUS                                     10
    GLOBAL_RECEIVE_SIZE_MAX                4,194,304
    GLOBAL_SEND_SIZE_MAX                   4,194,304
    TCP_RECEIVE_SIZE_DEFAULT                  16,384
    TCP_RECEIVE_SIZE_MAX      9.2233720368547758E+18
    TCP_RECEIVE_SIZE_MIN                       4,096
    TCP_SEND_SIZE_DEFAULT                     16,384
    TCP_SEND_SIZE_MAX         9.2233720368547758E+18
    TCP_SEND_SIZE_MIN                          4,096
    Operating System Statistics - Detail Snaps: 1016-101
    Snap Time           Load    %busy    %user     %sys    %idle  %iowait
    22-Aug 11:33:55      2.6      N/A      N/A      N/A      N/A      N/A
    22-Aug 11:50:23      5.6     12.0      7.1      4.9     88.0      0.0
              -------------------------------------------------------------

Maybe you are looking for