Table log

is there any table log in oracle EBS 12.0.4 which cause for increasing data growth?

Hi;
1. Please delete your old logs from your system(check jd post)
2. Please check below thread:
APPS_TS_TX_DATA growth
Re: EBS maintenance problem (DB grows 2 GB per day)
increasing APPS_TS_TX_DATA tablespace
APPS_TS_TX_IDX growth
APPS_TS_TX_IDX Tablespace increasing very speedly.
Regard
Helios

Similar Messages

Too Many Table logs in DBTABLOG, RSTBPDEL is taking too much time

Hi Experts,
In one of our CRM system, DBTABLOG table is logging one table which is having 1 Billion entries right now. Business dont want to switch off the logging at this moment. But the table is increasing rapidly 42 Gb per month. RSTBPDEL program is running from weeks to delete them, but no control on increment.
Can you please suggest any way to delete them quickly at first, so that my house keeping job will run daily and finish soon.
Regards,
Mohan.

Hello Mohan,
The DBTABLOG table does get large, the best is to switch off logging. If that's not possible, increase the frequency of your delete job, also explore one more alternative have a look at the archival object: BC_DBLOGS, you could archive old records (in accordance with your customer's data retention policies) to reduce the size of the table.
Also, have a look at the following notes, they will advise you on how to improve the performance of your delete job:
Note 531923 - Audit Trail: Indexes on table DBTABLOG
Note 579980 - Table logs: Performance during access to DBTABLOG
Regards,
Siddhesh

How to determine Default Table Logging (log data changes )

Does anyone know how to view exactly what tables and related data fields have change logging enabled by default? I know that some of the standard reports will produce "edit reports" show who changed what field, when ,old and new values, etc, but I don't know how to determine where the data is retrieved from.
For example: If I look in the ABAP Dictionary at table LFA1, technical settings, it shows that log data changes is not "checked" or enabled. But if I run the standard AR Master Data Change Report, I get output showing valid field changes.
I have seen other threads that refer to SCU3 but I can't determine the above this from report.
Any assistance would be greatly appreciated.

Hi Arthur,
As far as I am aware, these are 2 different things.
There is table logging which is at the table level & if activated (i.e. it's listed in table DD0LV, PROTOKOLL=X and the table logging parameter is set in the system profile/s).
The second one is programatical logging for change documents when data is maintained though a program that has been written to include a log. I'm not sure how to identify a complete lit of these though unfortunately.
Hope that is of some assistance.

Impact of Table Logging on Standard SAP Tables

Table Logging is not currently active in our system, so if we activate this parameter what will be the impact on system standard tables.
Please find the below example,
For some Standard SAP Tables, the table logging is already enabled, but as overall logging is not activated in the system, the logs are not getting saved for these tables as well.
in the above table the log data changes have been enabled, but as per the below screenshot the overall logging is disabled.
so, if this is enabled, what impact will it have on the system standard tables.

Please move this to BW area of SCN, BI platform space is for Analytics/Business Objects platform.

Recording Differences in Long Text Changes via Table Logging and AUT10

Hello,
I am trying to record changes to Long Text generated in a DMS DIR. (This field is the Language Dependent Description field.) We have set the system profile param rec/client.    We have enabled table logging for STXH & STXL in SE11. When we make a change to the Long Text, we try to display the results in AUT10. A change is indicated but when displayed, the text seems identical.
When displaying Logging status in RSTBHIST, the Active box for STXL is not checked despite the fact that we have set the "Log changes" box in SE11.
Note #573291 talks about installing a PH-ELR add-on. Is that necessary if we are already running SAP_APPL 6.04?
Also, is Table Logging the best approach to capture these changes to Long Text? Is there any way we could use Change Docs"?
The field width of DBTABLOG-LOGDATA = 16000 if that matters.
Thanks for any responses.
Edited by: John K Ryan on Oct 13, 2011 9:20 AM

Tobias,
"You created a dynpro based transaction which allows you to change
the content of a text. The text to change is not part of the dynpro
screen, but you want to set it into an ITS field where you can access
it using Bussiness HTML. Is this correct?"
<b><u>This is correct.</u></b>
Below is the portion of HTML template code in which I'm defining the web screen pushbuttons, providing the pushbutton names, and linking same to the function codes defined in the R/3 transaction.
This is my first experience with ITS, so if I've missed something glaringly obvious, I apologize in advance.
Thanks!
<table>
<tr>
    <input type=submit name="~OKCode=ANAL" value="Analysis Long Text">
</tr>
<tr>
    <input type=submit name="~OKCode=ROOT" value="Root Cause Long Text">
</tr>
<tr>
    <input type=submit name="~OKCode=RMCA" value="Remedial Corrective Action Plan Long Text">
</tr>
<tr>
    <input type=submit name="~OKCode=CRAP" value="Corrective Action Plan Long Text">
</tr>
<tr>
    <input type=submit name="~OKCode=PRAP" value="Preventative Action Plan Long Text">
</tr>
<tr>
    <input type=submit name="~OKCode=COMM" value="Comments">
</tr>
</table>

Automatic table logs?

Hi,
Logging table changes, produced by dml operations, is a very often requirement in today's information systems (what was changed, by whom, from which machine, when, etc). The best I could do in the past, explicitly with Oracle, was to automatically generate the change log table, procedure and triggers to handle the automatic logging, for a given table. I made it in pl/sql, so, it's not very flexible. A more general and portable solution could be to make the procedure in java, so using metadata you can have only one generic procedure for all the logging triggers (maybe this is not very efficient, mmm).
I was surfing the net and I found something called Change Data Capture (CDC) from Oracle, whose intended usage is for dataware house processing. I do not want, yet ;-), to enter into the exotic world of datawares, datamining, etc. But the article mentioned something that I have been thinking for a while: why do I need to manually store the changes made to the tables, if the dbms already has this information (redo-logs or something like that); in fact, I think that this detailed information is used to allow rollbacks and related stuff, but this is only a belief.
So, the point is to tell the dbms: let me access your internal logs, in a friendly and automatic way. Either, copy them for me into another table or let me access them with a tabular-view; so I can query them like any other table. The CDC seems to be a more general approach, since it allows to install some kind of "listeners" to the data-change-events and to do something with them (like synchronization). Then, maybe using CDC for normal table logging is like killing flies with bombs, I do not know.
Then, I was wondering: what is the better approach to make automatic table logging in Oracle?
Thanks in advance.
salu2
dario estepario ...

Hi,
Well, then I suppose the red-logs are discarded, but what about cdc in general?
On the other hand, following your advice, I took a quick look at both the fine-grained constraints and the workspace manager. These are my first impressions:
1. The fine-grained feature is more related to security concerns, so, the lowest level of data stored seems to be the sql instruction. Therefore, this options appears not so suitable for the task (I could be wrong, however).
2. The workspace manager is a control versioning system for the data, but in particular, or as a side effect of that feature, it implements change logs automatically. I ran a little example and it worked pretty well. I just had to call a pl/sql package procedure to enable versioning on the table and, automatically, another view was created. It mirrored the columns of the original table plus some fields with additional information (like timestamps, db user, operation, etc).
So, this option seems like a very good candidate for doing the logging work. The only concern I have right now, is how to tell the framework to save more data (like information coming from upper layers: app user, client ip, etc).
Thanks for your help,
Regards,
dario estepario ...

Question about table logs in SAP

Hello,
What table's do the transaction codes ST03 and STAD retrieve log history files from?
Are these tables automatically logged by SAP, such as table CHDHR, or does table logging specifically have to be turned on for these table's?
Help is greatly appreciated on this. Thanks in advance,
Adamo

ST03 tables I believe are SAP Workload Tables. You can search SE16 for:
SAPWL*
rgds,
Babak

Audit Log - Table Log

Hi everyone,
Can anyone tell me if i activate table logging on a table (not customizing table) like MARC table, what information is saved in the system?.
Can I check or know, previous the audit log activation over this table, what fields or what information is recorded?
thanks,
HEPC

This is table logging for customizing type entries in not necessarily what you are looking for.
For master data you need to use the application change documents (table CDHDR etc) which is a different concept (I would use that route and protect the object S_ARCHIVE).
What you are actually looking for (and waiting for) is [the package concept at runtime|http://forums.sdn.sap.com/click.jspa?searchID=58483939&messageID=4675719] which developers can already see as warnings. It also means that the package which the table is assigned to must have a complete set of APIs.
I would personally not look for workarounds with performance impacts, but rather clean up the code to make it package concept conform, and then use the application change documents and not the table change records.
This is a better design - more sustainable, less hassles and auditable (via where-used-lists).
My 2 cents,
Julius

Client copy error: Table logging in program RSCLXCOP disabled by user

Hi,
While doing client export from a system, I am getting the below error in test run:
Table logging in program RSCLXCOP disabled by user
Kindly advice.
Thanks & regards,
Kunal Patel.

Hi
Note 446485 - CC-ADMIN: Special copying options
It would help you out, but do check double time.

Table Logging in Fire Fighter (Super User Privilege Management)

Does anyone know exactly which sources does the Firefighter Log Report take into account?
I would think that Change Documents (CDHDR CDPOS) and Workload Stats for TX (STAT) exexcution are part of it. Does anyone know whether table logging entries (DBTABLOG) are also displayed in the report?
Thanks alot.
Best regards,
Alex

Amongst other things, you can check the status of the table logging in SE13.
Regardless of the application reporting, you can check the log via SCU3.
Cheers,
Julius

Table Logging

What is the best way to capture material determination changes?    The DBTABLOG table is 180GB in size so another way needs to be investigated other than setting on table logging for the material determination tables.
There is no built-in SAP change record functionality in VB11-VB13 like there is in (for example) VK11-VK13, price records.
I know this is a BASIS question but I cannot find a BASIS forum so I entered the question here because the tables are S/D tables.
Thank you,
Edited by: LP on Apr 14, 2008 4:23 PM

Why not do a quick test?
SQL> create table t as select * from user_tables;
Table created.
SQL>
SQL> create or replace
2 procedure count_t as
3     l_count number;
4 begin
5     select count(*)
6     into   l_count
7     from   t;
8 end;
9 /
Procedure created.
SQL>
SQL> alter table t nologging;
Table altered.
SQL> select object_name, object_type, status from user_objects where object_name = 'COUNT_T';
OBJECT_NAME                    OBJECT_TYPE        STATUS
COUNT_T                        PROCEDURE          VALIDAt least in this case, it doesn't invalidate it.

Tablespace, table logging and nologging

Hi i had a tablespace which is in logging mode.
i had a table in that tablespace which i want to place in nologging mode.
i do that using following command
ALTER TABLE SCOTT.XYZ NOLOGGING;
i want to know whether the above statement will work even though my tablespace is in logging mode?or should i place my tablespace also in nologging mode?
thanks in advance

The tablespace and table logging mode (specified during create tablespace and create table) DOES NOT affect the logging of inserts, deletes, updates.
Inserts, deletes, updates will be logged regardless, with the exception of "insert /*+ append. */ ...".
The following sentence from the blog should be re-worded because it is ambiguous:
Actually the real meaning of NOLOGGING is whatever operations are performed on
the object with the NOLOGGING option, will NOT be recorded in logfiles.

Active Table Logging T000 performance impact

Hi fellow SAP experts,
I need some advice on system performance impact when switching on Table Logging for T000 - configuration in production please?
We have decided to turn on Table Logging for auditing purposes, only allowing developer config in production following a volume of evidence being supplied.
I need to know how much this activation is going to impact the performance of the companies production environments, how much storage, memory, performance, etc. this function is going to consume and how much of the above consumables I need to cater for now and in the future?
We have a Dual Track environment, BAU want to switch on Table Logging for fix on fail, I want to swich it on for Project deliveries.
Please advise, with referencing if possible?
Thank you kindly
Paul

Hi Paul,
There has been a constant debate whether table logging affects the System performance, especially in Produciton environment. Please see my comments below :
1) To turn on logging for table T000, you will have to activate the parameter rec/client, with values for one client or all the clients in the System depending on your requirement.
2) This parameter setting will not only log changes to T000, but also for over 28000 tables.
3) But these are customizing tables which usually contain a relatively small amount of data which is changed occasionally.
4) After activating, if you suddenly find performance issues, you can check which tables are causing issues via transaction SCU3.
5) You can go to transaction SE13 and deactivate logging for a table, if you find too many entries for any particular table in SCU3.
So, logging tables doesn't necessarily impact performance. Hope this helps. Please refer to SAP Note-608835 related to this.
Best Regards,
Savitha

How to identified the size of table logging (SCU3)

hi SAP Expert,
currently i'm activating the table logging via parameter REC\CLIENT = ALL, understand that this will accumulate the log times to times, is there anyway i can identified how big is the log file already? since i'm concern the log files would make my hardisk full. thanks for any respon.
Regards
Hariyono

Table logging write to table DBTABPRT, just check the size of the table in DB02 (or number of entries in SE16) you can track the growth of the table and wipe the contents once the data is been consumed by whoever requested it.
You can check in DB02 in what tablespace the table is located and make sure that theres enough space in the filesystem for the table to grow without causing inconvenients.
Regards
Juan

SAPSR3DB XMII_TRANSACTION table LOG column is very big

Hi,
We have a problem about MII server.
SAPSR3DB XMII_TRANSACTION table LOG column is very big data in it.
How can it be decrease the size of data in this column?
Regards.

In 12.1 its XMII Administration Menu (Menu.jsp) --> System Management --> DefaultTransactionPersistance.
In production I recommend setting this to 'ONERROR'
There is also the TransactionPersistenceLifetime which determines how long entries will stay in the log table.
We set this to 8 hours.

Table log

Similar Messages

Maybe you are looking for