RTD Studio Does Not Import A Stored Procedure When it Uses A“TIMESTAMP WITH TIME ZONE” Datatype Column As Input
Last updated on JANUARY 31, 2017
Applies to:
Oracle Real-Time Decisions Base Application - Version 3.1.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
On trying to import a stored procedure that has a parameter with datatype “TIMESTAMP WITH TIME ZONE” using the Oracle Database,
- RTD does not bring in this parameter.
- For Example, for a Stored Procedure as below:
---------------------------------
PROCEDURE X1P_INS_ADVISOR_REQUEST_3
(
in_ADV_REQUEST_DT IN TIMESTAMP WITH TIME ZONE
) IS
BEGIN
DECLARE
SESSION_SEQUENCE_NBR INTEGER := 0;
BEGIN
SELECT COUNT(*)
INTO SESSION_SEQUENCE_NBR
FROM x1t_advisor_request;
END;
END X1P_INS_ADVISOR_REQUEST_3
--------------------------------------
- When importing this into RTD, it shows blank.
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms