Re: JOB_ERROR_DEL_BRKURI

We have solved this problem, helped SAP supporting

dialogue with SAP support:

________________________________________________________________________

1. 06.08.2015 - 11:38:33 CET -  by SAP                        

Hello Rinaz,

Please execute the following DELETE statements to remove obsolete

broken URIs and archived message keys related to archiving sessions

that are no longer existent:

DELETE FROM BC_MSG_ARC_BRKJOBS;

DELETE FROM BC_MSG_ARC_MSGKEYS;

The query result shows some records (345564) in XI_AF_LMS_DATA table

which means that you have configured User-Defined Message Search for

some messages. 95717 of them are related to messages that have been

moved to Archive store but were not archived themselves, most probably

because no archive store has been assigned to the home path of

xi_af_uds_msg archiving set. I#m not sure whether the messages to

which these records (UDS attributes) are related are still available

in Archive store or have been deleted. So I would suggest you the

following options:

1. 1. If you don#t need to archive UDS attributes related to archived

messages (because archive store has been cleared or because you don#t

need to search for messages in Archive store using UDS attributes),

execute the following DB update:

DELETE FROM XI_AF_LMS_DATA WHERE MSG_ID IN (SELECT MSG_KEY FROM

XI_AF_LMS_ARC_KEYS);

It would be better to do this either during system downtime or in time

with no message load on the system as this might delay processing of

messages for which UDS is configured (see active filters in

User-Defined Message Search Configuration in SAP NetWeaver

Administrator). Then assign Archive Store for the home path of

xi_af_uds_msg archiving set in XML DAS Administration: Archive

Hierarchy & Store Assignment in SAP NWA.

1. 2. If you want to archive these UDS attributes, simply assign an

Archive Store and next time UDS archiving is triggered it will try to

archive them.

After the obsolete broken URIs are cleared from DB, you can delete any

unused Archive Jobs from Background Job Processing Monitor-> Adapter

Engine Jobs. Typically you#ll need a single job of type Archive (e.g.

without rules, if you want to archive all messages). If you need to

archive just messages belonging to certain scenarios, you can use job

Rules to define which messages should be taken for archiving. Make

sure the archive job is activated and then after activating the

Default Delete Job, the latter will take care to delete expired

messages in final state that do not match the rules of the active

Archive jobs.

Note that there is one special job of type Archive which is

automatically created by the system # Default Version Archive Job.

This job is intended to only archive messages which have been manually

edited using Message Editor, so you cannot use it to archive other

messages (or define rules for this job as they would be disregarded).

That#s why you have to maintain at least one other job of type Archive

in order to archive messages when they expire.

Please check whether archiving sessions are started and completed

successfully for xi_af_msg and xi_af_uds_msg sets in Java Archiving

Cockpit after triggering the Archive job and let me know the result.

The archiving session for xi_af_uds_msg should be started after at

least one session for xi_af_msg is completed and archived messages

have been indexed according to UDS configuration.

Thank you and best regards,

SAP PI Development Support

__________________________________________________________________________

1. 06.08.2015 - 09:55:54 CET -  by Rinaz Makhmutov                          

Hello

File with the result of the query in an attachment

Best Regards

Rinaz

_______________________________________________________________________________

1. 05.08.2015 - 12:57:27 CET -  by SAP                        

Dear Customer,

Please provide the results of the following DB queries (attached also

in sql.txt):

SELECT COLURI, SESSIONSTATUS, WCOUNT, WSESSIONSTART, WSESSIONSTOP,

DCOUNT, DSESSIONSTART, DSESSIONSTOP FROM BC_XMLA_ASESSIONS WHERE

ARCHSET='xi_af_msg' AND SESSIONSTATUS<>'CLS';

SELECT * FROM BC_MSG_ARC_BRKJOBS;

SELECT JOB_ID, JOB_NAME, ACTIVE, MODE_FLAG FROM BC_MSG_JOB WHERE

JOB_TYPE='A';

SELECT COUNT(*) FROM BC_MSG_ARC_MSGKEYS;

SELECT COUNT(*) FROM XI_AF_LMS_DATA;

SELECT COUNT(*) FROM XI_AF_LMS_ARC_KEYS;

Thank you and best regards,

SAP PI Development Support

____________________________________________________________________________

1. 05.08.2015 - 07:12:10 CET -  by SAP                        

Hello Rinaz,

We have deleted the session info from XML side, but PI also maintains

these session info.

To remove those entries, I am forwarding your incident to PI component.

Best Regards

SAP PI Development Support

_________________________________________________________________________________

1. 04.08.2015 - 13:43:10 CET -  by Rinaz Makhmutov                          

Hello,

Thanks for your reply.

On your recommendation:

We remove all the folders created manually in the file system and

remove

their session info from the DB table BC_XMLA_ASESSIONS.

On former when deleting job, we have an error: BROKEN_URI_EXISTS

But if i doing "Execute Now"(Background Job Processing Monitor:

Process

Jobs) then Status details:

Executing ArchiveJob Archive failed. Reason:

1. com.sap.engine.interfaces.messaging.api.job.JobException: Could not get
2. SessionInfo. Reason:
3. com.sap.engine.interfaces.messaging.api.job.JobException: Status code:

488 message: null

The same error in the RWB.

Your early reply will be appreciated.

1. P.S. logs in the attachment (20150804)

Best Regards

Rinaz

______________________________________________________________________________

1. 04.08.2015 - 07:13:22 CET -  by SAP                        

Hello Rinaz,

Please remove all the folders created manually in the file system.

And remove their session info from the DB table BC_XMLA_ASESSIONS like

below mentioned:

XXX/xi_af_msg/2014/08/wurdt6i7zai6jhu5aaaaazzgoc"

And in future, please ask your basis team to not create folders

manually under archiving store.

Best Regards

SAP PI Development Support

______________________________________________________________________________

1. 03.08.2015 - 14:36:48 CET -  by Rinaz Makhmutov                          

Hello!

The entire contents of folders xi_af_msg and xi_af_msg3.

Full path:

/sapmnt/XXX/global/ArchiveMessages/XXX/xi_af_msg

/sapmnt/XXX/global/ArchiveMessages/XXX/xi_af_msg3

Of your answer we not understand what to do to solve this problem? You

can write a step by step what to do next?

Best Regards,

Rinaz

________________________________________________________________________________

1. 03.08.2015 - 08:05:52 CET -  by SAP                        

Hello Rinaz,

Thanks for the attachment, please find the findings below:

1. 1. In any case, manual creation of folders under your archive store

should be prohibited. This creates inconsistency between your DB table

entries and file system.

1. 2. Since the session was initiated on these collections, thus an entry

does appear in BC_XMLA_ASESSIONS table. But the entry is this:

XXX/xi_af_msg/2014/08/wurdt6i7zai6jhu5aaaaazzgoc" "BRD" "archuser" "T"

24260 09.08.14 13:26:02,174000000

Which means, it started on 8th August 2014. And in the 1st attachment,

the modified date for this folder is 23/7/2015, thus clearly these are

not in sync.

1. 3. Since the folder creation was manual, its obvious that these

folders wont be visible in the Collection tables, and the same is

• observed. BC_XMLA_COL doesn't hold any entries for these collections.

Now, firstly please ask your Basis team to no more create/delete any

files or folder directly from file system because what happens is that

when you create/delete these folders directly, the DB entry

corresponding to these files/folder remains unaltered and thus

inconsistency occurs. I hope this is clear because this can cause

serious problems in your productive environment.

Kindly provide more info on such actions from your basis team. How

many such folders/files have been manually altered. We need to remove

DB entries for them so that we can bring your DB and file system back

in sync.

Best Regards

SAP PI Development Support

_________________________________________________________________________

1. 31.07.2015 - 14:30:29 CET -  by Rinaz Makhmutov                          

Hello ,

Thanks for your answer.I checked yours recommendations:

1. 1. A screenshot of the attachment. (20150731.rar)
2. P.S. This directory it has not been, its basis added manually

1. 2. The contents of the BC_XMLA_ASESSIONS table in the

attachment(20150731.rar)

1. 3. The contents of the BC_XMLA_COL table in the attachment

(20150731.rar)

Best Regards,

Rinaz

_______________________________________________________________________________

1. 31.07.2015 - 11:17:16 CET -  by SAP                        

Hello Rinaz,

Can you please check few things:

1. 1. Path  XXX/xi_af_msg/2014/08/wurdt6i7zai6jhu5aaaaazzgoc actually

exists in your file system or not.

1. 2. In the table BC_XMLA_ASESSIONS there is any entry for this session.

1. 3. In table BC_XMLA_COL there are any records for the collection

2014/08/wurdt6i7zai6jhu5aaaaazzgoc

Best Regards

SAP PI Development Support

_______________________________________________________________________________

1. 30.07.2015 - 08:22:48 CET -  by Rinaz Makhmutov                          

Hello!

Earlier i answered on same request to your colleagues in this incident:

Sorry, but we can not provide you with remote access, this forbids us

to

make our organizational security policies. We can only give you the

logs

from the system, the screenshots and execute your recommendations.

Regards,

Rinaz

_________________________________________________________________________________

1. 29.07.2015 - 07:45:33 CET -  by SAP                        

Hello Rinaz,

I see lots of XML DAS related errors in the screenshot.

Can we setup a conference call with screen sharing session, so that we

can provide you better support.

I operate from Indian Time Zone and I assume you operate from

Russia/Moscow time zone.

Is it possible to have such session either today or tomorrow ?

Best Regards

SAP PI Development Support

_____________________________________________________________________________________

1. 28.07.2015 - 23:56:33 CET -  by SAP                        

Hello Rinaz,

Thanks for providing us this detailed screenshots.

I am involving my colleagues from BC-ILM-DAS in this incident for

additional investigation.

My colleagues will contact you with their findings and the next steps.

Regards,

SAP Active Global Support

________________________________________________________________________________

1. 28.07.2015 - 10:08:32 CET -  by Rinaz Makhmutov                          

Hello!

Screenshots and logs in the attachment (ArhiveJobDelError)

Regards,

Rinaz

1. 28.07.2015 - 10:05:59 CET -  by Rinaz Makhmutov                          

Hello!

Screenshots and logs in the attachment

Regards,

Rinaz

_________________________________________________________________________________

1. 24.07.2015 - 22:04:16 CET -  by SAP                        

Hello Rinaz!

Ok, no problem.

Can you please check if you face the same issue while using the old

Background Processing Monitor from the Runtime Workbench?

RWB -> Component Monitor -> Adapter Engine -> Background processing

monitor

1) If yes, please provide me the job logs from RWB.

2) Also, reproduce the issue by trying to delete the job error and

attach the full defaultTrace file to this incident.

3) And provide me screenshots from the issued job in the PIMON and in

the RWB with the job logs if possible.

Regards,

SAP Active Global Support

__________________________________________________________________________________-

1. 22.07.2015 - 08:41:30 CET -  by Rinaz Makhmutov                          

Hello!

Sorry, but we can not provide you with remote access, this forbids us

to

make our organizational security policies.

We can only give you the logs from the system, the screenshots and

execute

your recommendations

Regards,

Rinaz

________________________________________________________________________________

1. 21.07.2015 - 23:26:10 CET -  by SAP                        

Hello,

This is Denise Blume from PI team and I am the responsible for this

incident from now on.

By reading the issue description and the files you have attached, a

quick workaround I can recommend you is to use the old Background

Processing Monitor in the Runtime Workbench.

For proceed with the investigation, I need to perform some checks in

your system in order to get additional information about the error you

are getting in the Archive Job.

Could you please open the HTTP connection to XXX system? Read SAP note

#1916218 - Remote Service Connections to PI systems explained, for

additional information about how to set the connections to PI.

I will need a user which is copy of PISUPER plus the J2EE admin role

maintained in the secure area (Maintain Access Data button).

Regards,

SAP Active Global Support

Best Regards

Rinaz