Question

PSO Staging logic inbound issue

  • 28 November 2023
  • 3 replies
  • 74 views

Userlevel 1
Badge +3

Hi Team,

We have configured PSO staging logic as per the document.Outbound is working fine, but seems inbound is having an issue.We further checked the log too, log is stating the following error message: ‘Data member specified by attempt_cnt cannot be found’.

Screenshots for further reference:

I_XML Metadata

SQL Query

Thanks

Venkat


3 replies

Userlevel 4
Badge +12

@ruben.maas @Aaron.Sleight any idea why this is happening?

Userlevel 5
Badge +13

Hi @venkatesh  \ @SAMLK , 

 

The schema of the i_xml table is not valid. 

 

This i_xml table you have in your environment has probably been installed in earlier version and does NOT have all fields available to support the staging logic. 

 

the inbound staging table should match the following schema (SQL Server):

CREATE TABLE [dbo].[i_xml_pso](
    [message_id] [nvarchar] (64) NOT NULL, 
    [message_name] [nvarchar] (128) NULL, 
    [message_operation] [nvarchar] (16) NULL, 
    [message_priority] [numeric](28, 10) NULL, 
    [message_reference] [nvarchar] (128) NULL, 
    [message_response] [nvarchar] (MAX) NULL, 
    [message_response_code] [numeric](28, 10) NULL, 
    [message_status] [nvarchar] (32) NULL, 
    [message_type] [nvarchar] (128) NULL, 
    [message_xml] [nvarchar] (128) NULL, 
    [modified_by] [nvarchar] (32) NULL, 
    [modified_dttm] [datetime] NULL, 
    [node] [nvarchar] (256) NULL, 
    [not_after_dttm] [datetime] NULL, 
    [not_before_dttm] [datetime] NULL, 
    [problem_desc] [nvarchar] (MAX) NULL, 
    [process_end] [datetime] NULL, 
    [process_start] [datetime] NULL, 
    [remote_addr] [nvarchar] (32) NULL, 
    [remote_host] [nvarchar] (64) NULL, 
    [run_id] [nvarchar] (32) NULL, 
    [server_assigned_to] [nvarchar] (128) NULL, 
    [server_group_assigned] [nvarchar] (64) NULL, 
    [server_name] [nvarchar] (64) NULL, 
    [server_processed_by] [nvarchar] (128) NULL, 
    [server_received_by] [nvarchar] (128) NULL, 
    [source] [nvarchar] (32) NULL, 
    [target] [nvarchar] (256) NULL, 
    [user_def_dttm1] [datetime] NULL, 
    [user_def_dttm2] [datetime] NULL, 
    [user_def_dttm3] [datetime] NULL, 
    [user_def_dttm4] [datetime] NULL, 
    [user_def_num1] [numeric](28, 10) NULL, 
    [user_def_num2] [numeric](28, 10) NULL, 
    [user_def_num3] [numeric](28, 10) NULL, 
    [user_def_num4] [numeric](28, 10) NULL, 
    [user_def1] [nvarchar] (256) NULL, 
    [user_def10] [nvarchar] (256) NULL, 
    [user_def11] [nvarchar] (256) NULL, 
    [user_def12] [nvarchar] (256) NULL, 
    [user_def13] [nvarchar] (256) NULL, 
    [user_def14] [nvarchar] (256) NULL, 
    [user_def15] [nvarchar] (256) NULL, 
    [user_def16] [nvarchar] (256) NULL, 
    [user_def17] [nvarchar] (256) NULL, 
    [user_def18] [nvarchar] (256) NULL, 
    [user_def19] [nvarchar] (256) NULL, 
    [user_def2] [nvarchar] (256) NULL, 
    [user_def20] [nvarchar] (256) NULL, 
    [user_def21] [nvarchar] (256) NULL, 
    [user_def22] [nvarchar] (256) NULL, 
    [user_def23] [nvarchar] (256) NULL, 
    [user_def24] [nvarchar] (256) NULL, 
    [user_def25] [nvarchar] (256) NULL, 
    [user_def3] [nvarchar] (256) NULL, 
    [user_def4] [nvarchar] (256) NULL, 
    [user_def5] [nvarchar] (256) NULL, 
    [user_def6] [nvarchar] (256) NULL, 
    [user_def7] [nvarchar] (256) NULL, 
    [user_def8] [nvarchar] (256) NULL, 
    [user_def9] [nvarchar] (256) NULL, 
    [attempt_cnt] [numeric](28, 10) NULL, 
    [attempt_interval] [numeric](28, 10) NULL, 
    [attempt_max] [numeric](28, 10) NULL, 
    [batch_id] [nvarchar] (32) NULL, 
    [created_by] [nvarchar] (32) NULL, 
    [created_dttm] [datetime] NULL, 
    [message_body] [nvarchar] (MAX) NULL, 
    [message_comment] [nvarchar] (256) NULL, 
    [message_group] [nvarchar] (128) NULL, 
    [message_header] [nvarchar] (MAX) NULL
    ,constraint i_xml_pso_PK PRIMARY KEY CLUSTERED (message_id))

 

 

If you don't use the i_xml table for any other purpose you can drop and re-create the table to match the schema above. 

 

or otherwise you can setup a new staging table like I_XML_PSO.

 

If you create a separate staging table you have to ensure you copy the meta data as well. 

 

Cheers, 

 

Ruben

 

Userlevel 1
Badge +3

Hi Ruben,

 

Thanks for the response I dropped the existing I_XML table and Depolyed the schema you have provided, but still we are facing the same issue. Is there anything we are missing?

 

Screenshot for your reference

 

Thanks,

Venkat

Reply