-- ============================================================================ -- SAMPLE ONLY - mirrors the Shipment example so you can run the API end-to-end -- against a scratch 11g schema. For the real migration you map your EXISTING -- tables instead; do not run this against production. -- ============================================================================ CREATE TABLE SHIPMENTS ( SHIPMENT_ID NUMBER(18) NOT NULL, SHIPMENT_NO VARCHAR2(30) NOT NULL, ORIGIN_CODE VARCHAR2(10), DESTINATION_CODE VARCHAR2(10), WEIGHT_KG NUMBER(12,3), STATUS VARCHAR2(20) DEFAULT 'NEW' NOT NULL, IS_ACTIVE NUMBER(1) DEFAULT 1 NOT NULL, CREATED_AT DATE DEFAULT SYSDATE NOT NULL, UPDATED_AT DATE, ROW_VERSION NUMBER(10) DEFAULT 0 NOT NULL, CONSTRAINT PK_SHIPMENTS PRIMARY KEY (SHIPMENT_ID), CONSTRAINT UQ_SHIPMENTS_NO UNIQUE (SHIPMENT_NO), CONSTRAINT CK_SHIPMENTS_ACTIVE CHECK (IS_ACTIVE IN (0, 1)) ); CREATE SEQUENCE SHIPMENTS_SEQ START WITH 1 INCREMENT BY 1 CACHE 20 NOCYCLE; CREATE INDEX IX_SHIPMENTS_STATUS_CREATED ON SHIPMENTS (STATUS, CREATED_AT); -- Optional: if the legacy table uses ROW_VERSION-less updates, either add the -- column (ALTER TABLE ... ADD ROW_VERSION NUMBER(10) DEFAULT 0 NOT NULL) or -- remove the ROW_VERSION checks from the repository.