- October 24, 2017 at 4:01 am #11500
We got one error in the Integration today. <span style=”color: red; font-family: ‘GE Inspira’, sans-serif; font-size: 10pt; text-align: justify;”>DBMS error [ORA-01792: maximum number of columns in a table or view is 1000].</span>
Although the table had 516 columns(30 were made absent). But while merging the table with the Burst table we got the above error. We checked with the DBA and they told there are 526 columns in the Burst table. Not sure how count increased in the burst table.
Can you please put some insight in the issue.
<p class=”Body” style=”text-align: justify;”></p>October 24, 2017 at 4:23 am #11501Simon FaasKeymaster
The error is probably caused by a query that joins the burst and target tables.
Can you tell us
- How many columns are in the HVR channel for this table?
- How many columns in the burst table?
- How many columns in the target table?
For the burst table HVR is adding some extra internal columns. Also columns can be added using ColumnProperties /Extra.
SimonOctober 24, 2017 at 9:42 pm #11503
Below are the details
In HVR channel : 516 columns in the table(37 are marked as absent, and 6 extra columns added other than these 516 columns).
In the burst table : 526 columns
In target table : 484 columns
Please let me know if you need any more info.
AyushOctober 24, 2017 at 9:54 pm #11504
Sorry Simon, 5 extra columns are added in HVR channel on target side, not 6.October 27, 2017 at 8:31 am #11519Simon FaasKeymaster
When a column is marked as absent using ColumnProperties /Absent it will still be created in the burst-table. The reason is that this column may be used in an /IntegrateExpression to calculate a value for other columns.
To get rid of these columns completely you can delete them from the channel (double click on the table, find the columns, and delete them; alternatively you can delete them directly from the HVR catalogs hvr_column table in the hub repository)
After this run HVR Initialize for the Capture and Integrate location with “Scripts and Jobs” checked as well as “Table Enrollment”
After this an Online Refresh with re-create mismatched tables option for the affected table will be necessary to get the data and layout back in sync
- You must be logged in to reply to this topic.