Her er min tankegang, og noget at prøve.
Det er interessant for mig, at feltet det fejler på er den første forekomst af et TIMESTAMP i tabellen. Når vi arbejder på teorien om, at TIMESTAMP kan have noget at gøre med det, så lad os først oprette en visning på MV_BRM_COMMUNICATION_DM, der kaster alle TIMESTAMP-felterne til DATE:
CREATE VIEW MV_BRM_COMM_DM_VIEW AS
SELECT COMM_ITEM_PK, COMM_ERROR_PK, COMM_ADDRESS_PRLO_PK,
COMM_ADDRESS_LOPR_PK, COMM_ADDRESS_PR_PK,
COMM_OUTBOUNDMESSAGE_ID, COMM_PIDM, COMM_CREATED_BY,
TO_DATE(COMM_CREATION_DATE) AS COMM_CREATION_DATE,
COMM_GENERIC_TEMPLATE_NAME, COMM_TEMPLATE_NAME,
COMM_TEMPLATE_VERSION,
TO_DATE(DATE_COMM_SENT) AS DATE_COMM_SENT,
TO_DATE(COMM_DATE_SENT) AS COMM_DATE_SENT,
COMM_COMMUNICATION_CHANNEL, COMM_SUBJECT, COMM_EMAIL_PK,
COMM_TO_ADDRESS, COMM_ISP_DOMAIN, COMM_CCLIST,
COMM_BCCLIST, COMM_REPLYTO, COMM_SENDER, COMM_REFERENCE_DESC,
COMM_OPTOUT_TOKEN, COMM_DELIVERED_FLAG, COMM_OPTOUT_FLAG,
COMM_OPTOUT_DATE, COMM_OPTOUT_CHANNEL, COMM_OPTIN_FLAG,
COMM_OPTIN_DATE, COMM_OPTIN_CHANNEL, COMM_OPTLOCK,
COMM_ERROR_FLAG, COMM_BOUNCED_FLAG, COMM_ONE_OFF,
COMM_OWNERID, COMM_OWNERNAME, COMM_OWNER_KEY, COMM_ORG_ID,
COMM_ORG_NAME, COMM_CONTENT_PURGED, COMM_ACTIVITY_DATE,
ACTIVITY_DATE
FROM MV_BRM_COMMUNICATION_DM
Skift nu din SELECT for at læse fra visningen, og se om tingene fungerer anderledes.
Ikke garanteret, da jeg ikke kan teste mod dit miljø, men det er noget at starte fra.
Del og nyd.