ARCHIVE NOT DELETED

HI....
yesteday i had taken the scedule bakup (incremental level 2 with 'delete input' option)...
but it said that some of the archived no deleted....
so agian in the morning i took the archived log bakup with the command
RMAN> backup format 'd:\app\archbakup\feb3_%s_%t_%U.bkp' archivelog all delete i
nput;
so again it flashed back the error while taking the archived log backup...
RMAN> backup format 'd:\app\archbakup\feb3_%s_%t_%U.bkp' archivelog all delete i
nput;
Starting backup at 02-FEB-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=731 RECID=355 STAMP=741984037
input archived log thread=1 sequence=732 RECID=356 STAMP=741984043
input archived log thread=1 sequence=733 RECID=357 STAMP=741984111
input archived log thread=1 sequence=734 RECID=358 STAMP=741984159
input archived log thread=1 sequence=735 RECID=359 STAMP=741984204
input archived log thread=1 sequence=736 RECID=360 STAMP=741984225
input archived log thread=1 sequence=737 RECID=361 STAMP=741984255
input archived log thread=1 sequence=738 RECID=362 STAMP=741984271
input archived log thread=1 sequence=739 RECID=363 STAMP=742040853
input archived log thread=1 sequence=740 RECID=364 STAMP=742040927
input archived log thread=1 sequence=741 RECID=365 STAMP=742041046
input archived log thread=1 sequence=742 RECID=366 STAMP=742041092
input archived log thread=1 sequence=743 RECID=367 STAMP=742041131
input archived log thread=1 sequence=744 RECID=368 STAMP=742041172
input archived log thread=1 sequence=745 RECID=369 STAMP=742041212
input archived log thread=1 sequence=746 RECID=370 STAMP=742041436
input archived log thread=1 sequence=747 RECID=371 STAMP=742041595
input archived log thread=1 sequence=748 RECID=372 STAMP=742041761
channel ORA_DISK_1: starting piece 1 at 02-FEB-11
channel ORA_DISK_1: finished piece 1 at 02-FEB-11
piece handle=D:\APP\ARCHBAKUP\FEB3_40_742041762_18M3LA52_1_1.BKP tag=TAG20110202
T104241 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
channel ORA_DISK_1: deleting archived log(s)
archived log file name=D:\APP\ARCH\ARC00731_0740337093.001 RECID=355 STAMP=74198
4037
archived log file name=D:\APP\ARCH\ARC00732_0740337093.001 RECID=356 STAMP=74198
4043
archived log file name=D:\APP\ARCH\ARC00733_0740337093.001 RECID=357 STAMP=74198
4111
archived log file name=D:\APP\ARCH\ARC00734_0740337093.001 RECID=358 STAMP=74198
4159
archived log file name=D:\APP\ARCH\ARC00735_0740337093.001 RECID=359 STAMP=74198
4204
archived log file name=D:\APP\ARCH\ARC00736_0740337093.001 RECID=360 STAMP=74198
4225
archived log file name=D:\APP\ARCH\ARC00737_0740337093.001 RECID=361 STAMP=74198
4255
archived log file name=D:\APP\ARCH\ARC00738_0740337093.001 RECID=362 STAMP=74198
4271
archived log file name=D:\APP\ARCH\ARC00739_0740337093.001 RECID=363 STAMP=74204
0853
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00740_0740337093.001 thread=1 sequence=740
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00741_0740337093.001 thread=1 sequence=741
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00742_0740337093.001 thread=1 sequence=742
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00743_0740337093.001 thread=1 sequence=743
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00744_0740337093.001 thread=1 sequence=744
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00745_0740337093.001 thread=1 sequence=745
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00746_0740337093.001 thread=1 sequence=746
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00747_0740337093.001 thread=1 sequence=747
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=D:\APP\ARCH\ARC00748_0740337093.001 thread=1 sequence=748
Finished backup at 02-FEB-11
Starting Control File and SPFILE Autobackup at 02-FEB-11
piece handle=D:\APP\ANSARI.DILSHAD\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2011_02_0
2\O1_MF_S_742041824_6NKT0H4Y_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 02-FEB-11
so why rman not deleting the backup.....
thanks....

HI
thnks for usefull comment but i m using 11.1.0.6.0
RMAN> show all
2> ;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK; ----->bay be this one is creating issue ..any guess...
and also i think whn we take the backup of archived log on the same disk we need not to allocate channel...(.correct me here) and i am taking the backup on the same existig disk..
regards

Similar Messages

RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!

i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
Check the below queries.
Primary:-
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
Standby:-
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
HTH.

WARNING: archive log not deleted as it is still needed

Our Oralce Database is a single node database of version 10.1.0.
Dataguard/Standby is not configured.....we are executing the following command for archivelog backup
run
allocate channel c1 device type sbt;
backup archivelog all delete input;
This script is successfull in backingup all the archvied log files however it is not deleteing the input files. Instead it gives the warning....
"WARNING: archive log not deleted as it is still needed"
What could be the problem?

If you do a Metalink seach on "WARNING: archive log not deleted as it is still needed." you'll find a couple of documents that explain the issue.
The short answer is that RMAN has backed up logs which have not yet shipped to standby, so it won't delete them, cause they're still needed till they're successfully shipped to standby.
-Mark

PI 7.11 AAE- Archiving and deletion

Dear All,
I just want to get confirm on my understanding regarding AAE archiving and deletion.
We have 98% interfaces using only AAE in our landscape.
I had set up XMLDAS archiving for AAE ( After fixing so many issues ) which archives the AAE messages into the local file system. So no issues in that .
Now my requirements are,
1) I would like to keep only 7 days of data in the database and 100 days of data in the file system
2) I do not want to set up any rules for Archiving /Deletion. It means i would like to archive messages older than 7 days in the file system.
The steps are ( My understanding )
1) Set the persistence duration in NWA to 7 days . So only 7 days of data will be stored in table BC_MSG.
2) Set up the archival job in the background processing through RWB without ANY RULES. So all processed messages older than 7 days will be achieved in the file system. And Archive will come with default delete procedure as well hence Archived messages will be deleted from table BC_MSG.
3) Deactivate the delete job . If i have the active delete job in the background processing, it will delete all messages older than 7 days which i don want. The deletion of messages from BC_MSG will be taken care as part of archival job.
Is my understanding correct?
Thanks
Rajesh

Hello, any know what did they do to delete the files from the file system after 100 days?
We have the same problem, when we deleted manualy some messages from SO AIX but they still appear from the RWB, and when we clic over them we get an error: ...... java.lang.Exception: XML DAS GET command failed with ErrorCode: 598; ErrorText: 598 GET: Error while accessing resource; response from archive store: 598 I/O Error java.io.FileNotFoundException: /usr/sap/PID/javaarch/archive/usr/sap/pid/x
Is there any way to delete messages without generating errors / inconcistencias?

Archive and delete sap event management objects

Team, I need to configure the archiving objects and residence time to Archive and delete EM objects. there are three steps of configuration, and I have never done this before.
Can any one of you help me in setting up this config and the programs that need to run to archive and delete these objects.
I would really appreciate you help and quick response on this.
Define Archiving-Object-Specific Customizing
Define Residence Times for Archiving or Deleting
Define Settings for Deleting Document Flow
Thank you!!!

Hello Steffen,
I was told that it would be possible to display archived and deleted event handlers using BAPI /SAPTRX/BAPI_EH_GET_DATA_GEN. I tested it, but could not verify this statement. SAP Help reads:
"The archiving object /SAPTRX/A0 only supports a technical view in the Archive Explorer of the Archive Information System. This view is similar to the display in transaction SE16."
It would be great if you could help clarify this. Thank you!
Best regards,
Philiipp

How to do Archiving of deleted & disabled users in OIM11g

Hi All,
As per the requirement we have to do archive of deleted & disabled users in OIM11g(11.1.1.2) after 75days. Can i know how can i achieve this?
Regards,
user7609

Just to recap:
Your client requirement is to archive users out of OIM after 75 days. This means in addition to actually disabling and/or deleting them, fully removing any traces of them from the system.
As Kevin & GP said, OIM is just not built to do this. API alone is not going to accomplish this task... you'll also need to include SQL to actually drop data out of tables.
All that being said, your post said the reason for this was because of a "license for limited users". Oracle Identity Manager is licensed on an active user basis. You really should talk with your Oracle rep to confirm, but I've never had licensing contracts include deleted/disabled users.

I have not deleted ANY texts since I got my phone and Ihave not synched. I just can't scroll back in a thread to older texts. How can I get back to read those?

I have not deleted ANY texts since i got my phone 10 weeks ago. Nor have I syched. How can I go back to earlier texts in a thread to see them again?

I've found that the easiest way to view old texts is by archiving them to my computer using a program such as PhoneView (Mac) or TouchCopy (Mac or PC). I generally save important threads to a .pdf for future reference.

Question about Archive Log Deletion policy

I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
Messages of the database are in German, but I guess you'll understand them.
SQL> startup
ORACLE-Instance hochgefahren.
Total System Global Area 5344731136 bytes
Fixed Size                  2129240 bytes
Variable Size            2684355240 bytes
Database Buffers         2617245696 bytes
Redo Buffers               41000960 bytes
Datenbank mounted.
Datenbank geöffnet.
SQL> archive log list
Datenbank-Log-Modus              Archive-Modus
Automatische Archivierung             Aktiviert
Archivierungsziel            E:\oracle\thetis_iv\arch
Älteste Online-Log-Sequenz     17917
Nächste zu archivierende Log-Sequenz   17919
Aktuelle Log-Sequenz           17919
SQL> alter system switch logfile;
System wurde geändert.I created a brand new archive log.
SQL> exit
Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:04    <DIR>          .
06.04.2011 15:04    <DIR>          ..
06.04.2011 15:04        17.137.152 ARC17919_0721667907.001
               1 Datei(en),     17.137.152 Bytes
               2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
Kennwort für Recovery-Katalog-Datenbank:
Verbindung mit Datenbank des Recovery-Katalogs
RMAN> show all;
RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
Now I backup all archive logs, that havn't been backed up for at least two times.
RMAN> run { backup archivelog all not backed up 2 times
2>       format '%d_AR_%Y%M%D_%s_%t'
3>       tag 'ARCHIVE LOGS'
4>       DELETE ALL INPUT;
5>     }
Starten backup um 06.04.2011 15:08:01
Aktuelles Log archiviert
Zugewiesener Kanal: ORA_SBT_TAPE_1
Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
Beendet backup um 06.04.2011 15:08:10
RMAN> exit
Recovery Manager abgeschlossen.
D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:08    <DIR>          .
06.04.2011 15:08    <DIR>          ..
               0 Datei(en),              0 Bytes
               2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
Thats not what I expected. Where is my mistake?

Hi,
I do new tests it's very strange.
BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
You can open a SR on MOS. (to check bugs)
I reproduce the same test and the result was the same, it seems that this is a bug.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
RMAN> backup archivelog all not backed up 2 times delete all input;
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
Finished backup at 06-APR-11
RMAN> list archivelog all;
specification does not match any archived log in the repositoryOracle Docs Says:
The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
This command eliminates the separate step of manually deleting archived redo logs.
With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
As explained in "Configuring an Archived Redo Log Deletion Policy",
the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
But in ours case it's not honors this policy.
Only with the FORCE command should this happen. But it is not our case.
Oracle Docs:
If FORCE is not specified on the deletion commands,
then these deletion commands obey the archived log deletion policy.
If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
Alternatively you can do the following:
Set the commands separately.
Check this:
RMAN> run {
2> backup archivelog all not backed up 2 times ;
3> delete archivelog all backed up 2 times to disk;
4> }
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 06-APR-11
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

Archiving vs Deleting messages in PI/XI

Hi, I have successfully set up archiving on the PI system. No separate delete jobs are running, only the delete job in the connection with the archive process.
The questions is, will archiving delete and keep the DB from growing as good as the delete jobs would? Yes, the archive files need some space on the filesystem, but it seems that only archiving is enough to keep PI in a healthy state concerning the DB size. Am I correct?

Hi,
In XI All the data are transferred in form of messages and it may necessary to Archive data for future references .When we do the Archiving all the processed messages will be out of system and also it improves the performance. In General Rule the messages are multiplied into 10 times when compared to data which is sent,(Ex. If the data is 1 MB, the size of the message will be 10 MB.
Messages that have been processed correctly are deleted by default. You must archive all messages that are not to be deleted. Since correctly processed messages are flagged as either To Be Archived or To Be Deleted (and because this indicator cannot be changed), you must decide which messages you want to archive before the first message is processed.
History entries are spots for observing XML message processing. They are generated by persisting at the end of a processing step for an XML message and contain the current status and the execution date.
History entries remain in the database for an unspecified length of time and must be deleted at some stage so that the database table does not overflow. The deletion process only deletes history entries for XML messages that have already been archived or deleted. The history entry is kept in the database for at least seven days after an XML message has been deleted. This is necessary since history entries are also required for the quality of service Exactly Once.
The default retention period is 30 days.
Regards
Aashish Sinha
PS : reward points if helpful

After processing sender file is not deleting

Hi All,
I have configured the File-JDBC-File sync mode. the scenario is working fine upto last 2 days. but the problem is once the file picks and process its not deleting or archiving the file. but scenaio is working fine when i check in sxmb_moni but the error in sender file adaptor.
Could not delete file 'abc.dat' after processing: java.net.SocketException: Broken pipe.
in FTP server i have delete rights the other test scenario are working fine with out any error.
Please help me to reslove this issue.
Thanks,
Venkat

yes the processing mode is delete for sender communication chennal.
I have created the other test scenario to test the processing mode is delete its working for other communication chennal. and my scenario also worked upto last 2 days. i have done delta cache and also created the new communication chennal even no luck.
00:06:47 Success The message status set to DLNG.
22.04.2009 00:22:42 Success The application sent the message synchronously using connection File_http://sap.com/xi/XI/System. Returning to application.
22.04.2009 00:22:42 Success The message was successfully transmitted to endpoint http://SAPRtest.test.com:8047/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
22.04.2009 00:22:42 Success The message status set to DLVD.
22.04.2009 00:23:12 Error Attempt to delete file "abc.dat" after processing failed. Retry
Please help me to reslove this.
Thanks,
Venkat.

Messages are NOT deleted from tables XI_AF_MSG and XI_AF_MSG_AUDIT

Hello,
I set the retention period to 7 days (1 week)
I also set the default ARCHIVE and DELETE jobs and ALL are working fine.
However, messages with OLD dates are NOT deleted from the tables XI_AF_MSG and XI_AF_MSG_AUDIT.
These tables 32GB in the DBD table space.
I tried to use the URL:
http://<host>:<port>/MessagingSystem/archiving/reorgdb.jsp
BUT to NO avail.
How do I DELETE or ARCHIVE these messages ?
============================================
Here are some more details on the content of the tables (I took into account 1 MONTH retention):
db2 "select count(*) from sapxi3db.XI_AF_MSG_AUDIT where STATUS='SUCC' and TIME_STAMP < '2007-09-10 00:00:00'"
      28947
1 record(s) selected.
db2 "select count(*) from sapxi3db.XI_AF_MSG_AUDIT where STATUS='ERR' and TIME_STAMP < '2007-09-10 00:00:00'"
      13243
1 record(s) selected.
db2 "select count(*) from sapxipdb.XI_AF_MSG where PERSIST_UNTIL < '2007-09-10 00:00:00' and STATUS='NDLV'"
       1048
1 record(s) selected.
db2 "select count(*) from sapxipdb.XI_AF_MSG where PERSIST_UNTIL < '2007-09-10 00:00:00' and STATUS='DLVD'"
          0
1 record(s) selected.

Hi,
First, thank you VERY much for answering.
Now to your questions:
1. When using the URL:
http://<host>:<port>/MessagingSystem/archiving/reorgdb.jsp
    I did NOT get any ERROR messages.
    Thousands of messages where DELETED successfully.
    However, the number of rows in XI_AF_MSG_AUDIT did NOT reduce.
2. I used the default archiving and deletion customizations and jobs.
   However, I ran them manually a few times a day with NO change in the
   number of rows in XI_AF_MSG_AUDIT
   What do you mean by "customized any Archiving for adapter Engine" ?
. In RWB, I do see the default job is running
Have you customized any Archiving for adapter Engine or You are using default arciving which runs every 24 hrs.
3. I did ser the retention period for the adapter engine messages in visual admin in seconds...
Please, advise further.
Kind regards,
Gil

RMAN-08591: WARNING: invalid archived log deletion policy

Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,

kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
//         log deletion policy was APPLIED but there was no mandatory
//         archived log destinations.
// *Action: One of the following:
//          1) Change archived log deletion policy using CONFIGURE command
//          2) Make one or more of standby destination as MANDATORY.

Any RFC To Archive and Delete IDOC from XI?

hi,
Is there any standard RFC available which archives and deletes the IDOC?
In my scenario i have to delete the IDOC that has successfully transmistted an IDOC to a SOAP Receiver.
client's requirement is to delete the IDOC immediately instead of running a SAP batch program scheduled sometime later.
Let me know if there is one.
Thanks,
Tirumal

Vijaya -
I completely understand that scheduling the report every on a timely basis is the best way.
But you know if i were the manager i could have taken decisions but since i am not i have to do what the client says. No other way.
We will see.
Thanks for your patience and helpful answers.
- Tirumal

Sender FTP without Archive or delete

Hi All,
Has anyone tried using FTP sender channel without archiving or deleting .
Just read the file and continue.
The option seems to be not available in the comm channel.
Thanks
Bikram

Hi,
this is what the "Test" mode is doing, but it's recommended to avoid using it for productive systems.
Regards
Patrick

Archiving and deleting of equipment master data in plant maintenance module

Hi,
Can anyone explain me the process to archive and delete the equipment master data in PM module using archiving tools.
I tried doing it thru t-code SARA, would be grateful if anyone can help me with the steps to follow to archive the equipment master data.
Thanks in advance,

Many thanks for your reply,
I tried doing the same in IDES, but unfortunately the archive file is not getting generated when i write it. I have clearly specified in the variant to create an archive file. Can you please explain how does the system generate an archive file. And also in the customizing " Archiving Object-Specific Customizing " techincal settings, i have maintained the production variant and have marked start automatically.
Please advise,
thanks again ,

ARCHIVE NOT DELETED

Similar Messages

Maybe you are looking for