Errors and How to Resolve Them
A report occasionally lists a status of Failure for tables that are created successfully. These failures are generally due to problems creating indices and are not critical for the successful installation of the software.
During an upgrade or cumulative update, you could receive failures for some tables. To confirm successful table creation, verify that the following tables were created successfully:
F0007Z1
F00092
F0086
F03B11
F03B14
F03B112
F060116
F06106
F08042
F08330
F0911
F1501B
F1721
F1731
F17111
F30006Z1
F3002Z1
F3003Z1
F3460Z1
F39062
F4077
F4106
F4111
F41508
F4600
F4812H
F5215
F7302
F986113
Reports frequently list a status of No Action for tables the system created successfully. This status is accompanied by source and target data source warnings for these tables to explain why no action was taken. These warnings are normal and you can ignore them. The most common reasons for the warnings are because the source and target data sources are the same or the table was created by a previously installed environment.
When the source and target are the same, the report lists the following warnings:
Source data source warning |
Target data source warning |
---|---|
Source Same as Target |
Existing table |
This commonly occurs when the "copied from" data source is the same as the "target" data source (where the table is mapped), and often occurs for the following tables:
UDC tables |
Menu tables |
---|---|
F0004 and F0005 |
F0082, F00821, F0083, and F0084 |
If you load multiple environments that share the same mappings (for example, DV920 and TS920), the first environment loaded (DV920 in this case) lists the tables with a Success status. The second environment (TS920) lists any tables already created during the first environment load with a status of No Action and a target data source warning of Existing Table.
The No Action status and Existing Table warning for the second (TS920) environment are normal. You can verify that any table with a target data source warning of Existing Table has been created successfully by verifying it was created while loading a previous environment.