Data type support 9i Release 2

Does oracle 9i relase 2 support the float datatype for replication .

As a matter of fact oracle 9i has two types of api for external tables one is oracle_loader and the other is oracle_internal which in 10g become oracle_datapump.
What my question is how can I use the other type in case of external table as we are doing in 10g? Do I need to run any script to enable this feature or is there any privillege issue?
I've given the read, write privillege to the user and the oracle user has read/write permission in os level on the location of the directory.

Similar Messages

Tg4msql - Blob Data Type Support(Oracle 8i - sql server 2000)

hi,
We are trying to replicate the data from oracle 8i to sql server 2000 through tg4msql.if we want to replicate the data thet contains the blob field , we are getting invalid expression in the procedure marked with error line.
the procedure i am using is as follows
CREATE OR REPLACE PROCEDURE INSERT_SQL
AS
BEGIN
FOR VAL_CURSOR IN
--Get the Data from the table with status 0
SELECT rs_report_rowid FROM BIJU.rs_report where rs_report_status = 0
LOOP
for new_cursor in
--get the details of the record with the row id
select id ,name,DOB from biju.sample where rowid = val_cursor.rs_report_rowid
LOOP
---insert the data from oracle to sql where the oracle data type contains blob(here photo field data type is blob).
Error Line: insert into [email protected](id,name,photo) values(new_cursor.id,new_cursor.NAME,new_cursor.DOB);
END LOOP;
END LOOP;
COMMIT;
END;
i want to know that tg4msql won't support the blob data type on the oracle end?we configured blob eqivalent in sql server as binary.Any help or suggestion regarding this are welcome..
regards
Srini

Srini,
Support for LOB was added in v9.2. It is not supported in 8i.

Discoverer 4i - Time Series Data type support

Does Discoverer 4i support time-series data type i.e. the ability to store an entire string of
numbers representing for example daily or weekly data points?
Thanks & Regards,
Deepti

Hi O G-M,
Each model must contain one numeric or date column that is used as the case series, which defines the time slices that the model will use. The data type for the key time column can be either a datetime data type or a numeric data type. However, the column must
contain continuous values, and the values must be unique for each series. The case series for a time series model cannot be stored in two columns, such as a Year column and a Month column. For more information about it, please see:
http://msdn.microsoft.com/en-us/library/ms174923(v=sql.100).aspx
Thanks,
Eileen
Eileen Zhao
TechNet Community Support

Data Types supported by Express Edition

Dear All,
Is BLOB compatable in Express edition.
What are the data-types are supported by Express edition.
Thanks & regards,
Abk

http://download.oracle.com/docs/cd/B25329_01/doc/appdev.102/b25108/xedev_design.htm#XEDEV02000
HTH...

Data types supported in weblogic web service

I have used byte[] (base64) array to pass binary data using weblogic in a web service, since byte[] is a java datatype that is supported, is there a definite guideline available that byte [][] ( multi-dimensional array} is not supported in weblogic 8.1? (I have tried and failed with byte [][])
Thanks

Hi gchirrav ,
Multi-Dimentional array support not listed in supported Data Types in weblogic 8.1.
Go through the following link, you will find supported data types.
http://e-docs.bea.com/wls/docs81/webserv/implement.html#1054236
----Anilkumar kari

Object Data Type support and JDBC2 SQLData interface

Another useful and probably easy to implement feature is to support
persistent-aware classes based on JDBC SQLData interface._
It will let us persist such a member of persistent class to an object
type column._
The interface is very simple and quite limited (no support for arrays
etc) but useful.
The only thing we would need is to maintain jdbc object maps for our
database connections and tell Kodo metadata not to enhance this
particular class member but treat is as a simple type_
Alex

In SPROXY you can open your proxy and then view the Activation Log under the GoTo menu. The log will explain better what the problems might be. In my case I needed to activate another data type enhancement first.
Thanks,
Matt

JAX-RPC 9.0.4 --- Data Types Supported

Hi,
does any body know is java.util.List is a supported Datatype on OC4j 9.0.4.2 for JAX-RPC.
Cheers
Gaurav

Gaurav,
Not sure which version of JAX-RPC you are intended to run on top of 9.0.4.2 ?
In any way, if you want your service to work with the majority of the clients, you need to focus on the XML types; not the java types.
To my knowledge, the List will be mapped to a proprietary type, at best, which make it harder to re-use.
All the best,
Eric

XPath support for Date data type.

Hi,
I am using XPathAPI class for extracting data from an XML source.I have a column in the data which has date type (any date type supported by MS SQL, Ms Access etc).I want to select only some rows from that column.I'm not aware if XPath provides operations on date types.
Is there any way I could compare two date values using XPath expressions??
thanx,
regards.

After checking XPath 1.0 recommandation (http://www.w3.org/TR/xpath), I see nothing about date type support.
You will have to try little tricks, like converting 2002/09/05 into a number 20020905, making it available for < and > comparisons...

Matching data types b/w oracle and sql server

anyone here knows if there is a list of data types supported by both oracle and sql server (regardless of releases & versions?
an immediate response would be highly appreciated.
thanks.

Hi,
The following post might be of assistance to you:
http://msdn.microsoft.com/en-us/library/ms151817.aspx
If this is what you're looking for, then mark the question as answered and closed.
Regards,
Naveed.

Float data types

I don't really know SSAS but have been a .NET programmer and worked with SQL Server and T-SQL for years. I am working on a project where there is a database storing sales transactions and a cube that is created nightly so we can get MTD Sales, YTD
Sales, Profit $, etc.
I just ran into an issue where I got an error retrieving the Profit $ measure (using an MDX query inside of a SQL stored procedure using OPENQUERY) and found that the profit $ should be 0.07 but is coming back as 6.9999999999993179E-2. After talking
to our DBA, he said all of the calculations in the cube are double precision floating point and I need to round all results to 2 decimal places (programs like Excel handle the rounding and I should too.)
Our DBA also claims the measures can't be calculated and returned as currency. He claims that the potential for error is very small and no one has ever complained about a $ value being off.
I am struggling with this answer because I have always been told never to use floating point for monetary values. I am having a hard time believing there is no way to have a measure be a currency field that is accurate. I looked for articles
online but can't seem to find anything to answer my questions.
Could someone please point me in the right direction? Thanks so much!

Your DBA is not completely correct in his claims. All calculations are not floating point below is a link to all of the data types supported by SSAS (Multi-Dimensional)
https://technet.microsoft.com/en-us/library/gg471558%28v=sql.110%29.aspx?f=255&MSPPError=-2147217396
SSAS supports a currency data type. It's 4 decimal places not 2, but it is the recommended data type for currency values as it does not suffer from the imprecision of the double data type.
The other thing measures in a cube have is the concept of a format string, so you can ask the cube to return a pre-formatted value to you. But default an OPENQUERY will just return the raw value, but if you add the following:
CELL PROPERTIES FORMATTED_VALUE
to the end of your MDX query that should tell it to return the formatted value (which could be something like "$#,##0.00")
See here https://msdn.microsoft.com/en-us/library/ms146084.aspx for a list of all the different format masks that can be applied
http://darren.gosbell.com - please mark correct answers

Display data type

hi,
how to display oralce's data type from system table is there any system table to fetch the data types for that version i'm using Oracle 11g.
in sql server we fetch the details by using
select * from sys.types
this will return what the data types supported by that version
Thanks!

There is a package called STANDARD in the SYS schema that defines many of the standard datatypes and functions.
e.g.
CREATE OR REPLACE package SYS.STANDARD AUTHID CURRENT_USER is              -- careful on this line; SED edit occurs!
/********** Types and subtypes, do not reorder **********/
type BOOLEAN is (FALSE, TRUE);
type DATE is DATE_BASE;
type NUMBER is NUMBER_BASE;
subtype FLOAT is NUMBER; -- NUMBER(126)
subtype REAL is FLOAT; -- FLOAT(63)
subtype "DOUBLE PRECISION" is FLOAT;
subtype INTEGER is NUMBER(38,0);
subtype INT is INTEGER;
subtype SMALLINT is NUMBER(38,0);
subtype DECIMAL is NUMBER(38,0);
subtype NUMERIC is DECIMAL;
subtype DEC is DECIMAL;
subtype BINARY_INTEGER is INTEGER range '-2147483647'..2147483647;
subtype NATURAL is BINARY_INTEGER range 0..2147483647;
subtype NATURALN is NATURAL not null;
subtype POSITIVE is BINARY_INTEGER range 1..2147483647;
subtype POSITIVEN is POSITIVE not null;
subtype SIGNTYPE is BINARY_INTEGER range '-1'..1; -- for SIGN functions
type VARCHAR2 is NEW CHAR_BASE;
subtype VARCHAR is VARCHAR2;
subtype STRING is VARCHAR2;
subtype LONG is VARCHAR2(32760);
subtype RAW is VARCHAR2;
subtype "LONG RAW" is RAW(32760);
subtype ROWID is VARCHAR2(256);
-- Ansi fixed-length char
-- Define synonyms for CHAR and CHARN.
subtype CHAR is VARCHAR2;
subtype CHARACTER is CHAR;
type MLSLABEL is new CHAR_BASE;
-- Large object data types.
-- binary, character, binary file.
type BLOB is BLOB_BASE;
type CLOB is CLOB_BASE;
type BFILE is BFILE_BASE;
-- Verbose and NCHAR type names
subtype "CHARACTER VARYING" is VARCHAR;
subtype "CHAR VARYING" is VARCHAR;
subtype "NATIONAL CHARACTER" is CHAR CHARACTER SET NCHAR_CS;
subtype "NATIONAL CHAR" is CHAR CHARACTER SET NCHAR_CS;
subtype "NCHAR" is CHAR CHARACTER SET NCHAR_CS;
subtype "NATIONAL CHARACTER VARYING" is VARCHAR CHARACTER SET NCHAR_CS;
subtype "NATIONAL CHAR VARYING" is VARCHAR CHARACTER SET NCHAR_CS;
subtype "NCHAR VARYING" is VARCHAR CHARACTER SET NCHAR_CS;
subtype "NVARCHAR2" is VARCHAR2 CHARACTER SET NCHAR_CS;
subtype "CHARACTER LARGE OBJECT" is CLOB;
subtype "CHAR LARGE OBJECT" is CLOB;
subtype "NATIONAL CHARACTER LARGE OBJEC" is CLOB CHARACTER SET NCHAR_CS;
subtype "NCHAR LARGE OBJECT" is CLOB CHARACTER SET NCHAR_CS;
subtype "NCLOB" is CLOB CHARACTER SET NCHAR_CS;
subtype "BINARY LARGE OBJECT" is BLOB;
subtype pls_integer is binary_integer;
type TIME is new DATE_BASE;
type TIMESTAMP is new DATE_BASE;
type "TIME WITH TIME ZONE" is new DATE_BASE;
type "TIMESTAMP WITH TIME ZONE" is new DATE_BASE;
type "INTERVAL YEAR TO MONTH" is new DATE_BASE;
type "INTERVAL DAY TO SECOND" is new DATE_BASE;
SUBTYPE TIME_UNCONSTRAINED IS TIME(9);
SUBTYPE TIME_TZ_UNCONSTRAINED IS TIME(9) WITH TIME ZONE;
SUBTYPE TIMESTAMP_UNCONSTRAINED IS TIMESTAMP(9);
SUBTYPE TIMESTAMP_TZ_UNCONSTRAINED IS TIMESTAMP(9) WITH TIME ZONE;
SUBTYPE YMINTERVAL_UNCONSTRAINED IS INTERVAL YEAR(9) TO MONTH;
SUBTYPE DSINTERVAL_UNCONSTRAINED IS INTERVAL DAY(9) TO SECOND (9);
TYPE UROWID IS NEW CHAR_BASE;
type "TIMESTAMP WITH LOCAL TIME ZONE" is new DATE_BASE;
subtype timestamp_ltz_unconstrained is timestamp(9) with local time zone;
subtype BINARY_FLOAT is NUMBER;
subtype BINARY_DOUBLE is NUMBER;
-- The following data types are generics, used specially within package
-- STANDARD and some other Oracle packages. They are protected against
-- other use; sorry. True generic types are not yet part of the language.
type "<ADT_1>" as object (dummy char(1));
type "<RECORD_1>" is record (dummy char(1));
type "<TUPLE_1>" as object (dummy char(1));
type "<VARRAY_1>" is varray (1) of char(1);
type "<V2_TABLE_1>" is table of char(1) index by binary_integer;
type "<TABLE_1>" is table of char(1);
type "<COLLECTION_1>" is table of char(1);
type "<REF_CURSOR_1>" is ref cursor;
-- This will actually match against a Q_TABLE
type "<TYPED_TABLE>" is table of "<ADT_1>";
subtype "<ADT_WITH_OID>" is "<TYPED_TABLE>";
-- The following generic index table data types are used by the PL/SQL
-- compiler to materialize an array attribute at the runtime (for more
-- details about the array attributes, please see Bulk Binds document).
type " SYS$INT_V2TABLE" is table of pls_integer index by binary_integer;
-- The following record type and the corresponding generic index table
-- data types are used by the PL/SQL compiler to materialize a table
-- at the runtime in order to record the exceptions raised during the
-- execution of FORALL bulk bind statement (for more details, please
-- see bulk binds extensions document in 8.2).
type " SYS$BULK_ERROR_RECORD" is
          record (error_index pls_integer, error_code pls_integer);
type " SYS$REC_V2TABLE" is table of " SYS$BULK_ERROR_RECORD"
                               index by binary_integer;
/* Adding a generic weak ref cursor type */
type sys_refcursor is ref cursor;
/* the following data type is a generic for all opaque types */
type "<OPAQUE_1>" as opaque FIXED(1) USING LIBRARY dummy_lib
    (static function dummy return number);
type "<ASSOC_ARRAY_1>" is table of char(1) index by varchar2(1);
/********** Add new types or subtypes here **********/
/********** Predefined constants **********/
BINARY_FLOAT_NAN constant BINARY_FLOAT;
BINARY_FLOAT_INFINITY constant BINARY_FLOAT;
BINARY_FLOAT_MAX_NORMAL constant BINARY_FLOAT;
BINARY_FLOAT_MIN_NORMAL constant BINARY_FLOAT;
BINARY_FLOAT_MAX_SUBNORMAL constant BINARY_FLOAT;
BINARY_FLOAT_MIN_SUBNORMAL constant BINARY_FLOAT;
BINARY_DOUBLE_NAN constant BINARY_DOUBLE;
BINARY_DOUBLE_INFINITY constant BINARY_DOUBLE;
BINARY_DOUBLE_MAX_NORMAL constant BINARY_DOUBLE;
BINARY_DOUBLE_MIN_NORMAL constant BINARY_DOUBLE;
BINARY_DOUBLE_MAX_SUBNORMAL constant BINARY_DOUBLE;
BINARY_DOUBLE_MIN_SUBNORMAL constant BINARY_DOUBLE;
/********** Add new constants here **********/
/********** Predefined exceptions **********/
CURSOR_ALREADY_OPEN exception;
    pragma EXCEPTION_INIT(CURSOR_ALREADY_OPEN, '-6511');
DUP_VAL_ON_INDEX exception;
    pragma EXCEPTION_INIT(DUP_VAL_ON_INDEX, '-0001');
..and so it goes on... take a look yourself
Edited by: BluShadow on 18-Dec-2012 09:32

OBIEE-Answers Problems with NVARCHAR2 data type elements

Hello experts,
After we completed the .rpd development and ported to the real-time environment, when we try to create requests in Answers of Presentation services by selecting certain columns only and try to see results, we are getting an error if the columns are of NVARCHAR type. The error is given below.
This is stopping end users being not able to create any answers/requests. Please suggest how we can resolve this or if any specific things need to be done to solve the problem.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 87720170. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 24328, message: ORA-24328: illegal attribute value at OCI call OCIAttrSet. [nQSError: 17007] Error while executing OCIDefine routines. (HY000)

Hello Damon,
Thanks for the response.
We have also tried to query the same data through SQL*Plus and it went well. We had no issues with any data. Also the .RPD is working in our local system with the same data, on windows OS. But when we port the .RPD in the Server (Sun Solaris) we are having problems with the columns which are considered as NVARCHAR2 in the database and VARCHAR in the Physical layer of BI.
We observed there is no NVARCHAR2 data type supported in BI administrator in building the RPD. Is there any other datatype supports the NVARCHAR2 datatype in BI?
Thanks,
Narasimha

Data Type Mappings between BO and Netezza

Hi,
CAn anyone please tell me "What are the supported Netezza data types and corresponding BO data types supported?"

Hello,
Typically CR queries the database and the client tells CR what the field type is. If there are any types we can't match we usually convert it to a String type but it all depends on the version of Crystal Reports you are using.
I'm not familiar with Netezza so I can't help you with specifics.
All I can suggest is to try creating a report and if you have a problem then post your question with Specific details and any errors generated.
Thank you
Don

Which Data-Types can be used as Widget Parameters?

Hi,
I have been playing about with widgets (specifically widget parameters) for a while now.
I've got to wondering, exactly which data-types can Captivate turn into widget parameters?
So far I know that you can use:
Numbers,
Strings,
Arrays,
Objects
and Booleans,
as parameters.
Which ones am I missing?
I know some don't work, because I tried storing a MovieClip as a parameter and that didn't work.

Hi Eccles,
You can set all basic data types supported in flash viz.,
1)Numbers
2)Strings
3)Arrays
4)Objects
Since in Action script , an Object can be anything (array , array of objects , array of objects which by themselves are array of objects and so on ) , you can virtualy send anything as widget params
But there are two caveats to this
1)Object References
-Object References do not have any meaning once the swf is closed.But the widget params have to be stored across sessions.So If you send a reference as part of widget params it is not going to work.
This is why sending a Movie Clip (which is actually a reference to an Object ) does not work
If you want to send such things you will have to 'serialize' the object.
2)Size of the Object that you send
The size of the object that you send can have an impact on performance.And since any object that you send has to be converted into XML , objects like bitmaps can turn out to be huge and difficult to handle.
This brings us down to this - you can send any object across as widget param as long as it is small and serialized.

Oracle Forms New Features - Your input. Supporting data types

I am interested to know IF we were to support any new database types in Oracle Forms 11g, which types would you like supported and why. I'd also like to know if you are currently working around the absence of a database type.
Please note, this is not any kind of commitment to support new data types in Oracle Forms applications but we are interested to know if there is demand and if so, for what types.
Thanks
Grant Ronald
Oracle Forms Product Management
p.s lets keep the thread focused on the topic so please don't post technical questions or comments about different new features - if you want to, start a new thread - thanks

Hi Grant,
support for the "new" - well they exists since 9iR1 ... 2001 - data types TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE, INTERVAL YEAR TO MONTH and INTERVAL DAY TO SECOND would be very helpful.
Currently it's not possible to use the Data Block Wizard to create a data block for table/view that contains one of these columns.
(In Forms Builder 10.1.2.3 it fails with a strange error message ... iewbdbc_oracle_to_id ... C:\forms\101220\src\ie\iewbdb.c:724 ...)
So, one has to create the data block and the items manually. The items have to be CHARS.
Then forms is able to fetch and display these columns. The user can edit them as normal.
A WHEN-VALIDATE-ITEM trigger can be used to make sure that the implicit conversion from CHAR to the "new" datatype works.
For example, an INTERVAL YEAR TO MONTH column (b):
declare
l_invalid_interval exception;
pragma exception_init(l_invalid_interval, -1867);
l_invalid_month exception;
pragma exception_init(l_invalid_month, -1843);
l_dummy interval year(9) to month;
begin
l_dummy := to_yminterval(:block2.b);
exception
when l_invalid_interval
then
    message('invalid interval');
    raise form_trigger_failure;
when l_invalid_month
then
    message('invalid month');
    raise form_trigger_failure;
when others
then
    message(error_text);
    raise form_trigger_failure;
end;This nasty trick works for most of the "new" datatypes except with TIMESTAMP WITH TIME ZONE.
In Forms 10.1.2.3 the following WHEN-VALIDATE-ITEM trigger can (incorrectly!) fail:
declare
l_dummy timestamp with time zone;
begin
l_dummy := to_timestamp_tz(:block2.a);
end;It fails with "ORA-01804: failure to initialize timezone information", if the time zone is not like "-11:00", but like "EUROPE/PARIS". Don't know why...
If we recode our trigger to make a round-trip to the database, it works:
declare
l_dummy timestamp with time zone;
begin
select to_timestamp_tz(:block2.a)
into   l_dummy
from dual;
end;We could avoid these tricks, if Forms (and Reports) would support these type natively.
Thanks, Michael
PS: The TIMESTAMP and INTERVAL data types should of course be supported as items, parameters, globals and record groups columns.
Edited by: michael76 on 25.10.2010 01:14

Data type support 9i Release 2

Similar Messages

Maybe you are looking for