Message archival process in XI

Hi,
Could you please let me know if there is any standard process (like scheduling batchjobs to run at predefines frequency) for archiving old messages that were successfully processed in XI. Do we have to write any ABAP code for this or standard jobs/functions already available in XI.
Please share any documentation that you might have on this.

Below is the link
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50</a>

Similar Messages

MULTIPLE ARCHIVER PROCESSES FAQ ( ORACLE 8I NEW FEATURE )

제품 : ORACLE SERVER
작성날짜 : 2002-04-19
MULTIPLE ARCHIVER PROCESSES FAQ ( ORACLE 8I NEW FEATURE )
=========================================================
PURPOSE
1. LOG_ARCHIVE_MAX_PROCESSES가 하는 역할
2. LOG_ARCHIVE_MAX_PROCESSES 값은 동적으로 변경 가능한지 여부
3. Archiver process의 갯수가 동적으로 바뀌는 메카니즘
4. 어떤 archiver process가 online log를 archive시켰는지 판단 방법
Explanation
1. LOG_ARCHIVE_MAX_PROCESSES가 하는 역할
Oracle 8i에는 다중 archive destination을 지원하며, 단일 archiver의
부하를 줄여주기 위해 multiple archiver process를 사용할 수 있다.
LOG_ARCHIVE_MAX_PROCESSES 파라미터로 구동시킬 최대 ARCH 프로세스의
갯수를 지정하면 된다.
만약 LOG_ARCHIVE_START 값이 TRUE로 지정되어 있다면 인스턴스 구동시
init 파일에 지정된 LOG_ARCHIVE_MAX_PROCESSES에 지정된 값을 읽어
들인다. 만약 LOG_ARCHIVE_START 값이 true인데 LOG_ARCHIVE_MAX_PROCESSES
값이 별도로 지정되어 있지 않을 경우에는 arc0 프로세스만을 구동시킨다.
LOG_ARCHIVE_MAX_PROCESSES 값이 별도로 지정되었을 경우 (1 - 10 범위),
arc0, arc1 과 같은 추가 프로세스를 구동시킨다.
하지만, 이 파라미터 값을 기본값 1이 아닌 다른 값으로 명시적으로 지정할
필요는 없다. 왜냐하면, 시스템에서 몇개의 ARCn 프로세스가
필요한지를 판단하여, 추가 ARCn 프로세스를 생성하기 때문이다.
2. LOG_ARCHIVE_MAX_PROCESSES 값은 동적으로 변경 가능한지 여부
alter system 명령에서 set LOG_ARCHIVE_MAX_PROCESSES=n 으로
지정하여 동적으로 값을 변경할 수 있다. 이때 n은 1 부터 10사이의
값이어야 한다. 하지만, LOG_ARCHIVE_START 값이 FALSE로 지정되어
있을 경우에는, 명령을 실행시켜도 아무런 영향을 미치지
못한다.
3. Archiver process의 갯수가 동적으로 바뀌는 메카니즘
만약 LOG_ARCHIVE_START 값이 TRUE로 지정되어 있다면, 오라클에서는
구동시 하나의 archiver process (ARC0)를 구동시킨다. 이 파라미터
값은 필요시 LATER SYSTEM 명령으로 지정된 갯수만큼의
archive process를 구동시킬 수 있다.
예)
SVRMGRL>alter system set LOG_ARCHIVE_MAX_PROCESSES=4;
위 명령을 실행 시키면 다음과 같은 절차에 따라 ARC1, ARC2, ARC3를
추가한다.
1) Shadow process는 primary archive process에게 프로세스 갯수를
늘릴 것을 요청한다.
2) Archiver process는 kcrrschd 함수를 호출한다. (kcrrschd:
다중 arch process를 schedule)
3) 만약 요청된 process의 갯수가 현재 사용중인 archiver process
갯수보다 작은지 확인한다. 만약 새로 지정된 값이 적거나, ARCHIVING이
DISABLE 된 상태라면 다른 조치를 취하지 않고 return 한다. 그렇지
않다면 지원되는 최대 갯수인 10을 넘는지 확인하고 10을 넘을 경우에는
프로세스의 갯수를 10으로 지정한다.
4) Scheduler 함수는 kcrxs{} structure에 대한 latch를 확보한다.
여기서 kcrxs{} structure는 ARCH Activation status를 나타낸다.
5) Scheduler 함수는 지정된 process 갯수 만큼 loop를 돌면서
schedule된 상태를 structure KCRRSCHED에 반영시킨다.
6) 그리고 나서 latch를 release 시킨 후 kcrrsmp 함수를 ( kcrrsmp:
다중 arch processs 구동 ) 호출한다.
7) kcrrsmp 함수는 kcrrxs{} structure (ARCH 구동 상태)에 대한 latch를
확보하여 code 실행을 serialize 시켜 이 함수가 동시에 실행되더라도
한번에 하나씩 실행될 수 있도록 한다.
8) pending 상태에 있는 archiver process를 스케쥴링 하고, dead process가
있으면 clean up 시킨다.
9) 그리고 나서 이 함수는 지정된 process 갯수 만큼 loop를 돌면서
KCRRSCHED 상태를 KCRRSTART으로 바꾸어, archiver process들을
구동 준비 상태로 만든다.
10) latch를 release 시킨 후 ARCH 프로세스를 구동시킨다.
11) kcrrsmp함수는 latch를 다시 획득한다. 각각의 archiver 프로세스는
자기 자신을 activate 시킬 것을 통보 받는다. archiver process는
자기 자신을 activate 시킨 후 alert file에 관련 사항을 기록한다.
12) 호출을 하는 함수는 모든 archiver process가 자기 자신을
activate 시키고, kcrrxs structure의 내용을 갱신할 때 까지
sleep 상태에서 대기한다.
13) 끝으로, 현재 archiver process의 갯수가 요청된 archiver process
의 갯수와 일치 하면, latch를 release 시키고 break 한다. ( C
에서의 break )
alert. log 에는 위 과정이 다음과 같이 반영된다.
sql: prodding the archiver
ALTER SYSTEM SET log_archive_max_processes=4;
Tue Jul 13 02:15:14 1999
ARC0: changing ARC1 KCRRNOARCH->KCRRSCHED
ARC0: changing ARC2 KCRRNOARCH->KCRRSCHED
ARC0: changing ARC3 KCRRNOARCH->KCRRSCHED
ARC0: STARTING ARCH PROCESSES
ARC0: changing ARC1 KCRRSCHED->KCRRSTART
ARC0: changing ARC2 KCRRSCHED->KCRRSTART
ARC0: changing ARC3 KCRRSCHED->KCRRSTART
ARC0: invoking ARC1
Tue Jul 13 02:15:15 1999
ARC1: changing ARC1 KCRRSTART->KCRRACTIVE
Tue Jul 13 02:15:15 1999
ARC0: Initializing ARC1
ARC0: ARC1 invoked
ARC0: invoking ARC2
ARC1 started with pid=10
ARC1: Archival started
Tue Jul 13 02:15:15 1999
ARC2: changing ARC2 KCRRSTART->KCRRACTIVE
Tue Jul 13 02:15:15 1999
ARC0: Initializing ARC2
ARC2 와 ARC3도 동일한 절차를 따른다.
흥미로운 사실은 프로세스의 갯수를 줄일 수도 있다는 것이다. 예를 들어
다음과 같은 명령을 실행시킬 경우
SVRMGRL>alter system set LOG_ARCHIVE_MAX_PROCESSES=2;
다음과 같은 작업이 순서대로 실행된다.
1) shadow process는 현재 active 상태인 archiver process와 접속을 한다.
2) archiverprocess는 kcrrxmp 함수를 호출한다. ( kcrrxmp: 다중
Arch process 정지 )
3) kcrrxmp 함수는 kcrrxs{} structure에 (ARCH 구동 상태) 대한 latch를 획득하여 다른 프로세스에서 structure를 동시에 병경하지 않도록 한다.
4) 새로 요청된 archiver process의 갯수가 현재 사용중인 archiver process
의 갯수보다 작은지 확인한다.
5) 만약 작다면, archiver process 목록 가운데, 가장 최근에 schedule
되어, archival 작업에 schedule 차례가 금방 돌아 오지 않을 프로세스를
찾아낸다.
6) 각각의 프로세스에 대해 KCRRACTIVE 상태에서 KCRRSHUTDN로 상태를
변경할 것을 요청한다.
7) 상태가 바뀌면, OS에서 해당 프로세스를 종료시키도록 하고, 상태를
KCRRDEAD로 바꾼다. 관련된 상태 정보가 정리되고 kcrrxs{} structure의
내용이 갱신된다.
6) ,7) 과정은 지정된 archiver process 갯수로 줄어들 때 까지
반복된다.
8) 새로운 archiver process의 갯수로 kcrrxs structure 내용이 갱신된다.
9) latch를 release 시킨다.
상태 변동은 다음과 같이 alert. log 파일에 반영된다.
sql: prodding the archiver
Tue Jul 13 00:34:20 1999
ARC3: changing ARC0 KCRRACTIVE->KCRRSHUTDN
ARC3: sending ARC0 shutdown message
ARC3: changing ARC1 KCRRACTIVE->KCRRSHUTDN
ARC3: sending ARC1 shutdown message
ARC3: received prod
Tue Jul 13 00:34:20 1999
ALTER SYSTEM SET log_archive_max_processes=2;
Tue Jul 13 00:34:20 1999
ARCH shutting down
ARC0: Archival stopped
ARC0: changing ARC0 KCRRSHUTDN->KCRRDEAD
Tue Jul 13 00:34:20 1999
ARCH shutting down
ARC1: Archival stopped
ARC1: changing ARC1 KCRRSHUTDN->KCRRDEAD
4. 어떤 archiver process가 online log를 archive시켰는지 판단 방법
Archiver process는 round-robin 방식으로 archiving 작업을 수행하도록
schedule 된다. 만약 다중 archiver process가 부하에 따라 activate 된
경우는 여러가지 경우의 수가 있을 수 있다. Oracle 8i에서는 다중
archive log dest를 지원하면서 archive log에 대한 duplexing을 지원
하기 때문에, 어떤프로세스가 log file을 archive 시켰는지를 기록할 필요가
있다.
Oracle 8i에서 archival 작업은 성공할 때 마다 trace file에 archiver
process 명을 기록한다.
다음은 관련 trace file의 주요 내용이다.
Instance name: v815
Redo thread mounted by this instance: 1
Oracle process number: 12
Unix process pid: 3658, image: oracle@oracle8i (ARC3)
*** Session ID:(12. 1) 1999. 07. 13. 02. 15. 15. 000
*** 1999. 07. 13. 02. 15. 15. 000
*** 1999. 07. 13. 02. 33. 06. 000
ARC3: Begin archiving log# 1 seq# 38 thrd# 1
ARC3: VALIDATE
ARC3: PREPARE
ARC3: INITIALIZE
ARC3: SPOOL
ARC3: Creating archive destination 1 : '/bigdisk/oracle8i/dbs/arch/1_38.
dbf'
ARC3: Archiving block 1 count 1 to : '/bigdisk/oracle8i/dbs/arch/1_38.
dbf'
ARC3: Closing archive destination 1 : /bigdisk/oracle8i/dbs/arch/1_38.
dbf
ARC3: FINISH
ARC3: Archival success destination 1 : '/bigdisk/oracle8i/dbs/arch/1_38.
dbf'
ARC3: COMPLETE, all destinations archived
ARC3: ArchivedLog entry added: /bigdisk/oracle8i/dbs/arch/1_38. dbf
ARC3: ARCHIVED
*** 1999. 07. 13. 02. 33. 06. 000
ARC3: Completed archiving log# 1 seq# 38 thrd# 1
이 정보를 가지고, archive process 3이 log sequence 38번을
destination 1 :/bigdisk/oracle8i/dbs/arch 에 archive 시킨 것을 알 수 있다.
Reference Ducumment
<Note:73163.1>

제품 : ORACLE SERVER
작성날짜 : 2002-04-19
MULTIPLE ARCHIVER PROCESSES FAQ ( ORACLE 8I NEW FEATURE )
=========================================================
PURPOSE
1. LOG_ARCHIVE_MAX_PROCESSES가 하는 역할
2. LOG_ARCHIVE_MAX_PROCESSES 값은 동적으로 변경 가능한지 여부
3. Archiver process의 갯수가 동적으로 바뀌는 메카니즘
4. 어떤 archiver process가 online log를 archive시켰는지 판단 방법
Explanation
1. LOG_ARCHIVE_MAX_PROCESSES가 하는 역할
Oracle 8i에는 다중 archive destination을 지원하며, 단일 archiver의
부하를 줄여주기 위해 multiple archiver process를 사용할 수 있다.
LOG_ARCHIVE_MAX_PROCESSES 파라미터로 구동시킬 최대 ARCH 프로세스의
갯수를 지정하면 된다.
만약 LOG_ARCHIVE_START 값이 TRUE로 지정되어 있다면 인스턴스 구동시
init 파일에 지정된 LOG_ARCHIVE_MAX_PROCESSES에 지정된 값을 읽어
들인다. 만약 LOG_ARCHIVE_START 값이 true인데 LOG_ARCHIVE_MAX_PROCESSES
값이 별도로 지정되어 있지 않을 경우에는 arc0 프로세스만을 구동시킨다.
LOG_ARCHIVE_MAX_PROCESSES 값이 별도로 지정되었을 경우 (1 - 10 범위),
arc0, arc1 과 같은 추가 프로세스를 구동시킨다.
하지만, 이 파라미터 값을 기본값 1이 아닌 다른 값으로 명시적으로 지정할
필요는 없다. 왜냐하면, 시스템에서 몇개의 ARCn 프로세스가
필요한지를 판단하여, 추가 ARCn 프로세스를 생성하기 때문이다.
2. LOG_ARCHIVE_MAX_PROCESSES 값은 동적으로 변경 가능한지 여부
alter system 명령에서 set LOG_ARCHIVE_MAX_PROCESSES=n 으로
지정하여 동적으로 값을 변경할 수 있다. 이때 n은 1 부터 10사이의
값이어야 한다. 하지만, LOG_ARCHIVE_START 값이 FALSE로 지정되어
있을 경우에는, 명령을 실행시켜도 아무런 영향을 미치지
못한다.
3. Archiver process의 갯수가 동적으로 바뀌는 메카니즘
만약 LOG_ARCHIVE_START 값이 TRUE로 지정되어 있다면, 오라클에서는
구동시 하나의 archiver process (ARC0)를 구동시킨다. 이 파라미터
값은 필요시 LATER SYSTEM 명령으로 지정된 갯수만큼의
archive process를 구동시킬 수 있다.
예)
SVRMGRL>alter system set LOG_ARCHIVE_MAX_PROCESSES=4;
위 명령을 실행 시키면 다음과 같은 절차에 따라 ARC1, ARC2, ARC3를
추가한다.
1) Shadow process는 primary archive process에게 프로세스 갯수를
늘릴 것을 요청한다.
2) Archiver process는 kcrrschd 함수를 호출한다. (kcrrschd:
다중 arch process를 schedule)
3) 만약 요청된 process의 갯수가 현재 사용중인 archiver process
갯수보다 작은지 확인한다. 만약 새로 지정된 값이 적거나, ARCHIVING이
DISABLE 된 상태라면 다른 조치를 취하지 않고 return 한다. 그렇지
않다면 지원되는 최대 갯수인 10을 넘는지 확인하고 10을 넘을 경우에는
프로세스의 갯수를 10으로 지정한다.
4) Scheduler 함수는 kcrxs{} structure에 대한 latch를 확보한다.
여기서 kcrxs{} structure는 ARCH Activation status를 나타낸다.
5) Scheduler 함수는 지정된 process 갯수 만큼 loop를 돌면서
schedule된 상태를 structure KCRRSCHED에 반영시킨다.
6) 그리고 나서 latch를 release 시킨 후 kcrrsmp 함수를 ( kcrrsmp:
다중 arch processs 구동 ) 호출한다.
7) kcrrsmp 함수는 kcrrxs{} structure (ARCH 구동 상태)에 대한 latch를
확보하여 code 실행을 serialize 시켜 이 함수가 동시에 실행되더라도
한번에 하나씩 실행될 수 있도록 한다.
8) pending 상태에 있는 archiver process를 스케쥴링 하고, dead process가
있으면 clean up 시킨다.
9) 그리고 나서 이 함수는 지정된 process 갯수 만큼 loop를 돌면서
KCRRSCHED 상태를 KCRRSTART으로 바꾸어, archiver process들을
구동 준비 상태로 만든다.
10) latch를 release 시킨 후 ARCH 프로세스를 구동시킨다.
11) kcrrsmp함수는 latch를 다시 획득한다. 각각의 archiver 프로세스는
자기 자신을 activate 시킬 것을 통보 받는다. archiver process는
자기 자신을 activate 시킨 후 alert file에 관련 사항을 기록한다.
12) 호출을 하는 함수는 모든 archiver process가 자기 자신을
activate 시키고, kcrrxs structure의 내용을 갱신할 때 까지
sleep 상태에서 대기한다.
13) 끝으로, 현재 archiver process의 갯수가 요청된 archiver process
의 갯수와 일치 하면, latch를 release 시키고 break 한다. ( C
에서의 break )
alert. log 에는 위 과정이 다음과 같이 반영된다.
sql: prodding the archiver
ALTER SYSTEM SET log_archive_max_processes=4;
Tue Jul 13 02:15:14 1999
ARC0: changing ARC1 KCRRNOARCH->KCRRSCHED
ARC0: changing ARC2 KCRRNOARCH->KCRRSCHED
ARC0: changing ARC3 KCRRNOARCH->KCRRSCHED
ARC0: STARTING ARCH PROCESSES
ARC0: changing ARC1 KCRRSCHED->KCRRSTART
ARC0: changing ARC2 KCRRSCHED->KCRRSTART
ARC0: changing ARC3 KCRRSCHED->KCRRSTART
ARC0: invoking ARC1
Tue Jul 13 02:15:15 1999
ARC1: changing ARC1 KCRRSTART->KCRRACTIVE
Tue Jul 13 02:15:15 1999
ARC0: Initializing ARC1
ARC0: ARC1 invoked
ARC0: invoking ARC2
ARC1 started with pid=10
ARC1: Archival started
Tue Jul 13 02:15:15 1999
ARC2: changing ARC2 KCRRSTART->KCRRACTIVE
Tue Jul 13 02:15:15 1999
ARC0: Initializing ARC2
ARC2 와 ARC3도 동일한 절차를 따른다.
흥미로운 사실은 프로세스의 갯수를 줄일 수도 있다는 것이다. 예를 들어
다음과 같은 명령을 실행시킬 경우
SVRMGRL>alter system set LOG_ARCHIVE_MAX_PROCESSES=2;
다음과 같은 작업이 순서대로 실행된다.
1) shadow process는 현재 active 상태인 archiver process와 접속을 한다.
2) archiverprocess는 kcrrxmp 함수를 호출한다. ( kcrrxmp: 다중
Arch process 정지 )
3) kcrrxmp 함수는 kcrrxs{} structure에 (ARCH 구동 상태) 대한 latch를 획득하여 다른 프로세스에서 structure를 동시에 병경하지 않도록 한다.
4) 새로 요청된 archiver process의 갯수가 현재 사용중인 archiver process
의 갯수보다 작은지 확인한다.
5) 만약 작다면, archiver process 목록 가운데, 가장 최근에 schedule
되어, archival 작업에 schedule 차례가 금방 돌아 오지 않을 프로세스를
찾아낸다.
6) 각각의 프로세스에 대해 KCRRACTIVE 상태에서 KCRRSHUTDN로 상태를
변경할 것을 요청한다.
7) 상태가 바뀌면, OS에서 해당 프로세스를 종료시키도록 하고, 상태를
KCRRDEAD로 바꾼다. 관련된 상태 정보가 정리되고 kcrrxs{} structure의
내용이 갱신된다.
6) ,7) 과정은 지정된 archiver process 갯수로 줄어들 때 까지
반복된다.
8) 새로운 archiver process의 갯수로 kcrrxs structure 내용이 갱신된다.
9) latch를 release 시킨다.
상태 변동은 다음과 같이 alert. log 파일에 반영된다.
sql: prodding the archiver
Tue Jul 13 00:34:20 1999
ARC3: changing ARC0 KCRRACTIVE->KCRRSHUTDN
ARC3: sending ARC0 shutdown message
ARC3: changing ARC1 KCRRACTIVE->KCRRSHUTDN
ARC3: sending ARC1 shutdown message
ARC3: received prod
Tue Jul 13 00:34:20 1999
ALTER SYSTEM SET log_archive_max_processes=2;
Tue Jul 13 00:34:20 1999
ARCH shutting down
ARC0: Archival stopped
ARC0: changing ARC0 KCRRSHUTDN->KCRRDEAD
Tue Jul 13 00:34:20 1999
ARCH shutting down
ARC1: Archival stopped
ARC1: changing ARC1 KCRRSHUTDN->KCRRDEAD
4. 어떤 archiver process가 online log를 archive시켰는지 판단 방법
Archiver process는 round-robin 방식으로 archiving 작업을 수행하도록
schedule 된다. 만약 다중 archiver process가 부하에 따라 activate 된
경우는 여러가지 경우의 수가 있을 수 있다. Oracle 8i에서는 다중
archive log dest를 지원하면서 archive log에 대한 duplexing을 지원
하기 때문에, 어떤프로세스가 log file을 archive 시켰는지를 기록할 필요가
있다.
Oracle 8i에서 archival 작업은 성공할 때 마다 trace file에 archiver
process 명을 기록한다.
다음은 관련 trace file의 주요 내용이다.
Instance name: v815
Redo thread mounted by this instance: 1
Oracle process number: 12
Unix process pid: 3658, image: oracle@oracle8i (ARC3)
*** Session ID:(12. 1) 1999. 07. 13. 02. 15. 15. 000
*** 1999. 07. 13. 02. 15. 15. 000
*** 1999. 07. 13. 02. 33. 06. 000
ARC3: Begin archiving log# 1 seq# 38 thrd# 1
ARC3: VALIDATE
ARC3: PREPARE
ARC3: INITIALIZE
ARC3: SPOOL
ARC3: Creating archive destination 1 : '/bigdisk/oracle8i/dbs/arch/1_38.
dbf'
ARC3: Archiving block 1 count 1 to : '/bigdisk/oracle8i/dbs/arch/1_38.
dbf'
ARC3: Closing archive destination 1 : /bigdisk/oracle8i/dbs/arch/1_38.
dbf
ARC3: FINISH
ARC3: Archival success destination 1 : '/bigdisk/oracle8i/dbs/arch/1_38.
dbf'
ARC3: COMPLETE, all destinations archived
ARC3: ArchivedLog entry added: /bigdisk/oracle8i/dbs/arch/1_38. dbf
ARC3: ARCHIVED
*** 1999. 07. 13. 02. 33. 06. 000
ARC3: Completed archiving log# 1 seq# 38 thrd# 1
이 정보를 가지고, archive process 3이 log sequence 38번을
destination 1 :/bigdisk/oracle8i/dbs/arch 에 archive 시킨 것을 알 수 있다.
Reference Ducumment
<Note:73163.1>

Purchase Order is not deleted after archive process

Hi,
I want to delete completely a specific purchase order from the system so I followed the next steps to do that but is not working.. not sure if I'm doing something wrong.
Steps:
1) I marked up the PO as deleted in the ME22 transaction:
2) In the transaction SARA I followed these steps:
Step 1: Create variant for Archiving. Give it a name. Enter your PO number. Flag One step procedure. Flag detailed log. Erase flag for test run.
Step 2: Maintain your start date, you can use Immediate in such a small case.
Step 3: Maintain spool parameters. Enter your printer and set the values if you want to print immediatly and if you want keep the print. I suggest to hold the spool in the system. This helps you to determine any error.
Step 4. Execute the variant.
3) If I go to the transaction ME23N it says that the PO is archived but is there yet. Also, I can see it in the "Docuement Overview". How can I delete this PO completely from the system??
Thanks for the help!!

HI Carlos,
Since you archived PO, it is stored in archive physical drive not in SAP drive.
when u use me23n, the archived PO is picking from physical drive and it says "Already archived" message.
I'm sure there will be no table level entries for the archived documents
Go to SARA transaction - information system--> Archive Explorer - MM_EKKO and execute.
Check your PO is listed here.
So if you dont want to see your PO, then you need to De-activate information system
in SARA-Information System-->Customizing -
search infrastructure by Object name and use activate/deactivate icon -
A question i really need to know - Why you want to delete a particular PO, Archival process is not a small thing and usually it takes place as a MASS activity.
reg,
bhg

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

Message archiving in adapter engine

Hello Gurus,
We have successfully configured message archiving in the integration engine via all the sap documentation and sdn blogs.
For the archiving in adapter engine, we have followed the documentation as well however our messages are simply not being archived in the adapter engine.
The steps for AE we took are as follows:
1. goto DataArchivingService/DAS and created an archive store, home path synch and assigned it to an archive path (the ILM browser connects fine as well)
2. created the archiving background job in RWB (both default and a custom one with rules)
The jobs seem to be running fine on our schedule but no messages are being processed. I am assuming the retention period in AE is the one we have set up in SXMB_ADM for IE.
Is there anything we may have missed?

Hi,
Please check the [link|http://www.****************/Tutorials/XI/Archiving/Index.htm]
Also check this
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50?quicklink=index&overridelayout=true
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=147266890
Regards,
Naveen.

Connection Message Archiver problems

Hoping someone can help.
I'm attempting to capture voicemail messages from multiple users. I need to preserve message headers and voicemail messages.
I've downloaded and installed the Unity Connection Message Archiver program from http://www.ciscounitytools.com/Applications/CxN/MessageArchiver/MessageArchiver.html
I followed all the step for configuration.
I can login and search for and select a mailbox or messages for archiving.
However, when I click the "Archive", I see the processing message, but then it reports an error.
Here is the error from the log file: "Failed establishing IMAP connection in the ConnectionMessageBackupFunctions constructor:Failed to attach to Connection server on port 7993 for IMAP login in AttachViaImap"
I've attached the full log file.
I've verified that the IMAP service is running. I've also followed all troubshooting steps found here: http://www.ciscounitytools.com/Applications/CxN/MessageArchiver/Help/MessageArchiver.htm
Can anyone point me in the right direction.
Thanks in advance.

Hi Jonathan,
I would move this thread over to the Unified Communications
Applications sub-forum as tool designer/engineer and Unity Connection
guru Lindborg will most likely have a great answer for you
https://supportforums.cisco.com/community/netpro/collaboration-voice-video/unified-comm-application?view=discussions
Cheers!
Rob
"May your heart always be joyful
And may your song always be sung
May you stay forever young "
- Dylan

Find resource utilized in archive process....

Hello I am new to oracle.
I am deciding to configure standby database for my production database( oracle 9.2.0.6).
My database is running in archive log mode and its currently archiving in one location.
I was questioned by my line manager ?..
what will be the resource utilized at the production server if you try to archive redologs at 2 location (ie mandatory). interms of cpu, io and performance of current database running.
what difference it makes if I archived to second destination which can be local or on remote server.
I need to understand impact on performance of my production server if I archived to more than one location.
Is there any specific views that I have to query at database level or at os level.
Plz help.

Hi,
If you don't mind, I won't answer your questions in the order you asked them.
what difference it makes if I archived to second destination which can be local or on remote server.The destination for the 2nd set of archived redo log files must be remote (IMNSHO) if you want to set up anything close to a DR scenario. Standby Databases are used in case of crash of the Primary Database, when it can't be started up again fast, to failover to the standby in order to continue working. If you set up the Standby on the prod server, odds are 99% for it to be useless when the crash happens. And you don't want that, do you?
So, in that case, it'll "cost" nework badwidth. Up to you to check how much archive volume is generated on average per hour, to know what kind of bandwidth you need. I posted a query to compte that some time ago, but can't seem to find it anywhere in the Forum. Anyway it can be achieved by:
SELECT
TRUNC(ARCHIVED.NBARCHIVEDBLOCKS * BLOCKSIZE.VALUE /1024/1024/24/3600,2) "MebiBytes per Second"
FROM
(SELECT VALUE FROM V$PARAMETER WHERE NAME='db_block_size') BLOCKSIZE,
(SELECT SUM(BLOCKS) NBARCHIVEDBLOCKS FROM V$ARCHIVED_LOG WHERE TRUNC(FIRST_TIME) = TRUNC(SYSDATE)-1 AND STANDBY_DEST='NO') ARCHIVED;(as you're archiving to one destination only atm).
what will be the resource utilized at the production server if you try to archive redologs at 2
location (ie mandatory). interms of cpu, io and performance of current database running.There's no ROT to compute such things, they depend on way too much info. But you can count on a small overhead in CPU and memory (ram) usage on the production server. Though this will not have any noticeable impact on the production database. Except of course if you're realy running low on those resources!
Anyway, the first thing you should do if you want to set it up is to start 2 archiver processes (log_archive_max_processes=2) in order to archive fast enough. oh, and of course you should first try it yourself on a test server!
HTH,
Yoann.
Message was edited by:
Yoann Mainguy

Archive process cleared-Went thorugh Metalink docs

If there are 2 archive process defined how does the archiver works
i got 2 archiver proces running resuklting in an entry in log file saying
unable to archive log actively being archived by another rpocess
Message was edited by:
Maran Viswarayar

Inside the V2 folder are subfolders representing your Mail accounts. The names refer to the email addresses you use.
From the Mail menu bar, select
File ▹ Import Mailboxes...
Import from the mailboxes in the restored folder. The imported messages will appear in a new mailbox. Move the ones you want to keep wherever you like and delete the rest.

SAP XI message archiving

Hi
I am running sap archiving and deletion of messages. I have observed that only messages from the CENTRAL pipeline are getting archived while the other pipelines like PIPELINE_RECIEVER etc are not getting archived and deleted.
Please can anyone let me know what is the problem.
Many Thanks
Deb Sircar

Hi
As per the Archiving/ deletion settings, an Interface (its message on the whole) is either Archived or Not Archived.
when "Archived" all pipeline steps are archived & "once deleted" you cannot see that message any more in SXMB_MONI (but only from the archived msgs) and the archiving process is said to be complete.
Check my posts in this link
Re: XI Message archival
explain clearly the issues you face, what you mean as PIPELINE_RECEIVER.
Regards
Vishnu

Error message during processing in BI

1.i am loading the data into infoobject.
2.got error in text data load.
3.master info object have compound obj 0COUNTRY
4.and other normal fields are 0TXTSH,0LANGU,sold-to-party.
5.there is no PSA in this..its direct update to INFOobject.
The error message is:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Update
Diagnosis
There are duplicates of the data record 2. with the key '3.' for characteristic 1..
Procedure
If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.

Hi KP,
In the details tab,
1.under Transfer (IDOC and Trfc):
   Data Package 1 : arrived in BW ; Processing : Error records written to application log
2.Processing (data packet): Errors occurred
   Update ( 0 new / 0 changed ) : Errors occurred
   Error records written to application log
   0TRZONE : Data record 1 ('0000000001D ') : Duplicate data record
   0TRZONE : Data record 2 ('0000000002D ') : Duplicate data record
   Error 4 in the update
3. Process chain error
these are the error details.

Error messages in Process chains

Hello BI fans
In which transaction can I maintain batch-initiated error messages from process chains.
I am not looking for the process chain variant for messages.
I would like to create messages only for errorness messages.
thanks
BEO

Hi,
Please check the forum before posting for this issue.
Here You can follow below steps:
1) right click on process type and select "create messages".
2) choose "error" and create variant for error message
3)write message body in "EDIT DOCUMENT" and mention email ID's in "Maintain Recipient list" tab
4) save and schedule the chain again
Edited by: shailesh patil on Nov 14, 2011 5:51 PM

Message No processing because no items were selected

Hi,
We are using AFS SCC 6.0 system.
I am trying to allocate a SO, it is open, and there are no delivery/billing blocks.
The /afs/mdo4 report shows stock in T tab for this SO.
But when i try to allocate i get the message : No processing because no items were selected
Message no. /AFS/MGNT052
And stock is not shown, therefore i cant allocate.
In the past, we have allocated for the same customer / material combination.
Appreciate any ones ideas on the above message that we receive when trying to allocate - No processing because no items were selected
Message no. /AFS/MGNT052
Thanks in advance

d

Message Archiving for the Adapter Engine

Hi,
we have configured archiving for Integration Engine (SXMB_MONI) messages on the Production XI System. is it necessary to configure Message Archiving for the Adapter Engine also ? in which scenarios archived adapter messages are useful ? are there any other advantages/disadvantages for this(in case of errored messages on the adapter engine) ? Please share any ideas.
Thanks
Pavan.

>>is it necessary to configure Message Archiving for the Adapter Engine also
Not necessary,but depends upon the scenario,lets say you are posting messages to external partner's FTP and there was some issue in connectivity due to which file was not delivered,in this case you need to send the message again.
same thing can happen in inbound messages too.
>>in which scenarios archived adapter messages are useful ?
i would do this specifically for JDBC sender coz once you pick up the files based upon SQL query,you change the flag so that those values are not picked next time,in this case you can't re-run the old query and get same results.
this also holds for proxies and file too.
Thanx
Aamir

File-RFC_File Scenario - single message got processed twice.

Hi all,
I have a file-RFC-File scenario in which the reponse from ECC is written using adapter modules.Today one message got processed twice into SAP.When i checked FIle Receiver adapter in CC monitoring i could see the error given below:
2010-11-16 08:47:37 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-11-16 08:47:37 Success The XI response message for message 0fb0e660-f130-11df-a03d-00212816ab84(INBOUND) was successfully returned to the calling application.
2010-11-16 08:47:37 Success The message status set to DLVD.
2010-11-16 08:47:37 Success ROB: entering ResponseOnewayBean
2010-11-16 08:47:37 Success ROB: resuming the transaction
2010-11-16 08:47:37 Success ROB: calling the module processor ...
2010-11-16 08:47:37 Success MP: Entering module processor
2010-11-16 08:47:37 Success MP: Processing local module localejbs/CallSapAdapter
2010-11-16 08:47:37 Success File adapter receiver: processing started; QoS required: ExactlyOnce
2010-11-16 08:47:37 Success File adapter receiver channel File_Receiver_XXXX_CC: start processing: party " ", service "XXXX_BUSS"
2010-11-16 08:47:37 Success Connecting to FTP server "XX.XX.X.XXX"
2010-11-16 08:47:37 Success Write to FTP server "XX.XX.X.XXX", directory "/inbound", -> file "XXXResp20101116-084737-629.xml"
2010-11-16 08:47:37 Success Transfer: "BIN" mode, size 273 bytes, character encoding -
*2010-11-16 08:47:37 Error Attempt to process file failed with com.sap.aii.adapter.file.ftp.FTPEx: 550 XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified.
2010-11-16 08:47:37 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified. : com.sap.aii.adapter.file.ftp.FTPEx: 550 XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified.
2010-11-16 08:47:37 Error ROB: error during processing: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.RecoverableException: XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified. : com.sap.aii.adapter.file.ftp.FTPEx: 550 XI_ftp_0fb0e660-f130-11df-a03d-00212816ab84.tmp: The system cannot find the file specified. *
The tmp file was picked by the client system and may be that disturbed the entire scenario.But instead of throwing an error how can this reprocess the message from beginning. In SXMB_MONI i can see the pipeline steps executed twice for this message. Since the interface is critical i had to manually delete the replicated data from ECC after taking clients permission which wont be allowed everytime.
Could somepne help me in resolving the issue.
Thanks & Regards,
Lekshmi.

Nisar,
Which program to re-run? Are you talking about activating the channel again? If so, then I have done it many times changing the file name.
I got below error in Communication Channel Monitoring:
2008-02-06 02:27:39 Error Received XI System Error. ErrorCode: MSGGUID_EXISTING ErrorText: ErrorStack: Message ID 83F8B0B0D48311DCA544DA01C52F0606 for pipeline CENTRAL, version already exists in system
2008-02-06 02:27:39 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
2008-02-06 02:27:39 Error Transmitting the message using connection http://xibox:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
2008-02-06 02:27:39 Error The message status set to FAIL.
2008-02-06 02:27:39 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
2008-02-06 02:27:39 Error Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
2008-02-06 02:27:39 Error Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException

PI message archiving

Hello
I have recently been made responsible for a PI 7.1 system, and am new to SAP and PI. I have some general questions about message archiving and would be grateful for some advice.
I understand that message details are saved to SXMSPMAST and associated tables. There is a limit to the number of rows in the tables.
Q. What happens when the tables are full?
Q. Is it possible to increase the number of rows that they can hold?
I believe that none of our existing interfaces have been configured for archiving/retention.
Q. Should the interfaces have been configured for archiving before first use?
Q. Does this only apply to asynchronous interfaces?
The vast majority of messages in SXMXPMAST have ITFACTION set to 'INIT'. I understand that these messages will not be deleted or archived.
Q. Is it possible to change the ITFACTION and is this something I should be doing?
Q. There are some synchronous messages with a status of system error on our system. I am not able to cancel these messages in SXMB_MONI. I do not want to keep a record of these messages as they were sent before the system was 'live'. Is there anything I can do to delete them?
I have found several documents on the SAP forums and blogs, but none deal with the case where existing interfaces haven't been configured for archiving.
Kind regards
Steve

Dear Steve,
a lot of questions Let me answer them one by one...
I understand that message details are saved to SXMSPMAST and associated tables. There is a limit to the number of rows in the tables.
Q. What happens when the tables are full?
A. Nothing. The number which you refer to as 'limit of rows' reflects the number of expected entries. This value is used to control reorganizational tasks in PI.
Q. Is it possible to increase the number of rows that they can hold?
A. Yes, but SAP does not recommend this in general. Also there is no need to increase this number as it used as a threshold for reorganization only.
I believe that none of our existing interfaces have been configured for archiving/retention.
Q. Should the interfaces have been configured for archiving before first use?
A. Yes, definitely. The interface action nis determined right when the message enters the Integration Server. Therefore it is important to configure archiving beforehand. However, as of PI7.10 SP6 report RSXMB_DEL_TO_ARCH is available to change the interface action from 'deletion' to 'archiving' belatedly (this direction only!).
Q. Does this only apply to asynchronous interfaces?
A. Yes, synchronous messages will not be archived.
I

Message archival process in XI

Similar Messages

Maybe you are looking for