The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>CustomizingDocumentation>CustomizingModules>CheckDatabaseConsistencyMOD007213

Check Database Consistency MOD007213 From DB 39.5.0

Description for versions < S 39.5.8 or DB 39.5.0


Access path

  • Customizer Databases Check Database Consistency

From DB 39.5.7

Information
  • In this module, different objects (I-texts, hyperlinks, object protection, relationships) can be checked for data consistency or incorrect data for each database instance.
    • The I-text check displays whether there are I-texts that are incorrect, unused, or used twice.
    • The I-text correction (check and write I-texts) first checks whether there are incorrect or unused I-texts and thereafter corrects them according to the table below.
    • The hyperlink check shows whether there are hyperlinks that are incorrect, unused, or used twice.
    • The hyperlink correction (check and write hyperlinks) first checks whether there are incorrect or unused hyperlinks and thereafter corrects them according to the table below.
    • The relationship check shows, where parent records of records are missing in the database.
    • The object protection shows, where in the database the object protection is incorrect.
    • NEW The dash record check shows whether there are records with "-" in the database that can intermediately be "ZERO".
    • NEW The dash record correction (check and write dash records) first checks whether there are records with "-" in the database and thereafter corrects them in accordance with the table below.

Up to DB 39.5.7

Information
  • In this module, different objects (I-texts, hyperlinks, object protection, relationships) can be checked for data consistency or incorrect data for each database instance.
    • The I-text check displays whether there are I-texts that are incorrect, unused, or used twice.
    • The I-text correction (check and write I-texts) first checks whether there are incorrect or unused I-texts and thereafter corrects them according to the table below.
    • The hyperlink check shows whether there are hyperlinks that are incorrect, unused, or used twice.
    • The hyperlink correction (check and write hyperlinks) first checks whether there are incorrect or unused hyperlinks and thereafter corrects them according to the table below.
    • The relationship check shows, where parent records of records are missing in the database.
    • The object protection shows, where in the database the object protection is incorrect.

From DB 39.5.6

Details
  • The module shows the database views saved and activated under the current license (Active checkbox =Checked) QxxB-database instances and NEW database views.

Up to DB 39.5.6

Details
  • The module shows the QxxB database instances saved and activated under the current license (Active checkbox = Checked).

From S 39.5.5

Procedure
  • Select the required check-value for the required database from the Consistency check listbox.
  • Click on the Perform checks button.
    • The respective database instances are checked.
    • A file with the following structure is created:
      • NEW [Type]_check_[SchemaNameQ1-7B]_[Date]_[Time].chk or [Type]_fix_[SchemaNameQ1-7B]_[Date]_[Time].chk
        • Example: iText_Hyperlink_Relation_and_Object_check_Q3B_21092015_143656.chk / iText_and_Hyperlink_fix_Q3B_21092015_143656.chk
    • This file is stored in the Log folder in the PLANTA work directory.
    • The created ASCII file can be viewed via a text editor (e.g. Notepad).

Up to S 39.5.5

Procedure
  • Select the required check-value for the required database from the Consistency check listbox.
  • Click on the Perform checks button.
    • The respective database instances are checked.
    • A file with the following structure is created:
      • [Type]_check_[SchemaNameQ1-7B].chk, or [Type]_fix_[SchemaNameQ1-7B].chk
        • Relations_check_Q1B.chk or iText_fix_Q1B.chk
    • This file is stored in the Log folder in the PLANTA work directory.
    • The created ASCII file can be viewed via a text editor (e.g. Notepad).

See also: System parameters and Database instance parameter

Evaluation of the Log Files

General Output Information

Error type Error output example Description
Data table has incorrect data   Parent category for elements with incorrect files,
e.g. incorrect URL for hyperlinks
  Data table has incorrect relations

Hyperlinks with incorrect data

I-texts with wrong backlink 		 

I-text Check/Correction

Legend for example

  • [Location (schema or DT-ID.DI-ID] ([Number of incorrect records]) [List of the I-text-IDs of all incorrect I-texts]

From S 39.5.19

Error type Error output example Description Autom. correction Manual correction
I-texts with wrong backlink        
  DT441.DI000456 (1)
687, 		Incorrect values in the Data item, Data table, or Record ID fields, e.g. incorrect values in I-text 687 in DI000456 in DT441 NEW Missing or incorrect data is automatically corrected Not required.
duplicate I-texts in referencing tables        
  DT500.DI024237 (1)
761, 		I-texts that are used twice A new I-text with the same values is created and the reference uses it instead of the old I-text Not required.
I-text reference inexistent in I-text table        
  DT441.DI000456 (1)
712, 		I-texts that do not exist in the I-text table I-text-field of the reference DI is set to empty Not required.
I-text strings in I-text table, that are not referenced        
  Q3B (2)
11457, 11458, 		I-texts that are not used I-text is deleted Not required.

Up to S 39.5.19

Error type Error output example Description Autom. correction Manual correction
I-texts with wrong backlink        
  DT441.DI000456 (1)
687, 		Incorrect values in the Data item, Data table, or Record ID fields, e.g. incorrect values in I-text 687 in DI000456 in DT441 None Revise data.
duplicate I-texts in referencing tables        
  DT500.DI024237 (1)
761, 		I-texts that are used twice A new I-text with the same values is created and the reference uses it instead of the old I-text Not required.
I-text reference inexistent in I-text table        
  DT441.DI000456 (1)
712, 		I-texts that do not exist in the I-text table I-text-field of the reference DI is set to empty Not required.
I-text strings in I-text table, that are not referenced        
  Q3B (2)
11457, 11458, 		I-texts that are not used I-text is deleted Not required.

Hyperlink Check/Correction

From S 39.5.19

Error type Error output example Description Autom. correction Manual correction
Double used hyperlinks        
  Q2B (1)
=7,= 		Hyperlinks that are used multiple times A new hyperlink with the same values is created and
the reference uses it instead of the former hyperlink 		Not required.
Unused hyperlinks        
  Q2B (3)
=4, 5, 15,= 		Hyperlinks that are not used Hyperlinks are deleted Not required.
Hyperlink does not exist in hyperlink DT        
  DT031.DI026735 (2)
=255, 348,= 		Hyperlinks that do not exist in the Hyperlink DT
Hyperlink field of the reference DI is set to empty Not required.
Hyperlinks with incorrect data        
  Without text - DT397 (2)
=39045, 39092,= 		Hyperlinks the display text of which is missing NEW New text is generated from HL-URL, if available.
If no HL-URL exists:
* For HL type file in DB New text is generated hyperlink_XXX (ID)
* Hyperlinks of other types are deleted 		Not required.
  Without URL - DT397 (2)
=39045, 39092, 		Hyperlinks the URL of which is missing NEW New URL is generated with the help of the display text
Example: %TEMP%\Testdokument.doc 		Not required.
  Data item incorrect - DT397 (2)
=39045, 39092,= 		Hyperlinks the reference of which is incorrect NEW Reference data is entered Not required.
  Size incorrect - DT397 (2)
=39045, 39092,= 		Hyperlinks the file size of which is incorrect
(only for file in DB HL type) 		NEW The character length of the BLOBs is entered Not required.
  Storage incorrect - DT397 (2)
=39045, 39092,= 		Hyperlinks the BLOB of which is incorrect
(only for file in DB HL type) 		None Revise data.
  CRC incorrect - DT397 (2)
=39045, 39092,= 		Hyperlinks the check value (CRC) of which is incorrect
(only for file in DB HL type)
  • NEW If BLOB is available, the CRC is generated.
  • NEW If not available, correction is not possible.
 Not required.

Up to S 39.5.19

Error type Error output example Description Autom. correction Manual correction
Double used hyperlinks        
  Q2B (1)
7, 		Hyperlinks that are used multiple times A new hyperlink with the same values is created and
the reference uses it instead of the old hyperlink 		Not required.
Unused hyperlinks        
  Q2B (3)
4, 5, 15, 		Hyperlinks that are not used Hyperlinks are deleted Not required.
Hyperlink does not exist in hyperlink DT        
  DT031.DI026735 (2)
255, 348, 		Hyperlinks that do not exist in the Hyperlink DT
Hyperlink field of the reference DI is set to empty Not required.
Hyperlinks with incorrect data        
  Without Text - DT397 (2)
39045, 39092, 		Hyperlinks the display text of which is missing None Revise data.
  Without URL - DT397 (2)
39045, 39092, 		Hyperlinks the URL of which is missing None Revise data .
  Data item incorrect - DT397 (2)
39045, 39092, 		Hyperlinks the reference of which is incorrect None Revise data.
  Size incorrect - DT397 (2)
39045, 39092, 		Hyperlinks the file size of which is incorrect
(only for file in DB HL type) 		None Revise data.
  Storage incorrect - DT397 (2)
=39045, 39092, 		Hyperlinks the BLOB of which is incorrect
(only for file in DB HL type) 		None Revise data.
  CRC incorrect - DT397 (2)
39045, 39092, 		Hyperlinks the check value (CRC) of which is incorrect
(only for file in DB HL type) 		None Revise data.

Object Protection Check

Information on object protection

From S 39.5.19

Note
  • Empty data tables are not checked.
  • Data tables without Pos. OS are not checked.

From S 39.5.19

Error type Error output example Description Autom. correction Manual correction
Datatable without protection DIs NEW        
  Q5B (2)
=802, 425,= 		Data table has no object protection DIs, the Pos. OS field, however, is filled None Insert object protection or empty Pos. OS.
The DB pos. of the
Created on DI of the data table must be in the Pos. OS field.
Data table without protection values        
  Q5B (2)
=402, 473,= 		Data table has object protection DIs, but they do not contain data None Revise data.
Data table has wrong object protection        
  Wrong protection value (3)
=91, 93, 286,= 		Values in "Owner", "Group", or "Any" are not between 0 and 7. None Revise data.
  Wrong order (1)
=89,= 		Types of the object protection DIs are in the wrong order. None Object protection DIs must be in the
described order in the data table.
  Wrong creation date (1)
=101,= 		Creation date is empty None Revise data.
  Wrong modify date (1)
=101,= 		Modification date is empty None Revise data.
  Wrong creation user (1)
=373,= 		Creation user has not been set None Revise data.
  Wrong modify user (1)
=487,= 		Modification user has not been set None Revise data.
  Wrong license (1)
=8559,= 		No license available or incorrect
Valid licenses are PLANTA licenses or numeric customer licenses. 		None Revise data.

Up to S 39.5.19

Error type Error output example Description Autom. correction Manual correction
Datatable without rwd        
  Q5B (2)
802, 425, 		Data table has no object protection DIs, the Pos. OS field, however, is filled None Insert object protection or empty Pos. OS.
The DB pos. of the
Created on DI of the data table must be in the Pos. OS field.
Data table without protection values        
  Q5B (2)
402, 473, 		Data table has object protection DIs, but they do not contain data None Revise data.
Data table has wrong object protection        
  Wrong protection value (3)
91, 93, 286, 		Values in "Owner", "Group", or "Any"
are not between 0 and 7. 		None Revise data.
  Wrong order (1)
89, 		Types of the object protection DIs are in the wrong order. None Object protection DIs must be in the
described order in the data table.
  Wrong creation date (1)
101, 		Creation date is empty None Revise data.
  Wrong modify date (1)
101, 		Modification date is empty None Revise data.
  Wrong creation user (1)
373, 		Creation user has not been set None Revise data.
  Wrong modify user (1)
487, 		Modification user has not been set None Revise data.
  Wrong license (1)
8559, 		No license available or not correct
Valid licenses are PLANTA licenses or numeric customer licenses. 		None Revise data.

Relationship check

Error type Error output example Description Automatic correction Manual correction
  Data table DT457 has no upper relations Information, that no relationship check is carried out for this data table since the data table has no parent data table None None, since there is no error
  DT463: 12 reference(s) is/are inexistent in datatable DT461

=Use this SQL Statement to check:=
=SELECT * FROM DT463 WHERE NOT EXISTS (SELECT 1 FROM DT461 WHERE DI001001 = DI001097);= 		In the first mentioned data table, there is/are one/several record/s, which does/do not exist in the second mentioned parent data table.
With the help of this SQL statement, the incorrect records are displayed in the database. 		None Check the records on the database with the specified select (or customize direct modules to the respective data table alternatively), check records and delete the obsolete child records, or recreate the parent records.
Relation has wrong DIs        
  Start/End DI does not exist (1)
=461,= 		For the relation of DT461, no start or end DI was specified None Insert start or end DI
  Start/End DI - wrong length - DT461
123 		The start or end DI has an incorrect length None Enter (six digit) DI number

From DB 39.5.7

Dummy Record Check/Correction

Error type Error output example Description Autom. correction Manual correction
Data table with references to dummy record in a foreign key        
  DT466 for records with primary ids: [['000233', '1445', 'ORACLE'],  ['000233', '1445', 'SAP FI']] List of all records that reference a dash record. Changing the respective column to "Zero". Not required.
Data table with dummy records        
  Q5B (1)
DT840
Use this statement to check:
SELECT * FROM DT840  WHERE DI009754 = '-' AND DI009755 = '-'; 		List of all data tables that contain a dash record. Deleting dash records. Not required.

         PLANTA project







 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl