Issue with ROWID datatype

Hi,
I am moving 3 columns from source view into oracle target table....one of the column in the source view is "ROW_VALUE" with data type ROWID(this rows contains rowid of the table used in view)
when i map these 3 columns from source view to oracle table , my ROW_VALUE's (eg. AAAT16AAHAAACCfAAB) in changing into oracle.sql.rowid@aecfbi in the target table....
why is the value AAAT16AAHAAACCfAAB chaging when moved to target table
Thanks

Are you talking about the pseudo column ROWID which stores the "address of the row" in the database. Untill and unless you change the column name in the target I dont think so the "Value" itself in the source will get stored as it is an address and will automatically change depending on the target table.

Similar Messages

  • Issue with Date Datatype while importing from SQL Server to OBIEE

    Hi,
    We have a column in SQL Server Database with datatype as Date. When we imported this column into the Physical layer of OBIEE rpd,
    the datatype of this column is getting converted to VarChar automatically. Has anyone faced this issue before?
    Please let me know if you have a solution for this.
    Thanks in advance.

    Hi,
    How are you passing this date parameter ?
    Instead of passing this parameter in date format, you can pass this as string and then in PL/SQL package, you can convert this string to date.
    --Sushant                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Issue with ROWID

    There is an quite old app that runs in Forms 3.0.
    Currently it runs on Oracle 7. but it is decided to migrate DB to Oracle 10.2. I know it is not supported combination.
    We have migrated data, retargeted forms and tested.
    Most of forms work well.
    However some forms issue ORA-01410 Wrong ROWID.
    We traced them in Oracle and found that some forms issue "select for update" queries:
    "SELECT A,B,C FROM TBL WHERE ROWID=:0001 FOR UPDATE A,B,C NOWAIT"
    The issue is that the bind variable :0001 is VARCHAR type, not ROWID type.
    In this case BLOCK.ROWID is converted to string value of old format 'XXXX.XXX.XXXXX' that Oracle does not like in WHERE clause. Other SQLs that use binds of ROWID type work well.
    It is interesting that some forms issue such queries, some do not.
    I tried to find the query in .INP files - it is not there.
    The erro happens when Forms issues COMMIT_FORM, so I suppose that it is Forms itself, not the App, generates these SQLs and bind vars.
    Is my assumption correct?
    Is there any way to make Forms to use ROWID type for such binds? May be by using some keys, or by defining invisible field ROWID of type rowid?
    Or is it possible to customize locking SQL statement in ON-LOCK trigger?
    Or may be it will be more safe to migrate forms to v.4.5?
    Any ideas are welcome.
    thanks.

    Mark Malakanov (user11181920) wrote:
    There is an quite old app that runs in Forms 3.0.
    Currently it runs on Oracle 7. but it is decided to migrate DB to Oracle 10.2. I know it is not supported combination.
    We have migrated data, retargeted forms and tested.
    Most of forms work well.
    However some forms issue ORA-01410 Wrong ROWID.
    We traced them in Oracle and found that some forms issue "select for update" queries:
    "SELECT A,B,C FROM TBL WHERE ROWID=:0001 FOR UPDATE A,B,C NOWAIT"
    The issue is that the bind variable :0001 is VARCHAR type, not ROWID type.
    In this case BLOCK.ROWID is converted to string value of old format 'XXXX.XXX.XXXXX' that Oracle does not like in WHERE clause. Other SQLs that use binds of ROWID type work well.
    It is interesting that some forms issue such queries, some do not.
    I tried to find the query in .INP files - it is not there.
    The erro happens when Forms issues COMMIT_FORM, so I suppose that it is Forms itself, not the App, generates these SQLs and bind vars.
    Is my assumption correct?
    Is there any way to make Forms to use ROWID type for such binds? May be by using some keys, or by defining invisible field ROWID of type rowid?
    Or is it possible to customize locking SQL statement in ON-LOCK trigger?
    Or may be it will be more safe to migrate forms to v.4.5?
    Any ideas are welcome.
    thanks.try to upgrade to latest supported version. I think there is no other issue you have.
    hope this helps
    Hamid

  • Issue with Oracle datatypes like RAW,CLOB&BLOB

    Hello,
    I have developed an windows application using c#
    My requirement is to display data which having datatypes as RAW,CLOB,BLOB etc:
    But i am not able to bind these datatypes to gridview in my application.
    Pleasse ,suggest me way how to fix this.

    You'll need to provide some more details such as a short code snippet of what you are doing?
    What is your expectation as to how a RAW or BLOB should be displayed in a GridView?

  • Issue with date datatype

    Hi Team
    I am very much confused in the date related coversion
    for example if i query
    select name, hire_date from employee
    the o/p looks like this
    suresh 5/24/1999 but if i need to display like 24-may-1999 what i should use
    and please help me in understanding
    TO_CHAR,TO_DATE,TO_NUMBER function i bit confused in this ?please can get some suggestion in laymensterm
    Thanks
    Suresh

    RTM.
    You can find all the manuals at :
    http://tahiti.oracle.com/
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/functions203.htm#SQLRF06132
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements004.htm#i34924
    http://download.oracle.com/docs/cd/E11882_01/appdev.112/e17125/adfns_sqltypes.htm#ADFNS00304
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements002.htm#i46862
    PS: http://forums.oracle.com/forums/ann.jspa?annID=719
    Edited by: zep111 on May 6, 2011 2:24 PM

  • Table with RowID

    Hi,
    JDeveloper 11g.
    I have two tables one with a proper primary key and other one with rowid. I have observed that table with database primary key is loading very fast where as table with RowID is taking time to load.
    Is there any issue with RowID? If so, what would be the solution. Please help.
    Thanks.

    Hi,
    should not be a reason. However, having tables without a primary key sound strange to me.
    You don't provide much information about how you access and display data queried from the table. This is unfortunate as it prevents any better answer than what I gave.
    Frank

  • Issue with datatype

    Hi Folks,
    I just want to move SQL server table(2000) into oracle 10g.
    How to convert DATETIME datatype in SQL SERVER to oracle TIME STAMP and also there was a field named date(in SQL server) and Oracle would not accept it because Date is a reserved word.
    How to solve this.
    Iam new to OWB.
    Thanks in advance.

    Date problem try this:
    create table t11("date" date)
    this will create a field called date with the datatype of date or number or varchar.
    now how to convert datetime to timestamp.
    Why not convert datetime to a text format using to_char and then convert to_char to to_date in oracle with to_date(date,'dd/mm/yyyy hh24:mi:ss')
    this will give you the date in datetime format.

  • Issue with File Download(messageDownload) on Search Page.

    Hi,
    I created a custom OAF search page which fetches values from one table. The document in getting stored in my custom table in a BLOB colums and NOT in FND_LOBS.
    The table has 3 collumns along with others:
    1st is primary key (Record_Seq) ==> number data type
    2nd to store actual file name (File1Name) ==> varcahar2 data type
    3rd to store the actual uploaded data (File1Data) ==> BLOB data type
    The reason for having the “File1Name” is so that I can display the original file name of the document that was uploaded, instead of just the “view” in the search page results .
    On the File1Data BLOB and created a messageDownload for that under query results table with following details:
    ID : File1Data
    ItemStyle : messageDownload
    FileMIME Type : pdf
    Datatype : BLOB
    View Instance : LacEmpExposureVO1
    view Attribute : File1Name
    File View Attribute : File1Data
    When I click on the "File1Name" data hyperlink, it is opening only the first document corresponding to the first record in the search page results.
    For example, If my search page returns 10 rows then when I click on the file1name on any row, It is open the first row file name only.
    I have a primary key column(RECORD_SEQ) in the Table / EO / VO which is displayed in the search page results.
    Also one weird thing is happening:
    If I try to do this more than 2 times then it is opening the update page with the first record from the search page results…
    I tried to print the context and it is nul the first time, But the second time then context is changing to "update". Dont know how this is happening????
    Any advice is greatly appreciated as it is very crucial for me to get this resolved ASAP. I have looked at several forums and did a lot of things as advised in the forums . But nothing seems to work for me.
    Thanks,
    Mir
    CO code for the search page
    ===========================
    if (pageContext.getParameter("Create")!= null)
    System.out.println("Into LacEmpExposureCO in PROCESS FORM REQUEST with Context of CREATE");
    pageContext.setForwardURL
    ("OA.jsp?page=/lac/oracle/apps/lac/lacempexposure/webui/LacEmpExposureCreatePG",
    null,
    OAWebBeanConstants.KEEP_MENU_CONTEXT,
    null,
    null,
    true, //Retain AM
    OAWebBeanConstants.ADD_BREAD_CRUMB_YES,
    OAWebBeanConstants.IGNORE_MESSAGES);
    else if ("update".equals(pageContext.getParameter(EVENT_PARAM)))
    System.out.println("Into LacEmpExposureCO in PROCESS FORM REQUEST with Context of UPDATE");
    System.out.println("LacEmpExposureCO ==> RecordSeq in PROCESS FORM REQUEST is: " + RecordSeq);
    HashMap params = new HashMap(1);
    params.put("RecordSeq", RecordSeq);
    pageContext.setForwardURL
    ("OA.jsp?page=/lac/oracle/apps/lac/lacempexposure/webui/LacEmpExposureUpdatePG",
    null,
    OAWebBeanConstants.KEEP_MENU_CONTEXT,
    null,
    params,
    true, //Retain AM
    OAWebBeanConstants.ADD_BREAD_CRUMB_NO, // Do not display breadcrumbs
    OAWebBeanConstants.IGNORE_MESSAGES);
    else {           
    String strEvent = pageContext.getParameter(OAWebBeanConstants.EVENT_PARAM);
    System.out.println(strEvent);
    System.out.println("Into the last ELSE part in LacEmpExposureCO.java");

    Duplicate post -- Issue with File Download(messageDownload) on Search Page.

  • Performance issues with version enable partitioned tables?

    Hi all,
    Are there any known performance issues with version enable partitioned tables?
    I’ve been doing some performance testes with a large version enable partitioned table and it seems that OCB optimiser is choosing very expensive plans during merge operations.
    Tanks in advance,
    Vitor
    Example:
         Object Name     Rows     Bytes     Cost     Object Node     In/Out     PStart     PStop
    UPDATE STATEMENT Optimizer Mode=CHOOSE          1          249                    
    UPDATE     SIG.SIG_QUA_IMG_LT                                   
    NESTED LOOPS SEMI          1     266     249                    
    PARTITION RANGE ALL                                   1     9
    TABLE ACCESS FULL     SIG.SIG_QUA_IMG_LT     1     259     2               1     9
    VIEW     SYS.VW_NSO_1     1     7     247                    
    NESTED LOOPS          1     739     247                    
    NESTED LOOPS          1     677     247                    
    NESTED LOOPS          1     412     246                    
    NESTED LOOPS          1     114     244                    
    INDEX RANGE SCAN     WMSYS.MODIFIED_TABLES_PK     1     62     2                    
    INDEX RANGE SCAN     SIG.QIM_PK     1     52     243                    
    TABLE ACCESS BY GLOBAL INDEX ROWID     SIG.SIG_QUA_IMG_LT     1     298     2               ROWID     ROW L
    INDEX RANGE SCAN     SIG.SIG_QUA_IMG_PKI$     1          1                    
    INDEX RANGE SCAN     WMSYS.WM$NEXTVER_TABLE_NV_INDX     1     265     1                    
    INDEX UNIQUE SCAN     WMSYS.MODIFIED_TABLES_PK     1     62                         
    /* Formatted on 2004/04/19 18:57 (Formatter Plus v4.8.0) */                                        
    UPDATE /*+ USE_NL(Z1) ROWID(Z1) */sig.sig_qua_img_lt z1                                        
    SET z1.nextver =                                        
    SYS.ltutil.subsversion                                        
    (z1.nextver,                                        
    SYS.ltutil.getcontainedverinrange (z1.nextver,                                        
    'SIG.SIG_QUA_IMG',                                        
    'NpCyPCX3dkOAHSuBMjGioQ==',                                        
    4574,                                        
    4575                                        
    4574                                        
    WHERE z1.ROWID IN (
    (SELECT /*+ ORDERED USE_NL(T1) USE_NL(T2) USE_NL(J2) USE_NL(J3)
    INDEX(T1 QIM_PK) INDEX(T2 SIG_QUA_IMG_PKI$)
    INDEX(J2 WM$NEXTVER_TABLE_NV_INDX) INDEX(J3 MODIFIED_TABLES_PK) */
    t2.ROWID
    FROM (SELECT /*+ INDEX(WM$MODIFIED_TABLES MODIFIED_TABLES_PK) */
    UNIQUE VERSION
    FROM wmsys.wm$modified_tables
    WHERE table_name = 'SIG.SIG_QUA_IMG'
    AND workspace = 'NpCyPCX3dkOAHSuBMjGioQ=='
    AND VERSION > 4574
    AND VERSION <= 4575) j1,
    sig.sig_qua_img_lt t1,
    sig.sig_qua_img_lt t2,
    wmsys.wm$nextver_table j2,
    (SELECT /*+ INDEX(WM$MODIFIED_TABLES MODIFIED_TABLES_PK) */
    UNIQUE VERSION
    FROM wmsys.wm$modified_tables
    WHERE table_name = 'SIG.SIG_QUA_IMG'
    AND workspace = 'NpCyPCX3dkOAHSuBMjGioQ=='
    AND VERSION > 4574
    AND VERSION <= 4575) j3
    WHERE t1.VERSION = j1.VERSION
    AND t1.ima_id = t2.ima_id
    AND t1.qim_inf_esq_x_tile = t2.qim_inf_esq_x_tile
    AND t1.qim_inf_esq_y_tile = t2.qim_inf_esq_y_tile
    AND t2.nextver != '-1'
    AND t2.nextver = j2.next_vers
    AND j2.VERSION = j3.VERSION))

    Hello Vitor,
    There are currently no known issues with version enabled tables that are partitioned. The merge operation may need to access all of the partitions of a table depending on the data that needs to be moved/copied from the child to the parent. This is the reason for the 'Partition Range All' step in the plan that you provided. The majority of the remaining steps are due to the hints that have been added, since this plan has provided the best performance for us in the past for this particular statement. If this is not the case for you, and you feel that another plan would yield better performance, then please let me know and I will take a look at it.
    One suggestion would be to make sure that the table was been recently analyzed so that the optimizer has the most current data about the table.
    Performance issues are very hard to fix without a reproducible test case, so it may be advisable to file a TAR if you continue to have significant performance issues with the mergeWorkspace operation.
    Thank You,
    Ben

  • Issue with Bex report - key Figures not populating correctly.

    Hi Experts,
    I am facing an issue with a Bex report. There are three key figures of data type DATE having "Dec - Counter or amount field with comma and sign" datatype. After executing the query, in the report, for some sales documents the key figure fields are coming as 'X' and rest others are coming correctly in the date format as mm\dd\yyyy.
    When i check in the cube, these key figures shows values in decimal format and not in date format. The conversion is happening during execution.
    Pleas show me some light on how to identify the cause of getting 'X' for some Sales documents in the report eventhough some are coming correctly.
    Thanks,
    Anamika
    Edited by: Anamika Soni on Mar 12, 2010 10:48 AM

    Hi,
    The infobject has been defined with datatype "DATE" only. It has also been mapped from datasource to infocube correctly as these key figures are populating correctly for some of the sales documents in the report. It is not like that for all the sales documents the key figures are not converting properly.
    Some Sales documents are not converting into the date fields but for some conversion happens properly in the BEx report. This is the issue.
    Please guide accordingly.
    Many thanks,
    Anamika

  • Issue with Oracle LONG RAW data type

    Hi All,
    I am facing some issues with Oracle LONG RAW DATA Type.
    We are using Oracle 9IR2 Database.
    I got a table having LONG RAW column and I need to transfer the same into another table having LONG RAW column.
    When I tried using INSERT INTO SELECT * command (or) CREATE TABLE as select * , it is throwing ORA-00997: illegal use of LONG datatype.
    I have gone through some docs and found we should not use LONG RAW using these operations.
    So I did some basic PLSQL block given below and I was able to insert most of the records. But records where the LONG RAW file is like 7O kb, the inserting is faliling.
    I tried to convert LONG RAW to BLOB and again for the record where the LONG RAW is big in size I am getting (ORA-06502: PL/SQL: numeric or value error) error.
    Appreciate if anyone can help me out here.
    DECLARE
    Y LONG RAW;
    BEGIN
    FOR REC IN (SELECT * FROM TRU_INT.TERRITORY WHERE TERRITORYSEQ=488480 ORDER BY TERRITORYSEQ ) LOOP
    INSERT INTO TRU_CMP.TERRITORY
    BUSINESSUNITSEQ, COMPELEMENTLIFETIMEID, COMPONENTIMAGE, DESCRIPTION, ENDPERIOD, GENERATION, NAME, STARTPERIOD, TERRITORYSEQ
    VALUES
    REC.BUSINESSUNITSEQ, REC.COMPELEMENTLIFETIMEID, REC.COMPONENTIMAGE, REC.DESCRIPTION, REC.ENDPERIOD, REC.GENERATION, REC.NAME,
    REC.STARTPERIOD, REC.TERRITORYSEQ
    END LOOP;
    END;
    /

    Maddy wrote:
    Hi All,
    I am facing some issues with Oracle LONG RAW DATA Type.
    We are using Oracle 9IR2 Database.
    I got a table having LONG RAW column and I need to transfer the same into another table having LONG RAW column.
    When I tried using INSERT INTO SELECT * command (or) CREATE TABLE as select * , it is throwing ORA-00997: illegal use of LONG datatype.
    I have gone through some docs and found we should not use LONG RAW using these operations.
    So I did some basic PLSQL block given below and I was able to insert most of the records. But records where the LONG RAW file is like 7O kb, the inserting is faliling.
    I tried to convert LONG RAW to BLOB and again for the record where the LONG RAW is big in size I am getting (ORA-06502: PL/SQL: numeric or value error) error.
    Appreciate if anyone can help me out here.
    DECLARE
    Y LONG RAW;
    BEGIN
    FOR REC IN (SELECT * FROM TRU_INT.TERRITORY WHERE TERRITORYSEQ=488480 ORDER BY TERRITORYSEQ ) LOOP
    INSERT INTO TRU_CMP.TERRITORY
    BUSINESSUNITSEQ, COMPELEMENTLIFETIMEID, COMPONENTIMAGE, DESCRIPTION, ENDPERIOD, GENERATION, NAME, STARTPERIOD, TERRITORYSEQ
    VALUES
    REC.BUSINESSUNITSEQ, REC.COMPELEMENTLIFETIMEID, REC.COMPONENTIMAGE, REC.DESCRIPTION, REC.ENDPERIOD, REC.GENERATION, REC.NAME,
    REC.STARTPERIOD, REC.TERRITORYSEQ
    END LOOP;
    END;
    /below might work
    12:06:23 SQL> help copy
    COPY
    Copies data from a query to a table in the same or another
    database. COPY supports CHAR, DATE, LONG, NUMBER and VARCHAR2.
    COPY {FROM database | TO database | FROM database TO database}
                {APPEND|CREATE|INSERT|REPLACE} destination_table
                [(column, column, column, ...)] USING query
    where database has the following syntax:
         username[/password]@connect_identifier

  • Issue with "read by other session" and a parallel MERGE query

    Hi everyone,
    we have run into an issue with a batch process updating a large table (12 million rows / a few GB, so it's not that large). The process is quite simple - load the 'increment' from a file into a working table (INCREMENT_TABLE) and apply it to the main table using a MERGE. The increment is rather small (usually less than 10k rows), but the MERGE runs for hours (literally) although the execution plan seems quite reasonable (can post it tomorrow, if needed).
    The first thing we've checked is AWR report, and we've noticed this:
    Top 5 Timed Foreground Events
    Event     Waits     Time(s)     Avg wait (ms)     % DB time     Wait Class
    DB CPU           10,086           43.82     
    read by other session     3,968,673     9,179     2     39.88     User I/O
    db file scattered read     1,058,889     2,307     2     10.02     User I/O
    db file sequential read     408,499     600     1     2.61     User I/O
    direct path read     132,430     459     3     1.99     User I/OSo obviously most of the time was consumed by "read by other session" wait event. There were no other queries running at the server, so in this case "other session" actually means "parallel processes" used to execute the same query. The main table (the one that's updated by the batch process) has "PARALLEL DEGREE 4" so Oracle spawns 4 processes.
    I'm not sure how to fix this. I've read a lot of details about "read by other session" but I'm not sure it's the root cause - in the end, when two processes read the same block, it's quite natural that only one does the physical I/O while the other waits. What really seems suspicious is the number of waits - 4 million waits means 4 million blocks, 8kB each. That's about 32GB - the table has about 4GB, and there are less than 10k rows updated. So 32 GB is a bit overkill (OK, there are indexes etc. but still, that's 8x the size of the table).
    So I'm thinking that the buffer cache is too small - one process reads the data into cache, then it's removed and read again. And again ...
    One of the recommendations I've read was to increase the PCTFREE, to eliminate 'hot blocks' - but wouldn't that make the problem even worse (more blocks to read and keep in the cache)? Or am I completely wrong?
    The database is 11gR2, the buffer cache is about 4GB. The storage is a SAN (but I don't think this is the bottleneck - according to the iostat results it performs much better in case of other batch jobs).

    OK, so a bit more details - we've managed to significantly decrease the estimated cost and runtime. All we had to do was a small change in the SQL - instead of
    MERGE /*+ parallel(D DEFAULT)*/ INTO T_NOTUNIFIED_CLIENT D /*+ append */
      USING (SELECT
          FROM TMP_SODW_BB) S
      ON (D.NCLIENT_KEY = S.NCLIENT_KEY AND D.CURRENT_RECORD = 'Y' AND S.DIFF_FLAG IN ('U', 'D'))
      ...(which is the query listed above) we have done this
    MERGE /*+ parallel(D DEFAULT)*/ INTO T_NOTUNIFIED_CLIENT D /*+ append */
      USING (SELECT
          FROM TMP_SODW_BB AND DIFF_FLAG IN ('U', 'D')) S
      ON (D.NCLIENT_KEY = S.NCLIENT_KEY AND D.CURRENT_RECORD = 'Y')
      ...i.e. we have moved the condition from the MERGE ON clause to the SELECT. And suddenly, the execution plan is this
    OPERATION                           OBJECT_NAME             OPTIONS             COST
    MERGE STATEMENT                                                                 239
      MERGE                             T_NOTUNIFIED_CLIENT
        PX COORDINATOR
          PX SEND                       :TQ10000                QC (RANDOM)         239
            VIEW
              NESTED LOOPS                                      OUTER               239
                PX BLOCK                                        ITERATOR
                  TABLE ACCESS          TMP_SODW_BB             FULL                2
                    Filter Predicates
                      OR
                        DIFF_FLAG='D'
                        DIFF_FLAG='U'
                  TABLE ACCESS          T_NOTUNIFIED_CLIENT       BY INDEX ROWID    3
                    INDEX               AK_UQ_NOTUNIF_T_NOTUNI    RANGE SCAN        2
                      Access Predicates
                        AND
                          D.NCLIENT_KEY(+)=NCLIENT_KEY
                          D.CURRENT_RECORD(+)='Y'
                      Filter Predicates
                        D.CURRENT_RECORD(+)='Y' Yes, I know the queries are not exactly the same - but we can fix that. The point is that the TMP_SODW_BB table contains 1639 rows in total, and 284 of them match the moved 'IN' condition. Even if we remove the condition altogether (i.e. 1639 rows have to be merged), the execution plan does not change (the cost increases to about 1300, which is proportional to the number of rows).
    But with the original IN condition (that turns into an OR combination of predicates) in the MERGE ON clausule, the cost suddenly skyrockets to 990.000 and it's damn slow. It seems like a problem with cost estimation, because once we remove one of the values (so there's only one value in the IN clausule), it works fine again. So I guess it's a planner/estimator issue ...

  • Issues with importing from excel

    I have been running into a several issues with importing from Excel.
    First my configuration
    I am running SQL Developer ver 1.5.5 Build MAIN-5969
    I am on a Windows XP Professional Version 2002 with Service Pack 3
    I am importing into an Oracle 10g database.
    1. SQL Developer doesn't work on Excel 2007, I have to save all my files into Excel 97-2003 format before I can use them.
    2. If I run into an error loading and stop the process, SQL Developer doesn't release the Excel file and I get a sharing violation if I try to save the spreadsheet without closing SQL Developer.
    3. I have found that I have to set print area to the area I want to work with, otherwise the import wizard tries to keep adding rows.
    4. When using the Import wizard, it keeps adding commas on fields with numerics unless I specify the column in excel as text. Currently the column is formatted as General in the spreadsheet or I can change the wizard format to say the column is an integer, but it actually is just a code field with numeric characters so it may have leading zeroes that I need to keep.
    This might be related,
    I have a column in excel defined as text but only contains numerics. It is of length 4, but the wizard sets a precision of 5 with a datatype of VARCHAR2. If I try to change it to 4, I get an error saying the field is not large enough. Yet, when I do a LEN on the column, it only gives me a 4. I have other fields in the same sheet that a 3 position numeric and 2 position numeric and those are fine. I am thinking this is related to the comma being inserted in a numeric field for anything greater than 3 positions.
    5. Importing excel dates to oracle dates doesn't work. I have to convert the excel date column to text then import as a VARCHAR, then convert to Date once in the database.
    6. The default of nullible is not set on any columns and I have to set them before the import. (I would prefer it set to nullible and I have to uncheck the box to make it not nullible. I would prefer to import all of the data and then deal with the nulls after they have been pulled in)
    7. When I select header columns included it uses that as the column names. Is it possible to do the name length check then? It has bit me a few times where I try to import and forget to check the name length and then I get an error when I start running the import.
    8. If one of the columns to import has all nulls, then the precision comes out to 0 and if it isn't changed an error occurs on import. Could this situation default to a precision of 1?
    9. It would be nice if there was a completion message displayed and a cancel option while running.

    On point 3.
    I have a column in excel that consists of numbers. 4 digit numeric codes. Ex, 1111, 2345, etc
    The column's format is general. It displays as just 4 numbers.
    When I start the wizard initially, the column appears with data as 1,111, 2,345, etc, on the Data Preview screen.
    It determines the precision to be 5 on the column definition screen.
    If I change the precision to 4 then continue, that field will error out when I verify with "not big enough to hold the data in source columns"
    If, I change the excel column to a TEXT column.
    Excel still displays as 1111, 2345, etc
    The wizard then displays the same data 1111, 2345 on the Data Previeiw screen
    Yet, when I get to the column definition screen it still sizes it as a 5
    If I change it to a 4, I get the same error when verifying.
    If I leave them alone as 5, then it processes just fine.

  • Exporting a table with Long datatype col. name

    Hello,
    I need help exporting a table, One of the column is long datatype.
    How can I do this without using Export Util?
    Is it possible.
    (If someone has a solution then PLEASE Email
    me)
    URGENT.
    Thanks.
    Pankaj Patel.

    Just wanted to find out, if you already solved this problem. I have a similar issue with long column. I am trying to sql dump a table with long column that will be imported into another database(probably using sql*load), but the spooled file puts the data from the long column in separate lines 80 char long and not on a single line. I have set the long to 64000 and linesize to 32000. Wrap is on too.
    null

  • Reponse time issue with a simple qurey .

    hi all,
    i started facing a strange issue with the below query form the biging of the month. we have a DW system for a banking domain and in that our accounts table from the first of this month is taking a huge amount of time to retive the data. if i query a back dated data say 31st of may that would be '310509' it give the result in less that 5 seconds. this is a very simple query which i am joing with a transaction table.
    i assume the reason for the change in query reponce time is may be tha data from the beging of this month had a datablock extantion and this block is corrupted . kindly let me know what i am thinking is correct or there is another reaosn for this.
    Also let me know what resolution should i take to resolve this issue.
    my database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    Thanks in advance
    SELECT * FROM
    (select * from gtxn_dtl_v1 where batch_id='070609') a,
    (select * from gacc_dtl_v1 where batch_id='070609') b
    WHERE a.account_number = b.id
    SELECT * FROM
    (select * from gtxn_dtl_v1 where batch_id='310509') a,
    (select * from gacc_dtl_v1 where batch_id='310509') b
    WHERE a.account_number = b.id

    Hemant K Chitale wrote:
    I don't think that it is a simple query.
    The two objects "gtxn_dtl_v1" and "gacc_dtl_v1" seem to be Views. So, the queries are probably involving joins of other tables.
    Without an Execution Plan and information about table and index definitions and statistics on the tables and indexes, any attempt to answer your question would be meaningless.Both are tables. Explain plan is shown below:
    SQL> explain plan for
      2  SELECT * FROM
      3  (select * from gtxn_dtl_v1 where batch_id='070609') a,
      4  (select * from gacc_dtl_v1 where batch_id='070609') b
      5   WHERE a.account_number = b.id;
    Explained.
    SQL> select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 4236620027
    | Id  | Operation                    | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT             |             |     1 |   601 |    38   (0)| 00:00:01 |
    |   1 |  NESTED LOOPS                |             |     1 |   601 |    38   (0)| 00:00:01 |
    |*  2 |   TABLE ACCESS BY INDEX ROWID| GACC_DTL_V1 |     1 |   313 |     4   (0)| 00:00:01 |
    |*  3 |    INDEX RANGE SCAN          | IDX_ACC2_V1 |     1 |       |     3   (0)| 00:00:01 |
    |*  4 |   TABLE ACCESS BY INDEX ROWID| GTXN_DTL_V1 |     1 |   288 |    34   (0)| 00:00:01 |
    |*  5 |    INDEX RANGE SCAN          | IDX_TXN2_V1 |    55 |       |     8   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - filter("BATCH_ID"='070609')
       3 - access(SUBSTR("BATCH_ID",1,6)='070609')
       4 - filter("BATCH_ID"='070609' AND SUBSTR("GTXN_DTL_V1"."BATCH_ID",1,6)='070609')
       5 - access("GTXN_DTL_V1"."ACCOUNT_NUMBER"="GACC_DTL_V1"."ID")
           filter(SUBSTR("GTXN_DTL_V1"."ACCOUNT_NUMBER",1,3)=SUBSTR("GACC_DTL_V1"."ID",1
                  ,3))
    22 rows selected.
    SQL> explain plan for
      2  SELECT * FROM
      3  (select * from gtxn_dtl_v1 where batch_id='310509') a,
      4  (select * from gacc_dtl_v1 where batch_id='310509') b
      5  WHERE a.account_number = b.id;
    Explained.
    SQL>  select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 1249675553
    | Id  | Operation                     | Name            | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT              |                 |     1 |   601 |   785   (1)| 00:00:10 |
    |   1 |  TABLE ACCESS BY INDEX ROWID  | GACC_DTL_V1     |     1 |   313 |     4   (0)| 00:00:01 |
    |   2 |   NESTED LOOPS                |                 |     1 |   601 |   785   (1)| 00:00:10 |
    |   3 |    TABLE ACCESS BY INDEX ROWID| GTXN_DTL_V1     |   104 | 29952 |   368   (2)| 00:00:05 |
    |*  4 |     INDEX RANGE SCAN          | IDX_TXN1        |   104 |       |   340   (2)| 00:00:05 |
    |*  5 |    INDEX RANGE SCAN           | GACC_DTL_V1_IDX |     1 |       |     3   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       4 - access("BATCH_ID"='310509')
           filter(SUBSTR("GTXN_DTL_V1"."BATCH_ID",1,6)='310509')
       5 - access("GTXN_DTL_V1"."ACCOUNT_NUMBER"="GACC_DTL_V1"."ID" AND "BATCH_ID"='310509')
           filter(SUBSTR("GACC_DTL_V1"."BATCH_ID",1,6)='310509' AND
                  SUBSTR("GTXN_DTL_V1"."ACCOUNT_NUMBER",1,3)=SUBSTR("GACC_DTL_V1"."ID",1,3))
    21 rows selected.
    Indexes:
    select i.index_name,index_type,i.table_name,num_rows,column_name,COLUMN_EXPRESSION
    from all_indexes i,all_ind_columns c,ALL_IND_EXPRESSIONS e
    where i.table_name in ('GACC_DTL_V1','GTXN_DTL_V')
    and i.index_name = c.index_name
    and e.index_name(+) = i.index_name;
    INDEX_NAME     INDEX_TYPE          TABLE_NAME     NUM_ROWS     COLUMN_NAME     COLUMN_EXPRESSION
    GACC_DTL_V1_IDX     NORMAL               GACC_DTL_V1     57190895     ID     
    GACC_DTL_V1_IDX     NORMAL               GACC_DTL_V1     57190895     BATCH_ID     
    IDX_ACC5_V1     NORMAL               GACC_DTL_V1     34524304     POSTING_RESTRICT     
    IDX_ACC1_V1     NORMAL               GACC_DTL_V1     55919578     CATEGORY     
    IDX_CUS5_V1     NORMAL               GACC_DTL_V1     54461378     CUSTOMER_NUMBER     
    IDX_CUS6_V1     NORMAL               GACC_DTL_V1     3272052     LIMIT_REF     
    IDX_ACC3_V1     FUNCTION-BASED NORMAL     GACC_DTL_V1     52940894     SYS_NC00099$     "CUSTOMER_NUMBER"||'.'||"LIMIT_REF"
    IDX_ACC4_V1     FUNCTION-BASED NORMAL     GACC_DTL_V1     57238600     SYS_NC00100$     "CUSTOMER_NUMBER"||'.000'||"LIMIT_REF"
    GACC_DTL_V1_IX2     FUNCTION-BASED NORMAL     GACC_DTL_V1     54448627     SYS_NC00101$     SUBSTR("ID",1,3)
    IDX_ACC2_V1     FUNCTION-BASED NORMAL     GACC_DTL_V1     55566106     SYS_NC00102$     SUBSTR("BATCH_ID",1,6)Edited by: user577300 on Jun 10, 2009 11:41 PM
    So many strange things here:
    1.Query showing cost 38 is taking a long time  (hours). Other quey takes 5 sec
    2. Plans are different.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Maybe you are looking for

  • Display problems after update

    I recently updated- on balance things went ok- How ever for some odd reason something is causing KDE (3.5) to behave oddly- I used to have a app in the kde control panel that'd let me fine tune settings  (fonts and display size for instance)- I see t

  • CTAS with BLOB column very slow

    Hi, I am creating a new table from backup table having BLOB type of data. Table size for backup table is approx 250G (along with lob segment) and I am creating new table with predicate selectivity of 110 GB. Query used is "CREATE TABLE CLAIM AS SELEC

  • ORA-00918 issue joining tables for Update

    Hi, I have 2 tables : PAR_SPEC_OPS and T_PAR and I'm trying to update 2 columns in the first one with values from the second table. Here's my script : Update Select membership_id, membership_status From Par_Spec_Ops P,T_Par T Where P.Tracking_ID=T.Tr

  • Why does Shockwave Player keep reinstalling?

    I use Windows 7 and the latest version of Chrome. Every day for the past 10 days Shockwave Player has asked me to update to the latest version of itself. I do, it installs fine, and the next day we do it again. Why doesn't it 'stick'? This will happe

  • Compare: video shot with an iPhone to that shot with an iPad?

    Has anyone compared video shot with an iPhone to that shot with an iPad Touch, and edited on an iPad with iMovie? What was the results?  Is the iPhones camera significantly better than an iPod Touch for video? Thanks, Hal