Transaction Logs - Retention Period

Hi,
Which parameter/bg job is responsible for maintaining the transaction log for <n> number of days?
Regards,
Cs

Hi Cs,
The data is you get from STAD is stored at the OS level file (location given by the parameter stat/file). This parameter points by default to the instance-specific /Data-directory (for example: \usr\sap\<SID>\DVEBMGS00\data) however this can be changed depending on your choice.
For each hour a new stat file is written.
The parameter stat/maxfiles determines how many stat files will be written until the oldest is overwritten.
So depending on your requirement and available disk space size, you can increase these parameters.
Note - these parameters are instance specific. you have to maintain for each instance you may have.
Regards,
Debasis.

Similar Messages

  • Archive purchase document  log -  Retention period not maintained

    Hello Everybody,
       I have been trying to archive the Purchase document, I have also set the Retention period is 0 (Zero), but  when i archive the some Purchase document, it is give log like that
    Object                                                     Message
    4700000053 00010                                           Retention period not maintained
    4700000066 00010                                           Retention period not maintained
    4700000079 00010                                           Retention period not maintained
    So please suggest me how to solve the problem
    Thanks

    Solved, by archiving

  • How to adjust SM21 logs retention Period

    Hi,
    My requirement it to get the system logs for minimum for 5 months,
    i have set the parameter "rslg/max_diskspace/central"
    but still i am getting the logs for 13 days only.
    So please let me know the exact clean up job name for SM21 log,
    so that i can adjust the retention period.
    and also do i need to adjust the parameter "rslg/max_diskspace/local" too to get the required SM21 logs?
    Regards,

    hi,
    For the list of standard jobs please refer this sap note
    16083    Standard jobs, reorganization jobs
    1411877 New standard jobs
    For the system log details please refer this points
    1. The local system log file
    a) File names
    The local system log file that is written to each application server is determined by the profile parameter  rslg/local/file.
    The name of the file is usually SLOG<inr>, where <inr> is the instance number. Therefore, the name is SLOG77, for example.
    In most systems, the profile parameter rslg/local/old_file  is also set and points to a file SLOGO<inr>. This 'old' local system log file is not created by default. Instead, the current local system log file is written 'in a circle'.
    b) File size
    'Writing in a circle' means the following: If the file has reached the maximum size (profile parameter rslg/max_diskspace/local), the system overwrites the oldest entry with the latest entry and so on. The local system log file always has the same file size as of this moment. The profile parameter rslg/max_diskspace/local describes the maximum file size in bytes. If you switch from non-Unicode to Unicode, you must double the value of this profile parameter.
    The central system log file
    a) File names
    The profile parameter rslg/central/file describes the name of the current central system log file, and the profile parameter
    rslg/central/old_file describes the name of the 'old' central system log file.
    b) Size of files
    The profile parameter  rslg/max_diskspace/central specifies a size in  bytes. If the current system log file has reached half of this size, it  is copied to rslg/central/old_file, and a new current central system log file is started.
    Additionally refer this note
    862  Reduce size of system log file
    Regards,
    Naveen.
    Edited by: Naveen Kumar on Mar 5, 2012 2:18 PM

  • Increase retention period of  Audit logs.

    Friends,
    We have the requirement from the Auditors to increase the retention period of logs from
    3 months to 6 months.
    Can someone please guide me on this one? Thanks and let me know.
    Do I need to change any parameter in SAP to increase the size of Audit file @ OS level?
    Any help or suggestions is helpful.
    Regards,
    Pranav

    Lets return to the original question...
    >
    Pranav Thaker wrote:
    > We have the requirement from the Auditors to increase the retention period of logs from
    > 3 months to 6 months.
    >
    > Can someone please guide me on this one? Thanks and let me know.
    > Do I need to change any parameter in SAP to increase the size of Audit file @ OS level?
    >
    > Any help or suggestions is helpful.
    >
    The management of daily files seems not to be the problem here, although it is relevant for the number of files created and their size... for storing them on external media for safekeeping (incase some auditor wants to read the file as well, or you do to reconstruct an event).
    The possibility exists to delete the audit log files after 3 days. At the application layer, this is blocked for the 1st three days (as a security measure).
    Most likely you only need to speak to your basis folks to ensure that there is enough space on the file system for the logs, and reschedule the job which is deleting the files to do so for files older than 6 months (instead of 3).
    Now-a-days, 100 MB is not a lot of space and does not cost much. 600 MB will fit on a "vanialla" CD which costs less than 1 Euro. You can also copy then to an external medium before deleting them.
    FYI: Reading the logs are a major pain, and I doubt that the auditors actually do this... but there are some usefull techniques you can use to send alerts when certain audit log messages appear (to solve the needle in a haystack problem) or read them all remotely and then use the same to drill down and analyze patterns. But you first need to know what the "alerts" are and which "patterns" to look for in the data you will be collecting. If you are only logging "unsuccesfull transaction start" and stuff like that, then you might as well turn it off again (even if it does keep the auditors happy).
    Hope that helps a bit more,
    Julius

  • How to change the retention period of os watcher log,

    How to change the retention period of os watcher log, by default it is 7 days. but in our exadata env. automatically oswatcher logs are deleted , so i want to check the retention period.
    Regards,
    Ani

    Hi Ani,
    Go to :- /opt/oracle.cellos/validations/init.d/oswatcher
    Open the file "oswatcher" file.check for the line "/startOSW.sh X Y Z". Where X is the snapshot interval
    make the change and you are done
    Regards,
    Sunil Bhola

  • How does one read the Unity transaction logs on Exchange?

    I'm trying to find out who placed a call to whom on a particular day and time.  A subscriber receives a blank email periodically with no "from" statement, just a timestamp. They don't have unified messaging.  I want to see if the transaction logs (located on Exchange) contain that information but they are all cryptic symbols.  Is there an application or utility to read tham?  These are the files located in the \Exchsrvr\MDBDATA folder. This is Unity 5.x and Excahnge 2003. Thanks.

    Hi,
    I think you may be wanting to look at Message Tracking?
    http://www.msexchange.org/tutorials/Exchange-2003-Message-Tracking-Logging.html
    But here's also an explanation of the transaction logging and how to read them from the same site:
    http://www.msexchange.org/articles/Transaction-Logs-Lifeblood-Exchange.html
    Hope that helps,
    Brad

  • Transaction F.27 Periodic Account Statements

    Transaction F.27 Periodic Account Statements
    My goal is to save on server the PDF printout of each customer using spool request number. The problem is that the spool generated by the transaction is for all customers. I must find a way to generate one spool request per customer. Any ideas would be appreciate.
    Regards,
    Daniel Cantin

    Hi Daniel,
    As the documentation fo F.27 says:
    Output
         If correspondences are printed, a log with the spool requests created by
         the print programs is output for each program run. If you do not specify
         in the program on which printer the log is to be printed, the program
         may take the printer specified in the user master of the user who
         started the program or the printer specified when the job is scheduled.
         If the program is carried out online, the log is displayed on the
         screen. If the program is planned as a job, the spool request name of
         the log is made up of the identifier F140, the printer destination, the
         date of creation and the program ID KORK.
         The correspondences are printed by means of the corresponding print
         programs. If printing is possible on the basis of the data and the
         configuration, a spool request is created for each correspondence type
         and company code. Regardless of whether printing actually takes place,
         the processed correspondence requests are marked as completed by means
         of a print date, so that reorganization can be carried out.
    As it says " a spool request is created for each correspondence type and company code. " perhaps you will have only one spool order. So, in this case, you will need to create your own report using RFKORK00 as a template, creating a copy of include RFKORI93 and replacing it in your own report, changing the value for  KEEP IN SPOOL where
            NEW-PAGE
              PRINT ON
              LINE-SIZE               132
              LIST NAME               PROLISTN
              IMMEDIATELY             ' '
              NEW LIST IDENTIFICATION 'X'
              KEEP IN SPOOL           ' '        "change 'X' by space or ' '
    It's an idea.
    Regards
    Eduardo

  • Transaction mmpv incorrect period in control rec

    transaction mmpv close period for material master record
    i enter company code 4000 period 07 fy 2004
    check and close period
    i get specified year is not the current year when i execute
    in the log i get
    incorrect period in control rec cocd 4000current period of the control record is 07 2004.
    what am i doing wrong?

    Hi Janice,
    Check this thread.. It has ur answer..
    Quarry in Posting period
    cheers,
    Prashanth
    P.S Please mark helpful answers

  • How do I view the transaction log in SQL Server 2008?

    Hello,
    I want to know how to view all the transactions taken during a particular period of time. I know there is a log file, ending with .ldf, created for each database. But how do I view this file?
    Is there any tool in the SQL Server studio that can enable me to view the transactions for a given time period?
    The reason for me wanting to view the log file is that, last week during a power outage, certain amount of data was not written. And one my friend had also messed up some of the data (unfortunately, she doesn't remember what she did).
    Thanks in advance.

    Hi,
     It enables you to read from you transaction log which contains very valuable information about stuff that is happening in your database.
    select
    * from fn_dblog (null,null) ..
    EXAMPLE:
    SELECT
    FROM
    ::fn_dblog(NULL, NULL)
    WHERE
    operation = 'LOP_DELETE_SPLIT'
    Thanks,
    Leks

  • Exchange 2010 SP3, RU5 - Massive Transaction Log File Generation

    Hey All,
    I am trying to figure out why 1 of our databases is generating 30k Log Files a day! The other one is generating 20K log files a day. The database does not grow in size as the log files are generated, the problem is log file generation.
    I've tried running through some of the various solutions out there, reviewed message tracking logs, rpc client access logs, IIS Logs - all of which show important info, but none of which actually provide the answers.
    I Stopped the following services to see if that would affect the log file generation in any way, and it has not!
    MS Exchange Transport
    Mail Submission
    IIS (Site Stopped in IIS)
    Mailbox Assistants
    Content Indexing Service
    With the above services stopped, I still see dozens (or more) log files generated in under 10 minutes, I also checked mailbox size reports (top 10) and found that several users mailboxes were generating item count increases for one user of
    about 300, size increases for one user of about 150Mb (over the whole day).
    I am not sure what else to check here? Any ideas?
    Thanks,
    Robert
    Robert

    Hmm - this sounds like an device is chewing up the logs.
    If you use log parser studio, are there any stand out devices in terms of the # of hits?
    And for the ExMon was that logged over a period of time?  The default 60 second window normally misses a lof of stuff.  Just curious!
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    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.
    Rhoerick, 
    Thanks for the response. When checking the logs the highest number of hits were the (Source) Load Balancers, Port 25 VIP. The problem i was experience was the following: 
    1) I kept expecting the log file generation to drop to an acceptable rate of 10~20 MB Per Minute (Max). We have a large environment and use the exchange sevrers as the mail relays for the hated Nagios monitoring environment
    2) We didn't have our enterprise monitoring system watching SMTP traffic, this is  being resolved. 
    3) I needed to look closer at the SMTP transport database counters, logs, log files and focus less on the database log generation, i did do some of that but not enough of that. 
    4) My troubleshooting kept getting thrown off due to the monitoring notifications seeming to be sent out in batches (or something similar) stopping the transport service for 10 ~ 15 minutes several times seemed to finally "stop the transactions logs
    from growing at a psychotic rate". 
    5) I am re-running my data captures now that i have told the "Nagios Team" to quit killing the exchange servers, with their notifications, sometimes as much as 100+ of the same notifications for the same servers, issues. so far at a quick glance
    the log file generation seems to have dropped by about 30%. 
    Question: What would be the best counters to review in order to "Put it all together"? Also note: our Server roles are split, MBX and CAS/HT. 
    Robert 
    Robert

  • Message tracking log - time period

    Hi,
    How long are message tracking logs keeped on appliance?
    How can i control message tracking logs.
    Lots of HDD space available and I want 3 months of available Message Tracking logs.
    When are Message traking logs deleted from the appliance?

    Message tracking is based on the drive space available on the ESA appliance.
    It is not possible to configure the # of days for retention of message tracking data. The set HDD storage allocation for message tracking data is limited. HDD storage allocation is set based on the hardware:
    C1X0: 10G
    C3X0: 20G
    C6X0: 50G
    X10X0: 50G
    Your best solution in order to store mail logs/message tracking - would be to also have configured to store the mail_logs off to a syslog server --- that way you can determine the full extent/length of the retention period.  (And also allows you to search/manipulate all mail_logs with a little easier access that may be available on the ESA.)
    Hope that helps!
    -Robert

  • Need a Walkthrough on How to Create Database & Transaction Log Backups

    Is this the proper forum to ask for this type of guidance?  There has been bad blood between my department (Research) and the MIS department for 30 years, and long story short I have been "given" a virtual server and cut loose by my MIS department
    -- it's my responsibility for installs, updates, backups, etc.  I have everything running really well, I believe, with the exception of my transaction log backups -- my storage unit is running out of space on a daily basis, so I feel like I have to be
    doing something wrong.
    If this is the proper forum, I'll supply the details of how I currently have things set up, and I'm hoping with some loving guidance I can work the kinks out of my backup plan.  High level -- this is for a SQL Server 2012 instance running on a Windows
    2012 Server...

    Thanks all, after posting this I'm going to read the materials provided above.  As for the details:
    I'm running on a virtual Windows Server 2012 Standard, Intel Xeon CPU 2.6 GHz with 16 GB of RAM; 64 bit OS.  The computer name is e275rd8
    Drives (NTFS, Compression off, Indexing on):
    DB_HVSQL_SQL-DAT_RD8-2(E:) 199 GB (47.2 used; 152 free)
    DB_HVSQL_SQL-Dat_RD8(F:) 199 GB (10.1 used; 189 free)
    DB_HVSQL_SQL-LOG_RD8-2(L:) 199 GB (137 used; 62 free) **
    DB_HVSQL_SQL-BAK_RDu-2(S:) 99.8 GB (64.7 used; 35 free)
    DB_HVSQL_SQL-TMP_RD8-2(T:) 99.8 GB (10.6 used; 89.1 free)
    SQL Server:
    Product: SQL Server Enterprise (64-bit)
    OS: Windows NT 6.2 (9200)
    Platform: NT x64
    Version: 11.0.5058.0
    Memory: 16384 (MB)
    Processors: 4
    Root Directory: f:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL
    Is Clustered: False
    Is HADR Enabled: False
    Database Settings:
    Default index fill factor: 0
    Default backup media retention (in days): 0
    Compress backup is checkmarked/on
    Database default locations:
      Data: E:\SQL\Data
      Log: L:\SQL\LOGs
      Backup: S:\SQLBackups
    There is currently only one database: DistrictAssessmentDW
    To create my backups, I'm using two maintenance plans, and this is where I'm pretty sure I'm not doing something correctly.  My entire setup is me just guessing what to do, so feel free to offer suggestions...
    Maintenance Plan #1: Backup DistrictAssessmentDW
      Scheduled to run daily Monday Through Friday at 3:33 AM
      Step 1: Backup Database (Full) 
        Backup set expires after 8 days 
        Back up to Disk (S:\SQLBackups)
        Set backup compression: using the default server setting
      Step 2: Maintenance Cleanup Task
        Delete files of the following type: Backup files
        Search folder and delete files based on an extension:
          Folder: L:\SQL\Logs
          File extension: trn
          Include first-level subfolders: checkmarked/on
        File age: Delete files based on the age of the file at task run time older than 1 Day
      Step 3: Maintenance Cleanup Task
        Delete files of the following type: Backup files
        Search folder and delete files based on an extension:
          Folder: S:\SQLBackups
          File extension: bak
          Include first-level subfolders: checkmarked/on
        File age: Delete files based on the age of the file at task run time older than 8 Days
    Maintenance Plan #2: Backup DistrictAssessmentDW TRANS LOG ONLY
      Scheduled to run daily Monday through Friday; every 20 minutes starting at 6:30 AM & ending at 7:00 PM
      Step 1: Backup Database Task
        Backup Type: Transaction Log
        Database(s): Specific databases (DistrictAssessmentDW)
        Backup Set will expire after 1 day
        Backup to Disk (L:\SQL\Logs\)
        Set backup compression: Use the default server setting
    Around 2:30 each day my transaction log backup drive (L:) runs out of space.  As you can see, transactions are getting backed up every 20 minutes, and the average size of the backup files is about 5,700,000 KB.
    I hope this covers everything, if not please let me know what other information I need to provide...

  • Archiving and different Retention period by  specific interface

    We want to specify different Retention period for different interfaces (audit reasons)... and based on search in SDN, it does not seem like this is  supported by SAP...
    Do any of you know if SAP intends to support this in future? Any ideas for overcoming this gap? or is this limitation deliberate (and has been kept in place for a reason)?

    Hi Krish,
    Actually I don't think we have this option of setting the retention period for specific interfaces,
    but for the global interfaces in the system.
    If you want to increase the time for Audit Log messages you need to change parameter 'messaging.auditLog.memoryCache' to false in order to persist the audit logs in PI 7.1 system. Take a look at note #1314974 for more details.
    And notice that after changing the parameter to false, audit logs are persisted till the corresponding messages are deleted. The default retention period of messages on AE is 30 days, keep in mind that it could have a little impact on the data volume.
    To increase the retention time in AFW, go to:
    Services -> XPI Adapter: XI:
    "xiadapter.outbound.persistDuration.default"
    "xiadapter.inbound.persistDuration.default"
    For the Integration Engine, it's under SXMB_ADM -> Integration Engine Configuration and Configuration.
    Regards,
    Caio Cagnani

  • SQL Server Database - Transaction logs growing largely with Simple Recovery model

    Hello,
    There is SQL server database on client side in production environment with huge transaction logs.
    Requirement :
    1. Take database backup
    2. Transaction log backup is not required. - so it is set to Simple recovery model.
    I am aware that, Simple Recovery model also increases the transaction logs same as in Full Recovery model as given on below link.
    http://realsqlguy.com/origins-no-simple-mode-doesnt-disable-the-transaction-log/
    Last week, this transaction log became of 1TB size and blocked everything on the database server.
    How to over come with this situation?
    PS :  There are huge bulk uploads to the database tables.
    Current Configuration :
    1. Simple Recovery model
    2. Target Recovery time : 3 Sec
    3. Recovery interval : 0
    4. No SQL Agent job schedule to shrink database.
    5. No other checkpoints created except automatic ones.
    Can anyone please guide me to have correct configuration on SQL server for client's production environment?
    Please let me know if any other details required from server.
    Thank you,
    Mittal.

    @dave_gona,
    Thank you for your response.
    Can you please explain me this in more details -- 
    What do you mean by one batch ?
    1. Number of rows to be inserted at a time ?
    2. or Size of data in one cell does matter here.
    As in my case, I am clubbing together all the data in one xml (on c# side) and inserting it as one record. Data is large in size, but only 1 record is inserted.
    Is it a good idea to shrink transaction log periodically, as it is not happening itself in simple recovery model.
    HI Mittal,
    Shrinking is bad activity yu should not shrink log files regularly, in rare case if you want to recovery space you may do it.
    Have manual chekpoints in Bulk insert operation.
    I cannot tell upfront what should be batch size but you can start with 1/4 th of what you are currently inserting.
    Most important what does below query return for database
    select log_reuse_wait_desc from sys.databases where name='db_name'
    The value it returns is what stopping the log from getting cleared and reused.
    What is version and editon of SQl server we are talking about. What is output of
    select @@version
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Archiving data retention period (best practice)

    Hi,
    Can anybody provide the standard FI-CO data retention period I mean for how long data from the following table has to be retained: 
    BKPF, BSAD, BSAK, BSAS, BSIS
    Best business practice.
    Thanks in advance
    Joseph

    Hi,
    I would not recommend to change this setting. One major problem you get will be that the archiving function will delete data from database (which has been transferred to the archive). So far so good, that´s one of the archiving features
    But it sometimes happens that you have to open an already closed fiscal year again. And if you open this last closed fiscal year again, the realtime transactions could fail now if data (transactions, etc.) is missing which exists only in the archive at that point of time.
    By the way, you can have a look at SAP note 389920, in there the archiving functionality is documented for FI-AA application.
    Regards,
    Markus

Maybe you are looking for