Pre-Source Configuration Validations

Make sure that the application version you have chosen to configure with Oracle Utilities Analytics Warehouse product is in the product support matrix → Certified source list.

Run the following query in the source database application schema and in the target database MDADM schema. Validate that time zone is the same in both source and target.

select current_timestamp from dual;

Run the following query in the source database application schema and in the target database MDADM schema. Validate that character set is the same in both source and target.

select * from nls_database_parameters where parameter in ('NLS_NCHAR_CHARACTERSET','NLS_CHARACTERSET');

Run the following query in the source database application schema and validate that one row is displayed:

select * from v$database where log_mode = 'ARCHIVELOG';

Run the following query in the source database application schema and validate that one row is displayed:

Select * From v$database Where supplemental_Log_Data_Pk = 'YES';

Run the following query in the source database application schema and validate that one row is displayed:

select * from v$parameter where name = 'enable_goldengate_replication' and value = 'TRUE';

Run the following query in the source database application schema and validate that one row is displayed:

select * from dba_users where username = 'CCB01SRC'

Run the following query in the source database application schema and validate the following:

select grantee,granted_role,admin_option from dba_role_privs where grantee = 'CCB01SRC' union select grantee,privilege,grantable from dba_tab_privs where grantee = 'CCB01SRC' union select grantee,privilege,admin_option from dba_sys_privs where grantee = 'CCB01SRC' and privilege='UNLIMITED TABLESPACE' and admin_option='YES';

Validate that GG owner schema has CONNECT, RESOURCE, SELECT, EXECUTE, INSERT, UPDATE, UNLIMITED TABLESPACE, EXPORT/IMPORT FULL DATABASE privileges

Run the following query in the source database application schema and validate the following:

select * from dba_directories where directory_name = 'B1_DATA_DUMP_DIR';

1. It should return one row.

2. Ensure that the path mentioned in DIRECTORY_PATH column is a valid path.

3. Oracle user should be able to read and write on this directory.

Open the GoldenGate command line interface (ggsci) and validate that the version displayed in the command line interface should be as per the product support matrix.

To validate this:

1. Navigate to GoldenGate home path in source.

2. Validate that a folder with same name as the context code should be present under dirdat directory.

To validate this:

1. Navigate to GoldenGate home path in source.

2. Validate that a folder named diroby is present.

1. Navigate to GoldenGate home path in source.

2. Open the ENCKEYS file.

3. Validate that this file has a logical key name and key using which trail data will be encrypted.

Open manager.prm file present in <GoldenGate home>/dirprm location and validate that below parameters are appended:

autorestart replicat <context code>*, retries 5, waitminutes 2, resetminutes 60 purgeoldextracts dirdat/<context code>/*,usecheckpoints,minkeephours 4

Run the following command from the GoldenGate command line interface (ggsci) in the source server and validate that manager process is running:

ggsci> info mgr

1. Navigate to <GoldenGate monitoring agent instance home>/ogg_mon/Agents/OGGMonitorInstance/bin.

2. Execute the following command and validate that the version displayed is as per the product support matrix.

./displayMonitorAgentVersion.sh

Open GLOBALS file in the GoldenGate home location and validate that the EnableMonitoring command is present.

Run the following command from the GoldenGate command line interface (ggsci) and validate that the jagent process is in running state:

ggsci> info jagent

1. Application URL should be down, and users should not be able create/modify any transactions at the time of source configuration.

2. Application database should be up and running.

Run the following query in target database MDADM schema and validate the following:

select * from dba_directories where directory_name = 'B1_DATA_DUMP_DIR';

1. It should return one row.

2. Ensure that the path mentioned in DIRECTORY_PATH column is a valid path.

3. Oracle user should have read and write privileges on this directory.

Run the following query in target database MDADM schema and validate the following:

SELECT comp_name,owner FROM schema_version_registry where mrc_name='<schema prefix>';

<schema prefix>: Prefix you have provided at the time of running the RCU.

Query should retrieve one row for each of these components:

1. Audit Service

2. Audit Service Append

3. Audit Service Viewer

4. Oracle Platform Security Services

5. Service Table

6. WebLogic Services

1. Navigate to /<Oracle Data Integrator home> /user projects/domains/

2. Within this domain directory, there should be one directory with the same name as when the domain was created.

Log in to the WebLogic Administration Console for Oracle Data Integrator and validate that the user can login successfully.

1. Log in to the WebLogic Administration Console for ODI.

2. In the left pane, expand Environment and select Servers.

3. In the Servers table, the server's state is indicated in the State column.

4. It must be on running state.

1. Log in to Oracle Utilities Analytics work repository using Oracle Data Integrator Studio client.

2. Navigate to Topology → Agents → OracleDIAgent

3. Validate the host name and port number should be managed server port.

4. Right-click OracleDIAgent and click Test.

5. Test connection should be successful.

1. Navigate to GoldenGate home path in target.

2. Open ENCKEYS file.

3. Validate that this file should have logical key name and key using which trail data will be decrypted.

1. Navigate to GoldenGate home path in target.

2. Validate that a folder with name same as context code should be present under dirdat directory.

Run the following query in source database application schema and validate the following:

select value(x).getrootelement() src_parm_type, extractvalue(value(y),'//parameterType') src_param_type_cd, extractvalue(value(y),'//parameterValue') parm_value from f1_mst_config , table(xmlsequence(extract(xmltype('<xml>' ||mst_config_data ||'</xml>'),'//parameterType/../..'))) p , table(xmlsequence(extract(value(p),'/'))) x, table(xmlsequence(extract(value(x),'//parameterType/..'))) y where trim(bus_obj_cd) = 'C1-BIExtractParametersConfig';

Validate that four records are present with not null parameter value for parameter type toDoCharacteristicTypes.

Note: Use this query to validate scenarios from D01 - D14.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type recentToDoMiscellaneous.

Using the query listed in scenario D01, validate that two records are present with not null parameter value for parameter type ftCharacteristicValues.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type ftCharacteristicTypes.

This is not a mandatory parameter. If Exclude Archive Adjustment Types is configured then at least one record should be present with not null parameter value for parameter type excludeArchiveAdjustmentTypes.

Use the query listed in scenario D01 to validate.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type brokenPACharacteristicType.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type brokenPACharacteristicValue.

This is not a mandatory parameter. If Broken PA Adjustment Cancel Reasons is configured then at least one record should be present with not null parameter value for parameter type brokenPAAdjustmentCancelReasons.

Use the query listed in scenario D01 to validate.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type overdueProcessCharacteristicTypes.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type highBillCharacteristicTypes.

This is not a mandatory parameter. If Exclude High Bill Complaint Case Statuses is configured then at least one record should be present with not null parameter value for parameter type excludeHighBillCaseStatusTypes.

Use the query listed in scenario D01 to validate.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type highBillCaseTypes.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type saArrearsMiscellaneousTypes.

Using the query listed in scenario D01, validate that one record is present with not null parameter value for parameter type includeBillCalculationLines.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-BillingDayInWindow';

Two sets of bucket ranges should be present. One set is for inside day in window and another for outside day in window. In each set:

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-DaysBeforeBillWindowCloses';

Two sets of bucket ranges should be present. One set for day ranges when the bill window is still open, and another set for days when the bill window is closed. In each set:

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-DaysOfUnbilledUsage';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-DaysSinceLastFrozenBSeg';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-PAFuturePaymentAge';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-PANumberOfInstallments';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd= 'C1-RecurringChargeAmounts';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='C1-PPFuturePaymentAge';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following.

select value(x).getrootelement() src_parm_type, extractvalue(value(y),'//parameterType') src_param_type_cd, extractvalue(value(y),'//parameterValue') parm_value from f1_mst_config , table(xmlsequence(extract(xmltype('<xml>' ||mst_config_data ||'</xml>'),'//parameterType/../..'))) p , table(xmlsequence(extract(value(p),'/'))) x, table(xmlsequence(extract(value(x),'//parameterType/..'))) y where trim(bus_obj_cd) = 'D1-ODIBasedBIMasterConfig';

Validate that two records are present with marketRelationshipTypes.

Note: Use this query to validate scenarios from E01 - E04.

Using the query listed in scenario E01, validate that two records are present with subscriptionTypes.

Using the query listed in scenario E01, validate that at least one record is present with activityCategoryTypes.

It is not mandatory that above query should return one or more rows with deviceEventBOs. If this BO is configured and rows returned with deviceEventBOs, then ETL will exclude related device events, else it will load all device events.

Run the following query in the source database application schema and validate that at least one record is displayed:

select * from f1_ext_lookup_val where bus_obj_cd='D1-MeasurementConditionLookup';

Run the following query in the source database application schema and validate that at least one record is displayed:

select * from f1_ext_lookup_val where bus_obj_cd='D1-DaysSinceLastNormalMsrmtLkp';

Run the following query in the source database application schema and validate that at least one record is displayed:

select * from f1_ext_lookup_val where bus_obj_cd ='D2-ConsumptionSnapshotTypeLkup';

Run the following query in the source database application schema and validate that at least one record is displayed:

select * from f1_ext_lookup_val where bus_obj_cd ='D2-DaysSinceLastUTLookup';

Run the following query in the source database application schema and validate that at least one record is displayed:

select * from f1_ext_lookup_val where bus_obj_cd ='D2-SPUTAgingSnapshotTypeLookup';

This parameter is for integration of Oracle Utilities Meter Data Management with other utilities products. Validation of this parameter is not in the scope of this document.

This parameter is for integration of Oracle Utilities Meter Data Management with other utilities products. Validation of this parameter is not in the scope of this document.

Run the following query in the source database application schema and validate the following:

Select f1_ext_lookup_value,bo_data_area from f1_ext_lookup_val where bus_obj_cd='M1-CrewTimeUsageLookup';

1. Query should return one or more rows (i.e. crew time usage codes).

2. For each row in bo_data_area column a code should be present inside the tag <productivityIndicator>. For example: <productivityIndicator>M1NP</productivityIndicator>. Here, productivity code is M1NP.

Run the following query in the source database application schema and validate the following:

Select h.m1_hierarchy_cd,u.m1_hier_lev_flg from m1_hierarchy h , m1_hier_upstream u , m1_resrc_char c Where h.m1_hierarchy_cd=u.m1_hierarchy_cd and u.M1_Hier_Lev_Flg in ('M101','M102','M103') and c.char_val_fk1=h.m1_hierarchy_cd and c.char_type_cd='M1CRHIER';

1. Query should display rows with crew hierarchy code and hierarchy level if set already.

2. Validate that hierarchy level flag contains M101 or M102 or M103.

Run the following query in the source database application schema and validate the following:

Select h.m1_hierarchy_cd,u.m1_hier_lev_flg from m1_hierarchy h , m1_hier_upstream u , m1_svc_area_char c Where h.m1_hierarchy_cd=u.m1_hierarchy_cd and u.M1_Hier_Lev_Flg in ('M101','M102','M103') and c.char_val_fk1=h.m1_hierarchy_cd and c.char_type_cd='M1SAHIER';

1. Query should display rows with service area hierarchy code and hierarchy level if set already.

2. Validate that hierarchy level flag should contain M101 or M102 or M103.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-AppointmentTimeBucketConfig';

1. One negative bucket should be present for early appointment. For example, start range is -99999 and end range is 0.

2. No gaps or overlaps are allowed within the bucket ranges.

3. Bucket ranges should be configured as per the business need and it should cover all possible values. For example: -99999 to 0 (on time), 0-5(on time), 5-15 (15min Late), 15-30 (30min Late), 30-60(1 hour Late), 60-99999 (Too Late).

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-AppointmentTimeOfDayBktConf';

1. Bucket start and end range should be configured based on the crews business hours. For example, Crews will be available from 8am-8pm then start range is 480min end 1200min. This big bucket can be break into smaller multiple buckets like (8am-10am, 10am-12pm, 2pm-5pm, and 5pm-8pm).

2. Gaps and overlap ranges are allowed.

3. At least one bucket should be present to cover each time of the day.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-LateLogonBucketConf';

1. One negative bucket range -99999 to 0 should be configured to represent on time logon.

2. No gaps or overlaps are allowed within the bucket ranges.

3. Bucket ranges should be configured as per the business need and it should cover all possible values. For example: -99999 to 0 (on time), 0-5(on time), 5-15 (15min Late), 15-30 (30min Late), 30-60(1 hour Late), 60-99999 (Too Late).

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-EarlyLogoffBucketConf';

1. One negative bucket range -99999 to 0 should be configured to represent on time/Late logoff.

2. No gaps or overlaps are allowed within the bucket ranges.

3. Bucket ranges should be configured as per the business need and it should cover all possible values. For example: -99999 to 0 (on time/Late logoff), 0-5(on time), 5-15 (15min early), 15-30 (30min early), 30-60(1 hour early), 60-99999 (Too early).

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-WorkDurationDeviationBktCon';

1. Negative bucket ranges should be present for underestimated or as expected (i.e. actual duration is more than the expected duration).

2. Positive bucket ranges should be present for overestimated or as expected (i.e. actual duration is less than the expected duration).

3. No gaps or overlaps are allowed within the bucket ranges.

4. Bucket ranges should be configured as per the business need and it should cover all possible values. For example: -99999 to -25 (>25% Under), -25- to -10 (10–25% Under), -10 to -1 (1–10% Under), -1 to 0 (As Expected), 0 to 10(<10% Over), 10 to 25 (10–25% Over), and 25 to 99999(>25% Over).

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-TravleDurationDeviBktCon';

1. Negative bucket ranges for underestimated or as expected (i.e. actual duration is more than the expected duration).

2. Positive bucket ranges for overestimated (i.e. actual duration is less than the expected duration).

3. No gaps or overlaps are allowed within the bucket ranges.

4. Bucket ranges should be configured as per the business need and it should cover all possible values. For example: -99999 to -25 (>25% Under), -25- to -10 (10–25% Under), -10 to -1 (1–10% Under), -1 to 0 (As Expected), 0 to 10(<10% Over), 10 to 25 (10–25% Over), and 25 to 99999(>25% Over).

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='M1-TravleDistanceDeviBktCon';

1. Negative bucket ranges for underestimated or as expected (i.e. actual distance is more than the expected distance).

2. Positive bucket ranges for overestimated (i.e. actual distance is less than the expected distance).

3. No gaps or overlaps are allowed within the bucket ranges.

4. Bucket ranges should be configured as per the business need and it should cover all possible values. For example: -99999 to -25 (>25% Under), -25- to -10 (10–25% Under), -10 to -1 (1–10% Under), -1 to 0 (As Expected), 0 to 10(<10% Over), 10 to 25 (10–25% Over), and 25 to 99999(>25% Over).

Run the following query in the source database application schema and validate the following:

select value(x).getrootelement() "Extract Parameter Type", extractvalue(value(y),'//parameterType') "Parameter Code", extractvalue(value(y),'//parameterValue') "Parameter Value" from f1_mst_config , table(xmlsequence(extract(xmltype('<xml>'||mst_config_data||'</xml>') ,'//parameterType/../..'))) p , table(xmlsequence(extract(value(p),'/'))) x , table(xmlsequence(extract(value(x),'//parameterType/..'))) y where trim(bus_obj_cd) in ('W1-WAMBIExtractParameters','W1-BIExtractParameters');

Validate that at least one record is present with locationBOParameter.

Note: Use this query to validate scenarios from G01 - G05

Using the query listed in scenario G01, validate that at least one record is present with assetBOParameter.

Using the query listed in scenario G01, validate that at least one record is present with firmwareParameter.

Using the query listed in scenario G01, validate that at least one record is present with operationalDeviceBOParameter.

Using the query listed in scenario G01, validate that at least one record is present with assetFailureParameter.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-WAssetAgeBuckets';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-WAssetInstallAgeBuckets';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-AssetCriticalityBuckets';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-AssetConditionScoreBuckets';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-WorkPriorityBuckets';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-NumberOfCyclesOverdueBucket';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-MTBFMTTRBuckets';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-AssetAgeBktConfig';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.

Run the following query in the source database application schema and validate the following:

Select c.bkt_config_cd,val.bkt_start_range,val.bkt_end_range from f1_bkt_config c, f1_bkt_config_val val Where c.bkt_config_cd=val.bkt_config_cd and c.bus_obj_cd='W1-AssetInstallAgeBktConfig';

1. One bucket should have the start range as 0.

2. One bucket should have the end range as 99999.

3. No gaps or overlaps are allowed within the bucket ranges.