Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error during validation of SIARD file #337

Open
gillianh1 opened this issue Nov 1, 2022 · 3 comments
Open

Error during validation of SIARD file #337

gillianh1 opened this issue Nov 1, 2022 · 3 comments
Assignees

Comments

@gillianh1
Copy link

Description:
50,122,865+ errors and 2G error log produced when validating SIARD file produced byt DBPTK desktop.
In one table a column of type "NUMBER" contains decimal values and believe this is the cause of this error?
Can you advise how to resolve? Is there is any config within DBPTK that we could change to allow validation to complete?

Context:
DBPTK Desktop: Windows version 2.7

Steps required to reproduce the bug:

  1. Extracted 7 tables from oracle database (one of which has column with type NUMBER and contains decimal point values)
  2. Ran validation on file. Failed with 50,122,865 errors like "Data type invalid - 48.22 is not in conformity with 'NUMERIC(38)' type"
  3. Validation completed but failed.

Attach any related screenshots below.
image

image

Logs too large - here is extract

"T_6.0 - Requirements for table data
T_6.0-1: [OK]
A_T_6.0-1-1: [OK]
A_T_6.0-1-2: [ERROR] - Data type invalid - 48.22 is not in conformity with 'NUMERIC(38)' type in content/schema1/table1/table1.xml
A_T_6.0-1-2: [ERROR] - Data type invalid - 581.44 is not in conformity with 'NUMERIC(38)' type in content/schema1/table1/table1.xml"
...
"A_T_6.0-1-2: [ERROR] - Data type invalid - 58.6 is not in conformity with 'NUMERIC(38)' type in content/schema1/table1/table1.xml
A_T_6.0-1-2: [ERROR]
Requirements for table data [FAILED]"

Find DBPTK Desktop logs at Help -> Logs menu.
Find DBPTK Enterprise logs with docker logs command.

@krosenbe
Copy link

krosenbe commented Feb 5, 2025

I am also experiencing this issue. Oracle column defined as NUMBER with no precision/scale is a floating point number, but DBPTK is interpreting this as NUMERIC(38) which is an integer. Please advise.

@luis100
Copy link
Member

luis100 commented Feb 5, 2025

@krosenbe could you please provide a reproducible example or instruction on how to create one?

@krosenbe
Copy link

krosenbe commented Feb 5, 2025

To reproduce, create a table in Oracle with NUMBER datatype (no precision or scale). Insert some numbers with decimal values (e.g., 10.2, 99.9999, 0.000003). Create SIARD. Validate the SIARD. Validation fails with errors including: "A_T_6.0-1-2: [ERROR] - Data type invalid - 10.2 is not in conformity with 'NUMERIC(38)' type..."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

5 participants