PI 7.3 AEX - Archive job failed

[Former Member]

Hi All,

My PI database is growing massively with Message logs. When I checked BC_MSG is growing massively with these logs.

I want to schedule archive job to fix this issue and when I have scheduled Default Version Archive Job in PI 7.3 AEX (java only Stack).

But it is failed with this error

Executing ArchiveJob Default Version Archive Job failed. Reason: java.io.IOException:response_code=401

any clue on this? Not sure why?

[former_member198872]

Hi

The error is due to authorization issue to fix the issue open NWA search for destinations and select DASdefault HTTP destination and maintain logon data for this destination with a user having the roles NWA_SUPERADMIN and SAP_ARCH_SUPERADMIN and try to execute job again.

Thanks

Venkatesh

[Former Member]

Hi Basis Lady,

did you check if the XML DAS communication user (used in destination "DASdefault") is configured correctly according to the documentationhttp://help.sap.com/saphelp_nwpi71/helpdata/EN/43/68fac39a363d33e10000000a11466f/frameset.htmand is assigned to the "XMLDASSecurityRole" role?

And check if you have configured the rules for your Archiving job (Component Monitoring -> Adapter Engine XIE -> Background Processing).

It seems the archiving does not work because of configuration issues.

An archiving job without rules means: all messages are relevant for archiving. The delete job will only delete messages which are not relevant for archiving. So it does not do anything in this system. It can lead to the database table keeps growing, if it's the case too.

You should check the archiving configuration so that the archiving job runs successfully.

If you do not want to archive the messages, please deactivate the archiving job. Then the delete job should clean the old messages with the next execution.

You may delete it straightly on the Background Processing.

Check for more details.

[Former Member]

Hi Indrajit,

If my understanding is correct even though Archive job failed, Default delete job delete the log entries in BC_MSG table.

In My system after I had database full issue, I have extended tablespace with another 10GB and noticed that in log configuration  severity recording set to all and I changed it to error only.

This morning Again that 10GB filled and causing lot off issues. this time database logs written to SAP Lob segment instead BC_MSG table.

And also, In system availability and performance tab , Logs per minute showing 3740 which is extremely High.

Why this number of logs are occurring, where else I can look for any clues, And If Default delete job running 1 day what exactly it is deleting?

Can anybody help me please? I have lot of trouble with this PI system.

[chrisjoice]

Hi there,

Hope the issue is resolved for you. I'm having the exact problem, could you please let me know the solution that worked for you?

Thanks

Christina

[former_member445936]

Hi,

the last weekend I had a similar issue, the error http 401 describe a error of authorization please

check if the XML DAS communication user (used in destination"DASdefault") is configured correctly according to the documentation:

http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/68fac39a363d33e10000000a11466f/frameset.htm

Good luck!

[Former Member]

Hi,

response_code=401 normally it refers unauthorized.

Pls check below link:

[Former Member]

What authrization / Role require to execute a job then?

[Former Member]

Hi

Check this. It may help

Troubleshooting Archiving and Deletion in PI

[Eoin_Kierans]

Hello,

Can you detail the path to which the files are to be archived? Can you also detail the OS on which the PI system is running?

Regards

Eoin

[Former Member]

Hi Eoin,

I am sorry. I am new to Java stack job scheduling.these are some standrad jobs.

all are success in Dev system But Only archive job failing in Test, Prod systems.

• Default Delete Job
• Default Recover Job
• Default Version Archieve Job

If you ask me the path to which the files are to be archived - I don't know where to look

detail the OS on which the PI system is running? - Linux x86_64

[Former Member]

Thanks Indrajit for this note, I looked it earlier, But I didn't find any clue with this

[former_member184720]

Hi - You need to setup the archiving as explained in the below blog in order to archive the messages on adapter engine..

However the default delete job should delete the messages from BC_MSG table, in case you don't want to archive.

[Former Member]

Hi Hareesh

AAE archiving with XMLDAS is separate concept. But we have anoother option which is using back ground jobs which is used by this blog.

In my system I can see that archive job is running fine, did not find anything why for this post owner it is not working

I did not see any places where we need to maintain any user id and password. Don't know why she is getting  401 error.

[former_member184720]

Hi Indrajit - AFAIK - Inorder to store the messages on PI database, we increase the retention period and to archive we should set up Data Archiving Service.

[former_member184720]

• To archive interfaces in the Adapter Framework (AFW), the XML DAS (Data Archiving Store) has to be set up. If no archiving has been set up XML message will be deleted from the AFW by the standard deletion job after a default time of 1 day (releases 7.10 and higher). You can define which interfaces should be archived via archiving rules.

Reference : 872388 - Troubleshooting Archiving and Deletion in PI

[Former Member]

Hi Hareesh

Yes I can see it is mentioned there. In the destination DASdefault we have not used any user id and password.I can see the below error while checking in Java Archiving Cockpit

'Could not connect to the XML Data Archiving Service. Contact your system administrator to check userID and password of HTTP destination "DASdefault": UserID may be locked or the password may have expired.'

But in the adapter engine--> Background Job Processing Monitor , the job is showing as successful and not showing any error.

[former_member184720]

Hi Indrajit - Not sure why your archiving job displaying the successful status.. try restarting the job manually and see if it displays the error message.

However it's not working right