Problem:
After cloning fsdev to fstst, SYSAUDIT was run. It showed the following error:
(QUERY-22) Following Queries Were Created Without PUBLIC Access Query Name ------------------------------- Oper ID ------------------------------- FJBG_CALENDARS VP1 FJBG_NAVIGATION VP1 FJBG_SET_CONTROL_GROUP VP1 FJBG_TIMESPANS VP1 4 Total Rows
Solution:
Spoke to consultant (FB). He said that he created these queries and they were set to be private. Therefore, the error could be ignored.
Problem:
After cloning fsdev to fstst, SYSAUDIT was run. It showed the following error:
(TREE-21) Tree Selector Control contains Tree name that is not defined in Tree Definition table: Tree Name -------------------- Set Id ------------ Effect DT ------------ Selector Number ---------- ACCT_BY_LOB_DETAIL SHARE 01/01/1900 101 1 Total Rows
Solution:
This tree was created by the consultant FB and he advised that it could be ignored.
Problem:
After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:
Operation Version Routing --------- ------- ------- QAS_CRASH_MSG VERSION_1 ~GEN_UPG~18727 QAS_CRASH_MSG VERSION_1 ~GEN~UPG~19278 2 Total Rows
Solution:
In PIA, navigate to PeopleTools > Integration Broker > Service Utilities > Service Administration.
Click on the Routing tab.
Expand Delete Duplicate Routings.
Click Search
The duplicate Routing Definitions appear. The second item will be checked.
Click Delete Tem…
Then click Search again. Ensure that no rows appear.
Problem:
After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:
(IBRK-10): IB Routing referencing invalid handlers: Routing On Send Handler On Receive Handler - ------ --------------- ------------------ ~GENERATED~17288 ACK 1 Total Rows
Solution:
Log on to SQL Server Management Studio and run the following queries against fsdev:
select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = '~GENERATED~17288' select * from PSIBRTNGDEFN where ONRCVHDLRNAME = 'ACK' select ONRCVHDLRNAME, count(*) from PSIBRTNGDEFN group by ONRCVHDLRNAME select * from PSSRVHDLRRCV_VW
The outputs were:
ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- ~GENERATED~17288 2005-10-21 00:00:00.000 6 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-30 11:38:38.000 VP1 PPT GENERATED NULL (1 row(s) affected) ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- ~GENERATED~17288 2005-10-21 00:00:00.000 6 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-30 11:38:38.000 VP1 PPT GENERATED NULL (1 row(s) affected) ONRCVHDLRNAME COUNT(*) ------------------------------ ----------- 1500 ACK 1 (2 row(s) affected) IB_OPERATIONNAME ONRCVHDLRNAME DESCR ------------------------------ ------------------------------ --------------------------- CREATE_WORKLIST_ITEM OnAckForMarkedWorkedResp Create worklist entry (1 row(s) affected)
On fsdmo, ran the following queries:
select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = '~GENERATED~17288' select * from PSIBRTNGDEFN where ONRCVHDLRNAME = 'ACK' select ONRCVHDLRNAME, count(*) from PSIBRTNGDEFN group by ONRCVHDLRNAME select * from PSSRVHDLRRCV_VW
The outputs were:
ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- ~GENERATED~17288 2005-10-21 00:00:00.000 1 A ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-18 16:04:16.000 PPLSOFT PPT GENERATED NULL (1 row(s) affected) ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- CREATE_WORKLIST_ITEM 2005-10-21 00:00:00.000 1 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-23 11:11:56.000 PPLSOFT Create worklist entry NULL ~GENERATED~17288 2005-10-21 00:00:00.000 1 A ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-18 16:04:16.000 PPLSOFT PPT GENERATED NULL (2 row(s) affected) ONRCVHDLRNAME ------------------------------ ----------- 1513 ACK 2 (2 row(s) affected) IB_OPERATIONNAME ONRCVHDLRNAME DESCR ------------------------------ ------------------------------ --------------------------- CREATE_WORKLIST_ITEM ACK CREATE_WORKLIST_ITEM OnAckForMarkedWorkedResp Create worklist entry (2 row(s) affected)
Note that in PSSRVHDLRRCV_VW, there is a new row for ACK.
1. The simplest solution, however, is to delete the offending routing, ~GENERATED~17288.
2. In PIA, navigate to Integration Broker > Service Utilities > Service Administration. Select the Routings tab, and open the Delete section. Enter ~GENERATED~17288 into the Routing Name field and click Search. Check Select and then click Delete.
Under Results, the following message appears: Unable to delete. Routing belongs to a restricted service.
3. One way to resolve this is to change the restricted service to unrestricted. Navigate to Integration Broker > Configuration > Service Configuration. Click the Restricted Services tab, and search for PT_WORKLIST. Uncheck Restricted, and then Save.
4. Determine the field that is used as the lookup. Navigate to Integration Broker > Integration Setup > Routings. In the Find an Existing Value tab, in Routing Name, enter ~GENERATED~17288 and click Search.
5. Type Ctrl + J and note the Page name: IB_ROUTINGDEFN
6. On GL-WEB-APP, launch Application Designer and click Insert Definitions into Project. Choose Page and enter IB_ROUTINGDEFN. Choose IB_ROUTINGDEFN and click Close.
7. Double-click IB_ROUTINGDEFN. Right-click on the OnReceive Handler field and choose View Definition. On the ONRCVHDLRNAME field, right click and choose Record Field Properties. Click the Edits tab and note the Prompt Table: PSSRVHDLRRCV_VW.
8. In Management Studio, for the fsdev database, expand the Views navigator and locate PSSRVHDLRRCV_VW. Right click on PSSRVHDLRRCV_VW, choose Script View as, choose CREATE To, and click New Query. Note the command to create the view:
CREATE VIEW [dbo].[PSSRVHDLRRCV_VW] (IB_OPERATIONNAME, ONRCVHDLRNAME, DESCR) AS SELECT IB_OPERATIONNAME , HANDLERNAME , DESCR FROM PSOPRHDLR WHERE HANDLERID = 'RECV'
9. In PIA, navigate to Integration Broker > Integration Setup > Service Operations. In the Find Service Operation tab, in the Service Operation field, enter CREATE_WORKLIST_ITEM. Then click Search. Click CREATE_WORKLIST_ITEM to view it.
10. If the record is restricted, you will not be able to enter new Handlers. See step 3 above to resolve.
11. Click the Handler tab. Add a new Handler with the following information:
Name: ACK
Type: OnReceive
Implementation: Application Class
Status: Active
Click Details and add the following information:
Package Name: PT_WF_WORKLIST
Path: : [that is, only a colon must be entered]
Class ID: OnAckForMarkedWorkedResp
Method: OnAckReceive
12. Click Save.
Problem:
After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:
(IBRK-08): IB Routing referencing invalid service operation:
Routing Operation Version
– —— ——— ——-
~GEN~UPG~24567 IB_INST_VER_ASYNC_MSG VERSION_1
~GEN~UPG~17626 IB_INST_VER_RESP_MSG VERSION_1
2 Total Rows
Solution:
Delete the above two routings:
1. Query records that appear in Integration Broker Audit section IBRK-08
select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = ‘~GEN~UPG~24567’ or ROUTINGDEFNNAME = ‘~GEN~UPG~17626’
2. Launch PIA and search for the page that contains these values. Navigate to Integration Broker > Integration Setup > Routings. In the Find an Existing Value tab, in the Routing Name begins with field, enter ~GEN~UPG~24567. Click Search. It returns ‘No matching values were found.’ Then click the Add a New Value tab. The record appears.
3. Type Ctrl + J to get the page information. Note the Page (IB_ROUTINGDEFN).
4. On GL-WEB-APP, launch Application Designer. Insert Definitions into Project. Choose Definition Type Page and enter IB_ROUTINGDEFN in the Name field. Then press Enter. Insert the IB_ROUTINGDEFN page.
5. Right-click the Service Operation field, and choose Field Definition. In the Record Definition, choose Record Field Properties. Click the Edits tab and note the Prompt Table: PSOPERATION.
select * from PSOPERATION
select * from PSOPERATION where IB_OPERATIONNAME = ‘IB_INST_VER_RESP_MSG’ or IB_OPERATIONNAME = ‘IB_INST_VER_ASYNC_MSG’
6. Delete the two routings above (~GEN~UPG~24567 and ~GEN~UPG~17626). In PIA, navigate to PeopleTools > Integration Broker > Service Utilities > Service Administration. Select the Routings tab, and expand the Delete section. For each routing name (~GEN~UPG~24567 and ~GEN~UPG~17626), enter the Routing Name and click Search. The routing name appears. Check Select and then click Delete.
Reference:
E-IB: IBRK-xx SYSAUDIT exceptions after applying Maintenance Pack(s) (Doc ID 654766.1)
EFSCM: Orphan routing issue for FSCM9 customers after upgrading to 8.49 tools (Doc ID 661088.1)
[amazon asin=0071664939&template=iframe image&chan=default] [amazon asin=1430237074&template=iframe image&chan=default] [amazon asin=0071787925&template=iframe image&chan=default]
Problem:
After running the SYSAUDIT report, the following error appears under Integration Broker Audits:
(IBRK-05): Service Operation with missing service: Service Operation Service - ---------------- ------- PV_ORDER_XCBL3 PV_ORDER_XCBL3 1 Total Rows
Solution:
1. Check the “Data Management” PeopleBook, under the “Ensuring Data Integrity” section for information on resolving Integration Broker errors.
2. Check the Service Operations (PSOPERATION) and Service’s (PSSERVICE) tables in the fsdmo and fsdev databases.
select * from PSOPERATION where IB_SERVICENAME like 'PV_ORDER%' select * from PSSERVICE where IB_SERVICENAME like 'PV_ORDER%'
Note that PV_ORDER_XCBL3 appears in the PSOPERATION table in fsdev, but not in the PSSERVICE table. Note also that PV_ORDER_XCBL3 appears only in fsdev, but not in fsdmo.
Therefore, backup the row containing PV_ORDER_XCBL3 and then delete the row from the PSOPERATION table in the fsdev instance:
select * from PSOPERATION where IB_SERVICENAME = 'PV_ORDER_XCBL3' delete from PSOPERATION where IB_SERVICENAME = 'PV_ORDER_XCBL3'
3. Deleting the record introduced an IBRK-06 error on the SYSAUDIT report. To restore the data that was deleted:
insert into PSOPERATION
(IB_OPERATIONNAME, VERSION, DEFAULTVER, RTNGTYPE, IB_USERPWDREQ, IB_SERVICENAME, IB_ALIASNAME, LASTUPDDTTM,
LASTUPDOPRID, OBJECTOWNERID, DESCR, DESCRLONG)
values
('PV_ORDER_XCBL3', 1, 'VERSION_1', 'A', 'N', 'PV_ORDER_XCBL3', '', '2008-12-11 16:47:00.000', 'SVP1',
'DPV', 'xCBL Order', NULL)
4. In PIA, navigate to Integration Broker > Service Utilities > Service Administration. Click the Service Operations tab. Expand Delete and in the Service Operation field, enter PV_ORDER_XCBL3. Check Select, and then click Delete.
Under Results, ‘Successful delete’ appears.
After rerunning SYSAUDIT, the exception no longer appears.
(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist in PSXLATITEM Table
Problem:
After running SYSAUDIT on FSDEV, the following error appears:
(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist In PSXLATITEM Table: Query Name Field Name ---------- ---------------------- ARDISH01 DRAFT_TYPE 1 Total Rows
Solution:
1. Determine if scriptsPTPATCH.DMS was run. Log onto SQL Server Management Studio and running the following command:
select * from PS_MAINTENANCE_LOG where UPDATE_ID = '768890';
2. Next, load Application Designer and copy the PATCH849 project from file.
It was already copied.
3. Check PS_QRYFIELD_VW to see the fields used in the ARDISH01 query:
select * from dbo.PS_QRYFIELD_VW where QRYNAME = 'ARDISH01'
4. Get list of ‘DRAFT_’ field names from the PSXLATITEM table:
select distinct FIELDNAME from PSXLATITEM where FIELDNAME like 'DRAFT_%'
There is no DRAFT_TYPE field in this table.
5. Get list of ‘DRAFT_’ field names from the PSXLATITEM table:
Checked SYSAUDIT for FSDMO. This error is not present. Apply MP5 to FSDEV to resolve issue.
Problem:
After completing installing FSDEMO, SYSAUDIT is run. The following errors appear on the report:
Application Engine Audits Result: OK Clear List Audits Result: OK Electronic Commerce Audit Result: OK Field Definition Audit Result: OK Menu Definition Audit Result: OK Security Audits Result: Exception(s) Found (SEC-30) Role User table (ROLEXLATOPR) should be populated when new User Profiles (entries in PSOPRDEFN) are created using User Profile component through PIA. The following User Profiles need to be fixed by simply opening and saving them through PIA: Oper ID Description - ----------------------------- ------------------------------ ENTMGR_PRO Procurement Catalog Manager 1 Total Rows Page Definition Audit Result: OK PeopleCode Definition Audit Result: OK Process Scheduler Audit Result: OK Query Definition Audit Result: Exception(s) Found (QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist In PSXLATITEM Table: Query Name Field Name - --------------------------------------------------------------------- ARDISH01 DRAFT_TYPE 1 Total Rows Record Definition Audit Result: OK Language Definition Audit Result: OK SQL Audits Result: OK Tree Definition Audit Result: OK Version Check Audits Result: OK XLATT Definition Audit Result: OK Analytic Audit Result: OK XML Publisher Audit Result: OK Integration Broker Audits Result: Exception(s) Found (IBRK-08) : IB Routing referencing invalid service operation: Routing Operation Version - ------ --------- ------- ~GEN~UPG~24567 IB_INST_VER_ASYNC_MSG VERSION_1 ~GEN~UPG~17626 IB_INST_VER_RESP_MSG VERSION_1 2 Total Rows (IBRK-21) : Operations with duplicate routings: Operation Version Routing - -------- ------- ------- QAS_CRASH_MSG VERSION_1 ~GEN_UPG~18727 QAS_CRASH_MSG VERSION_1 ~GEN~UPG~19278 2 Total Rows
Solution:
Apply the latest Financials/SCM Maintenance Pack to resolve some of these errors.
Recent Comments