Archive The Log When Full Disabled

Currently I'm having problem in setting up auto archive log for "Applications and Services Logs > Microsoft > Windows > Application Server - Applications > Debug", because the option is disabled (I've disabled the log to setup the properties).
Please take a look screenshot below:
How to choose "Archive the log when full, do not overwrite events"? Thanks in advance.

Hi ,
"How to choose "Archive the log when full, do not overwrite events"?"
Generally , you need to enable logging then you can choose the action after the log size is reached .
 If this machine is domain joined , you can edit the domain policy on DC :
computer configuration \windows settings \security settings \event log
The Retention method for event log policy settings determine the wrapping method for the application, security, and system logs .
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
I've tried to enable the log and make the maximum size reached, but I still can't choose automatically archive log:
and also take a look a screenshot below, it is a different type of event (Operational) and it shows us that I can choose Archive the log when full without activating it and make it reach its maximum log size:
How to solve this issue? Thanks in advance.

Similar Messages

  • Batch file to archive the logs

    I have log file under below directory (actually multiple directories with different names under E:\TIBCO\)
    E:\TIBCO\*\6.0.0\LogFiles with Spotfire.Dxp.Automation.*.*
    I need to get perform below steps with the batch script
    1. move (copy & delete) all the files that are with Spotfire.Dxp.*.*.* (ex Spotfire.Dxp.*.1.*)  from the above paths to E:\TIBCO\logsArchival\rotatedDir 
    2. zip all the files that are older than 60 from E:\TIBCO\logsArchival\rotatedDir to E:\TIBCO\logsArchival\ArchiveDir
    3. delete the zip files that are older than 120 days from E:\TIBCO\logsArchival\ArchiveDir
    all the above steps need to be written to the logs.
    Thanks,
    Nikku

    Sorry, we do not write scripts on demand. However, if you post the script you have written so far then we'll gladly help you with the finer details.

  • Why don't I see the log when I repair permissions with Disk Utility

    I'm having issues with Safari hanging or bogging down to a snail's pace lately. I have tried several times to repair permissions with Disk Utility. It runs for several minutes, but shows nothing in the log even though the box is checked to show details. I've never seen this before. I don't know if Disk Utility is doing it's job or not....
    Any thoughts?

    If the progress bar goes to the end, then you don't have any permissions needing repair. The fact that Safari is slowing down has nothing really to do with permissions.

  • SAPDB : Archive the Log and Data files

    Hi,
    I am running a SAP WAS JAVA on my laptop with SAPDB as the database. Its used for my local developments.
    I have 3 log files and 3 data files of 1 GB each. I want to reduce this to 1 log file and 1 data file to free some space on my Laptop.
    How can this be done.
    Regards,
    Shubham

    Hi,
    well, you should check the <b>current filling level</b> of your database instance to see how large your single data volume should become.
    Then, I would recommend you put your db in <b>admin</b> state and make a full data <b>backup</b>.
    Then, you would need to do do a <b>recovery with initialization</b>. This is most conveniently done using the newest available version of the Database Manager GUI.
    During this process, you should be able to specify your desired new volume setup (please keep the filling level from your the beginning in mind). For the backup to recover, choose the one you just made.
    Hope that helps.
    Kind regards,
    Roland

  • Content database transaction log is full

    Hi guys,
    i am facing some very serious issues right here, SharePoint content can't be updated because the transaction log drive for the logs is full. the following message is displayed in the event viewer
    'The transaction for database wss_content_guid is full. To find out why space can't be reused see the log_reuse_wait_desc column in sys.databases'
    Pls help

    Hi,
    The recommended way to truncate the transaction log if you are using a full recovery model is to back up the log. SQL Server 2005 automatically truncates the inactive parts of the transaction log when you back up the log. It is also recommended that you pre-grow the transaction log to avoid auto-growing the log. For more information about growing the transaction log, see Managing the Size of the Transaction Log File (http://go.microsoft.com/fwlink/?LinkId=124882). For more information about using a full recovery model, see Backup Under the Full Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127985). For more information about using a simple recovery model, see Backup Under the Simple Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127987).
    We do not recommend that you manually shrink the transaction log size or manually truncate the log by using the Truncate method.
    Transaction logs are also automatically backed up when you back up the farm, Web application, or databases by using either the SharePoint Central Administration Web site or the Stsadm command-line tool. For more information about the Stsadm command-line tool, see Backup: Stsadm operation (Windows SharePoint Services).
    So I would suggest you backing up SharePoint by either the SharePoint Central Administration Web site or the Stsadm command-line tool.
    For more information about Best Practice on Backups, please refer to the following articles:
    Best Practice on Backups
    http://blogs.msdn.com/joelo/archive/2007/07/09/best-practice-on-backups.aspx
    Back up logs (Windows SharePoint Services 3.0)
    http://technet.microsoft.com/en-us/library/cc811601.aspx
    Hope this helps.
    Rock Wang
    Rock Wang– MSFT

  • SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends

    Hi
    Configmgr 2007 sp2
    Client versions : 4.00.6487.2000
    On many of our servers (2003 SP2, 2008 R2 SP1) the SCCM agent writes endless lines to servicewindosmanager.log when maintenance window start or ends. The log gets full in
    less then a second then another log opens and so on!
    Here is an example of a small part of the log file:
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
    ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
    ServiceWindowManager 17/10/2013 05:59:59 7152 (0x1BF0)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
    ServiceWindowManager 17/10/2013 05:59:59 524 (0x020C)
        Scheduling the Timer Task ServiceWindowManager 17/10/2013 05:59:59 6988 (0x1B4C)
        Scheduled the timer to fire on 10/17/2013 5:00:00 AM ServiceWindowManager 17/10/2013 06:00:00 6988 (0x1B4C)
    Thanks for any help!
    Daniel

    Yes, I know this is an old post, but I’m trying to clean them up.
    This is not normal, I would check the health of the server and I would also use WMIdiag to see if WMI is healthy.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Adding time stamp while archiving the file in b2b

    Hi
    I want to add the time stamp when archiving the file when I am using file/ftp channel. can anybody tell me how can I do that. otherwise it is overwriting the exising file in archive directory.
    Thanks
    Sri

    Hi Sri,
    otherwise it is overwriting the exising file in archive directory.It might be happening because inbound files are not having unique name. You have two options -
    1. Make sure that inbound files have unique name (you may add timestamp in inbound filename format)
    2. Do not use the archive feature of Oracle B2B. Instead use a transport callout to write a copy of incoming document into desired directory with desired filename. To know more about callout offering of Oracle B2B, please refer -
    http://docs.oracle.com/cd/E28280_01/user.1111/e10229/callouts.htm#CHDEFBDG
    Regards,
    Anuj

  • Scroll lock on the log window...

    Can the Jdev team make it so when the log window is not at the bottom it should not reset the scroll. So something like this...
    if(scroll.y != scroll.height) { /*KEEP SCROLL POSITION!*/ }
    I print a lot of debug code I guess in the log when testing my webapps, and I'll scroll up to review some debug. But there are some ajax updaters I have built into the web interface that pings back to the server causing more debug code to generate... and then jdev resets the scroll from where I'm at to the bottom.

    Besides the dynamic log output, you can read the previously saved log contents when you open the text log file shown at the jdev log output.
    The path to the log file is printed when the weblogic server starts:
    <17 Νοε 2010 10:23:33 μμ EET> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Nick\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <17 Νοε 2010 10:23:33 μμ EET> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Nick\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00030. Log messages will continue to be logged in C:\Users\Nick\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
    You could also choose to save the log output to a file you define, by clicking on preferences>environment>log to select save logs to a file and define the path as you wish.
    NA
    http://nickaiva.blogspot.com

  • Archive Log vs Full Backup Concept

    Hi,
    I just need some clarification on how backups and archive logs work. Lets say starting at 1PM I have archive logs 1,2,3,4,5 and then I perform a full backup at 6PM.
    Then I resume generating archive logs at 6PM to get logs 6,7,8,9,10. I then stop at 11PM.
    If my understanding is correct, the archive logs should allow me to restore oracle to a point in time anywhere between 1PM and 11PM. But if I only have the full backup then I can only restore to a single point, which is 6PM. Is my understanding correct?
    Do the archive logs only get applied to the datafiles when the backup occurs or only when a restore occurs? It doesn't seem like the archive logs get applied on the fly.
    Thanks in advance.

    thelok wrote:
    Thanks for the great explanation! So I can do a point in time restore from any time since the datafiles have last been written (or from when I have the last set of backed up datafiles plus the archive logs). From what you are saying, I can force the datafiles to be written from the redo logs (by doing a checkpoint with "alter set archive log current" or "backup database plus archivelog"), and then I can delete all the archive logs that have a SCN less than the checkpoint SCN on the datafiles. Is this true? This would be for the purposes of preserving disk space.Hi,
    See this example. I hope this explain your doubt.
    # My current date is 06-11-2011 17:15
    # I not have backup of this database
    # My retention policy is to have 1 backup
    # I start listing  archive logs.
    RMAN> list archivelog all;
    using target database control file instead of recovery catalog
    List of Archived Log Copies
    Key     Thrd Seq     S Low Time            Name
    29      1    8       A 29-10-2011 12:01:58 +HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837
    30      1    9       A 31-10-2011 23:00:30 +HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025
    31      1    10      A 03-11-2011 23:00:23 +HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105
    32      1    11      A 04-11-2011 23:28:23 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065
    33      1    12      A 05-11-2011 23:28:49 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349
    ## See I have archive logs from time "29-10-2011 12:01:58" until "05-11-2011 23:28:49" but I dont have any backup of database.
    # So I perfom backup of database including archive logs.
    RMAN> backup database plus archivelog delete input;
    Starting backup at 06-11-2011 17:15:21
    ## Note above RMAN forcing archive current log, this archivelog generated will be usable only for previous backup.
    ## Is not my case... I don't have backup of database.
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=159 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8 recid=29 stamp=766018840
    input archive log thread=1 sequence=9 recid=30 stamp=766278027
    input archive log thread=1 sequence=10 recid=31 stamp=766366111
    input archive log thread=1 sequence=11 recid=32 stamp=766516067
    input archive log thread=1 sequence=12 recid=33 stamp=766516350
    input archive log thread=1 sequence=13 recid=34 stamp=766516521
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:23
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:15:38
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 tag=TAG20111106T171521 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837 recid=29 stamp=766018840
    archive log filename=+HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025 recid=30 stamp=766278027
    archive log filename=+HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105 recid=31 stamp=766366111
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065 recid=32 stamp=766516067
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349 recid=33 stamp=766516350
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_13.414.766516521 recid=34 stamp=766516521
    Finished backup at 06-11-2011 17:15:38
    ## RMAN finish backup of Archivelog and Start Backup of Database
    ## My backup start at "06-11-2011 17:15:38"
    Starting backup at 06-11-2011 17:15:38
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=+HR/dbhr/datafile/system.386.765556627
    input datafile fno=00003 name=+HR/dbhr/datafile/sysaux.396.765556627
    input datafile fno=00002 name=+HR/dbhr/datafile/undotbs1.393.765556627
    input datafile fno=00004 name=+HR/dbhr/datafile/users.397.765557979
    input datafile fno=00005 name=+BFILES/dbhr/datafile/bfiles.257.765542997
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:39
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:03
    piece handle=+FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539 tag=TAG20111106T171539 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:24
    Finished backup at 06-11-2011 17:16:03
    ## And finish at "06-11-2011 17:16:03", so I can recovery my database from this time.
    ## I will need archivelogs (transactions) which was generated during backup of database.
    ## Note during backup some blocks are copied others not. The SCN is inconsistent state.
    ## To make it consistent I need apply archivelog which have all transactions recorded.
    ## Starting another backup of archived log generated during backup.
    Starting backup at 06-11-2011 17:16:04
    ## So automatically RMAN force another "checkpoint" after backup finished,
    ## forcing archive current log, because this archivelog have all transactions to bring database in a consistent state.
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=35 stamp=766516564
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:16:05
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:06
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565 tag=TAG20111106T171604 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_14.414.766516565 recid=35 stamp=766516564
    Finished backup at 06-11-2011 17:16:06
    ## Note: I can recover my database from time "06-11-2011 17:16:03" (finished backup full)
    ##  until "06-11-2011 17:16:04" (last archivelog generated) that is my recover window in this scenary.
    ## Listing Backup I have:
    ## Archive Logs in backupset before backup full start - *BP Key: 40*
    ## Backup Full database in backupset - *BP Key: 41*
    ##  Archive Logs in backupset after backup full stop - *BP Key: 42*
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    40      196.73M    DISK        00:00:15     06-11-2011 17:15:37
            *BP Key: 40*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171521
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
      List of Archived Logs in backup set 40
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    8       766216     29-10-2011 12:01:58 855033     31-10-2011 23:00:30
      1    9       855033     31-10-2011 23:00:30 896458     03-11-2011 23:00:23
      1    10      896458     03-11-2011 23:00:23 937172     04-11-2011 23:28:23
      1    11      937172     04-11-2011 23:28:23 976938     05-11-2011 23:28:49
      1    12      976938     05-11-2011 23:28:49 1023057    06-11-2011 17:12:28
      1    13      1023057    06-11-2011 17:12:28 1023411    06-11-2011 17:15:21
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    41      Full    565.66M    DISK        00:00:18     06-11-2011 17:15:57
            *BP Key: 41*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171539
            Piece Name: +FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539
      List of Datafiles in backup set 41
      File LV Type Ckp SCN    Ckp Time            Name
      1       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/system.386.765556627
      2       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/undotbs1.393.765556627
      3       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/sysaux.396.765556627
      4       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/users.397.765557979
      5       Full 1023422    06-11-2011 17:15:39 +BFILES/dbhr/datafile/bfiles.257.765542997
    BS Key  Size       Device Type Elapsed Time Completion Time
    42      3.00K      DISK        00:00:02     06-11-2011 17:16:06
            *BP Key: 42*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171604
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565
      List of Archived Logs in backup set 42
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    14      1023411    06-11-2011 17:15:21 1023433    06-11-2011 17:16:04
    ## Here make sense what I trying explain
    ## As I don't have backup of database before of my Last backup, all archivelogs generated before of my backup full is useless.
    ## Deleting what are obsolete in my env, RMAN choose backupset 40 (i.e all archived logs generated before my backup full)
    RMAN> delete obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    *Backup Set           40*     06-11-2011 17:15:37
      Backup Piece       40     06-11-2011 17:15:37 +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted backup piece
    backup piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 recid=40 stamp=766516523
    Deleted 1 objectsIn the above example, I could before starting the backup run "delete archivelog all" because they would not be needed, but to show the example I follow this unnecessary way. (backup archivelog and delete after)
    Regards,
    Levi Pereira
    Edited by: Levi Pereira on Nov 7, 2011 1:02 AM

  • I have a new Macbook Pro.  When watching Youtube videos, it works perfectly until I attempt to watch the video in full screen.  When in full screen, the video freezes immediately and the audio continues.  When minimized it works fine as before. Help?

    I have a brand new Macbook model A1502.  I am taking online college classes that incorporate youtube tutorial videos.  I can watch the videos if I don't maximize the screen to full screen.  When in full screen, the video freezes immediately and the audio continues uninterrupted.  I can press escape and go back to the previous screen and the video continues to play with no problems.  Can anyone help me please?  This machine is literally just out of the box with maybe an hour of use.  Thanks in advance

    First, back up all data immediately, as your boot drive might be failing.
    There are a few other possible causes of generalized slow performance that you can rule out easily.
    Reset the System Management Controller.
    If you have many image or video files on the Desktop with preview icons, move them to another folder.
    If applicable, uncheck all boxes in the iCloud preference pane.
    Disconnect all non-essential wired peripherals and remove aftermarket expansion cards, if any.
    Check your keychains in Keychain Access for excessively duplicated items.
    If you have more than one user account, you must be logged in as an administrator to carry out this step.
    Launch the Console application in the same way you launched Activity Monitor. Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Select the 50 or so most recent entries in the log. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). You're looking for entries at the end of the log, not at the beginning.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some personal information, such as your name, may appear in the log. Anonymize before posting. That should be easy to do if your extract is not too long.

  • Problem while archiving the redo Log

    Hi all,
    I m having few issues in my server...
    I get the following error in the alert log of oracle..
    There are many errors
    1) No space left on device
    2) ARC0: I/O error 19502 archiving log 1 to
    '/oracle/admin/SNM/arch/arch_1_393_668727286.arc'
    ARCH: Archival stopped, error occurred. Will continue retrying
    3) ORA-16014: log 1 sequence# 393 not archive*d, no available destinations*
    Also please find the v$log file query
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
    1 1 405 1073741824 1 NO CURRENT
    60275455 20-OCT-09
    2 1 403 1073741824 1 NO INACTIVE
    59987366 19-OCT-09
    3 1 404 1073741824 1 NO INACTIVE
    60125083 20-OCT-09
    Also the diskspace is almost 97%.
    Can anyone let me know whether archival of redo log files is causing the issue here?
    If so if i stop the archival of logs ,will it solve the problem?
    Can anyone help me on this?
    Mon Oct 19 09:54:39 2009
    Errors in file /oracle/admin/SNM/bdump/snm_arc0_23831.trc:
    ORA-19502: write error on file
    "/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno
    577537 (blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    SVR4 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    ORA-19502: write error on file
    "/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno
    559105 (blocksize=512)
    Mon Oct 19 09:54:39 2009
    Errors in file /oracle/admin/SNM/bdump/snm_arc0_23831.trc:
    ORA-19502: write error on file
    "/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno
    577537 (blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    SVR4 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    ORA-19502: write error on file
    *"/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno*
    *559105 (blocksize=512)*
    ARC0: I/O error 19502 archiving log 1 to
    '/oracle/admin/SNM/arch/arch_1_393_668727286.arc'
    ARCH: Archival stopped, error occurred. Will continue retrying
    Mon Oct 19 09:54:40 2009
    ORACLE Instance SNM - Archival Error
    Mon Oct 19 09:54:40 2009
    ORA-16038: log 1 sequence# 393 cannot be archived
    ORA-19502: write error on file "", blockno (blocksize=)
    ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
    Mon Oct 19 09:54:40 2009
    Errors in file /oracle/admin/SNM/bdump/snm_arc0_23831.trc:
    ORA-16038: log 1 sequence# 393 cannot be archived
    ORA-19502: write error on file "", blockno (blocksize=)
    ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
    Mon Oct 19 09:54:40 2009
    ARCH: Archival stopped, error occurred. Will continue retrying
    Mon Oct 19 09:54:40 2009
    ORACLE Instance SNM - Archival Error
    Mon Oct 19 09:54:40 2009
    ORA-16014: log 1 sequence# 393 not archived, no available destinations
    ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
    Mon Oct 19 09:54:40 2009
    Errors in file /oracle/admin/SNM/bdump/snm_arc1_23833.trc:
    ORA-16014: log 1 sequence# 393 not archive*d, no available destinations*
    ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
    Mon Oct 19 10:00:16 2009
    ARC0: Encountered disk I/O error 19502
    Mon Oct 19 10:00:16 2009
    ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1:
    '/oracle/admin/SNM/arch/arch_1_393_668727286.arc' (error
    19502)
    (SNM)

    yes it is the production server.
    Also the arch folder contains 2 GB file - arc file....
    Does disable of archival will solve the issue?
    I am try to clear the space or move to some other location..But the thing is my application files is of 3 to 4 GB.remaining thing is of dbf files.
    6564 drwxr-x--- 2 oracle oinstall 512 Oct 21 2008 .
    6563 drwxr-x--- 3 oracle oinstall 512 Oct 21 2008 ..
    6568 -rw-r----- 1 oracle oinstall 7061504 Sep 30 11:58 control01.ctl
    6569 -rw-r----- 1 oracle oinstall 7061504 Sep 30 11:58 control02.ctl
    6570 -rw-r----- 1 oracle oinstall 7061504 Sep 30 11:58 control03.ctl
    9283 -rw-r----- 1 oracle oinstall 5128192 Sep 30 10:21 mfxpima.dbf
    6600 -rw-r----- 1 oracle oinstall 17179877376 Sep 30 11:50 muse0.dbf
    6572 -rw-r----- 1 oracle oinstall 1073742336 Sep 30 08:10 redo01.log
    6573 -rw-r----- 1 oracle oinstall 1073742336 Sep 30 10:16 redo02.log
    6574 -rw-r----- 1 oracle oinstall 1073742336 Sep 30 11:58 redo03.log
    6578 -rw-r----- 1 oracle oinstall 19293806592 Sep 30 11:58 sysaux01.dbf
    6576 -rw-r----- 1 oracle oinstall 1698701312 Sep 30 11:56 system01.dbf
    6579 -rw-r----- 1 oracle oinstall 2147491840 Sep 30 11:04 temp01.dbf
    6577 -rw-r----- 1 oracle oinstall 4084211712 Sep 30 11:58 undotbs01.dbf
    6580 -rw-r----- 1 oracle oinstall 5251072 Sep 30 10:21 users01.dbf
    What as to be done....in this case....
    Help me out...
    I have no other option ....
    SRinivasan

  • The file structure online redo log, archived redo log and standby redo log

    I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
    1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
    2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
    3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

    FZheng:
    Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
    But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
    My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
    This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
    Edited by: 853153 on Jun 22, 2011 9:42 AM

  • The checkbox: "When iChat opens, automatically log in" is not present anymore, how do I get it back??

    First pic shows the button as I'm used to, second pic shows it missing.... running 10.7.2 and iChat 6.0.1

    Hi,
    In looking this up I have looked at the com.apple.ichat.AIM.plist on a computer running Snow Leopard (iChat 5.x.x) and also on a computer using Messages 6.1  (it seems Messages Beta still uses the same .plist to store info about the AIM Accounts)
    All have a Line about Auto Login set to 1 even though in Messages the option to set it is not there.
    As you have found out this setting also depends on whether or not the account is Logged in on Quit.
    (In Snow Leopard/iChat 5 I could not get the "1" to even if I set the account to Not Login Automatically)
    I see the same Auto Login setting of 1 in my com.apple.ichat.Jabber.plist as well (Seeing you are talking about a Jabber Login)
    There is obviously more to this than I have found so far.
    It seems if an Account is Enabled then the setting kicks in but it stays set at one even if the account is Not Enabled.
    This was the closest that I have found elsewhere
    http://hints.macworld.com/article.php?story=20080826165311174
    I say closest as I don't fully understand what they were setting up and where to edit it.
    (I think several of the posts refer to what is being done in a short form rather than in Full which is not helping understanding - I did follow some of the links (in the original post and the reference to an Archived thread) in the thread.)
    9:23 PM      Sunday; March 4, 2012
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • Set up Signal Express to log when there is a change in state of the inputs (NI USB-6501 logger)

    Hello NI Forum, I have recently purchased digital I/O logger NI USB-6501.  This arrived with Signal Express, which I intend to use as a Lite version.  I just wondered if it was possible to set up Signal Express to only add a log entry when there is a change in state of the inputs?  I have this working on a 0.1sec sample period and can interrogate the logs after recording.  Most of the time nothing will be happenning, I just wondered if there was a way to reduce the ammount of data captured?  Cheers.

    Ah that unfortunate, and yes start/stop conditions for loging are part of the Full version of SignalExpress
    Here's the comparision: http://www.ni.com/labview/signalexpress/purchasing-options.htm
    Sorry about that

  • When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode

    Question :
    When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode ?
    Example:
    Create Tablespace
    CREATE SMALLFILE TABLESPACE "TEST_DATA"
    LOGGING
    DATAFILE '+DG_TEST_DATA_01(DATAFILE)' SIZE 10G
    AUTOEXTEND ON NEXT  500K MAXSIZE 31000M
    EXTENT MANAGEMENT LOCAL
    SEGMENT SPACE MANAGEMENT AUTO;
    LOGGING: Generate redo logs for creation of tables, indexes and  partitions, and for subsequent inserts. Recoverable
    Are they not logged and not recoverable if we do not enable LOGGING? What is that ARCHIVELOG mode does?

    What is that ARCHIVELOG Mode Does?
    Whenever your database is in archive log mode , Oracle will backup the redo log files in the form of Archives so that we can recover the database to the consistent state in case of any failure.
    Archive logging is essential for production databases where the loss of a transaction might be fatal.
    Why Logging?
    Logging is safest method to ensure that all the changes made at the tablespace will be captured and available for recovery in the redo logs.
    It is just the level at which we defines:
    Force Logging at DB level
    Logging at Tablespace Level
    Logging at schema Level
    Before the existence of FORCE LOGGING, Oracle provided logging and nologging options. These two options have higher precedence at the schema object level than the tablespace level; therefore, it was possible to override the logging settings at the tablespace level with nologging setting at schema object level.

Maybe you are looking for