Archive Deletion Issue

Hi,
I have the following archive backup and maintenence scripts configured in my cron which run on a daily basis. How ever of late I faced an issue where in the archive destination got filled up. On check I found that there were archives that were older than 10 days in my system and I had to manually cross check them and get them deleted. Where as I expect not more than 3 days old archives to be available.
But I fail to understand as why those archive got piled up in the system where as they had to get deleted anyways by the maintenence script?
Only one thing I remember is that I had some network issue and the crons had not run for 5 days after which it had started to work.
Can some one tell me if there is any flaw in the script or configuration? Appreciate your help...
My Backup Script:
run
allocate channel n1t11 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/u/app/admin/ut.../tdpo.opt)';
allocate channel n2t22 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/u/app/admin/ut.../tdpo.opt)';
allocate channel n3t33 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/u/app/admin/ut.../tdpo.opt)';
allocate channel n4t44 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/u/app/admin/ut.../tdpo.opt)';
sql 'alter system archive log current';
backup archivelog all format 'archbkp_%d_set%s_piece%p_%T_%U';
+++++++++++++++++++++++++++++++++++++
My Maintenance Script:
run
allocate channel n1t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/u/app/admin/ut.../tdpo.opt)';
delete noprompt archivelog until time 'SYSDATE-2' backed up 1 times to device type sbt_tape;
crosscheck backup of database completed before 'SYSDATE-10';
crosscheck backup of ARCHIVELOG ALL completed before 'SYSDATE-2';
crosscheck backup of controlfile completed before 'SYSDATE-10';
crosscheck backup of spfile completed before 'SYSDATE-10';
delete noprompt expired backup of database completed before 'SYSDATE-10' device type sbt_tape;
delete noprompt expired backup of archivelog all completed before 'SYSDATE-2' device type sbt_type;
delete noprompt expired backup of controlfile;
delete noprompt expired backup of spfile;
delete noprompt obsolete recovery window of 10 days device type 'SBT_TAPE';
release channel n1t1;
+++++++++++++++++++++++++++++++++++++
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 10 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/u/app/admin/ut.../tdpo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u/app/oracle/ut.../snapcf_name.f'; # default

Similar Messages

Issue with Archiving & Deletion of messages in PI ,SXMB_MONI messages

Hello experts
I am working on Archiving & Deletion of messages in PI ,SXMB_MONI, i have fallowed all the steps which are avialable in /people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-2, but the messages still there in SXMB_MONI.
please help me to resolve this issue.
regards
chandra

Hi Krish
i have fallowed steps like....
in SXMB_ADM
>>>step 1: Define the interface for archivng and retnetion period
>>>step2):Schedule Archive Jobs,
after this i have checked the in SM37 the jobs got sheduled and released after that it showing finished.
>>>step3):ARV_BC_XMB_WRP<date> (archiving, step 1)
ARV_BC_XMB_DEL<date> (archiving, step 2)
here i am getting message like "0 XML messages got archived".
"0 XML message for deleated".
I have doubt in SXMBPMAST table here when i check the status of interface , ITFACTION field is containing the value INIT and if I understood correctly it job deletes only those messages where ITFACTION is set to DEL.
We are actually trying to delete the messages avoiding archiving but what I am seeing is we cannot delete error messages and for them we must have to go through archiving. Please correct me if I am wrong.
Thanks
Chandra

RSEXARCD: Idoc archiving deletion program issues

Hi,
I have two queries:
1. The Idoc archive deletion program, RSEXARCD, when executed in background, terminates when there are no archive files to process (as seen in SARA). How can we prevent this? Our deletion jobs are scheduled weekly, but sometimes there are no archive files created from the archive write program RSEXARCA.
2. Secondly, how can we process multiple archive files using this program RSEXARCD in background? Currently, it processes only one archive file at a time and takes up the oldest unprocessed archive file. Also, would like to know how it gets this information of the oldest unprocessed archive file?
Thanks.

if a program terminates, then you should look into the dump to see the root cause and follow the instructions. e.g. search for OSS notes with the metioned terms
I just searched with the terms "archiving idocs termination" and found 12 notes with program fixes.
Further, the program names you mentioned are not the most recent programs.
Have a look into OSS note Note 582828 - IDoc archiving: Standardization
maybe you will not have your problems anymore if you use the new programs

Issue about GP Archive&Delete functionality

Hi,
When using Guided Procedures in the Portal, how can I found out were the GP Archive&Delete functionality (to clean up old proccess instances) is porformed?
Cheers,
Fernando

Hi,
If you are looking for the tool to perform Archiving and Deletion management of GP processes, then below would he help link for your reference.
[http://help.sap.com/saphelp_nw70/helpdata/en/a4/114a42a597b430e10000000a155106/frameset.htm]
If this is not what you are looking for then kindly provide more details on your query.
Thanks & Regards,
Swapna Priya.

RMAN BACKUPS AND ARCHIVED LOG ISSUES

제품 : RMAN
작성날짜 : 2004-02-17
RMAN BACKUPS AND ARCHIVED LOG ISSUES
=====================================
Scenario #1:
1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
database는 두 개의 archive destination에 archive file을 생성한다.
다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
run {
allocate channel c1 type 'sbt_tape';
backup database;
backup archivelog all delete input;
Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
같은 메시지가 발생함.
RMAN> change archivelog all crosscheck;
RMAN-03022: compiling command: change
RMAN-06158: validation succeeded for archived log
RMAN-08514: archivelog filename=
/oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
2) 원인분석
이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
archived log file들은 삭제되지 않고 남게 되는 것이다.
3) 해결책
RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
백업하고 삭제하도록 해야 한다.
이것은 아래와 같이 구현될 수 있다.
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
backup
archivelog like '/oracle/arch/dest1/%' channel t1 delete input
archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
Scenario #2:
1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
이 시나리오에서 database를 incremental backup한다고 가정한다.
이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
RMAN-6089: archive log NAME not found or out of sync with catalog
2) 원인분석
이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
3) 해결책
가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
예를 들면
run {
allocate channel c1 type 'sbt_tape';
backup archivelog all delete input;
두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
RMAN>allocate channel for maintenance type disk;
RMAN>change archivelog all crosscheck;
Oracle 8.0:
RMAN> change archivelog '/disk/path/archivelog_name' validate;
Oracle 8i:
RMAN> change archivelog all crosscheck ;
Oracle 9i:
RMAN> crosscheck archivelog all ;
catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
RMAN> connect target /
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters are successfully stored
RMAN>
----------------------------------------------------------------------------------

PI 7.1 Archiving - Delete

hi Team,
We have PI 7.1 production environment and planning to implement ARCHIVING & DELETE for Integration Engine, Adapter Engine and Business Process Engine based messages.
I had referred to 'How to arhive & delete' doc that highly available in SDN but few question after going through the doc.
1. If a interface flagged for ARCHIVING then all messages in complete message status gets automatically Archived
2. And if interface not flagged for ARCHIVING then all messages of those interfaces gets automatically Deleted
Ofcourse on these both the cases, the corresponding action takes place only provided the retention period candition meets.
1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
4. Either Archiving or Delete mechanism has any dependance or functional variations on Synchronous and Asysnchronous?
I highly appriciate all those add their knowledge here to clarify
Regards
Sekhar

Dear Sekhar,
let me go through your questions step by step...
1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
This is almost correct. Canceling is required for asynchonous messages in error state only. By canceling a message its state changes from error to final and this it is allowed to be archived. In contrast synchronous messages are final right when processing fails.
Please note: archiving applies to asynchronous messages only. It is a general decision by SAP to not archive synchronous messages.
2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
Once an asynchronous message enters the central Intergation Server(IS) or the local Integration Engine(IE) XI/PI takes over responsibility for this message. Canceling a message means a serious violation of the EO/EOIO protocol. This violation needs to be documented in productive environments for the purpose of tracebility.
3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
I am not quite sure that I got the point. For each message entering the IS/IE SAP has to provide a guided procedure to reorganize this message. For successfully processed messages this is done by standard house-keeping jobs for archivng and deletion. For messages in error state there are basically two ooptions:
(1) restert message after error has been fixed;
- if message processing is sucessful this time, we are back to normal
- if message processing fails again, we are in the very same siutation as before
(2) cancel messages; this males the message 'final' and then it is treated like sucessfully processed messages.
Thus, this is all about defining an end point in the lifecycle of each message.

Message archiving/deletion in PI 7.1

Hi All,
I'm new to SAP PI. We have newly implemented PI 7.1 in our landscape. We have installed PI in HP UX 23 with oracle as the database.
We have configured the messge archival/deletion in our PI production server. We have allocated a dedicated file system to store the archived messages. Eventhough we have maintained the path of the archival_interface, no messages are archived in this drectory.
We are using synchronous interfaces and while executing the report ( RSXMB_SHOW_REORG_STATUS ) as per the note 872388, the report says that there are more than 1700 messages to be archived. But no messages are getting archived in the path mention as of now.
I think we have missed out some steps while configuring the archiving process. Can somebody help me with the steps involved in PI integration engine message archival/deletion.
Your timely help will be much appreciated.
Thanks in advance.
Regards,
Varadhu

Hi,
Go to transaction "SXMB_ADM" on the ABAP stack of your XI installation. Go to "Integration Engine Configuration" and click on tab "Specific configuration". Check if you have the parameter "LOGGING_SYNC" enabled (It should have a value 1). In case it is not present, please create this entry and have the default value as "1". This will enable you to view all sync messages on sxmb_moni.
Thanks,
Sidhartha

Archival/Deletion of messages in XI 3.0 SP23

Dear All,
We need to carry out a data deletion/purging activity at our XI box, where no archival/deletion policy has been incorporated ever. As a preparatory measure, I need to have some guidelines for the activities as under,
1. While defining an Archival policy, is there any recomendation from SAP or others that message archival exercise has to be carried out first, before proceeding with message deletion? To be more precise, can we directly delete/purge the messages without archiving them? What will be the impact of such an exercise on the XI system?
This point may sound confusing but the reality is that we do not have enough H/W to carry out an activity of Archival and Deletion.
2. What is the SAP recomendation/best practice in this regard?
3. Although we are defining the Archival/Deletion policy now, we need to purge data that is 3 years old and we do not require them any more. What would be the best practice to carryout this activity?
Thanks and regards,
Sugata Basu

Hi Sugatada,
is there any recomendation from SAP or others that message archival exercise has to be carried out first, before proceeding with message deletion?
No as per my knowledge..
can we directly delete/purge the messages without archiving them? What will be the impact of such an exercise on the XI system?
This wholly depends on requirement...if the data is too old...you can directly delete it..no need to archieve..
What is the SAP recomendation/best practice in this regard?
you can set these values which close to best practice...
Retention period for both synch and asynch
msgs without error awaiting deletion : 180 days
msgs without error awaiting archieving : 45 days
retention period for history entris for deleted msgs : 30 days
in XI we have 2 types of action:
(1) deletion of XML messages (without prior archiving)
(2) archiving of XML messages with subsequent deletion
SAP_BC_XMB_DELETE* for type (1)
SAP_BC_XMB_ARCHIVE* for type (2)
Regds,
Pinangshuk.

Seeburger message tracking archiving / deleting question

Hello,
We are using Seeburger 1.7 with XI 7.0 for our EDI translations..We store information in Seeburger Message Tracking for our business requirements.I would like to know how these entries could be archived(Compressed) and stored or deleted after certain days so that we wont max up our storage..?
Any suggestions are appreciated.
Thanks in advance!
Larry

Prateek,
Thanks for your response.Yes,I could find the "Archive Configuration" option..when I click that it shows me a screen saying show master data with two items with check boxes (Document Types & Archiving Systems)..On clicking the details of them I see set of parameters which shows the profile and the document type..not sure how to proceed from here to set up any archiving / deletion..any help is appreciated..
Regards,
Larry.

Archive / Delete Q-INFO records

Hello ,
Which object in sara code should i use/create to archive/delete Q info records ?
Thx in advance .

Hi
I am not very sure about archiving of the Quality info record but
Deletion is possible only by putting the Deletion Indicator to the same in T code QI02 screen -->"deletion Screen"
I hope this will add some value.
Regards
Sujit

Archiving & Deleting the Cost center line items

My requirement is to delete the line items in the cost cneter as of today, but when i tried to archive & delete the Cost center line items using CO_item,i aam sucesfull in deleteing the past data, but the data of the last month and currenct month i was unable to ........
when i tried in the spro>img>controlling>general ontrolling>archiving>prepare archiving for co line items
i set the resident time to 0,but i was unable to delete the line items.what colud be the reason and what is the way to delete the currenct data also from the system.
your earlier reply surely appreciated .......

Hi Rajesh,
I think SAP help says that the period for which you are planning to delete or archive data may have to be locked.
Check the following links:
For Archiving
http://help.sap.com/saphelp_47x200/helpdata/en/8d/3e55ec462a11d189000000e8323d3a/frameset.htm

Apple to resolve my archive utility issue

Apple has to resolve my archive utility issue with the error message Error 32: Broken Pipe. Apple says I have to re-install the Yosemite 10.10.2 software. I am totally against re-installing the software for the simple reason that Archive Utility is "untar" the files with tar.gz file. I am really unable to download and install some of the software that comes with tar.gz extension. It is really frustrating.
Apple has opened the case but since they told me to re-install the software which I declined and advised them to close my case.
I want to talk with Apple Software Engineer team but Apple said they could not connect me with their Software Engineer Team.
With regards,
Vasu

So, what do you expect us to do? We can't contact the Apple Software Engineering team, either.
If you don't want to reinstall to get Archive Utility working again, use tar in the Terminal. Type man tar at the prompt for help on using it.

Setting up archive delete functionalities using background job

Hi,
Through SARA transaction there we can set up a archive delete job by selecting the files, job timing details. Instead of this, we want to set up this functionality using a background job as per the variant and timing requirements.
Is there any option to set up a background job of archive delete functionality by selecting the files through a program or function moduel. Please suggest me if anyone has done this in previous.
Thanks,
Siva

Hello,
Take a look at OSS note 205585 which describes how to schedule archive delete jobs indirectly using program RSARCHD.
Hope this helps.
Best Regards,
Karin Tillotson

Online Archive - Deleted Items Folder

Hello,
I have setup retention policy and tags. It seems to be working okay, almost. A default retention tag applies which archives items after one year. This seems to be working ok for folders such as inbox, and sent. However, it does not
seem to be working for the deleted items folder.
I've also created personal tags to archive after various periods. Users try to apply those personal tags to the Deleted Items folder, but the managementAssistent never listens to that personal tag on the deleted items folder. Personal tags do
work for other folder (custom and inbox, etc). And the managementAssistant does run as expected... just not on the deleted items folder. This happens for another (6 month personal tag to archive deleted items folder), and same for my mailbox (1
week personal tag to archive deleted items folder).
Any suggestions?
Drew

Hi,
Deleted items folder is managed by "Deleted Item Retention" Either on DB level or mailbox level
http://technet.microsoft.com/en-us/library/ee364752(v=exchg.141).aspx

Restrict user from deleting issued component in Tcode CN22

1) In T Code - CN22 user can delete issued components ( thru movt type - 281 ) how this can be restricted .
2) Deletion indicator for deleted component not seen in CN22.
Pls tell me what are the settings required to set deleted component indicator on.

Hi,
In OPSG u can restrict deletion of withdrawn material component as error....

Archive Deletion Issue

Similar Messages

Maybe you are looking for