Oracle Version 10.1.0: Data type is not supported

Hi,
I am getting "Data Type is not supported" whenever I try to access tables with lob column in Toad.
Oracle server version is 10.1.0 and using toad version 7.6. Sql net version 9.2.0
Any pointers towards the resolution?
Thanks in advance.
Bhavesh

You could take this opportunity to upgrade your Toad to version 10 of sqlplus.
Failing that there are mail lists for those less productive souls struggling with the amphibious software at which can be found at.
http://www.toadsoft.com/maillist.htm

Similar Messages

Microsoft OLE DB Provider for Oracle: Data type is not supported.

I got the error:
Microsoft OLE DB Provider for Oracle: Data type is not supported.
Shortly after upgrading from Oracle 8 to Oracle 9. I was advised to download more up to date oracle drivers, but I was wondering if there was a way to tell what version of the 'OLE DB Provider for Oracle' is already at. Is there a command I can use via SQL Plus or something?

I have found Microsoft ODBC for Oracle to be more stable than the Microsoft OLEDB for Oracle driver. I have also found both Microsoft ODBC and OLEDB drivers to be more stable than the drivers from Oracle.
You could always get the latest MDAC (Microsoft Data Access Components) from Microsoft's MSDN Download site and then get the ODAC (Oracle Data Access Components) from Oracle's OTN Download site. ODAC requires MDAC. And ODAC has the latest drivers.
I suppose it would help to have the latest patches for your Oracle client software too. Maybe Oracle MetaLink would have these?
It may even help to have the latest service pack for Visual Studio 6 (Visual C++ 6 and Visual Basic 6) too.

Xml data type is not supported in distributed queries. Remote object 'OPENROWSET' has xml column(s).

Hi,
Can anyone help me out please.
I have written one stored Procedure to create a views using Openrowset(openquery) but for tables which contains xml data types throwing error while executing the SP. Error
" Xml data type is not supported in distributed queries. Remote object 'OPENROWSET' has xml column(s)."
Please refer the Stored Procedure & error message below.
USE [Ice]
GO
/****** Object: StoredProcedure [dbo].[Pr_DBAccess] Script Date: 08/14/2014 16:08:20 ******/
SET
ANSI_NULLS ON
GO
SET
QUOTED_IDENTIFIER ON
GO
ALTER
PROCEDURE [dbo].[ Pr_DBAccess](@SERVERTYPE
NVARCHAR(50),@SERVERNAME
NVARCHAR(100),@DATABASENAME
NVARCHAR(100),@SCHEMANAME
NVARCHAR(100),@TABLENAME
NVARCHAR(100),@USERNAME
NVARCHAR(100),@PASSWORD
NVARCHAR(100))
AS
BEGIN
DECLARE @openquery
NVARCHAR(4000),
@ETL_CONFIG_IDN
NVARCHAR(100);
IF @SERVERTYPE='SQL'
BEGIN
SET @openquery=
'CREATE VIEW '+@TABLENAME+
' WITH ENCRYPTION AS SELECT * FROM OPENROWSET(''SQLNCLI'',''SERVER='+@SERVERNAME+';TRUSTED_CONNECTION=YES;'',''SELECT * FROM '+@DATABASENAME+'.'+@SCHEMANAME+'.'+@TABLENAME+''')'
SELECT @openquery
END
EXECUTE
sp_executesql @openquery
END
----While running the SP manually below error occured

HI ,
1. You cannot use a table or view that contains xml or clr type as 4-part name in your query
2. You need to cast the column to either nvarchar(max) or varbinary(max) or other appropriate type to use
3. If you have a table that has xml type for example then you need to create a view that contains all columns other than xml and query it instead. Or you can issue a pass-through query using OPEN QUERY with the appropriate columns only.
Here is a work around:
SELECT
Cast(a.XML_Data as XML) as XML_Data
FROM
OPENQUERY([LINKED SERVER NAME HERE],'
SELECT
Cast(XML_Data as Varchar) as XML_Data
FROM
[DATABASE NAME].[SCHEMA].[TABLE NAME]'
) a
Basically, the data is queried on the remote server, converts the XML data to a varchar, sends the data to the requesting server and then reconverts it back to XML.
You can take help from below link;
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c6e0f4da-821f-4ba2-9b01-c141744076ef/xml-data-type-not-supported-in-distributed-queries?forum=transactsql
Thanks

JDBC-ODBC Bridge to SPSS data files - Result Set Type is not supported

Hello,
As mentioned in the subject I am trying to read SPSS data files using the SPSS 32-Bit data driver, ODBC and the JDBC-ODBC Bridge.
Using this SPSS Driver I manged to read the data directly into an MS-SQL Server using:
SELECT [...] FROM
OPENROWSET(''MSDASQL.1'',''DRIVER={SPSS 32-BIT Data Driver (*.sav)};DBQ=' SomePathWhereTheFilesAre';SERVER=NotTheServer'', ''SELECT 'SomeSPSSColumn' FROM "'SomeSPSSFileNameWithoutExt'"'') AS a
This works fine!
Using Access and an ODBC System DNS works for IMPORTING but NOT for LINKING.
It is even possible to read the data using the very slow SPSS API.
However, when it comes to JDBC-ODBC the below code does only work in part. The driver is loaded successfully, but when it comes to transferring data into the resultset object the error
SQLState: null
Result Set Type is not supported
Vendor: 0
occurs.
The official answer from SPSS is to use .Net or to use their implementation with Python in their new version 14.0. But this is obviously not an option when you want to use only Java.
Does anybody have experience with SPSS and JDBC-ODBC??? I have tried the possible ResultSet Types, which I took from:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/ad/rjvdsprp.htm
and none of them worked.
Thank you in advance for your ideas and input & stay happy!
Here the code without all the rest of the class arround it:
// Module: SimpleSelect.java
// Description: Test program for ODBC API interface. This java application
// will connect to a JDBC driver, issue a select statement
// and display all result columns and rows
// Product: JDBC to ODBC Bridge
// Author: Karl Moss
// Date: February, 1996
// Copyright: 1990-1996 INTERSOLV, Inc.
// This software contains confidential and proprietary
// information of INTERSOLV, Inc.
public static void main1() {
String url   = "jdbc:odbc:SomeSystemDNS";
String query = "SELECT SomeSPSSColumn FROM 'SomeSPSSFileName'";
try {
    // Load the jdbc-odbc bridge driver
    Class.forName ("sun.jdbc.odbc.JdbcOdbcDriver");
    DriverManager.setLogStream(System.out);
    // Attempt to connect to a driver. Each one
    // of the registered drivers will be loaded until
    // one is found that can process this URL
    Connection con = DriverManager.getConnection (url);
    // If we were unable to connect, an exception
    // would have been thrown. So, if we get here,
    // we are successfully connected to the URL
    // Check for, and display and warnings generated
    // by the connect.
    checkForWarning (con.getWarnings ());
    // Get the DatabaseMetaData object and display
    // some information about the connection
    DatabaseMetaData dma = con.getMetaData ();
    System.out.println("\nConnected to " + dma.getURL());
    System.out.println("Driver       " +
      dma.getDriverName());
    System.out.println("Version      " +
      dma.getDriverVersion());
    System.out.println("");
    // Create a Statement object so we can submit
    // SQL statements to the driver
    Statement stmt = con.createStatement(ResultSet.TYPE_FORWARD_ONLY ,ResultSet.CONCUR_READ_ONLY);
    // Submit a query, creating a ResultSet object
    ResultSet rs = stmt.executeQuery (query);
    // Display all columns and rows from the result set
    dispResultSet (rs);
    // Close the result set
    rs.close();
    // Close the statement
    stmt.close();
    // Close the connection
    con.close();
}

Thank you for your reply StuDerby!
Actually the above script was before, as you suggested, leaving the ResultSetTeype default. This did not work...
I am getting gray hair with SPSS - in terms of connectivity and "integratebility" none of their solutions offered is sufficient from my point of view.
Variable definitions can only be read by the slow API, data can only be read by Python or Microsoft Products... and if you want to combine both you are in big trouble. I can only assume that this is a company strategy to sell their Dimensions Platform to companies versus having companies developping their applications according to business needs.
Thanks again for any furthur suggestions and I hope, that some SPSS Developper will see this post!
Cheers!!

Sybase ODBC driver for Linux - handle of numeric data type is not correctly

Linux RHEL 4 + Oracle 10.2.0.3 - all work fine. But numeric data type does not coorectly show values. I gor driver from ASE 15. Who has already resolve this issue???

To begin with:
- what is the table definition in Sybase?
- what is the table definition in Oracle: SQL> describe <table>@<sybase_hsodbc_link>;
and probably you need to start a gateway debug trace (HS_FDS_TRACE_LEVEL-DEBUG) and an ODBC trace to see what happens.
You could paste the appropriate section(s) here. Also paste the init<hsodbc>.ora and odbc.ini .
Ed

Date type is not captured in Visual composer 7.0 using SQL server as DB

Date type is not captured in Visual composer 7.0 when using SQL server as DB, and field type is "SmallDateTime" in DB.

Create new Text tab in fields of Table & select Type as Date in VC or use DSRT date function

Power view couldn't load the model or data source because the data source type is not supported

Hi,
I have SQL 2012 standard edition in my local. I have developed SSAS & deployed in local. I have been asked to develop power view report in excel 2013 using this SSAS. But when I tried to do in Excel 2013 professional Plus, I am getting below error:
Power view couldn't load the model or data source because the data source type is not supported.
Does power view is supported in standard edition of SQL or it requires Business/Enterprise edition of SQL server?
Thanks in advance

What type of SSAS install are you using?
PowerView in Excel 2013 currently only supports Tabular data sources.
Only PowerView in Sharepoint 2013 supports both Tabular and Multi-Dim data sources. (provided you have the required Sharepoint and SQL updates installed)
http://darren.gosbell.com - please mark correct answers

Getting error when view - Requested data type does not match with existing

I have the siebel web service
In the BI publisher as mentioned in the 'Siebel_BI_Publisher_Integration_Concepts.pdf', I have imported the siebel web service
BI can recognize the 'Web service' and methods.
I have created the paramters. The data type is 'String'
When I try to view the report using the BI publisher, I am getting teh following error in th UI
"Requested data type does not match with existing data type"
This is the first time I am using BI publisher to call the Siebel web service. I don't know what this error means
I don't know whether any log file generated wit the details of this erro message
Any help is much appriciated
Thanks,
Kavitha

Hi all,
have you find a fix for this issue? Im facing the same situation, using Complex type, and String data type both in the service and Bi publisher. We are consuming CC&B services, and we have noticed this error appears when BIPublisher is running on WebLogic (10.3) but it does not appear when BIPublisher is running on OC4J , of course running the same report on both application servers.
Any idea?
Thanks a lot, regards
Nestor

Data Type Is Not Vailid for Input

Hello,
I'm new in (ABAP) WebDynpro and I have a problem with displaying data - particularly with HROBJECTs from our e-Recruiting system.
In my WebDynpro-Component i read some data of candidates into my context. One table (with candidate-infos) which i save in my context includes a field which is datatype of HROBJECT. After I've read this infos into my itab, I bind this table to my context. All this works fine! But as soon as I bind this context to a table-ui-element in my layout, i get a error message "Data Type Is Not Valid for Input", when i start the application.
If I delete the binding with the attribute which is a HROBJECT, it works.
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_WDR_CONVERSION_EXCEPTION
Information on where terminated
    Termination occurred in the ABAP program "CL_WDR_CONVERSION_UTILS=======CP" -
     in "IF_WD_CONVERSION_UTILS~TO_STRING".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 138
    of the (Include) program "CL_WDR_CONVERSION_UTILS=======CM00G".
    The termination is caused because exception "CX_WDR_CONVERSION_EXCEPTION"
     occurred in
    procedure "IF_WD_CONVERSION_UTILS~TO_STRING" "(METHOD)", but it was neither
     handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "CL_WDR_CONVERSION_UTILS=======CP "; its source
     code begins in line
    1 of the (Include program "CL_WDR_CONVERSION_UTILS=======CM00G ".
136     WHEN cl_abap_typedescr=>typekind_struct1    "'u'     " structure
137     OR   cl_abap_typedescr=>typekind_struct2.   "'v'.    " structure
>>>>       RAISE EXCEPTION TYPE cx_wdr_conversion_exception exporting textid = cx_wdr_conversion_
139 *      raise exception type cx_wdr_conv_unsupported exporting type_name = l_type.
Please Help.
Thanks

now i've tried it with a independent candidate node (without) supply funciton. =>
The same error: "Data Type Is Not Vailid for Input"
Here's the code of my supply-function:
(probably not the best coding - but it works until i want to display a hro.)
METHOD get_cand_info .
DATA: lr_cdcy                    TYPE REF TO cl_hrrcf_candidacy_bl,
        lr_cand                    TYPE REF TO cl_hrrcf_candidate_bupa_bl,
        stru_requisitions          TYPE if_componentcontroller=>element_requisitions ,
        lt_h_cdcy_list             TYPE rcf_t_list_candidacies_x,
        ls_h_cdcy_list             TYPE rcf_s_list_candidacies_x,
        lt_cdcy_list               TYPE if_componentcontroller=>elements_candidate,
        ls_cdcy_list               TYPE if_componentcontroller=>element_candidate,
        lt_addr                    TYPE rcf_t_addressdata_bp,
        ls_addr                    TYPE rcf_s_addressdata_bp,
        lt_email                   TYPE rcf_t_emaildata_bp,
        ls_email                   TYPE rcf_s_emaildata_bp.
* get all declared attributes
parent_element->get_static_attributes(
    IMPORTING
      static_attributes = stru_requisitions ).
CALL METHOD cl_hrrcf_candidacy_bl=>get_instance
    RECEIVING
      return = lr_cdcy.
CALL METHOD cl_hrrcf_candidate_bupa_bl=>get_instance
    RECEIVING
      return = lr_cand.
* Hole Kandidatur-Informationen der Kandidaten
TRY.
      lr_cdcy->get_candidacy_list_x(
        EXPORTING
          ps_req_hrobject = stru_requisitions-hrobject
*    ps_cand_hrobject =
*    ps_appl_hrobject =
*    p_exclude_draft = 'x'
        IMPORTING
          pt_candidacies_x = lt_h_cdcy_list
    CATCH cx_hrrcf .
ENDTRY.
* Ergänzen der Informationen mit BusinessPartner-Infos
LOOP AT lt_h_cdcy_list INTO ls_h_cdcy_list.
    TRY.
        lr_cand->get_contact_data(
          EXPORTING
            ps_cand_hrobject = ls_h_cdcy_list-cand_hrobject
          IMPORTING
            pt_addressdata   = lt_addr
*    pt_telefondata   =
*    pt_faxdata       =
            pt_emaildata     = lt_email
      CATCH cx_hrrcf .
    ENDTRY.
    READ TABLE lt_addr INDEX 1 INTO ls_addr.
    READ TABLE lt_email INDEX 1 INTO ls_email.
    MOVE-CORRESPONDING ls_h_cdcy_list TO ls_cdcy_list.
    ls_cdcy_list-postcode1 = ls_addr-postl_cod1.
    ls_cdcy_list-city1 = ls_addr-city.
    ls_cdcy_list-email = ls_email-e_mail.
    APPEND ls_cdcy_list TO lt_cdcy_list.
ENDLOOP.
CALL METHOD node->bind_table
    EXPORTING
      new_items = lt_cdcy_list.
ENDMETHOD.

I have tried to view videos created in premiere elements 10 and I get the following message: "this file type is not supported, or the required codec is not installed. When it opens there is a red screen in the monitor panel with Korean writing which als

I have tried to view videos created in premiere elements 10 and I get the following message: "this file type is not supported, or the required codec is not installed. When it opens there is a red screen in the monitor panel with Korean writing which also appears in the place of each clip in the video. I tried uninstalling and reinstalling premiere elements 10, but that did not have any effect on the video. Do you have any suggestions? I researched codec, but do not understand them at all.

gloucester
In case you did not find it, the following is a copy/paste of the Announcement on Premiere Elements 19/NVIDIA GeForce
that appears at the top of this forum.
Premiere Elements 10 NVIDIA Video Card Driver Roll Back
If you are a Premiere Elements 10 user whose Windows computer uses a NVIDIA GeForce video card and you are experiencing
Premiere Elements 10 display and/or unexplained program behavior, then your first line of troubleshooting needs to be rolling
back the video card driver version instead of assuring that it is up to date.
Since October 2013 to the present, there have been a growing number of reports about display and unexplained workflow
glitches specific to the Premiere Elements 10 user whose Windows computer has a NVIDIA GeForce video card. If this applies
to you, then the “user to user” remedy is to roll back the NVIDIA GeForce video card driver as far as is necessary to get rid of
the problems. The typical driver roll back has gone back as far as March – July 2013 in order to get a working Premiere
Elements 10. Neither NVIDIA nor Adobe has taken any corrective action in this regard to date, and none is expected moving forward.
Since October 2013, the following thread has tried to keep up with the Premiere Elements 10 NVIDIA reports
http://forums.adobe.com/thread/1317675
Older NVIDIA GeForce drivers can be found
http://www.nvidia.com/Download/Find.aspx?lang=en-us
A February 2014 overview of the situation as well as how to use the older NVIDIA GeForce drivers for the driver roll back can be found
http://atr935.blogspot.com/2014/02/pe10-nvidia-video-card-roll-back.html
ATR

TOAD ERROR : OCI version 10.2.0.1.0 is not supported

Hi all,
Previously i have oracle 9i in my system, now i installed oracle 10.2.., after this when i am trying to retrieve data from tables im getting this error "OCI version 10.2.0.1.0 is not supported". Please help me how can i solve this problem.
Thanks in advance

You need deinstall the old version of toad and install version higher than V 8.5 which will fix the issue. Because the default home is read by Toad sometimes reinstallation will fix the issue.
--kccrga

OCI version 10.1.0.2.0 is not supported in Toad

I have upgraded my 9203 Oracle database to 10.1.0.2. Now when I connect to the database via TOAD 7.6, it gives me the following error:
"OCI version 10.1.0.2.0 is not supported"
Can some one let me know about how to solve this problem.
Thanks in Advance.
-Bikash

Here an answer from askTom:
Hi Tom,
I am not sure if I can ask this question in this thread or whether you are aware
of the following problem (as you are very fond of SQL*plus... ;) ).
I was happily usig toad 7.6 to work with oracle 9i. But now an upgrade to 10g
has caused toad fail to connect. Error "OCI version 10.1.0.2.0 is not
supported". But if I install 9i client and try to connect, then it works fine.
Is there any workaround?
Thanks and regards
Praveen
Followup:
you'd have to ask the makers of toad if they have a 10g client version or not.
Basically what is happening is that you have a 9i compiled piece of client
software (toad).
it uses, it depends on the 9i client software.
in order to use the 10g client software -- you'd need a new binary from the
makers of toad.
SQLPlus would be the same -- the 9i sqlplus needs the 9i client, the 10g sqlplus
needs the 10g client and so on.
As it is -- you are OK right now, you have installed the software needed by toad
and a 9i client connecting to a 10g database is "ok, supported and normal"

Firefox error: video format or MME type is not supported

Client said that video cannot load on firefox except other browsers.
It shows "Video format or MIME type is not supported".
Firefox version is 33.0.3. Video is mp4 format.

P.S. In case it helps, here are some mp4 video tests you can try (from mozillaZine's [http://kb.mozillazine.org/Testing_plugins#Other_media_tests Testing plugins] article) to see if they work for you in Firefox 33. (They both work fine for me on Windows 7 without needing a plugin.)
*http://www.html5videoplayer.net/html5video/mp4-h-264-video-test/
*http://techslides.com/demos/sample-videos/small.mp4

Conversion of type "u" to type "v" not supported (cl_abap_tabledescr)

Help! I am struggling with implementing a solution using cl_abap_tabledescr.
At below statement :
<f_interim_data> = <f_ref_data>.
I get the error:
Conversion of type "u" to type "v" not supported.
Coding:
DATA:
    l_r_tabledescr      TYPE REF TO cl_abap_tabledescr,
    l_r_itab            type ref to data,
    l_r_data_ref        type ref to data,
    l_r_data            type ref to data.
field-symbols:
    <gt_itab>          TYPE ANY TABLE,
    <gt_itab_BCCMP07> TYPE STANDARD TABLE.
field-symbols:
    <f_ref_data>            type any,
    <f_new_data>            type any,
    <f_interim_data>        type any.
go_tdescr ?= cl_abap_tabledescr=>describe_by_data( i_th_ref_data ).
go_sdescr ?= go_tdescr->get_table_line_type( ).
gd_tabnam     = 'I_TH_REF_DATA'.
loop at go_sdescr->components INTO gs_component.
    "   Build fieldname
    CONCATENATE gd_tabnam gs_component-name INTO gd_tabfield
                                            SEPARATED BY '-'.
    CLEAR: gs_comp.
    gs_comp-name = gs_component-name.
    gs_comp-type ?= cl_abap_datadescr=>describe_by_data( gd_tabfield ).
    APPEND gs_comp TO gt_components.
endloop.
Begin create dynamic standard table copy of I_TH_REF_DATA
"   Create instances of dynamic structure and dynamic internal table
go_sdescr_new = cl_abap_structdescr=>create( P_COMPONENTS = gt_components p_strict = abap_false ).
go_tdescr      = cl_abap_tabledescr=>create( go_sdescr_new ).
"   Create data refence followed by table creation
CREATE DATA gdo_handle TYPE HANDLE go_tdescr.
ASSIGN gdo_handle->* TO <gt_itab_BCCMP07>.
End create dynamic standard table copy of I_TH_REF_DATA
"Generate ref record
create data l_r_data_ref like line of <gt_itab_BCCMP07>.
assign l_r_data_ref->* to <f_interim_data>.
loop at i_th_ref_data assigning <f_ref_data>.
     <f_interim_data> = <f_ref_data>.
      append <f_interim_data> to <gt_itab_BCCMP07>.

Hi ,
Check the code below which is similar to waht you are doing. It gets the existing fields from a structure and then adds some extra fields to it ( decimals 3 )and creates a dyn table. If you need it with decimals 2 then use WTGXXX data element
DATA:lf_startdate TYPE sy-datum,
       li_index(2) TYPE n,
       la_datum TYPE type_date.
DATA:i_comp TYPE cl_abap_structdescr=>component_table,
       i_tot_comp TYPE cl_abap_structdescr=>component_table,
       lf_struct TYPE REF TO cl_abap_structdescr,
       lf_element TYPE REF TO cl_abap_elemdescr,
       la_comp LIKE LINE OF i_comp,
       lf_new_type TYPE REF TO cl_abap_structdescr,
       lf_new_tab TYPE REF TO cl_abap_tabledescr.
CLEAR: lf_startdate,li_index,la_datum,i_comp[],i_tot_comp[].
*--Getting Compoents from existing type
lf_struct ?= cl_abap_typedescr=>describe_by_name( 'TYPE_PUT' ).
i_comp = lf_struct->get_components( ).
APPEND LINES OF i_comp TO i_tot_comp.
*--Adding weekly bukets fields based on date in selection screen
DO.
    li_index = sy-index.
    IF lf_startdate GT s_lfdat-high.
      EXIT.
    ENDIF.
    IF li_index EQ 1.
      PERFORM get_first_day_of_week USING s_lfdat-low
                                    CHANGING lf_startdate.
      la_datum-dat = lf_startdate .
*--Element Description
      lf_element ?= cl_abap_elemdescr=>describe_by_name( 'MESXXX' ).
      CONCATENATE 'MES0' li_index INTO la_comp-name.
      la_datum-field = la_comp-name.
*--Field Type
      la_comp-type =
        cl_abap_elemdescr=>get_p( p_length = lf_element->length
                                  p_decimals = lf_element->decimals ).
      APPEND la_comp TO i_tot_comp.
      CLEAR: la_comp.
      APPEND la_datum TO i_datum.
      CLEAR: la_datum.
      CONTINUE.
    ENDIF.
    lf_startdate = lf_startdate + 6.
    la_datum-dat = lf_startdate .
    lf_element ?= cl_abap_elemdescr=>describe_by_name( 'MESXXX' ).
    CONCATENATE 'MES0' li_index INTO la_comp-name.
    la_datum-field = la_comp-name.
    la_comp-type =
      cl_abap_elemdescr=>get_p( p_length = lf_element->length
                                p_decimals = lf_element->decimals ).
*--Fill the component table
    APPEND la_comp TO i_tot_comp.
    CLEAR: la_comp.
    APPEND la_datum TO i_datum.
    CLEAR: la_datum.
ENDDO.
*--Create type
TRY.
      lf_new_type = cl_abap_structdescr=>create( i_tot_comp ).
    CATCH cx_sy_struct_creation .                       "#EC NO_HANDLER
ENDTRY.
*--Create Table type
TRY.
      lf_new_tab =
      cl_abap_tabledescr=>create( p_line_type = lf_new_type
      p_table_kind = cl_abap_tabledescr=>tablekind_std p_unique = ' ' ).
    CATCH cx_sy_table_creation .                        "#EC NO_HANDLER
ENDTRY.
*--data to handle the new table type
CREATE DATA wf_data TYPE HANDLE lf_new_tab.
*--data to handle the work area
CREATE DATA wf_str TYPE HANDLE lf_new_type.
*--Assign to fs
ASSIGN wf_data->* TO <fs_tab>.
ASSIGN wf_str->* TO <fs_line>.

Avorcldb verify - ERROR: specified version 10.2.0.1.0 is not supported

Hello all,
I got this error when verify operation of source compatibility with the Collectors:
Audit Vault Server: Windows Server 2003, Oracle 10.2.0.3
Audit Vault Client: Windows Server 2003, Oracle 10.2.0.1
Run this command on Audit Vault Server:
E:\>avorcldb verify -src 10.10.70.51:1521:orcl -srcusr system/oracle -colltype ALL
source ORCL.REGRESS.RDBMS.DEV.US.ORACLE.COM verified for OS File Audit Collector collector
source ORCL.REGRESS.RDBMS.DEV.US.ORACLE.COM verified for Aud$/FGA_LOG$ Audit Collector collector
ERROR: specified version 10.2.0.1.0 is not supported
Please provide me any infomation to fix this error.
Do I need to upgrade the Audit Vault Client to 10.2.0.3 ?
Thanks.

Thank Damorgan,
It's ok after upgrading to 10.2.0.3.
But now I get another errors, please help:
urgent: could not get AV agent connection using jdbc:oracle:oci:@AV
Thanks.

Oracle Version 10.1.0: Data type is not supported

Similar Messages

Maybe you are looking for