SAP-samples / SAP-samples/analytics-cloud-datasphere-community-content

Deployement of 6 SQL views of SAP_CC_DSP_Monitoring_Reporting_Tables.package failed

Open
#10 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
120
Forks
51
Avg merge
16h 12m
Merged PRs (30d)
1

Description

Hello,

I have been able to import successfully the package SAP_CC_DSP_Monitoring_Reporting_Tables.package in my SAP Datasphere SAP_ADMIN space.
But 6 SQL Views have errors :

  1. TCT_TASK_SCHEDULES_V_EXT_SRC has the following invalid SQL error : "return type mismatch: Function TCT_TASK_SCHEDULES_V_EXT_SRC_$TF: "RESULT_RAW"[ SPACE_ID:NVARCHAR(64) OBJECT_ID:NVARCHAR(256) APPLICATION_ID:NVARCHAR(256) ACTIVITY:NVARCHAR(256) OWNER:NVARCHAR(512) CRON:NVARCHAR(512) FREQUENCY:NVARCHAR(2048) CHANGED_BY:NVARCHAR(512) CHANGED_AT:TIMESTAMP ] != expected result [ SPACE_ID:NVARCHAR(64) OBJECT_ID:NVARCHAR(256) APPLICATION_ID:NVARCHAR(256) ACTIVITY:NVARCHAR(256) OWNER:NVARCHAR(512) CRON:NVARCHAR(512) FREQUENCY:NVARCHAR(2048) CHANGED_BY:NVARCHAR(512) CHANGED_AT:TIMESTAMP TZ_NAME:NVARCHAR(512) ]: line : line 36 col col 9 (at pos 1382), Code: 1306, SQL State: HY000"

  2. TASK_LOGS_V_EXT_SRC_PARAM has the following invalid SQL error : "return type mismatch: Function TASK_LOGS_V_EXT_SRC_PARAM_$TF: "RESULT_RAW"[ TASK_LOG_ID:INT SPACE_ID:NVARCHAR(64) APPLICATION_ID:NVARCHAR(256) OBJECT_ID:NVARCHAR(256) ACTIVITY:NVARCHAR(256) PEAK_MEMORY:DECIMAL(10,2) PEAK_CPU:BIGINT RECORDS:INT STATUS:NVARCHAR(256) SUB_STATUS_CODE:INT START_TIME:TIMESTAMP END_TIME:TIMESTAMP TRIGGER_TYPE:NVARCHAR(9) TRIGGERED_BY:NVARCHAR(512) DURATION:BIGINT START_DATE:NVARCHAR(10) ] != expected result [ TASK_LOG_ID:INT SPACE_ID:NVARCHAR(64) APPLICATION_ID:NVARCHAR(256) OBJECT_ID:NVARCHAR(256) ACTIVITY:NVARCHAR(256) PEAK_MEMORY:DECIMAL(10,2) PEAK_CPU:BIGINT RECORDS:INT STATUS:NVARCHAR(256) SUB_STATUS_CODE:INT SUB_STATUS:NVARCHAR(64) START_TIME:TIMESTAMP END_TIME:TIMESTAMP TRIGGER_TYPE:NVARCHAR(9) TRIGGERED_BY:NVARCHAR(512) DURATION:BIGINT START_DATE:NVARCHAR(10) ]: line : line 70 col col 9 (at pos 2720), Code: 1306, SQL State: HY000"

  3. TASK_LOGS_V_EXT_SRC has the following invalid SQL error : "invalid name of function or procedure: TASK_LOGS_V_EXT_SRC_PARAM: line : line 1 col col 302 (at pos 925), Code: 328, SQL State: HY000" --> depends on TASK_LOGS_V_EXT_SRC_PARAM which is KO.

  4. TCT_TASK_SCHEDULES_V_01 --> depends on TCT_TASK_SCHEDULES_V_EXT_SRC which can't be deployed.

  5. TASK_LOG_MESSAGES_V_EXT_RT : SQL is valid but error at deployment " "TASK_LOG_MESSAGES_V_EXT_RT" - Execution of a database statement for artifact 'TASK_LOG_MESSAGES_V_EXT_RT' failed with error: invalid default value: invalid default value for argument 'REALTIME_ACCESS': line 1 col 101 (at pos 100),"

  6. TASK_LOGS_V_EXT_RT has the following invalid SQL error : "invalid name of function or procedure: TASK_LOGS_V_EXT_SRC_PARAM: line 44 col 6 (at pos 1849), Code: 328, SQL State: HY000"

Could you please have a look ?

Thank you for your help,

Best regards,

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by importing SAP_CC_DSP_Monitoring_Reporting_Tables.package in the SAP Datasphere SAP_ADMIN space and inspect the deployment errors for the six named SQL views. Trace the dependencies from TCT_TASK_SCHEDULES_V_EXT_SRC and TASK_LOGS_V_EXT_SRC_PARAM, including the REALTIME_ACCESS default-value error. Done means all six views deploy successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.