My Oracle Support Banner

W1-GISID Is Not Creating Records In W1_GIS_BATCH_DTLS Table Because K1-RIUSS And K1-RIUSP Need To Be Run After Truncate (Doc ID 2796835.1)

Last updated on OCTOBER 19, 2021

Applies to:

Oracle Utilities Work and Asset Management Enterprise Edition - Version 2.2.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.2.0.1.0 version, BT - Batch

W1-GISID is not creating records in W1_GIS_BATCH_DTLS table

The K1-CLNTB batch was used to truncate the W1_GIS_BATCH_DTLS table. W1-GISID batch job should be inserting entries in 2 different tables W1_GIS_ID_DTLS and W1_GIS_BATCH_DTLS but it is not since running K1-CLNTB. As result, W1-PRGIS batch job is not picking any records to process because it is identifying that W1_GIS_BATCH_DTLS table is empty which should be populated during the W1-GISID batch job run.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.