WF_ITEM_ACTIVITY_STATUSES_H table is growing rapidly in PROD.

Hi,
We are noticing one of the table WF_ITEM_ACTIVITY_STATUSES_H size was 6 GB on 20-APR-11. Today it is at 25 GB (in 1 month) with 356 million rows and growing rapidly! any idea.
Thanks
Rao

I have one question for you. How to purge the workflow date where item_type(OEOH,OEOL) specific only. I would really appreciate if you can guide us in the right direction this issue is becoming more and more critical to the business and also it's degrading the whole back groung process too.
Righ now in prod we are running the "Purge Obsolete Workflow Runtime Data" 21 days Temporary:Y:500:N. i checked the count fro OEOL and OEOH by using below query
select item_type, count(*)
from WF_ITEM_ACTIVITY_STATUSES_H group by item_type
OEOL14982271 14 Million
OEOH504495652 510 Million
select count(*) from WF_ITEM_ACTIVITY_STATUSES_H;
519793016 519 million
Thanks
Ganga

Similar Messages

PSAPUNDO Table space growing rapidly

Hello
The tablespace PSAPUNDO is growing rapidly on one of client server how to .
PSAPUNDO     1,736.13     151.2
PSAPUNDO     441.125     42.6
PSAPUNDO     183.125     15
PSAPUNDO     142.125     12.6
PSAPUNDO     81.125     5.9
PSAPUNDO     74.125     3.3
PSAPUNDO     44.125     1.9
PSAPUNDO     35.125     1.7
PSAPUNDO     39.125     0.3
PSAPUNDO     20.125     0.3
this growth in six days...? can any one help me as im new to sap

letzfriend wrote:
Hello
>
> The tablespace PSAPUNDO is growing rapidly on one of client server how to .
>
> PSAPUNDO     1,736.13     151.2
> PSAPUNDO     441.125     42.6
> PSAPUNDO     183.125     15
> PSAPUNDO     142.125     12.6
> PSAPUNDO     81.125     5.9
> PSAPUNDO     74.125     3.3
> PSAPUNDO     44.125     1.9
> PSAPUNDO     35.125     1.7
> PSAPUNDO     39.125     0.3
> PSAPUNDO     20.125     0.3
>
>
> this growth in six days...? can any one help me as im new to sap
Hi,
Did you check the note 1035137 - Oracle Database 10g: Automatic Undo Retention?
Best regards,
Orkun Gedik

How to effectively manage large table which is rapidly growing

All,
My environment is single node database with regular file system.
Oracle - 10.2.0.4.0
IBM - AIX
A tablespace in this database is growing rapidly. Especially a single table in that tablespace having "Long Raw" column datatype has grown from 4 GBs to 900 GBs in 6 months.
We had discussion with application team and they mentioned that due to acquisitions, data volume is increased and we are expecting it to grow up to 4 TBs in next 2 years.
In order to effectively manage the table and to avoid performance issues, we are looking for different options as below.
1) Table is having date column. With that thought of converting to partitioned table like "Range" partitioning. I never converted a table of 900 GBs to a partitioned table. Is it a best method?
a) how can I move the data from regular table to partitioned table. I looked into google, but not able to find good method for converting to regular table to partitioned table. Can you help me out / share best practices?
2) In one of the article, I read, BLOB is better than "Long RAW" datatype, how easy is to convert from "Long RAW" datatype. Will BLOB yield better performance and uses disk space effectively?
3) Application team is having purging activity based on application logic. We thought of using shrinking of tables option with enable row movement- "alter table <table name> shrink space cascade". But it is returning the error that table contains "Long" datatype. Any suggestions.
Any other methods / suggestions to handle this situation effectively..
Note: By end of 2010, we have plans of moving to RAC with ASM.
Thanks

To answer your question 2:
2) In one of the article, I read, BLOB is better than "Long RAW" datatype,
how easy is to convert from "Long RAW" datatype. Will BLOB yield better
performance and uses disk space effectively?Yes, LOBs, BLOBs, or CLOBs are (supposed) to be better than raws (or long raws). In addition, I believe Oracle has or will shortly be desupporting the use of long raws in favor of LOBs, CLOBs, or BLOBs (as appropriate).
There is a function called "to_lob" that you have to use to convert. Its a pain because you have to create the second table and then insert into the second table from the first table using the 'to_lob' function.
from my notes...
=================================================
Manually recreate the original table...
Next, recreate (based on describe of the table), except using CLOB instead of LONG:
SQL> create table SPACER_STATEMENTS
2 (OWNER_NAME VARCHAR2(30) NOT NULL,
3 FOLDER VARCHAR2(30) NOT NULL,
4 SCRIPT_ID VARCHAR2(30) NOT NULL,
5 STATEMENT_ID NUMBER(8) NOT NULL,
6 STATEMENT_DESC VARCHAR2(25),
7 STATEMENT_TYPE VARCHAR2(10),
8 SCRIPT_STATEMENT CLOB,
9 ERROR VARCHAR2(1000),
10 NUMBER_OF_ROWS NUMBER,
11 END_DATE DATE
12 )
13 TABLESPACE SYSTEM
14 ;
Table created.
Try to insert the data using select from original table...
SQL> insert into SPACER_STATEMENTS select * from SPACER_STATEMENTS_ORIG;
insert into SPACER_STATEMENTS select * from SPACER_STATEMENTS_ORIG
ERROR at line 1:
ORA-00997: illegal use of LONG datatype
That didn't work...
Now, lets use TO_LOB
SQL> insert into SPACER_STATEMENTS
2 (OWNER_NAME, FOLDER, SCRIPT_ID, STATEMENT_ID, STATEMENT_DESC, STATEMENT_TYPE, SCRIPT_STATEMENT, ERROR, NUMBER_OF_ROWS, END_DATE)
3 select OWNER_NAME, FOLDER, SCRIPT_ID, STATEMENT_ID, STATEMENT_DESC, STATEMENT_TYPE, TO_LOB(SCRIPT_STATEMENT), ERROR, NUMBER_OF_ROWS, END_DATE
4 from SPACER_STATEMENTS_ORIG;
10 rows created.
works well...
===============================================================

SRRELROLES table entries growing

Hi Experts,
Can you please help me understand what is the exact use of table SRRELROLES.
What i know is this table is used to store the link information between systems connected to SAP CRM.
I need help on the followings:
1. How the table get its entries? Is it like whenever a message flow (to and fro) between SAP CRM and another system(say SAP ECC), a BDoc flows.
And for this BDoc flow, an entry will be created in SRRELROLES.
2.Also can the old entries from this table be deleted. This table is growing like any thing in SAP CRM system.
I have found some SAP Notes which suggested how to delete the entries. But what can be the effect of deletion is no where explained.
I have checked many blogs but i am ot able to find exact reason for this.
Please help me in this regards.
Thanks in Advance.
regards,
Vicky

Hello Vicky,
Please read note 505608 to find out what can be don to avoid the rapid growth of table SRRELROLES.
The table SRRELROLES can be archived by running the reports RSRLDREL, RSRLDREL2 and RSRLDREL3.
The links are not archived as separate object. The links are archived with the respective business object. You can use report RSRLDREL2 from note 853035 for mass deletion. And for the report RSRLDREL please leave the business object empty. You will use the role as selection
criteria which most of the entries in the table srrelroles use for the document flow.
thanks
Willie

SYSAUX Growing Rapidly

Hi,
When i configured IC mode the SYSAUX Growing Rapidly.
Please let me know what happens.
Thank

Hello,
Seems like the log mining server has grow this tables due any reason. May be the execution of a large transacction, a massive UPDATE, DELETE or INSERT.
Once these tables have grown, no free space.
Would have to test whether making a shutdown / startup instance these tables are truncated. Since the information they hold, I think, would only be necessary for the Log Miner session.
Which is the result of this queries:
SELECT COUNT(*) FROM SYSTEM.LOGMNRC_GTCS ;
SELECT COUNT(*) FROM SYSTEM.LOGMNR_COL$ ;
You can confirm that there is no transaction in the database for long term? You can look at the view v $ TRANSACTION, has a column that specifies the date and time when a transaction began.
From MOS:
There is no official way to reclaim the space but as a workaround you can use the DBMS_LOGMNR_D.SET_TABLESPACE routine to recreate all LogMiner tables in an alternate tablespace. For example, the following statement will recreate all LogMiner tables to use the LOGMNRTS tablespace:
From MOS.
How to Reclaim Space Used by LogMiner Tables (Doc ID 456814.1)
SQL> connect / as sysdba
SQL> EXECUTE DBMS_LOGMNR_D.SET_TABLESPACE ('LOGMINER_DATA');
However this command requiere stop GG capture process.
This procedure move the Logminer tables to the tablespace indicated, then, in the move operation the space is compacted.
May be a good practice using GG IC is to define a dedicated tablespace to Logminer.
I hope help.
Regards
Arturo

PSAPSID tablespace grows rapidly

Hi All,
We are having a BI7[SP11] system on oracle. All were normal operations till the 1 month past. This month, we have been observing that the PSAP<SID> tbspc has been growing rapidly very much. When checked with functionals no extra loads were used.
Now I can monitor from DB02 on the tbspc by checking the history, when more delta occured, but I wanted to see which table, related to which data, all that delta happened, so that i can check with functionals.
Is there anyway to still dig this and get the proof. Can any body please help..
Thanks a lot
VR.

Hi Vera,
I would recommend to you if you wish to see the table, via the table space name, in transaction DB02, and then relate that to the table in your BW system.
I would use the following steps
Monitor in DB02 and then get your table space name
Under DB02 you should see under the "Space" drill down a option called "Tables and Indexes" double click on this option
Hopefully your basis team would of Reorged the tables so you have the latest stats
Hit continue then enter your table space name as selection criteria
From here you can get the table space name,
Take your table space name and enter this into the table SE16 RSTSODS you should be able to get the generic PSA name that is being wrote to
Other wise if it is not in this table you should have a very good idea of what sort of data is being recorded by the naming convention.
Thanks
Ben
**Please assign points if helpful**

Can't create table that grows using the button object

Im a beginner, and this seems like a simple issue. Appreciate your help in advance. When I try to do this, the button fails to add a row.
So, I printed out the Help section entitled, "create a table that grows using the button object" and started from scratch with a simple table as the only object on the form- and followed the instructions to the letter.
When I go to preview and click the button, a row is not added.
Can you suggest something?

Try this:
Select body row of table from hierarchy palette that you want to repeat then on he object tab of the properties tab select binding tab. You need to click on "Repeat Row for Each Data Item"
I hope this helps
Murat
www.muratkuru.com.tr

OAI_AGENT_ERROR table growing rapidly

Hi
I have a problem with my oai_agent_error table growing at a rate of a 1000 records every few minutes. My DB adapter reports the following error before dropping the messages,
oracle.oai.agent.server.transform.database.DBTransformationException: PLSQLTransformation.transform: Transformation failed
at oracle.oai.agent.server.transform.database.PLSQLTransformation.transform(PLSQLTransformation.java:359)
at oracle.oai.agent.server.transform.BuiltInTransformation.transform(BuiltInTransformation.java:293)
at oracle.oai.agent.server.transform.MessageTransformer.processStackFrame(MessageTransformer.java:849)
at oracle.oai.agent.server.transform.MessageTransformer.processTransformMetadatalet(MessageTransformer.java:489)
at oracle.oai.agent.server.transform.MessageTransformer.transformMessage(MessageTransformer.java:276)
at oracle.oai.agent.server.InMessageTransformer.processObject(InMessageTransformer.java:87)
at oracle.oai.agent.common.QueueAgentComponent.run(QueueAgentComponent.java:110)
at java.lang.Thread.run(Thread.java:534)
We have a custom PL/SQL package that does the AV to CV transforms for us and this is valid at the moment.
I also see that its not all messages that are getting dropped as some messages have reached my Spoke systems properly transformed.
I would really like to know how to debug this further to stop these messages from being dropped.
Any help is much appreciated!
Thank you

HI
"oracle.oai.agent.server.transform.database.DBTransformationException: PLSQLTransformation.transform: Transformation failed" in the log file means this error occured at agent level /application level.So,using metadata interconnect is not able to convert input data in to application view.
Error is transformation failed.So reason can be
--> any unhandled exceptions
--> mismatch in data type of fields/parameters used.
--> mis match in number of field/elements in input data.
Transformation failed indicates interconnect not able to transform input data in to sepcified format in Application view or common view.
As you mentioned,this is happening only with few records.
--> check if failed records are to test negative cases.
--> check if failed records have all values expected as mandatory for transformation.
--> check if failed records have the data with expected datatypes(For eg field a is defined as number and field a in record have value 'abc' instea dof 123).
Hope this information helps you.

APPS_TS_MEDIA tablespace growing rapidly

Hi,
The APPS_TS_MEDIA tablespace stores all the attached documents in Oracle Applications. But it is growing at a very rapid rate.
Is there a way to delete the old attachments from this tablespace?
When users raise a PO/PR, they attach the document along with the PR. But once the PR is closed, we no longer require those attachments.
Could someone please let me know if there is any way of deleting those old files from APPS_TS_MEDIA tablespace?
Thanks!

OWNER     SEGMENT_NAME          SEGMENT_TYPE     SIZ
APPLSYS     SYS_LOB0000057442C00004$$     LOBSEGMENT     53,561,262,080
APPLSYS     FND_LOBS               TABLE          114,294,784
APPLSYS     SYS_IL0000057442C00004$$     LOBINDEX     22,544,384
APPLSYS     FND_LOBS_N1          INDEX          2,359,296
APPLSYS     FND_LOBS_U1          INDEX          2,097,152
CSF     CSF_MD_LYR_METADATA     TABLE          131,072
CSF     CSF_MD_RD_SEGS          TABLE          131,072
CSF     CSF_TDS_BINARY_TILES     TABLE          131,072
CSF     CSF_TDS_SEGMENTS          TABLE          131,072
CSF     SYS_IL0000060656C00011$$     LOBINDEX     131,072
CSF     SYS_IL0000061938C00007$$     LOBINDEX     131,072
CSF     SYS_IL0000061011C00013$$     LOBINDEX     131,072
CSF     SYS_LOB0000060628C00010$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060628C00011$$     LOBSEGMENT     131,072
CSF     CSF_LF_ROADSEGMENTS     TABLE          131,072
CSF     CSF_MD_RAIL_SEGS          TABLE          131,072
CSF     SYS_IL0000060656C00010$$     LOBINDEX     131,072
CSF     SYS_IL0000061068C00016$$     LOBINDEX     131,072
CSF     SYS_IL0000061938C00008$$     LOBINDEX     131,072
CSF     SYS_IL0000209418C00012$$     LOBINDEX     131,072
CSF     SYS_IL0000060957C00013$$     LOBINDEX     131,072
CSF     SYS_IL0000061112C00011$$     LOBINDEX     131,072
CSF     SYS_IL0000060704C00011$$     LOBINDEX      131,072
QP     QP_DOCUMENTS_U1          INDEX          131,072
CSF     SYS_LOB0000060588C00018$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060869C00012$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061979C00003$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000062083C00011$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209422C00011$$     LOBSEGMENT     131,072
CSF     CSF_LF_NAMES          TABLE          131,072
CSF     CSF_LF_PLACE_NAMES          TABLE          131,072
CSF     CSF_LF_POIS          TABLE          131,072
CSF     CSF_LF_ROADSEGM_PLACES     TABLE          131,072
CSF     CSF_MD_INST_STYLE_SHTS     TABLE          131,072
CSF     CSF_MD_NAMES          TABLE          131,072
CSF     CSF_TDS_ROADBLOCKS     TABLE          131,072
CSF     CSF_MD_OM_ROADS          TABLE          131,072
CSF     SYS_IL0000061938C00005$$     LOBINDEX      131,072
CSF     SYS_IL0000061068C00017$$     LOBINDEX 131,072
CSF     SYS_IL0000060588C00018$$     LOBINDEX      131,072
FRM     SYS_IL0000285924C00004$$     LOBINDEX      131,072
CSF     SYS_LOB0000060588C00017$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060656C00010$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060656C00011$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060704C00011$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061068C00016$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061938C00005$$     LOBSEGMENT     131,072
CSF     CSF_LF_PLACES          TABLE          131,072
CSF     CSF_LF_POI_NAMES          TABLE          131,072
CSF     CSF_LF_ROADSEGM_POSTS     TABLE          131,072
CSF     CSF_MD_LAND_USES          TABLE          131,072
CSF     CSF_MD_POI_NM_ASGNS     TABLE          131,072
CSF     CSF_MD_THEME_METADATA     TABLE          131,072
CSF     CSF_TDS_CONDITIONS     TABLE          131,072
CSF     CSF_TDS_TILES          TABLE          131,072
CSF     CSF_MD_OM_POIS          TABLE          131,072
FRM     FRM_REPOSITORY_LOBS     TABLE          131,072
CSF     SYS_IL0000060588C00017$$     LOBINDEX      131,072
CSF     SYS_IL0000061979C00004$$     LOBINDEX      131,072
CSF     SYS_IL0000062083C00011$$     LOBINDEX      131,072
CSF     SYS_IL0000209418C00011$$     LOBINDEX      131,072
CSF     SYS_IL0000209420C00012$$     LOBINDEX      131,072
CSF     SYS_IL0000061112C00010$$     LOBINDEX      131,072
CSF     SYS_IL0000060704C00012$$     LOBINDEX      131,072
CSF     SYS_LOB0000060897C00012$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061011C00013$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061112C00010$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061156C00028$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061938C00008$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000062261C00013$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209418C00012$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209422C00010$$     LOBSEGMENT     131,072
CSF     CSF_LF_ROADSEGM_NAMES     TABLE          131,072
CSF     CSF_MD_ADM_BOUNDS     TABLE          131,072
CSF     CSF_MD_HYDROS          TABLE          131,072
CSF     CSF_TDS_BINARY_MAPS     TABLE          131,072
CSF     CSF_TDS_NODES          TABLE          131,072
CSF     CSF_TDS_RDBLCK_INTVLS     TABLE          131,072
CSF     SYS_IL0000062083C00010$$     LOBINDEX      131,072
CSF     SYS_IL0000060628C00010$$     LOBINDEX      131,072
CSF     SYS_IL0000061011C00012$$     LOBINDEX      131,072
CSF     SYS_IL0000209422C00010$$     LOBINDEX      131,072
CSF     SYS_IL0000060957C00012$$     LOBINDEX      131,072
CSF     SYS_LOB0000060897C00013$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060957C00012$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060957C00013$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061011C00012$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061938C00007$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061979C00004$$     LOBSEGMENT     131,072
QP     SYS_LOB0000296934C00002$$     LOBSEGMENT     131,072
CSF     CSF_MD_LYR_STYLE_SHTS     TABLE          131,072
CSF     CSF_TDS_COND_SEGS          TABLE          131,072
CSF     CSF_TDS_INTERVALS          TABLE          131,072
CSF     SYS_IL0000061979C00003$$     LOBINDEX      131,072
CSF     SYS_IL0000060628C00011$$     LOBINDEX      131,072
CSF     SYS_IL0000060869C00013$$     LOBINDEX      131,072
CSF     SYS_IL0000061156C00028$$     LOBINDEX      131,072
CSF     SYS_IL0000061156C00029$$     LOBINDEX      131,072
CSF     SYS_IL0000209424C00011$$     LOBINDEX      131,072
CSF     SYS_IL0000209420C00011$$     LOBINDEX      131,072
CSF     SYS_IL0000060897C00012$$     LOBINDEX      131,072
CSF     SYS_IL0000060897C00013$$     LOBINDEX      131,072
CSF     SYS_IL0000062261C00014$$     LOBINDEX      131,072
CSF     SYS_LOB0000061938C00006$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209424C00010$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209424C00011$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209420C00012$$     LOBSEGMENT     131,072
FRM     SYS_LOB0000285924C00004$$     LOBSEGMENT     131,072
CSF     CSF_MD_POIS          TABLE          131,072
CSF     CSF_MD_RDSEG_NM_ASGNS     TABLE          131,072
CSF     CSF_MD_OM_HYDROS          TABLE          131,072
CSF     SYS_IL0000061938C00006$$     LOBINDEX     131,072
CSF     SYS_IL0000060869C00012$$     LOBINDEX     131,072
CSF     SYS_IL0000062261C00013$$     LOBINDEX     131,072
FRM     FRM_REPOSITORY_LOBS_N1     INDEX          131,072
QP     SYS_IL0000296934C00002$$     LOBINDEX     131,072
CSF     SYS_LOB0000060704C00012$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000060869C00013$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061068C00017$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061112C00011$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000061156C00029$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209418C00011$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000209420C00011$$     LOBSEGMENT     131,072
CSF     CSF_LF_PLACE_POSTCS     TABLE          131,072
CSF     CSF_LF_POSTCODES          TABLE          131,072
CSF     CSF_TDS_RDBLCK_SGMNTS     TABLE          131,072
CSF     CSF_TDS_SEGM_NODES     TABLE          131,072
CSF     CSF_MD_OM_ADMINS          TABLE          131,072
QP     QP_DOCUMENTS          TABLE          131,072
CSF     SYS_IL0000209424C00010$$     LOBINDEX     131,072
CSF     SYS_IL0000209422C00011$$     LOBINDEX     131,072
FRM     FRM_REPOSITORY_LOBS_UK1     INDEX          131,072
CSF     SYS_LOB0000062083C00010$$     LOBSEGMENT     131,072
CSF     SYS_LOB0000062261C00014$$     LOBSEGMENT     131,072
I looked into thoe MOS, but nothing seems to help!
I have raised a TAR with Oracle and they say, this functionality of deleting attachment doesnt exist and they are finding a solution for it.
Thanks!

Temporay tablespace grows rapidly. . .

Dear All,
When I run a large query the temporary tablespace grows continuously.
The max size of temporary tablespace is 6G.
I set Autoextend on, next size is 10m and maxsize is 6291456M.
Also I set the SORT_AREA_SIZE = 256m.
How to stop the rapid growth of temporary tablespace.
Thanks in advance,
PratHamesh.

If your Oracle version is 9i you can set your PGA_AGGREGATE_TARGET into a appropriate value(i.e. PGA_AGGREGATE_TARGET=1G to avoid sorting on TEMP tablespace.
Frequently sorting happens on your DB and it supposed to shrink.
You can also think of allocating other users to an specific TEMP tablespace but you have to identify which users it is.

Reporting Database growing rapidly

Hello,
Is it normal for the reporting database in SSRS to grow so rapidly? I created a new database 2 days ago, and already it has gone from 300 megabytes the first day to 3gb today. Usually, in a matter of 4-5 months, it grows to 30+ gb.
Is it normal for it to do this? Once it get's too large it starts to slow the nightly refresh of content down and causes it to take much longer. Also, it seems that when it gets large like that, there are noticeable bottlenecks on the SQL box.
If this is normal, is the solution just to create a new reporting database once in a while? Shrink it? What? I looked online and didn't see much info addressing this topic.

It all depends on the number of transactions is carried over the database. If space is going to be constraint
then take a log backup and shrink the log file.
Refer the below article
http://technet.microsoft.com/en-us/library/ms178037(v=sql.105).aspx
-Prashanth

How to fill depended Z-Table, created by Rapid Application Tool, with initial data?

Hello gurus,
I created a component ZBOOKING with RAD Tool and will fill booking detail table with initial data during a creation of new booking objekt.
My Booking component looks like on the picture below. It was created with Rapid Application Tool and is based on one ZBOOKING Table with was created in CRM Backend and one “Booking details” Table with was created with Rapid Application.
My Question is how should I populate initial Template-Data to this dependent “booking details” Table wenn I will create a new booking object.
Web UI of ZBooking component
Component structure of ZBooking
I have tried to do sample implementation in do_init_context method of ZACL_CLASS00000C_IMPL class to fill ZBOOKING_DETAILS with some data.
method DO_INIT_CONTEXT.
CALL METHOD SUPER->DO_INIT_CONTEXT.
DATA: lr_col TYPE REF TO if_bol_bo_col,
lr_valuenode TYPE REF TO cl_bsp_wd_value_node,
lr_template TYPE REF TO ZBOOKING_DETAIL.
CREATE DATA lr_template.
CREATE OBJECT lr_valuenode
EXPORTING
IV_DATA_REF = lr_template.
if lr_valuenode is BOUND.
lr_valuenode->SET_PROPERTY_AS_STRING(
iv_attr_name = 'ZZVISITDATE' "#EC NOTEXT
iv_value     = '01.01.2014'
ENDIF.
CREATE OBJECT lr_col TYPE cl_crm_bol_bo_col.
lr_col->ADD(
exporting
iv_entity = lr_entity
IV_SET_FOCUS = ABAP_TRUE
me->TYPED_CONTEXT->ZBOOKING_DETAIL->SET_COLLECTION( lr_col ).
endmethod.
After this implementation the initial data is displayed in “Booking details”.
However if I press an Edit-List-button (Assignment block) I get an error “CUST Operation”.
May be I should fill this depented table ZBOOKING_DETAILS without cl_bsp_wd_value_node?
Where should I implement logic if I want to fill initial data just during creation of booking object and not every
time when the booking object is called or initialized?
Regards Dmitry

Hi,
I get an error "Dereferencing of the NULL reference" during created_related_entity.
If you see on the picture below I think that I use right relation name for my zbooking_detail table.
method DO_INIT_CONTEXT.
CALL METHOD SUPER->DO_INIT_CONTEXT.
data :   lr_leading_entity TYPE REF TO cl_crm_bol_entity,
            lr_col TYPE REF TO if_bol_bo_col.
           lr_leading_entity->create_related_entity(
                  iv_relation_name = 'ZAET_CA_ATAB000000' ).
           lr_leading_entity->SET_PROPERTY_AS_STRING(
                       iv_attr_name = 'ZZVISITDATE' "#EC NOTEXT
                       iv_value     = '01.01.2014'
lr_col->ADD(
   exporting
     iv_entity = lr_leading_entity
     IV_SET_FOCUS = ABAP_TRUE
me->TYPED_CONTEXT->ZBOOKING_DETAIL->SET_COLLECTION( lr_col ).
endmethod.
Many Thanks & Regards,
Dmitry

Transporting Z table entries to QA and Prod

Hi Guys,
I have z table (has field MANDT) with delivery class A and no table maintenance in Dev box with 600 records. I need to delete 3 records and change 10 records and then transport them to QA and Prod. I am not adding new records.
I created one CUSTOMIZING transport.
I am using SE16 -> Table Entry -> Transport Entries. It is asking for workbench transport instead of Customizing transport.
Can I transport the deleted and changed entries using WORKBENCH transport?
Please help.
mini

Hi
Yes u can.
Max

Table ASO_ORDER_FEEDBACK_T growing fast in R12

Hi All,
In My R12 instance table ASO_ORDER_FEEDBACK_T is growing very fast. while checking on google sone one says to delete record from this table. Can some one suggest me some concurrent program/policy which can safely delete data from this.
Kindly advice.
Thanks
Krishna

Krishna Agnihotri wrote:
Hi All,
In My R12 instance table ASO_ORDER_FEEDBACK_T is growing very fast. while checking on google sone one says to delete record from this table. Can some one suggest me some concurrent program/policy which can safely delete data from this.
Kindly advice.
Thanks
KrishnaPlease see these docs.
Troubleshooting Issues With Maintaining ASO_ORDER_FEEDBACK_T Table [ID 946942.1]
Why Is The "Service Contracts Aso Queue Migration" Program Running For A Long Time (Slow)? [ID 1354422.1]
How to efficiently remove messages associated with an unwanted Recipient [ID 550274.1]
Troubleshooting Performance Problems in the OZF-TM:Funds Accrual Engine Due to the ASO_ORDER_FEEDBACK_T Queue [ID 470174.1]
Quoting/Order Capture Order Feedback Queue [ID 181410.1]
Thanks,
Hussein

Make the table status has modifiable in prod.

Hi All,
I need to make a Z* table has modifiable in production thru Sm30 , it says "Client 100 has status 'not modifiable', Actually the user needs to make some changes directly in prod. which is possible for other tables but not for this.
Please advice...

Hi,
At first , you should put the MANDT in your table, this is client number.
2nd, in tab"Delivery and Maintainance" , the delevery class choose "C" and data browser/Table view Maint choose "Display/Maintain allowed".
3rd, In Util->Table main generator, set the recording routine to "no, or user,recording routine".
That's all.
Hope it helps.
BR
Bob

WF_ITEM_ACTIVITY_STATUSES_H table is growing rapidly in PROD.

Similar Messages

Maybe you are looking for