ORACLE CLOB data type and WIS 10901

Hello! I have several objects in universe that has connection to ORACLE DB. One of them has type CLOB in db and Long Text in universe, other has type number and has definition COUNT(db_column).
When I'm using this objects separate in webi query - everything fine, but when I put them together I've got error message:
A database error occured. The database error text is: ORA-00932: inconsistent datatypes: expected - , got CLOB
. (WIS 10901)
What's going wrong?

I''ve got a solution! I've had sql in my query
SELECT
ltrim(OPERATIVE_REPORT."orderText",11),
OPERATIVE_REPORT."resolID",
COUNT(OPERATIVE_REPORT."(usrID)order_executionUser")
FROM
OPERATIVE_REPORT
GROUP BY
ltrim(OPERATIVE_REPORT."orderText",11),
OPERATIVE_REPORT."resolID"
where orderText has clob datatype. And the reason is GROUP BY. GROUP BY deny CLOB usage.

Similar Messages

Oracle Object Data Type and EJB

Hi, All:
Has anyone implemented a project with Oracle user-defined data type (Object
Data Type) together
with EJB? That is, using ORDBMS (Object Relational Database) together with
EJB. I am thinking to use ORDBMS together with EJB. Any information, samples
and references to this direction is appreciated.
Thanks,
John Wen
RM2M, LLC
[email protected]

I''ve got a solution! I've had sql in my query
SELECT
ltrim(OPERATIVE_REPORT."orderText",11),
OPERATIVE_REPORT."resolID",
COUNT(OPERATIVE_REPORT."(usrID)order_executionUser")
FROM
OPERATIVE_REPORT
GROUP BY
ltrim(OPERATIVE_REPORT."orderText",11),
OPERATIVE_REPORT."resolID"
where orderText has clob datatype. And the reason is GROUP BY. GROUP BY deny CLOB usage.

Clob data type oracle to oracle issue

Hi Guys
i am unable to load clob data type and am getting the following error
" java.lang.NumberFormatException: For input "string: "4294967295"
i also have checked for clob data type in topology manager -- technology -- oracle -- data type
and it is available.
i have added the following statement in my parameter file
set ODI_ADDITIONAL_JAVA_OPTIONS=%ODI_ADDITIONAL_JAVA_OPTIONS% " -Doracledatabasemetadata.get_lob_precision=false";
but i don't see any statement like the one below after which i have to add the above statement.
set ODI_ADDITIONAL_JAVA_OPTIONS="-Djava.security.policy=server.policy";
please let me know how to make the clob data type work
Regards
janakiram

Hi Sutirtha
Yes i am able to view source data with clob data type by Right click onto your source datastore ---> View data
I have checked metalink
it says
1. Oracle recommends the setting of the "get_lob_precision" flag to FALSE to avoid this message when dealing with LOB family datatypes (CLOB, BLOB, NCLOB, BFILE...).
i have used the follwoing setting
set ODI_JAVA_OPTIONS="-Djava.security.policy=server.policy"
set ODI_ADDITIONAL_JAVA_OPTIONS=%ODI_ADDITIONAL_JAVA_OPTIONS% "-Doracledatabasemetadata.get_lob_precision=false"
2. checked the internal id of CLOB data type and it ends with 999
but still i have the same problem
Regards
janakiram

Using CLOB data type - Pros and Cons

Dear Gurus,
We are designing a database that will be receiving comments from external data source. These comments are stored as CLOB in the external database. We found that only 1% of incoming data will be larger than 4000 characters and are now evaluating the Pros and Cons of storing only 4000 characters of incoming comments in VARCHAR2 data type or using CLOB data type.
Some of the concerns brought up during discussion were:
- having to store CLOBs in separate tablespace;
- applications, such Toad require changing defaults settings to display CLOBs in the grid. Default value is not to display them;
- applications that build web page with CLOBs will be struggling to fit 18 thousand chararcters of which 17 thousand are blank lines;
- cashing CLOBs in memory will consume big chunk of data buffers which will affect performance;
- to manipulate CLOBs you need PL/SQL anonymous block or procedure;
- bind variables cannot be assigned CLOB value;
- dynamic SQL cannot use CLOBs;
- temp tables don't work very well with CLOBs;
- fuzzy logic search on CLOBs is ineffective;
- not all ODBC drivers support Oracle CLOBs
- UNION, MINUS, INTERSECT don't work with CLOBs
I have not delt with CLOB data type in the past, so I am hoping to hear from you of any possible issues/hastles we may encounter?

848428 wrote:
Dear Gurus,
We are designing a database that will be receiving comments from external data source. These comments are stored as CLOB in the external database. We found that only 1% of incoming data will be larger than 4000 characters and are now evaluating the Pros and Cons of storing only 4000 characters of incoming comments in VARCHAR2 data type or using CLOB data type.
Some of the concerns brought up during discussion were:
- having to store CLOBs in separate tablespace;They can be stored inline too. Depends on requirements.
- applications, such Toad require changing defaults settings to display CLOBs in the grid. Default value is not to display them;Toad is a developer tool so that shouldn't matter. What should matter is how you display the data to end users etc. but that will depend on the interface. Some can handle CLOBs and others not. Again, it depends on the requirements.
- applications that build web page with CLOBs will be struggling to fit 18 thousand chararcters of which 17 thousand are blank lines;Why would they struggle? 18,000 characters is only around 18k in file size, that's not that big to a web page.
- cashing CLOBs in memory will consume big chunk of data buffers which will affect performance;Who's caching them in memory? What are you planning on doing with these CLOBs? There's no real reason they should impact performance any more than anything else, but it depends on your requirements as to how you plan to use them.
- to manipulate CLOBs you need PL/SQL anonymous block or procedure;You can manipulate CLOBs in SQL too, using the DBMS_LOB package.
- bind variables cannot be assigned CLOB value;Are you sure?
- dynamic SQL cannot use CLOBs;Yes it can. 11g supports CLOBs for EXECUTE IMMEDIATE statements and pre 11g you can use the DBMS_SQL package with CLOB's split into a VARCHAR2S structure.
- temp tables don't work very well with CLOBs;What do you mean "don't work well"?
- fuzzy logic search on CLOBs is ineffective;Seems like you're pulling information from various sources without context. Again, it depends on your requirements as to how you are going to use the CLOB's
- not all ODBC drivers support Oracle CLOBs not all, but there are some. Again, it depends what you want to achieve.
- UNION, MINUS, INTERSECT don't work with CLOBsTrue.
I have not delt with CLOB data type in the past, so I am hoping to hear from you of any possible issues/hastles we may encounter?You may have more hassle if you "need" to accept more than 4000 characters and you are splitting it into seperate columns or rows, when a CLOB would do it easily.
It seems as though you are trying to find all the negative aspects of CLOBs and ignoring all the positive aspects, and also ignoring the negative aspects of not using CLOB's.
Without context you're assumptions are just that, assumptions, so nobody can tell you if it will be right or wrong to use them. CLOB's do have their uses, just as XMLTYPE's have their uses etc. If you're using them for the right reasons then great, but if you're ignoring them for the wrong reasons then you'll suffer.

Mapping between oracle data types and ms sql server data types

hello
i need mapping between oracle data types and ms sql server data types
where can i find them ?

read this
http://download.oracle.com/docs/cd/E10405_01/doc/appdev.120/e10379/ss_oracle_compared.htm

Error while loading data into clob data type.

Hi,
I have created interface to load data from oracle table into oracle table.In target table we have attribute with clob data type. while loading data into clob field ODI gave below error. I use odi 10.1.3.6.0
java.lang.NumberFormatException: For input string: "4294967295"
     at java.lang.NumberFormatException.forInputString(Unknown Source)
     at java.lang.Integer.parseInt(Unknown Source)
     at java.lang.Integer.parseInt(Unknown Source)
Let me know if anyone come across and resolved this kind of issue.
Thanks much,
Nishit Gajjar

Mr. Gajjar,
You didnt mention what KMs you are using ?
have a read of
Re: Facing issues while using BLOB
and
Load BLOB column in Oracle to Image column in MS SQL Server
Try again.
And can you please mark the Correct/Helpful points to the answers too.
Edited by: actdi on Jan 10, 2012 10:45 AM

Scheduled Web Intelligence report fails with ORA-01013 and WIS 10901

Hi,
the environment I'm working in is BOXI R2 SP4 on a Solaris 10 server using WebLogic running against Oracle 9i database.
I have a report written by one of the users. In SQL Viewer the SQL detailed is two joined Select statements. Each time this report is either scheduled or refreshed is fails with an ORA-01012 and WIS 10901 error.
I am of the understanding that this failure relates to the fact that the 'Limit Execution Time To;' value is being exceeded.
I also understand that this value is infact divided by the number of Select statements present, and that each Select statment is them allocated an equal portion of this value.
If any of this is incorrect please correct me.
I therefore have two questions
1. As such would I be correct in assuming that in my scenario where 2 Select statments are present and where the execution limit is set to 30 minutes, that each Select has 15 minutes to complete, and that if either fails the ORA-01012 and WIS 10901 error is generated.
2. Also would this error message get generated as soon as the first failure occurred, or would BO initiate a cancellation of the SQL by Oracle, ORA-01012, only when the final request has either succeeded or failed.

The queries are not executed in parallel but in serial. So the total execution time configured will be for all the Select statements in the report combined.
As for your second question, since the execution is not parallel hence BO will not initiate any error message until the total execution time exceeds the defined limit. This could be during the execution of first select statement or the second.
Try executing the queries directly in database one by one and see how much time they are taking.
- Noman Jaffery

Pl/sql Procedure is Not Creating With the CLOB data Type

Hi,
I am Using Oracle 10g Express Edition Release2.... My Doubt is While creating a table With CLOB Data Type the table is created successfully,but while Creating a Procedure With the CLOB Data type i am getting an Error Message
2667/5 PL/SQL: Statement ignored
2667/24 PLS-00382: expression is of wrong type
then i tried With the Varchar2(30000) the Procedure is Created Successfully note i have not changed any thing in my code except the data type.
I am Just Confused ......Why the Procedure is not Created with CLOB Data type?
Please advice ...
Thank U
SHAN

hi,
Thanks for reply....Another Example
CREATE TABLE USER_MAS (USER_ID VARCHAR2 (20 Byte),MAIL_ID VARCHAR2 (255 Byte));
set serveroutput on
declare
atable varchar2(64) := 'USER_MAS';
acolumn varchar2(64) := 'MAIL_ID';
avalue varchar2(64) := 'NEWYORK' ;
dyn_sql clob;
begin
dyn_sql := 'update '||atable||' set '||acolumn||' = '''||avalue|| '''' ;
dbms_output.put_line(dyn_sql);
execute immediate dyn_sql;
end;
commit ;
Error at line 2
ORA-06550: line 9, column 23:
PLS-00382: expression is of wrong type
ORA-06550: line 9, column 5:
PL/SQL: Statement ignored
When i Changed the Data type to varchar2(64)
update USER_MAS set MAIL_ID = 'NEWYORK'
PL/SQL procedure successfully completed.
Commit complete.
I like to Know the Reason Why the Procedure is Not Created in Oracle 10g XE DB
Note :the Same Script i used in 11g DB the Procedure is Created Successfully....
Why you need use CLOB or VARCHAR2 in your temp_num variable as you sending parameters as number?
In the Procedure we are create some run time queries while executing the procedure. There are around 10 run time queries created.
The size of each query is more than 4000 characters . We then add all the queries using union all after each query to the clob variable as the normal varchar will not support.
Please Advice
Thank U
SHAN

ADF View Object query to use Oracle LONG data type

Hi,
I'm using a view object that uses Oracle LONG data type.The following exception is thrown
*"java.sql.SQLException: Stream has already been closed"* and it is not fetching the correct data.
I have searched in many forums,they suggested to use LOB instead of LONG as LONG is deprecated. But in my case I can't avoid using LONG as some of my legacy applications using the same DB.
Please suggest me a way
Thanks in Advance
Felix

Thanks for your reply Arun,
I have solved this problem using the solution suggested by this blog [AskTom-Link|http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:839298816582]
In the above blog link,they have suggested to convert Long to Varchar by functions and asked to use this function in the column.
Thank you all guys who have seen this post.
Regards,
Felix

Error when Converts rows to columns dynamically in clob data type

Hi
I am using below pl/sql statement
SELECT NO,
MAX (DECODE (NAME, 'A', VALUE1, NULL)) AS A,
MAX (DECODE (NAME, 'B', VALUE1, NULL)) AS B,
MAX (DECODE (NAME, 'C, VALUE1, NULL)) AS C,
MAX (DECODE (NAME, 'D', VALUE1, NULL)) AS D
FROM ( SELECT NO,
RTRIM (
XMLAGG (XMLELEMENT (E, VALUE || ',')).EXTRACT ('//text()').
GETCLOBVAL (),
VALUE1,
NAME
FROM DA
while i am execute for varchar type its as i expected. when i tried with clob data type i am getting follwoing error.
ORA-00932: inconsistent datatypes: expected - got CLOB
can any one pleas me?
thanks
Nagarajan.V

Nagarajan Venu wrote:
Thanks for your reply
This is scenario.
This is my table
NO--name--value
1--A--ASDF
2--B--IOP
all columns are clob type and i want the output like below.
No--A
1--ASDF
2--IOP
i just want to convert all rows to coulmns(clob type) dynamically.I don't get how you got that output from the data? What happened to "B"?
Please post a suitable example and expected output using create table and insert statements as well as giving your database version and using {noformat}{noformat} tags as detailed in the FAQ: {message:id=9360002}

Oracle-specific data types vs Connection pool

Hi, using Oracle-specific data types such as
ArrayDescriptor and create it by a connection to an Oracle database from a WebSphere datasource throw a ClassCastException. There is no problem using these Oracle-specific data types when the connection is obtained via the DriverManager. WebSphere cannot fix the problem because these data types are
not part of the JDBC specification.
Some reply from Oracle?
Thank you very much.

Thank you but I there is no solution in that thread.
Also, I know that WebLogic from BEA has a way around this issue... No Websphere work around ?
No Oracle fixing ?
Thanks.

Do data modeler support ORACLE Secure Data Masking and Subsetting ?

How to use the security(Contains PII, Masking Type, ...) in conjunction with ORACLE Secure Data Masking and Subsetting. Is it possible to generate masking definitions for ORACLE Data Masking ?

Hi Philip,
it's a XML-format an looks like:
<?xml version="1.0"?>
-<MASKING_DEFINITION PROD_VER="10.2.0.4.4" META_VER="1.0">
<DEFINITION_NAME>MASKING_DEF_1</DEFINITION_NAME>
<TARGET_NAME>orcl</TARGET_NAME>
<TARGET_TYPE>oracle_database</TARGET_TYPE>
<ADV_OPTION_DISABLE_LOGS>Y</ADV_OPTION_DISABLE_LOGS>
<ADV_OPTION_REFRESH_STATS>Y</ADV_OPTION_REFRESH_STATS>
<ADV_OPTION_DROP_TEMP_TABLES>Y</ADV_OPTION_DROP_TEMP_TABLES>
<PARALLEL_DEGREE>DEFAULT</PARALLEL_DEGREE>
<DM_FLAGS>15</DM_FLAGS>
MASKING_COLUMN>
<OWNER>OWNER</OWNER>
<TABLE>TABLE</TABLE>
<COLUMN>COLUMN</COLUMN>
<COLUMN_GROUP/> <FORMATS> <FORMAT> <RULE_ORDER>1</RULE_ORDER> -<RULE_CONDITION>
<![CDATA[ 1=1 ]]>
</RULE_CONDITION> -<FORMAT_ENTRY> <ORDER>1</ORDER> <TYPE>RS</TYPE> <START>1</START> <END>40</END> </FORMAT_ENTRY> </FORMAT> </FORMATS>
</MASKING_COLUMN>
</MASKING_DEFINITION>
This is a example from my local 11 g database control on our OEM 12 c it starts with:
MASKING_DEFINITION PROD_VER="12.1.0.4.0" META_VER="1.0">
Perfect would be if we can choose the type of masking "Redaction/Data Masking" in the preferences and the properties of "Masking Type" and "Mask Template" properties would match the choosed type of masking.(i assume they can be found somewhere in the SYSTEM data dictionary)
Besides the present properties there exists many others for "Data Masking Pack" like Start/End, ...
Complete support of Data Masking Pack over Data Modeler would be great, OEM is more a dba tool and on our site definition of security is a product-owner/designer responsibility.
Regards Günter

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

XI settings, change of Data Types and XI still maps old structures

Hi,
I have defined XI scenario, where synchronous WebService is being called, and XI calls RFC function module, which returns data. It was working perfectly, until
I have changed the order of few fields in Data Type and added a few new (exactly as the changes in RFC function module).
And now the WebService returns exception, on the first field added to the interface:
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:MT_BMS_Response/CUSTOMERS_PERSON/TITLE. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at
TITLE is added field.
I have reactivated everything one by one again, clear cache from Integration Builder and Integration Directory, but it does not help and still old structures are being used in XI.
I have tested the Interface Mapping and all fields are transformed correctly.
Please help as it comes a little urgent and I have run out of ideas what to do to refresh the customizing of data types?
Thank you in advance!

Hi Peter,
Yes, I am calling RFC function module from XI.
After I changed the interface of RFC in SAP, I have imported this RFC once more to XI in Integration Builder and new structures appeared.
And exception returned is that first new field added to the RFC and Data Type and so on, returns an exception.
And returned XML structures (in message monitoring) appears to be still old structures.

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
         In the ABAP type concept, fields are called data objects. Each data object is an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data   object as well as the name of a data type.
<b>Data Types:</b>
                 As well as occurring as attributes of a data object, data types can also be defined independently. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program (using the TYPES statement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
         Data types can be divided into elementary, reference, and complex types
<b>Data objects:</b>
                  Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their data type. You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
ABAP contains the following kinds of data objects
Literals
   Named Data Objects
Predefined Data Objects
Dynamic Data Objects

ORACLE CLOB data type and WIS 10901

Similar Messages

Maybe you are looking for