SQL Queries - CAST Measure Base - Checking and removing corruptions - integer out of range for dss_history table

Purpose of Query

This page handle the issue of getting out of range integer for dss_history table.

Applicable CAST Version

Release	Yes/No
8.3.x
8.2.x
8.1.x
8.0.x

Applicable RDBMS

RDBMS	Yes/No
Oracle Server
Microsoft SQL Server
CSS2
CSS3

Query for CSS

In order to confirm this, you can try to insert any information inside the DSS_HISTORY table via an sql session in pgadmin. For example:

INSERT INTO dss_history
            (description)
VALUES     ('TEST INFO');

Query result example

ERROR: integer out of range

Query result interpretation

Error mentioning integer out of range

Remediation:

In order to repair this, you have to drop the table DSS_HISTORY in the measure schema, recreate it, then do the upload from the central to the measure schema via the CLI, you can perform the drop and the recreate of the table as follows:

DROP TABLE dss_history

CREATE TABLE dss_history
             (
                          description CHARACTER VARYING(500) NOT NULL,
                          action_date TIMESTAMP without time zone NOT NULL DEFAULT Clock_timestamp(),
                          history_id serial NOT NULL
             )
             WITH
             (
                          oids=false
             );
 
ALTERALTER TABLE dss_history owner TO operator;

CREATE INDEX dss_history_idx ON dss_history USING btree (history_id);

Query for Oracle

NA

Query for SQL server

NA

Notes/comments

Related Pages