OVI backup .nbu file size does not match actual da...

Hi,
I just backed up my phone through the Ovi Suite. The backup was VERY fast (compared to previous backups doen in earlier versions of Ovi Suite) probably due to the new fixed version of Ovi Suite.
Anyway... The backup file (.nbu) is almost 1.85 GB but when I browse my phone (in My Computer folder) and do 'Select All' the size of the data on my Phone Mass Memory reads 2.44 GB.......
SO.... is the backup data in the .nbu file somehow compressed?? Or maybe incomplete? 
Thank you

Not sure but..My 1.7 GB (Phone) is equivalent to 0.6 GB (PC) .. but I have done restore without anything missing out..
The phones OS related files may not be getting Backed-up..
--------------------------------------------------​--------------------------------------------------------​--------------------------------------------------​--If you find this helpful, pl. hit the White Star in Green Box...

Similar Messages

  • Cannot submit widget to Apple Downloads : File size does not match

    Hello all,
    I made a widget to play Go that I finalized yesterday ( http://lesiteajulien.free.fr ).
    Unfortunately, I have not succeeded to uploading it to the Apple widget repository, since the submit page keeps returning the following error :
    "The filesize from the file you uploaded and the file that is downloaded from the given download URL do NOT match."
    But I am absolutely sure that both zip files are the SAME. I downloaded it from my server a few times and compared the size with the original file I'm sending to Apple: they match. So I guess my server is not the cause.
    I tryied from various places and with various browsers.
    Did anybody have any similar problem while trying to upload a widget ?
    Any idea ?
    Thanks for your help.
    Julien

    tntemerson wrote:
    The sales people at the Apple store told me that Time Machine makes a true restorable system picture of the native HDD during backups.
    So I'm surprised when the backup runs through to a reported completion but the final backup size does not match the stated estimate for a "full backup" which is the same as the Macintosh HD used space.
    Time Machine automatically excludes some things that aren't needed for a full system restore:  system work files, most logs & caches, trash, some indexes, etc.  So it should be a few GBs less than what's on your system, but of course varies a lot from one Mac to another.
    See the tan box in #11 of Time Machine - Frequently Asked Questions for the gory details.

  • Iphone 4 file size does not match the ACTUAL file size

    My iphone 4 is reading 27 gigs of music as over 29 gigs of music. I don't understand why. Anyone else having an issue like this? My 3gs reads it as 27 gigs and so does my computer. I even set my 3gs to sync off a backup of my iphone 4 and it reads it as 2 less gigs. Why?

    Don't know, though Apple has been known to play with the numbers a bit:
    http://www.tuaw.com/2009/08/29/snow-leopard-the-new-one-gigabyte-now-slimmer-tha n-before/
    Or you could have had a conversion box checked in iTunes when you loaded your IPh4
    Phil

  • Database name ORCL in file header does not match given name of

    Hi all,
    DB version is 10.2.0.4
    While doing db cloning..restoring the database..made a mistake of restoring the db to a different running mountpoint database..But in 20 minutes realised that after a while and restarted the clone.
    But that running db went down..trying to recover it shows
    ERROR at line 1:
    ORA-01161: database name ORCL in file header does not match given name of
    PRODhow can i recover it?
    thanks,
    baskar.l

    baskar.l wrote:
    Hi all,
    DB version is 10.2.0.4
    While doing db cloning..restoring the database..made a mistake of restoring the db to a different running mountpoint database..But in 20 minutes realised that after a while and restarted the clone.
    But that running db went down..trying to recover it shows
    ERROR at line 1:
    ORA-01161: database name ORCL in file header does not match given name of
    PRODhow can i recover it?
    thanks,
    baskar.lHi,Baskar.How you clone your database and which command after you got this error.You can resolve this problem with re-create controlfile as(It mean is you actually change your database name):
    C:\Documents and Settings\Administrator>sqlplus "sys/sm as sysdba"
    SQL*Plus: Release 10.2.0.1.0 - Production on Sun Jun 20 15:34:21 2010
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> startup nomount pfile=D:\oracle\product\10.2.0\admin\SB\pfile\init.ora.5152
    010163530
    ORACLE instance started.
    Total System Global Area  138412032 bytes
    Fixed Size                  1247732 bytes
    Variable Size              62916108 bytes
    Database Buffers           71303168 bytes
    Redo Buffers                2945024 bytes
    SQL> CREATE CONTROLFILE reuse DATABASE "SB1" RESETLOGS  ARCHIVELOG
      2      MAXLOGFILES 16
      3      MAXLOGMEMBERS 3
      4      MAXDATAFILES 100
      5      MAXINSTANCES 8
      6      MAXLOGHISTORY 292
      7  LOGFILE
      8    GROUP 1 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO01.LOG'  SIZE 50M,
      9    GROUP 2 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO02.LOG'  SIZE 50M,
    10    GROUP 3 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO03.LOG'  SIZE 50M
    11  DATAFILE
    12    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSTEM01.DBF',
    13    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\UNDOTBS01.DBF',
    14    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSAUX01.DBF',
    15    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\USERS01.DBF',
    16    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\EXAMPLE01.DBF';
    CREATE CONTROLFILE reuse DATABASE "SB1" NORESETLOGS  ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01161: database name SB in file header does not match given name of SB1
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSTEM01.DBF'
    SQL> CREATE CONTROLFILE set DATABASE "SB1" RESETLOGS  ARCHIVELOG
      2      MAXLOGFILES 16
      3      MAXLOGMEMBERS 3
      4      MAXDATAFILES 100
      5      MAXINSTANCES 8
      6      MAXLOGHISTORY 292
      7  LOGFILE
      8    GROUP 1 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO01.LOG'  SIZE 50M,
      9    GROUP 2 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO02.LOG'  SIZE 50M,
    10    GROUP 3 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO03.LOG'  SIZE 50M
    11  DATAFILE
    12    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSTEM01.DBF',
    13    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\UNDOTBS01.DBF',
    14    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSAUX01.DBF',
    15    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\USERS01.DBF',
    16    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\EXAMPLE01.DBF';
    CREATE CONTROLFILE set DATABASE "SB1" RESETLOGS  ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-00200: control file could not be created
    ORA-00202: control file: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\CONTROL01.CTL'
    ORA-27038: created file already exists
    OSD-04010: <create> option specified, file already exists
    /*remove all controlfile  from D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\ */
    SQL> CREATE CONTROLFILE set DATABASE "SB1" RESETLOGS  ARCHIVELOG
      2      MAXLOGFILES 16
      3      MAXLOGMEMBERS 3
      4      MAXDATAFILES 100
      5      MAXINSTANCES 8
      6      MAXLOGHISTORY 292
      7  LOGFILE
      8    GROUP 1 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO01.LOG'  SIZE 50M,
      9    GROUP 2 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO02.LOG'  SIZE 50M,
    10    GROUP 3 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\REDO03.LOG'  SIZE 50M
    11  DATAFILE
    12    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSTEM01.DBF',
    13    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\UNDOTBS01.DBF',
    14    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\SYSAUX01.DBF',
    15    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\USERS01.DBF',
    16    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SB\EXAMPLE01.DBF';
    Control file created.
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 742571 generated at 06/20/2010 15:32:41 needed for thread 1
    ORA-00289: suggestion :
    D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SB1\ARCHIVELOG\2010_06_20\O1_MF_1_1
    1_%U_.ARC
    ORA-00280: change 742571 for thread 1 is in sequence #11
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    D:\oracle\product\10.2.0\oradata\SB\REDO01.LOG
    Log applied.
    Media recovery complete.
    SQL> alter database open resetlogs;
    Database altered.
    SQL> create spfile from pfile;
    File created.
    SQL>In additionally see metalink note
    ORA-01503 ORA-01161 While creating a clone database. [ID 294555.1]
    Edited by: Chinar on Jun 20, 2010 3:52 AM

  • ORA-01161: database name DEV in file header does not match given name UAT

    This is my cloning process.... I get the following errors.. I also double check with my process and still couldn't find anything.
    SQL> @backup_control.sql
    ORACLE instance started.
    Total System Global Area  479298392 bytes
    Fixed Size                   742232 bytes
    Variable Size             385875968 bytes
    Database Buffers           81920000 bytes
    Redo Buffers               10760192 bytes
    CREATE CONTROLFILE REUSE DATABASE "UAT" NORESETLOGS  ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01161: database name OBS in file header does not match given name of UAT
    ORA-01110: data file 1: '/u01/oracle/uatdata/system01.dbf'
    Any ideas of this error?
    Best Regards,
    Amy

    Please see followings:
    STARTUP NOMOUNT
    CREATE CONTROLFILE SET DATABASE "OBS" RESETLOGS ARCHIVELOG
    -- SET STANDBY TO MAXIMIZE PERFORMANCE
    MAXLOGFILES 16
    MAXLOGMEMBERS 2
    MAXDATAFILES 500
    MAXINSTANCES 1
    MAXLOGHISTORY 2042
    LOGFILE
    GROUP 1 '/u01/oracle/obsdata/log01a.dbf' SIZE 10M,
    GROUP 2 '/u01/oracle/obsdata/log02a.dbf' SIZE 10M,
    GROUP 3 '/u01/oracle/obsdata/log03a.dbf' SIZE 10M,
    GROUP 4 '/u01/oracle/obsdata/log04a.dbf' SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
    '/u01/oracle/obsdata/system01.dbf',
    '/u01/oracle/obsdata/system02.dbf',
    '/u01/oracle/obsdata/system03.dbf',
    '/u01/oracle/obsdata/system04.dbf',
    '/u01/oracle/obsdata/system05.dbf',
    '/u01/oracle/obsdata/rbs01.dbf',
    '/u01/oracle/obsdata/ctxd01.dbf',
    '/u01/oracle/obsdata/owad01.dbf',
    '/u01/oracle/obsdata/abmd01.dbf',
    '/u01/oracle/obsdata/abmx01.dbf',
    '/u01/oracle/obsdata/akd01.dbf',
    '/u01/oracle/obsdata/akx01.dbf',
    '/u01/oracle/obsdata/alrd01.dbf',
    '/u01/oracle/obsdata/alrx01.dbf',
    '/u01/oracle/obsdata/amsd01.dbf',
    '/u01/oracle/obsdata/amsx01.dbf',
    '/u01/oracle/obsdata/amvd01.dbf',
    '/u01/oracle/obsdata/amvx01.dbf',
    '/u01/oracle/obsdata/apd01.dbf',
    '/u01/oracle/obsdata/apx01.dbf',
    '/u01/oracle/obsdata/applsysd01.dbf',
    '/u01/oracle/obsdata/applsysx01.dbf',
    '/u01/oracle/obsdata/ard01.dbf',
    '/u01/oracle/obsdata/arx01.dbf',
    '/u01/oracle/obsdata/asfd01.dbf',
    '/u01/oracle/obsdata/asfx01.dbf',
    '/u01/oracle/obsdata/asgd01.dbf',
    '/u01/oracle/obsdata/asgx01.dbf',
    '/u01/oracle/obsdata/asod01.dbf',
    '/u01/oracle/obsdata/asox01.dbf',
    '/u01/oracle/obsdata/astd01.dbf',
    '/u01/oracle/obsdata/astx01.dbf',
    '/u01/oracle/obsdata/axd01.dbf',
    '/u01/oracle/obsdata/axx01.dbf',
    '/u01/oracle/obsdata/azd01.dbf',
    '/u01/oracle/obsdata/azx01.dbf',
    '/u01/oracle/obsdata/bend01.dbf',
    '/u01/oracle/obsdata/benx01.dbf',
    '/u01/oracle/obsdata/bicd01.dbf',
    '/u01/oracle/obsdata/bicx01.dbf',
    '/u01/oracle/obsdata/bild01.dbf',
    '/u01/oracle/obsdata/bilx01.dbf',
    '/u01/oracle/obsdata/bimd01.dbf',
    '/u01/oracle/obsdata/bimx01.dbf',
    '/u01/oracle/obsdata/bisd01.dbf',
    '/u01/oracle/obsdata/bisx01.dbf',
    '/u01/oracle/obsdata/bixd01.dbf',
    '/u01/oracle/obsdata/bixx01.dbf',
    '/u01/oracle/obsdata/bomd01.dbf',
    '/u01/oracle/obsdata/bomx01.dbf',
    '/u01/oracle/obsdata/bscd01.dbf',
    '/u01/oracle/obsdata/bscx01.dbf',
    '/u01/oracle/obsdata/cctd01.dbf',
    '/u01/oracle/obsdata/cctx01.dbf',
    '/u01/oracle/obsdata/ced01.dbf',
    '/u01/oracle/obsdata/cex01.dbf',
    '/u01/oracle/obsdata/cnd01.dbf',
    '/u01/oracle/obsdata/cnx01.dbf',
    '/u01/oracle/obsdata/crpd01.dbf',
    '/u01/oracle/obsdata/crpx01.dbf',
    '/u01/oracle/obsdata/csd01.dbf',
    '/u01/oracle/obsdata/csx01.dbf',
    '/u01/oracle/obsdata/cscd01.dbf',
    '/u01/oracle/obsdata/cscx01.dbf',
    '/u01/oracle/obsdata/csdd01.dbf',
    '/u01/oracle/obsdata/csdx01.dbf',
    '/u01/oracle/obsdata/csfd01.dbf',
    '/u01/oracle/obsdata/csfx01.dbf',
    '/u01/oracle/obsdata/cspd01.dbf',
    '/u01/oracle/obsdata/cspx01.dbf',
    '/u01/oracle/obsdata/csrd01.dbf',
    '/u01/oracle/obsdata/csrx01.dbf',
    '/u01/oracle/obsdata/cssd01.dbf',
    '/u01/oracle/obsdata/cssx01.dbf',
    '/u01/oracle/obsdata/cuad01.dbf',
    '/u01/oracle/obsdata/cuax01.dbf',
    '/u01/oracle/obsdata/cufd01.dbf',
    '/u01/oracle/obsdata/cufx01.dbf',
    '/u01/oracle/obsdata/cuid01.dbf',
    '/u01/oracle/obsdata/cuix01.dbf',
    '/u01/oracle/obsdata/cund01.dbf',
    '/u01/oracle/obsdata/cunx01.dbf',
    '/u01/oracle/obsdata/cupd01.dbf',
    '/u01/oracle/obsdata/cupx01.dbf',
    '/u01/oracle/obsdata/cusd01.dbf',
    '/u01/oracle/obsdata/cusx01.dbf',
    '/u01/oracle/obsdata/czd01.dbf',
    '/u01/oracle/obsdata/czx01.dbf',
    '/u01/oracle/obsdata/eaad01.dbf',
    '/u01/oracle/obsdata/eaax01.dbf',
    '/u01/oracle/obsdata/ecd01.dbf',
    '/u01/oracle/obsdata/ecx01.dbf',
    '/u01/oracle/obsdata/ecxd01.dbf',
    '/u01/oracle/obsdata/ecxx01.dbf',
    '/u01/oracle/obsdata/engd01.dbf',
    '/u01/oracle/obsdata/engx01.dbf',
    '/u01/oracle/obsdata/evmd01.dbf',
    '/u01/oracle/obsdata/evmx01.dbf',
    '/u01/oracle/obsdata/fad01.dbf',
    '/u01/oracle/obsdata/fax01.dbf',
    '/u01/oracle/obsdata/femd01.dbf',
    '/u01/oracle/obsdata/femx01.dbf',
    '/u01/oracle/obsdata/fiid01.dbf',
    '/u01/oracle/obsdata/fiix01.dbf',
    '/u01/oracle/obsdata/flmd01.dbf',
    '/u01/oracle/obsdata/flmx01.dbf',
    '/u01/oracle/obsdata/fptd01.dbf',
    '/u01/oracle/obsdata/fptx01.dbf',
    '/u01/oracle/obsdata/frmd01.dbf',
    '/u01/oracle/obsdata/frmx01.dbf',
    '/u01/oracle/obsdata/fvd01.dbf',
    '/u01/oracle/obsdata/fvx01.dbf',
    '/u01/oracle/obsdata/gld01.dbf',
    '/u01/oracle/obsdata/glx01.dbf',
    '/u01/oracle/obsdata/gmad01.dbf',
    '/u01/oracle/obsdata/gmax01.dbf',
    '/u01/oracle/obsdata/gmdd01.dbf',
    '/u01/oracle/obsdata/gmdx01.dbf',
    '/u01/oracle/obsdata/gmed01.dbf',
    '/u01/oracle/obsdata/gmex01.dbf',
    '/u01/oracle/obsdata/gmfd01.dbf',
    '/u01/oracle/obsdata/gmfx01.dbf',
    '/u01/oracle/obsdata/gmid01.dbf',
    '/u01/oracle/obsdata/gmix01.dbf',
    '/u01/oracle/obsdata/gmld01.dbf',
    '/u01/oracle/obsdata/gmlx01.dbf',
    '/u01/oracle/obsdata/gmpd01.dbf',
    '/u01/oracle/obsdata/gmpx01.dbf',
    '/u01/oracle/obsdata/gmsd01.dbf',
    '/u01/oracle/obsdata/gmsx01.dbf',
    '/u01/oracle/obsdata/grd01.dbf',
    '/u01/oracle/obsdata/grx01.dbf',
    '/u01/oracle/obsdata/hrd01.dbf',
    '/u01/oracle/obsdata/hrx01.dbf',
    '/u01/oracle/obsdata/hrid01.dbf',
    '/u01/oracle/obsdata/hrix01.dbf',
    '/u01/oracle/obsdata/hxcd01.dbf',
    '/u01/oracle/obsdata/hxcx01.dbf',
    '/u01/oracle/obsdata/hxtd01.dbf',
    '/u01/oracle/obsdata/hxtx01.dbf',
    '/u01/oracle/obsdata/ibad01.dbf',
    '/u01/oracle/obsdata/ibax01.dbf',
    '/u01/oracle/obsdata/ibed01.dbf',
    '/u01/oracle/obsdata/ibex01.dbf',
    '/u01/oracle/obsdata/ibpd01.dbf',
    '/u01/oracle/obsdata/ibpx01.dbf',
    '/u01/oracle/obsdata/ibud01.dbf',
    '/u01/oracle/obsdata/ibux01.dbf',
    '/u01/oracle/obsdata/ibyd01.dbf',
    '/u01/oracle/obsdata/ibyx01.dbf',
    '/u01/oracle/obsdata/icxd01.dbf',
    '/u01/oracle/obsdata/icxx01.dbf',
    '/u01/oracle/obsdata/iebd01.dbf',
    '/u01/oracle/obsdata/iebx01.dbf',
    '/u01/oracle/obsdata/iemd01.dbf',
    '/u01/oracle/obsdata/iemx01.dbf',
    '/u01/oracle/obsdata/ieod01.dbf',
    '/u01/oracle/obsdata/ieox01.dbf',
    '/u01/oracle/obsdata/iesd01.dbf',
    '/u01/oracle/obsdata/iesx01.dbf',
    '/u01/oracle/obsdata/ieud01.dbf',
    '/u01/oracle/obsdata/ieux01.dbf',
    '/u01/oracle/obsdata/iexd01.dbf',
    '/u01/oracle/obsdata/iexx01.dbf',
    '/u01/oracle/obsdata/igcd01.dbf',
    '/u01/oracle/obsdata/igcx01.dbf',
    '/u01/oracle/obsdata/igfd01.dbf',
    '/u01/oracle/obsdata/igfx01.dbf',
    '/u01/oracle/obsdata/igsd01.dbf',
    '/u01/oracle/obsdata/igsx01.dbf',
    '/u01/oracle/obsdata/igwd01.dbf',
    '/u01/oracle/obsdata/igwx01.dbf',
    '/u01/oracle/obsdata/invd01.dbf',
    '/u01/oracle/obsdata/invx01.dbf',
    '/u01/oracle/obsdata/ipad01.dbf',
    '/u01/oracle/obsdata/ipax01.dbf',
    '/u01/oracle/obsdata/iscd01.dbf',
    '/u01/oracle/obsdata/iscx01.dbf',
    '/u01/oracle/obsdata/jad01.dbf',
    '/u01/oracle/obsdata/jax01.dbf',
    '/u01/oracle/obsdata/jed01.dbf',
    '/u01/oracle/obsdata/jex01.dbf',
    '/u01/oracle/obsdata/jgd01.dbf',
    '/u01/oracle/obsdata/jgx01.dbf',
    '/u01/oracle/obsdata/jld01.dbf',
    '/u01/oracle/obsdata/jlx01.dbf',
    '/u01/oracle/obsdata/jtfd01.dbf',
    '/u01/oracle/obsdata/jtfx01.dbf',
    '/u01/oracle/obsdata/med01.dbf',
    '/u01/oracle/obsdata/mex01.dbf',
    '/u01/oracle/obsdata/mfgd01.dbf',
    '/u01/oracle/obsdata/mfgx01.dbf',
    '/u01/oracle/obsdata/mrpd01.dbf',
    '/u01/oracle/obsdata/mrpx01.dbf',
    '/u01/oracle/obsdata/mscd01.dbf',
    '/u01/oracle/obsdata/mscx01.dbf',
    '/u01/oracle/obsdata/msdd01.dbf',
    '/u01/oracle/obsdata/msdx01.dbf',
    '/u01/oracle/obsdata/msod01.dbf',
    '/u01/oracle/obsdata/msox01.dbf',
    '/u01/oracle/obsdata/mwad01.dbf',
    '/u01/oracle/obsdata/mwax01.dbf',
    '/u01/oracle/obsdata/oed01.dbf',
    '/u01/oracle/obsdata/oex01.dbf',
    '/u01/oracle/obsdata/okcd01.dbf',
    '/u01/oracle/obsdata/okcx01.dbf',
    '/u01/oracle/obsdata/oked01.dbf',
    '/u01/oracle/obsdata/okex01.dbf',
    '/u01/oracle/obsdata/oksd01.dbf',
    '/u01/oracle/obsdata/oksx01.dbf',
    '/u01/oracle/obsdata/okxd01.dbf',
    '/u01/oracle/obsdata/okxx01.dbf',
    '/u01/oracle/obsdata/ontd01.dbf',
    '/u01/oracle/obsdata/ontx01.dbf',
    '/u01/oracle/obsdata/opid01.dbf',
    '/u01/oracle/obsdata/opix01.dbf',
    '/u01/oracle/obsdata/osmd01.dbf',
    '/u01/oracle/obsdata/osmx01.dbf',
    '/u01/oracle/obsdata/otad01.dbf',
    '/u01/oracle/obsdata/otax01.dbf',
    '/u01/oracle/obsdata/ozfd01.dbf',
    '/u01/oracle/obsdata/ozfx01.dbf',
    '/u01/oracle/obsdata/ozpd01.dbf',
    '/u01/oracle/obsdata/ozpx01.dbf',
    '/u01/oracle/obsdata/ozsd01.dbf',
    '/u01/oracle/obsdata/ozsx01.dbf',
    '/u01/oracle/obsdata/pad01.dbf',
    '/u01/oracle/obsdata/pax01.dbf',
    '/u01/oracle/obsdata/pjmd01.dbf',
    '/u01/oracle/obsdata/pjmx01.dbf',
    '/u01/oracle/obsdata/pmid01.dbf',
    '/u01/oracle/obsdata/pmix01.dbf',
    '/u01/oracle/obsdata/pnd01.dbf',
    '/u01/oracle/obsdata/pnx01.dbf',
    '/u01/oracle/obsdata/pod01.dbf',
    '/u01/oracle/obsdata/pox01.dbf',
    '/u01/oracle/obsdata/poad01.dbf',
    '/u01/oracle/obsdata/poax01.dbf',
    '/u01/oracle/obsdata/pomd01.dbf',
    '/u01/oracle/obsdata/pomx01.dbf',
    '/u01/oracle/obsdata/psad01.dbf',
    '/u01/oracle/obsdata/psax01.dbf',
    '/u01/oracle/obsdata/psbd01.dbf',
    '/u01/oracle/obsdata/psbx01.dbf',
    '/u01/oracle/obsdata/pspd01.dbf',
    '/u01/oracle/obsdata/pspx01.dbf',
    '/u01/oracle/obsdata/qad01.dbf',
    '/u01/oracle/obsdata/qax01.dbf',
    '/u01/oracle/obsdata/qpd01.dbf',
    '/u01/oracle/obsdata/qpx01.dbf',
    '/u01/oracle/obsdata/rgd01.dbf',
    '/u01/oracle/obsdata/rgx01.dbf',
    '/u01/oracle/obsdata/rhxd01.dbf',
    '/u01/oracle/obsdata/rhxx01.dbf',
    '/u01/oracle/obsdata/rlad01.dbf',
    '/u01/oracle/obsdata/rlax01.dbf',
    '/u01/oracle/obsdata/rlmd01.dbf',
    '/u01/oracle/obsdata/rlmx01.dbf',
    '/u01/oracle/obsdata/sspd01.dbf',
    '/u01/oracle/obsdata/sspx01.dbf',
    '/u01/oracle/obsdata/vead01.dbf',
    '/u01/oracle/obsdata/veax01.dbf',
    '/u01/oracle/obsdata/vehd01.dbf',
    '/u01/oracle/obsdata/vehx01.dbf',
    '/u01/oracle/obsdata/wipd01.dbf',
    '/u01/oracle/obsdata/wipx01.dbf',
    '/u01/oracle/obsdata/wmsd01.dbf',
    '/u01/oracle/obsdata/wmsx01.dbf',
    '/u01/oracle/obsdata/wpsd01.dbf',
    '/u01/oracle/obsdata/wpsx01.dbf',
    '/u01/oracle/obsdata/wshd01.dbf',
    '/u01/oracle/obsdata/wshx01.dbf',
    '/u01/oracle/obsdata/wsmd01.dbf',
    '/u01/oracle/obsdata/wsmx01.dbf',
    '/u01/oracle/obsdata/xdpd01.dbf',
    '/u01/oracle/obsdata/xdpx01.dbf',
    '/u01/oracle/obsdata/xlad01.dbf',
    '/u01/oracle/obsdata/xlax01.dbf',
    '/u01/oracle/obsdata/xncd01.dbf',
    '/u01/oracle/obsdata/xncx01.dbf',
    '/u01/oracle/obsdata/xnmd01.dbf',
    '/u01/oracle/obsdata/xnmx01.dbf',
    '/u01/oracle/obsdata/xnpd01.dbf',
    '/u01/oracle/obsdata/xnpx01.dbf',
    '/u01/oracle/obsdata/xnsd01.dbf',
    '/u01/oracle/obsdata/xnsx01.dbf',
    '/u01/oracle/obsdata/xtrd01.dbf',
    '/u01/oracle/obsdata/xtrx01.dbf',
    '/u01/oracle/obsdata/applsysd02.dbf',
    '/u01/oracle/obsdata/applsysx02.dbf',
    '/u01/oracle/obsdata/asld01.dbf',
    '/u01/oracle/obsdata/aslx01.dbf',
    '/u01/oracle/obsdata/pvd01.dbf',
    '/u01/oracle/obsdata/pvx01.dbf',
    '/u01/oracle/obsdata/system06.dbf',
    '/u01/oracle/obsdata/itgd01.dbf',
    '/u01/oracle/obsdata/itgx01.dbf',
    '/u01/oracle/obsdata/ipdd01.dbf',
    '/u01/oracle/obsdata/ipdx01.dbf',
    '/u01/oracle/obsdata/eamd01.dbf',
    '/u01/oracle/obsdata/eamx01.dbf',
    '/u01/oracle/obsdata/enid01.dbf',
    '/u01/oracle/obsdata/enix01.dbf',
    '/u01/oracle/obsdata/okrd01.dbf',
    '/u01/oracle/obsdata/okrx01.dbf',
    '/u01/oracle/obsdata/cued01.dbf',
    '/u01/oracle/obsdata/cuex01.dbf',
    '/u01/oracle/obsdata/fted01.dbf',
    '/u01/oracle/obsdata/ftex01.dbf',
    '/u01/oracle/obsdata/msrd01.dbf',
    '/u01/oracle/obsdata/msrx01.dbf',
    '/u01/oracle/obsdata/igid01.dbf',
    '/u01/oracle/obsdata/igix01.dbf',
    '/u01/oracle/obsdata/portal01.dbf',
    '/u01/oracle/obsdata/ahld01.dbf',
    '/u01/oracle/obsdata/ahlx01.dbf',
    '/u01/oracle/obsdata/ahmd01.dbf',
    '/u01/oracle/obsdata/ahmx01.dbf',
    '/u01/oracle/obsdata/aspd01.dbf',
    '/u01/oracle/obsdata/aspx01.dbf',
    '/u01/oracle/obsdata/bivd01.dbf',
    '/u01/oracle/obsdata/bivx01.dbf',
    '/u01/oracle/obsdata/csed01.dbf',
    '/u01/oracle/obsdata/csex01.dbf',
    '/u01/oracle/obsdata/csid01.dbf',
    '/u01/oracle/obsdata/csix01.dbf',
    '/u01/oracle/obsdata/csld01.dbf',
    '/u01/oracle/obsdata/cslx01.dbf',
    '/u01/oracle/obsdata/cugd01.dbf',
    '/u01/oracle/obsdata/cugx01.dbf',
    '/u01/oracle/obsdata/iecd01.dbf',
    '/u01/oracle/obsdata/iecx01.dbf',
    '/u01/oracle/obsdata/imcd01.dbf',
    '/u01/oracle/obsdata/imcx01.dbf',
    '/u01/oracle/obsdata/imtd01.dbf',
    '/u01/oracle/obsdata/imtx01.dbf',
    '/u01/oracle/obsdata/jtmd01.dbf',
    '/u01/oracle/obsdata/jtmx01.dbf',
    '/u01/oracle/obsdata/jtsd01.dbf',
    '/u01/oracle/obsdata/jtsx01.dbf',
    '/u01/oracle/obsdata/okbd01.dbf',
    '/u01/oracle/obsdata/okbx01.dbf',
    '/u01/oracle/obsdata/okid01.dbf',
    '/u01/oracle/obsdata/okix01.dbf',
    '/u01/oracle/obsdata/okod01.dbf',
    '/u01/oracle/obsdata/okox01.dbf',
    '/u01/oracle/obsdata/posd01.dbf',
    '/u01/oracle/obsdata/posx01.dbf',
    '/u01/oracle/obsdata/xnid01.dbf',
    '/u01/oracle/obsdata/xnix01.dbf',
    '/u01/oracle/obsdata/system07.dbf',
    '/u01/oracle/obsdata/system08.dbf',
    '/u01/oracle/obsdata/system09.dbf',
    '/u01/oracle/obsdata/rbs02.dbf',
    '/u01/oracle/obsdata/amfd01.dbf',
    '/u01/oracle/obsdata/amfx01.dbf',
    '/u01/oracle/obsdata/bned01.dbf',
    '/u01/oracle/obsdata/bnex01.dbf',
    '/u01/oracle/obsdata/csmd01.dbf',
    '/u01/oracle/obsdata/csmx01.dbf',
    '/u01/oracle/obsdata/dddd01.dbf',
    '/u01/oracle/obsdata/dddx01.dbf',
    '/u01/oracle/obsdata/domd01.dbf',
    '/u01/oracle/obsdata/domx01.dbf',
    '/u01/oracle/obsdata/egod01.dbf',
    '/u01/oracle/obsdata/egox01.dbf',
    '/u01/oracle/obsdata/ibcd01.dbf',
    '/u01/oracle/obsdata/ibcx01.dbf',
    '/u01/oracle/obsdata/okld01.dbf',
    '/u01/oracle/obsdata/oklx01.dbf',
    '/u01/oracle/obsdata/pjid01.dbf',
    '/u01/oracle/obsdata/pjix01.dbf',
    '/u01/oracle/obsdata/pond01.dbf',
    '/u01/oracle/obsdata/ponx01.dbf',
    '/u01/oracle/obsdata/qotd01.dbf',
    '/u01/oracle/obsdata/qotx01.dbf',
    '/u01/oracle/obsdata/qrmd01.dbf',
    '/u01/oracle/obsdata/qrmx01.dbf',
    '/u01/oracle/obsdata/discoverer01.dbf',
    '/u01/oracle/obsdata/cinvd01.dbf',
    '/u01/oracle/obsdata/cinvx01.dbf',
    '/u01/oracle/obsdata/cpod01.dbf',
    '/u01/oracle/obsdata/cpox01.dbf',
    '/u01/oracle/obsdata/capd01.dbf',
    '/u01/oracle/obsdata/capx01.dbf',
    '/u01/oracle/obsdata/card01.dbf',
    '/u01/oracle/obsdata/carx01.dbf',
    '/u01/oracle/obsdata/cqcd01.dbf',
    '/u01/oracle/obsdata/cqcx01.dbf',
    '/u01/oracle/obsdata/cfndd01.dbf',
    '/u01/oracle/obsdata/cfndx01.dbf',
    '/u01/oracle/obsdata/cgld01.dbf',
    '/u01/oracle/obsdata/cglx01.dbf',
    '/u01/oracle/obsdata/convd01.dbf',
    '/u01/oracle/obsdata/applsysd03.dbf',
    '/u01/oracle/obsdata/applsysx03.dbf',
    '/u01/oracle/obsdata/cwpld01.dbf',
    '/u01/oracle/obsdata/cwplx01.dbf',
    '/u01/oracle/obsdata/csyd01.dbf',
    '/u01/oracle/obsdata/csyx01.dbf',
    '/u01/oracle/obsdata/cpod02.dbf',
    '/u01/oracle/obsdata/csyd02.dbf'
    CHARACTER SET UTF8
    ALTER DATABASE OPEN RESETLOGS;
    DROP tablespace TEMP;
    DROP tablespace TEMPSYN;
    CREATE temporary tablespace TEMP TEMPFILE '/u01/oracle/obsdata/temp01.dbf'
         SIZE 1048576000 REUSE extent management local uniform size 128K;
    CREATE temporary tablespace TEMPSYN TEMPFILE '/u01/oracle/obsdata/tempsyn01.dbf'
         SIZE 1048576000 REUSE extent management local uniform size 128K;
    Edited by: amychan60 on Jun 17, 2009 9:30 PM

  • Annoying 'Could not use the history eraser because the current canvas size does not match that of the history state' message

    Does anyone know if it is possible to get rid of the message 'Could not use the history eraser because the current canvas size does not match that of the history state'?. It comes up if I hit the alt/option key while I have the eraser selected. Something I do by accident all the time.

    The way you've described it, one gets the distinct impression you do not have a clue as to what the history brush does and how to use it.
    You need to read up on it.  Read the Help files and google for tutorials.
    First you need to create an image (with actual pixels in it), edit it as desired, then make a snapshot of the edited image, then target the snapshot with the history brush tool, then go back in the History panel to the step before your edits and selectively paint your edits in with the History Brush.

  • ERROR ITMS-9000: "File given does not match type JPEG ... Image is likely corrupt

    Hi ALl,
    On compliing my book  get these errors with ITunes producer...I've resaved the files out with photoshop and they seems fine?
    Package Summary:
    1 package(s) were not uploaded because they had problems:
              /Users/Umran/Music/iTunes Producer/Playlists/9780957408654.itmsp - Error Messages:
                        Apple's web service operation was not successful
                        Unable to authenticate the package: 9780957408654.itmsp
                        ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@1cf629f[userString=An unknown error occured while parsing. Image is likely corrupt.  Exception message: null]" at Book (MZItmspBookPackage)
                        ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@1801285[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                        ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@1e056e9[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                        ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@11d58e0[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                        ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues: ; Error=com.apple.jingle.leghorn.fileformat.ValidationError@127c00e[userString=We reached the end of the file before we expected. Image is likely corrupt]" at Book (MZItmspBookPackage)
                        ERROR ITMS-5107: "VirtualLandscapesTheModernEra20002012.epub: Fixed-layout books must supply a text or bodymatter starting location in the guide." at Book (MZItmspBookPackage)
    Any advice??? Hope someone can help!

    iBookstore Publisher Support send me a fast response email which included some helpful info:
    Please make sure that all image files inside the ePub end with one of the following: ".tif", ".jpg", or ".png" and that the file itself matches the file extension type. To check if the image file matches the file extension type, please right click on the image then select "Get Info". Once the info tab appears, please make sure that the file extension type of the image file matches the "Kind" found under "General".
    For further information regarding embedded images, please refer to the iBookstore Asset Guide, which is available for download in the Deliver Your Content module in iTunes Connect.
    And they INCLUDED THE TRANSPORTER LOG (!), the log generated by iTunes Producer as it tries to upload a book. We were able to search for the Validation Error # within the log and find out which image Producer was trying to upload when it encountered an error. Turns out the problem was a corrupted screenshot jpeg.
    Grateful!

  • ERROR ITMS-9000 "File given does not match type JPEG....

    I'm trying to upload our iBook. I first did an export outside of publish, then did publish and reloaded everything under the .itmsp file publish created. About 10 minutes into the upload, I received a message that read:
    1 Apple's web service operation was not successful.
    2 Unable to authenticate the package ISBN#...:itmsp
    3: ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@387eb9b2[userString=Th is file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    4 ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@6bad662[userString=Thi s file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    5 ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@450fcee3[userString=Th is file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    6 ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@69c736ea[userString=Th is file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    7 ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@15e672e7[userString=Th is file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    8 ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@4c812a6ec[userString=T his file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    9ERROR ITMS-9000: "File given does not match type JPEG Image because of these validation issues:
    Error=com.apple.jingle.leghorn.fileformat.ValidationError@54180fd6[userString=Th is file does not start with a start of image marker.] at Book (MZitmspBookPackage)
    Any suggestions would be greatly appreciated.

    I had done screen shots on the iPad and then emailed them to my Mac. I then worked to cut the black bar off the top, but some how Photoshop wasn't saving them correctly. I couldn't even reopen them in PS. So, I downloaded them again, went back in, saved them as .jpegs and then reuploaded.  That solved it.  It was quite bizarre. 
    Now trying to get the description listing right in the iBookstore.
    I wrote the piece out, I thought in TextEdit.  Then pasted it into the box in iTunesProducer. When I was getting the error message above, it also was saying that there's a 4,000-character limit. So, I copied it into Pages and did a character count and saw 3,887.  I still had to cut about 500 chactacters out.  Support responded and said I was still very close to the limit, so I don't know what it was they were counting. My Pages counter said it was close to 3,300....
    My problem now is that they have bullet points on lines with no text now.  They've fixed it from how it was first diplaying.  So, I'm trying to get that cleaned up.  It's their fault, but it looks like me, the publisher, is the one who is clueless......
    Here's the link to our iBook!
    http://itunes.apple.com/us/book/2012-science-prophecy-ancient/id555557425?mt=11

  • Brush preview size does not match brush stroke

    The brush preview size does not match brush stroke. I've insert a pic of the problem. I tried allmost everythning, but nothing works.
    Does anyone have a solution for this problem?
    *I use a wacom tablet.

    Is your system cursor size set to something other than normal?
    under Apple, System Preferences, Universal Access.

  • Final print size does not match screen view.

    Hi
    I am having problems getting my final prints to match the screen view.  Most recently I have had this problem:  I have an image that is sized to 5X7.  I have it on a 5X7 template in the print module of Lightroom.  The image dimensions in Lightroom say 5X7.  I print on 5X7 paper (I actually measured it to be sure).  ON the screen they look perfect, match the the templates and measure out fime with the onscreen rulers.  Without fail a portion of the print is cut off on the final print.  The long side of the print is the most effected.  This is not just limited to 5X7's, it happens across the board.  Is this a common problem or I am I doing something wrong?  In the 5X7 example above the print comes out 5.2 X 7.3 give or take.  I am using Lightroom 5.3 on an iMac running OS 10.9.1.  The printer is a Canon Pro 100. 
    I welcome any help with this.
    Thank you
    Joe

    If the problem is that the printed image is being scaled larger, this is a very common side effect with borderless mode settings in print drivers. Typically, (though sometimes you can prevent this where alternative borderless options are given) - an extra unrequested scaling % ensures that any physical mis-registration or inaccuracy of the paper size, does not leave any accidental white edges.
    That's nothing to do with LR's end of the process, if so.

  • PDF Page Size does not match Canvas Size

    Hello,
    I'm using Xcelsius 2008 Engage SP1 on Vista 64bit with Office 2007 installed. When I'm exporting a Xcelsius file to PDF, the resulting Page Size of the PDF file is 8.5in x 11in. However, the Canvas size in Xcelsius is 800x600 (pixels). The resulting PDF file has quite a bit of whitespace in the top and bottom sections of the file.
    Is there anyway that I can export to PDF but with a file size that is in the same aspect ratio than the Canvas Size?
    Thanks for any input.
    Regards,
    Jon

    We regularly export to PDF and face this issue.  I believe that the adjustments need to be made in Acrobat as there is, from my understanding, no way to change the default export in Xcelsius.  You are probably already be doing this, but if not ... our solution has been, once you have exported your model into Acrobat, to simply rotate the page before saving the file.  At 800 x 600 you may still have some white space at the top and bottom of your model.  We typically use an Xcelsius canvas size of 1100 x 850.  When exported (and rotated in Acrobat) this gives a nice crisp image that also fills the page.  I hope this helps you.

  • File paths does not match with file name

    Hi,
    somehow iTunes does not properly file my audiobooks.  Eventhough all audiobooks are marked as media type: AudioBooks and Genre: AudioBook (German: Hörbuch), but when looking in Music --> iTunes --> iTunesMedia --> AudioBooks  there's only a few AudioBooks that I bought with Audible.
    All the other AudioBooks are stored I don't know where.  When opening the information about an AudioBook, and select "overview" it says at "location" ...iTunesMedia/Music/...  and an artist name or compilation followed by an artist name.
    How can I easily redirect iTunes to store the AudioBooks in AudioBooks and not under some wired musican's name where I never placed the audiobook before
    Any idea? Does anybody know of this bizare problem?
    thanks for your help from Cologne, Germany,
    Daniel Vollmer

    HDash-Tech,
    thanks for the tip, but since I have my iTunes Library on a NAS I have to direct iTunes every now and than via "choose library" to the folder and it doesn't make a difference...
    I think it's somehow due to my iTunes Match.  I know they do not sync audiobooks, but they mess up pretty much everything else within my library.  Songnames here and there and especially cd covers!
    Any other idea how to get it straigten out again?
    Thank,
    Daniel

  • .psd file size does not make any sense to me

    I am hoping someone can explain the huge .psd file sizes I am seeing.
    I have a Canon 7D and shoot raw.  I have a raw file that is 24.6 Mbytes and is a 3456 x 5184 pixel image. I then open with ACR and do nothing but save it as a 16-bit .psd file with the same image (pixel) resolution.  The .psd file is 102.5 Mbytes.
    By my calcs a 3456 x 5184 x 2 bytes (16 bit depth) is 35.8 Mbytes uncompressed.  Yet the .psd is nearly 3 times this size before it is ever opened in Photoshop.
    Can anyone explain why?  My 256 GByte disk has been eaten up like a bunch of breath mints...

    Your assumptions are wrong.
    "16 bit" RGB data has 3 colors per pixel x 16 bits per color.  Thus, 3456 x 5184 x 6 bytes = 107 megabytes and change.
    The raw file has, as I recall, 14 bits per photosite of measurement data that has not been debayered.  Only one color range of light is measured per photosite.
    Both the Canon CR2 raw format and the Photoshop PSD format include lossless compression as well.
    I hope this helps clear things up.
    -Noel

  • Data type column size does not match size of values returned

    I've tried searching but couldn't find what I was looking for, sorry if this has been answered or is a duplicate.
    I am using the (Java) method below to get the column definitions of a table. I am doing this through an ODBC connection (using Oracle ODBC driver) and I have NO CHOICE in the matter.
    The problem I am having is that one particular column has a column size is smaller than the size of the data it purportedly holds (ie attendance_code = varchar size 3 but data value is "Absent". I suspect the data is actually a look up to situation, where my attendance_code column has a value of 'ABS' and Oracle goes and fetchs the "Absent" value.
    My issue is that the meta data returned from ODBC is the actual column definition (ie varchar(3) and not varchar2(10) for example).
    The resultset metadata has a size of 3 for the column in question, and querying the schema also yields 3 for that column.
    How do I resolve this? I do not have access to all_columns table etc. I have to do it using ODBC metadata only.
    I've tried recreating the situation using the Oracle XE DB, but as I am not familiar with Oracle, I do not know how to recreate this scenario (which would then lead me to test other options with ODBC).
    TIA.
    The select I am using is SELECT * FROM <tableName>.
    public ArrayList<SchemaColumn> getColumnsForTable(String catalog,
    String schema,
    String tableName) {
    ArrayList<SchemaColumn> columns = new ArrayList<SchemaColumn>();
    ResultSet rs = null;
    try {
    DatabaseMetaData metaData = connection.getMetaData();
    rs = metaData.getColumns(catalog, schema, tableName, "%");
    SchemaColumn column;
    while (rs.next()) {
    column = new SchemaColumn();
    column.setName(rs.getString("COLUMN_NAME"));
    column.setDataType(rs.getInt("DATA_TYPE"));
    column.setTypeName(rs.getString("TYPE_NAME"));
    column.setColumnSize(rs.getInt("COLUMN_SIZE")); <-------- this is the value that is coming back smaller than the data it actually returns
    column.setDecimalDigits(rs.getInt("DECIMAL_DIGITS"));
    column.setNumPrecisionRadix(rs.getInt("NUM_PREC_RADIX"));
    column.setNullable(rs.getInt("NULLABLE"));
    column.setRemarks(rs.getString("REMARKS"));
    column.setDefaultValue(rs.getString("COLUMN_DEF"));
    column.setSqlDataType(rs.getInt("SQL_DATA_TYPE"));
    column.setSqlDateTimeSub(rs.getInt("SQL_DATETIME_SUB"));
    column.setCharOctetLength(rs.getInt("CHAR_OCTET_LENGTH"));
    column.setOrdinalPosition(rs.getInt("ORDINAL_POSITION"));
    columns.add(column);
    } catch (Exception e) {
    Log.getLogger().error("Could not capture table schema");
    closeResultSet(rs);
    return columns;
    }

    I can't say I've ever seen a case where a column held more data than it was declared as, and would have to file that under "see it to believe it" category.
    Even if that somehow were the case, I'd expect the ODBC driver to return what the column is defined as anyway, not the data. The data changes with every row, but I'd expect the table metadata to be consistent, and refer to the table definition.
    For grins though, can you provide system.out.println output of the metadata, and also a "describe xxxx" from sqlplus if you can, where xxx is the table name?
    ie,
    while (rs.next()) {
    System.out.println("column name is " + rs.getString("COLUMN_NAME"));
    System.out.println("data type is " + rs.getInt("DATA_TYPE"));
    ..etc..
    Greg

  • Data type size does not match values returned

    I've tried searching but couldn't find what I was looking for, sorry if this has been answered or is a duplicate.
    I am using the (Java) method below to get the column definitions of a table. I am doing this through an ODBC connection (using Oracle ODBC driver) and I have NO CHOICE in the matter.
    The problem I am having is that one particular column has a column size is smaller than the size of the data it purportedly holds (ie attendance_code = varchar size 3 but data value is "Absent". I suspect the data is actually a look up to situation, where my attendance_code column has a value of 'ABS' and Oracle goes and fetchs the "Absent" value.
    My issue is that the meta data returned from ODBC is the actual column definition (ie varchar(3) and not varchar2(10) for example).
    How do I resolve this? I do not have access to all_columns table etc. I have to do it using ODBC metadata only.
    TIA.
    public ArrayList<SchemaColumn> getColumnsForTable(String catalog,
                   String schema,
                   String tableName) {
              ArrayList<SchemaColumn> columns = new ArrayList<SchemaColumn>();
              ResultSet rs = null;
              try {
                   DatabaseMetaData metaData = connection.getMetaData();
                   rs = metaData.getColumns(catalog, schema, tableName, "%");
                   SchemaColumn column;
                   while (rs.next()) {
                        column = new SchemaColumn();
                        column.setName(rs.getString("COLUMN_NAME"));
                        column.setDataType(rs.getInt("DATA_TYPE"));
                        column.setTypeName(rs.getString("TYPE_NAME"));
                        column.setColumnSize(rs.getInt("COLUMN_SIZE")); <-------- this is the value that is coming back smaller than the data it actually returns
                        column.setDecimalDigits(rs.getInt("DECIMAL_DIGITS"));
                        column.setNumPrecisionRadix(rs.getInt("NUM_PREC_RADIX"));
                        column.setNullable(rs.getInt("NULLABLE"));
                        column.setRemarks(rs.getString("REMARKS"));
                        column.setDefaultValue(rs.getString("COLUMN_DEF"));
                        column.setSqlDataType(rs.getInt("SQL_DATA_TYPE"));
                        column.setSqlDateTimeSub(rs.getInt("SQL_DATETIME_SUB"));
                        column.setCharOctetLength(rs.getInt("CHAR_OCTET_LENGTH"));
                        column.setOrdinalPosition(rs.getInt("ORDINAL_POSITION"));
                        columns.add(column);
              } catch (Exception e) {
                   Log.getLogger().error("Could not capture table schema");
              closeResultSet(rs);
              return columns;
    Edited by: user10382699 on Apr 11, 2011 4:15 PM

    John, thanks for your reply.
    As far as I know I'm not doing anything inaccurately/incorrectly.
    The select I am using is SELECT * FROM <tableName>.
    The resultset metadata has a size of 3 for the column in question, and querying the schema also yields 3 for that column.
    I've tried recreating the situation using the Oracle XE DB, but as I am not familiar with Oracle, I do not know how to recreate this scenario (which would then lead me to test other options with ODBC).

Maybe you are looking for