Conversion of datatypes

Hi,
How to convert a field of type 'date' into 'decimal' on target side in while doing mapping.Anybody Pleaseee.....
Thanks & Regards,
Radhika.

Hi Radhika,
As Raj suggested you can use Format Number function...but can you please tell us by converting date into Dec what actually you are trying to achieve. I mean if you tell us exact requirement we can provide you better solution.
If you want to convert date into number for comparison then we can declare a variable as a integer than decimal...becase there wont be any decimal places..
Please let us know the exact requirement.
Nilesh

Similar Messages

Conversion of Datatype

Hi All,
How to convert Number(6) datatype to Number (6,2) Data type.
Thanks in advance.

Hi,
First thing, the source number is of precision 5 and the target is of number(5,2). This means that target will be of precision 3 and scale 2. which of course wont allow you to insert the records.
You need to change it to Number(7,2). means precision 5 and scale 2.
Secondly, even if you use an expression to conver the input column and do to_char(input,99999.99), the output of the expression is as expected but since the target is of datatype number, this will again change to the original input number without scale.
May be you have to change the datatype to varchar2(9)@target. or else try using anydata_cast operator.
HTH

Arabic Character set conversion-help needed

We have our main database running in 10g (Solaris o/s) & planning to move these to RAC 11g.
One of our old oracle DB(8.0.5)/solaris, which is not used till recently need to upgrade to 10g Rel2.
I know Supported direct upgrade 8.0.6/8.1.7/9i -> 10g
Current DB: 8.0.5 (Character Set: AR8ISO8859P6)
Target DB : 10g Rel 2 (Character Set: AR8MSWIN1256)
I am thinking to go the following way by using exp/imp
8.0.5(AR8ISO8859P6) -> 8.1.7(AR8ISO8859P6) -> 10G(AR8MSWIN1256)
OR
8.0.5(AR8ISO8859P6) -> 8.1.7(AR8MSWIN1256) -> 10G(AR8MSWIN1256)
please advice
thanks

(1) At source db 8.0.5 (solaris)
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-YY
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET AR8ISO8859P6
NLS_SORT BINARY
NLS_NCHAR_CHARACTERSE T AR8ISO8859P6
$set NLS_LANG=AMERICAN_AMERICA.AR8ISO8859P6
$exp sys/dba file=full251109.dmp full=y
(2):>> At target db 10g R2 (solaris)
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RRRR
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET AR8ISO8859P6
NLS_SORT BINARY
NLS_NCHAR_CHARACTERSET UTF8
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
$export NLS_LANG=AMERICAN_AMERICA.AR8ISO8859P6
$imp testdba/testdba file=full251105.dmp fromuser=PROFINAL touser=PROFINAL
*$csscan testdba/testdba FULL=Y FROMCHAR=AR8ISO8859P6 TOCHAR=AR8ISO8859P6 LOG=P6check CAPTURE=Y ARRAY=100000 PROCESS=2*
There is EXCEPTIONAL DATA in .err file+
clients accessing 8.0.5 dataabase uses characterset AR8IS08859P6, which is SAME as 8.0.5 database
-CSSCAN result->>[Database Scan Parameters]
Parameter Value
CSSCAN Version v2.1
Instance Name MIG1
Database Version 10.2.0.1.0
Scan type Full database
Scan CHAR data? YES
Database character set AR8ISO8859P6
FROMCHAR AR8ISO8859P6
TOCHAR AR8ISO8859P6
Scan NCHAR data? NO
Array fetch buffer size 100000
Number of processes 2
Capture convertible data? YES
[Scan Summary]
Some character type data in the data dictionary are not convertible to the new
haracter set Some character type application data are not convertible to the new characters
[Data Dictionary Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 2,235,403 0 0 *1,492*
CHAR 1,097 0 0 0
LONG 155,188 0 0 6
CLOB 24,643 0 0 0
VARRAY 21,352 0 0 0
Total 2,437,683 0 0 1,498
Total in percentage 99.939% 0.000% 0.000% 0.061%
The data dictionary can not be safely migrated using the CSALTER script
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 16,986,594 0 0 *1,240,383*
CHAR 164,114 0 0 0
LONG 7 0 0 0
CLOB 1 0 0 0
VARRAY 1,436 0 0 0
Total in percentage 93.256% 0.000% 0.000%
6.744%
[Distribution of Convertible, Truncated and Lossy Data by Table]
USER.TABLE Convertible Truncation Lossy
PROFINAL.BASE_MASTER_DATAS 0 0 *362,003*
PROFINAL.CODE_ALLOW 0 0 *53*
PROFINAL.CODE_ALLOWANCE_TYPES 0 0 *1*
PROFINAL.CODE_BONUS_TYPES 0 0 *2*
PROFINAL.CODE_BRANCHES 0 0 *2*
PROFINAL.CODE_CERTIFICATES 0 0 *94*
Kindly help,,,
Edited by: userR12 on Nov 25, 2009 1:43 AM
Edited by: userR12 on Nov 25, 2009 1:52 AM

R12 Characterset conversion to UTF8 on 11 G R2 Database

We are doing Characterset conversion to UTF8, i ran csscan its complaning lot of lossy chars and Convertible chars,do i need to take export below all tables..?
ata Dictionary Tables:
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 117,133,414 0 0 0
CHAR 17,402 0 0 0
LONG 8,074,421 0 0 0
CLOB 4,348,695 22,903 0 0
VARRAY 42,001 0 0 0
Total 129,615,933 22,903 0 0
Total in percentage 99.982% 0.018% 0.000% 0.000%
The data dictionary can be safely migrated using the CSALTER script
XML CSX Dictionary Tables:
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 501 0 0 0
CHAR 0 0 0 0
LONG 0 0 0 0
CLOB 0 0 0 0
VARRAY 0 0 0 0
Total 501 0 0 0
Total in percentage 100.000% 0.000% 0.000% 0.000%
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 118,182,641 0 103 1,260,883
CHAR 265 0 0 0
LONG 61,948 0 0 0
CLOB 129,455 827 0 0
VARRAY 32,797 0 0 0
Total 118,407,106 827 103 1,260,883
Total in percentage 98.946% 0.001% 0.000% 1.054%
Data Dictionary Tables:
USER.TABLE Convertible Truncation Lossy
MDSYS.OPENLS_NODES 17 0 0
MDSYS.SDO_COORD_OP_PARAM_VALS 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE 1 0 0
MDSYS.SDO_STYLES_TABLE 78 0 0
MDSYS.SDO_XML_SCHEMAS 3 0 0
ORDDATA.ORDDCM_CT_PRED_OPRD 51 0 0
ORDDATA.ORDDCM_DOCS 9 0 0
ORDDATA.ORDDCM_MAPPING_DOCS 1 0 0
SYS.METASTYLESHEET 178 0 0
SYS.REGISTRY$ERROR 2 0 0
SYS.RULE$ 21 0 0
SYS.SCHEDULER$_EVENT_LOG 182 0 0
SYS.WRH$_SQLTEXT 2,099 0 0
SYS.WRH$_SQL_PLAN 1,736 0 0
SYS.WRI$_ADV_ACTIONS 5,452 0 0
SYS.WRI$_ADV_DIRECTIVE_META 5 0 0
SYS.WRI$_ADV_OBJECTS 2,278 0 0
SYS.WRI$_ADV_RATIONALE 9,594 0 0
SYS.WRI$_ADV_SQLT_PLANS 455 0 0
SYS.WRI$_ADV_SQLT_PLAN_STATS 288 0 0
SYS.WRI$_DBU_FEATURE_METADATA 188 0 0
SYS.WRI$_DBU_FEATURE_USAGE 16 0 0
SYS.WRI$_DBU_HWM_METADATA 20 0 0
SYS.WRI$_REPT_FILES 27 0 0
XDB.XDB$DXPTAB 2 0 0
XML CSX Dictionary Tables:
USER.TABLE Convertible Truncation Lossy
Application Data:
USER.TABLE Convertible Truncation Lossy
APPLSYS.BISM_OBJECTS 4 0 0
APPLSYS.DR$FND_LOBS_CTX$I 0 103 1,260,883
APPLSYS.FND_CONC_PROG_ANNOTATIONS 272 0 0
APPLSYS.FND_OAM_CONTEXT_FILES 15 0 0
APPLSYS.FND_OAM_DOC_LINK 1 0 0
APPS.FND_OAM_CONTEXT_FILES_1 6 0 0
AZ.AZ_APIS 11 0 0
AZ.AZ_SELECTION_SET_ENTITIES_B 48 0 0
ECX.ECX_DTDS 205 0 0
ECX.ECX_FILES 91 0 0
IBC.IBC_ATTRIBUTE_BUNDLES 41 0 0
JTF.JTF_HEADER_DTD 1 0 0
JTF.JTF_MESSAGE_OBJECTS 82 0 0
JTF.JTY_TRANS_USG_PGM_SQL 29 0 0
ODM.ODM_PMML_DTD 1 0 0
OKC.OKC_REPORT_SQL_B 3 0 0
OKC.OKC_REPORT_SQL_TL 2 0 0
OKC.OKC_REPORT_XSL_TL 5 0 0
XDP.XDP_PROC_BODY 10 0 0
[Distribution of Convertible, Truncated and Lossy Data by Column]
Data Dictionary Tables:
USER.TABLE|COLUMN Convertible Truncation Lossy
MDSYS.OPENLS_NODES|SYS_NC00004$ 17 0 0
MDSYS.SDO_COORD_OP_PARAM_VALS|PARAM_VALUE_FILE 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE|XMLSCHEMA 1 0 0
MDSYS.SDO_STYLES_TABLE|DEFINITION 78 0 0
MDSYS.SDO_XML_SCHEMAS|XMLSCHEMA 3 0 0
ORDDATA.ORDDCM_CT_PRED_OPRD|SYS_NC00004$ 51 0 0
ORDDATA.ORDDCM_DOCS|SYS_NC00005$ 9 0 0
ORDDATA.ORDDCM_MAPPING_DOCS|SYS_NC00007$ 1 0 0
SYS.METASTYLESHEET|STYLESHEET 178 0 0
SYS.REGISTRY$ERROR|MESSAGE 1 0 0
SYS.REGISTRY$ERROR|STATEMENT 1 0 0
SYS.RULE$|CONDITION 21 0 0
SYS.SCHEDULER$_EVENT_LOG|ADDITIONAL_INFO 182 0 0
SYS.WRH$_SQLTEXT|SQL_TEXT 2,099 0 0
SYS.WRH$_SQL_PLAN|OTHER_XML 1,736 0 0
SYS.WRI$_ADV_ACTIONS|ATTR5 2,726 0 0
SYS.WRI$_ADV_ACTIONS|ATTR6 2,726 0 0
SYS.WRI$_ADV_DIRECTIVE_META|DATA 5 0 0
SYS.WRI$_ADV_OBJECTS|ATTR4 2,278 0 0
SYS.WRI$_ADV_RATIONALE|ATTR5 9,594 0 0
SYS.WRI$_ADV_SQLT_PLANS|OTHER_XML 455 0 0
SYS.WRI$_ADV_SQLT_PLAN_STATS|OTHER 288 0 0
SYS.WRI$_DBU_FEATURE_METADATA|INST_CHK_LOGIC 21 0 0
SYS.WRI$_DBU_FEATURE_METADATA|USG_DET_LOGIC 167 0 0
SYS.WRI$_DBU_FEATURE_USAGE|FEATURE_INFO 16 0 0
SYS.WRI$_DBU_HWM_METADATA|LOGIC 20 0 0
SYS.WRI$_REPT_FILES|SYS_NC00005$ 27 0 0
XDB.XDB$DXPTAB|SYS_NC00006$ 2 0 0
XML CSX Dictionary Tables:
USER.TABLE|COLUMN Convertible Truncation Lossy
Application Data:
USER.TABLE|COLUMN Convertible Truncation Lossy
APPLSYS.BISM_OBJECTS|SYS_NC00023$ 4 0 0
APPLSYS.DR$FND_LOBS_CTX$I|TOKEN_TEXT 0 103 1,260,883
APPLSYS.FND_CONC_PROG_ANNOTATIONS|PROGRAM_ANNOTAT 272 0 0
APPLSYS.FND_OAM_CONTEXT_FILES|TEXT 15 0 0
APPLSYS.FND_OAM_DOC_LINK|DOC_LINK_INFO 1 0 0
APPS.FND_OAM_CONTEXT_FILES_1|TEXT 6 0 0
AZ.AZ_APIS|FILTERING_PARAMETERS 11 0 0
AZ.AZ_SELECTION_SET_ENTITIES_B|FILTERING_PARAMETE 48 0 0
ECX.ECX_DTDS|PAYLOAD 205 0 0
ECX.ECX_FILES|PAYLOAD 91 0 0
IBC.IBC_ATTRIBUTE_BUNDLES|ATTRIBUTE_BUNDLE_DATA 41 0 0
JTF.JTF_HEADER_DTD|HEADER_DTD 1 0 0
JTF.JTF_MESSAGE_OBJECTS|BUS_OBJ_DTD 41 0 0
JTF.JTF_MESSAGE_OBJECTS|BUS_OBJ_SQL 41 0 0
JTF.JTY_TRANS_USG_PGM_SQL|BATCH_DEA_SQL 1 0 0
JTF.JTY_TRANS_USG_PGM_SQL|BATCH_INCR_SQL 5 0 0
JTF.JTY_TRANS_USG_PGM_SQL|BATCH_TOTAL_SQL 6 0 0
JTF.JTY_TRANS_USG_PGM_SQL|INCR_REASSIGN_SQL 5 0 0
JTF.JTY_TRANS_USG_PGM_SQL|REAL_TIME_INSERT 6 0 0
JTF.JTY_TRANS_USG_PGM_SQL|REAL_TIME_SQL 6 0 0
ODM.ODM_PMML_DTD|DTD 1 0 0
OKC.OKC_REPORT_SQL_B|SQL_TEXT 3 0 0
OKC.OKC_REPORT_SQL_TL|HELP_TEXT 2 0 0
OKC.OKC_REPORT_XSL_TL|HELP_TEXT 2 0 0
OKC.OKC_REPORT_XSL_TL|XSL_TEXT 3 0 0
XDP.XDP_PROC_BODY|PROC_BODY 10 0 0
[Indexes to be Rebuilt]
USER.INDEX on USER.TABLE(COLUMN)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_TEXT)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_TYPE)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_FIRST)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_LAST)
APPLSYS.DR$FND_LOBS_CTX$X on APPLSYS.DR$FND_LOBS_CTX$I(TOKEN_COUNT)
IBC.IBC_ATTRIBUTE_BUNDLES_CTX on IBC.IBC_ATTRIBUTE_BUNDLES(ATTRIBUTE_BUNDLE_DATA)
-----------------------------------------------------------------------------------------

Sawwan,
I am getting below error
[oracle@uat nls]$ exp file=exp_utf8.dmp parfile=exp.par
Export: Release 11.2.0.1.0 - Production on Wed Apr 20 18:43:11 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in UTF8 character set and AL16UTF16 NCHAR character set
server uses US7ASCII character set (possible charset conversion)
About to export specified tables via Conventional Path ...
Current user changed to APPLSYS
. . exporting table BISM_OBJECTS 4 rows exported
EXP-00011: APPLSYS.DR$FND_LOBS_CTX$I does not exist ( do i need to procced with truncation of convertable objects..?, please confirm me, i am confusing here)
http://www.oracle-latest-technology.com/2011/02/how-to-convert-character-set-of-oracle.html
. . exporting table FND_CONC_PROG_ANNOTATIONS 290 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table FND_OAM_CONTEXT_FILES 15 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table FND_OAM_DOC_LINK 1 rows exported
EXP-00091: Exporting questionable statistics.
Current user changed to APPS
. . exporting table FND_OAM_CONTEXT_FILES_1 6 rows exported
EXP-00091: Exporting questionable statistics.
Current user changed to AZ
. . exporting table AZ_APIS 356 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table AZ_SELECTION_SET_ENTITIES_B 490 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to ECX
. . exporting table ECX_DTDS 205 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table ECX_FILES 91 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to IBC
EXP-00011: IBC.IBC_ATTRIBUTE_BUNDLES_DATA does not exist
. . exporting table IBC_ATTRIBUTE_BUNDLES 41 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to JTF
. . exporting table JTF_HEADER_DTD 1 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table JTF_MESSAGE_OBJECTS 41 rows exported
EXP-00091: Exporting questionable statistics.
. . exporting table JTY_TRANS_USG_PGM_SQL 7 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
EXP-00010: MDSYS is not a valid username
Current user changed to ODM
. . exporting table ODM_PMML_DTD 1 rows exported
EXP-00091: Exporting questionable statistics.
Current user changed to OKC
. . exporting table OKC_REPORT_SQL_B 3 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table OKC_REPORT_SQL_TL 3 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table OKC_REPORT_XSL_TL 3 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00010: XDB is not a valid username
Current user changed to XDP
. . exporting table XDP_PROC_BODY 10 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Current user changed to ORDDATA
. . exporting table ORDDCM_CT_PRED_OPRD 51 rows exported
. . exporting table ORDDCM_DOCS 9 rows exported
. . exporting table ORDDCM_MAPPING_DOCS 1 rows exported
EXP-00091: Exporting questionable statistics.
Export terminated successfully with warnings.
[oracle@uat nls]$ exp file=exp_fnd_lobs.dmp table=APPLSYS.DR$FND_LOBS_CTX$I
LRM-00101: unknown parameter name 'table'

Data type conversion issue

Trying make the parent-child hierarchy to work, where all the keys in the dimension table and parent-child closure table are RAW ( VARBINARY(16) in admin tool)
In BI Answer, when parent-child logical dimension is used with the fact table, got the following error message:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46035] Datatype(VARBINARY) nullable(0) unicode(1) external char(0) conversion to datatype(VARCHAR) nullable(0) unicode(1) external char(0) is not supported. (HY000)
SQL Issued: SELECT 0 s_0, "Chargeback"."Target Instance"."Target Name" s_1, CASE WHEN ISLEAF("Chargeback"."Target Instance"."H51 Target Instance") THEN 1 ELSE 0 END s_2, IDOF("Chargeback"."Target Instance"."H51 Target Instance") s_3, PARENT("Chargeback"."Target Instance"."H51 Target Instance") s_4, "Chargeback"."Base Facts"."Charge" s_5 FROM "Chargeback" WHERE ISROOT("Chargeback"."Target Instance"."H51 Target Instance")
Two questions:
1. The column with the conversion problem is not listed in the error message. How to find out the column with the problem?
2. The SQL listed is not the final text send over to database. How to find out the actual query send over to the database? (Tried EM console, and searched for trace message for bi server, but could not find it there)

Srix, thanks for the reply.
The query is generated by the tool, so it takes some understanding of the internals to make it work. By 'casting the column' do you mean changing the datatypes in the RPD file? If yes, change on the logical table metadata or the physical table metadata? ?

Why there is no datatype which only stores date (without time part)

Hi All,
Is there any specific reason for not having a data type which only stores date (without time part) in ORACLE - I am asking this because DATE (without time) is a very frequently used data type in any application.
Thanks.

884476 wrote:
Then why ORACLE is allowing to have scale and precision in a NUMBER data type. If I want to store an integer there is no harm in storin it just as NUMBER. But I habe option to give something like NUMBER(10). But in DATE, the time part is mandatory.a) because there's no need for seperate DATE and DATETIME datatatypes, and b) the time part is not 'mandatory'.
SQL> create table mytable (x date);
Table created.
SQL> insert into mytable (x) values (to_date('01/01/1980','DD/MM/YYYY'));
1 row created.
SQL>The DATE datatype contains the Time as well, to make it flexible... a single datatype that can do both things without the need for any conversion between datatypes (either explicitly or implicitly).
Yes, many application need to have fields on the screen that just show a date, such as a date of birth as you say, but that's simply a display issue, and any application interface will allow for a date format to be specified for displaying the data from the database, so in terms of such "Date only" dates, you would simply use a format mask that ignores the time portion.
There's absolutely no issue with the fact that it's just a single datatype... it causes no problems... it's perfectly flexible at being used for just dates or for dates and times... so why such a concern?

Database Characterset Conversion from AMERICAN to JAPANESE

Hello
We are creating a test environment from a database with NLS_LANG = AMERICAN_AMERICA.WE8ISO8859P1. This needs to be converted into Japanese characterset with NLS_LANG = JAPANESE_JAPAN.JA16EUC
As per my understanding, I need to first export the database, then create a new database with Japanese NLS_LANG, and then re-import it
Could someone please confirm the steps please
1. Do I need to change NLS_LANG before exporting the database?
2. Can I run a database characterset conversion check before exporting db?
3. Is there any other pre-cautions that I need to take
Oracle Version: Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
OS Version: HP-UX B.11.11
Regards
Sudhanshu

Hello,
I have used the Character Set Scan utility (csscan) Version 1.2. I have attached the report results below.
To convert the character set instead of export/import, can I simply do
ALTER DATABASE CHARACTER SET ja16euc;
I would appreciate feedback on this if anyone has worked on this conversion before.
Parameter Value
CSSCAN Version v1.2
Database Version 9.2.0.6.0
Scan type Full database
Scan CHAR data? YES
Database character set WE8ISO8859P1
FROMCHAR WE8ISO8859P1
TOCHAR JA16EUC
Scan NCHAR data? NO
Array fetch buffer size 10240
Number of processes 20
Capture convertible data? NO
[Scan Summary]
Some character type data in the data dictionary are not convertible to the new character set
Some character type application data are not convertible to the new character set
[Data Dictionary Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 3,303,684 386 0 8
CHAR 5 0 0 0
LONG 219,988 1 0 0
CLOB 0 58 0 0
Total 3,523,677 445 0 8
Total in percentage 100% 0% 0% 0%
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 3,316,273,097 8,517 56 2,675
CHAR 6,954 0 0 0
LONG 197,690 0 0 0
CLOB 0 0 0 0
Total 3,316,477,741 8,517 56 2,675
Total in percentage 100% 0% 0% 0%
Convertible Truncation Lossy
1 0 0
4 0 0
28 0 6
2,792 43 20
55 1 0
45 0 0
3 0 0
39 0 0
978 0 0
69 0 0
36 0 0
16 0 0
45 0 0
21 0 0
102 4 0
195 4 0
205 0 2
102 4 0
61 0 470
2 0 0
6 0 0
67 0 487
0 0 1
1 0 0
3 0 0
8 0 0
1 0 0
3,115 0 1,689
261 0 0
4 0 0
230 0 0
5 0 0
4 0 0
4 0 0
6 0 0
3 0 0
1 0 0
58 0 0
386 0 8
Convertible Truncation Lossy
1 0 0
4 0 0
28 0 6
2,792 43 20
55 1 0
45 0 0
3 0 0
20 0 0
11 0 0
2 0 0
4 0 0
2 0 0
978 0 0
69 0 0
16 0 0
10 0 0
4 0 0
4 0 0
2 0 0
10 0 0
4 0 0
2 0 0
45 0 0
21 0 0
4 0 0
4 0 0
0 4 0
59 0 0
27 0 0
8 0 0
4 0 0
93 0 0
4 0 0
0 4 0
59 0 0
27 0 0
8 0 0
102 0 1
58 0 1
35 0 0
10 0 0
4 0 0
4 0 0
0 4 0
59 0 0
27 0 0
8 0 0
61 0 470
2 0 0
6 0 0
67 0 487
0 0 1
1 0 0
3 0 0
8 0 0
1 0 0
3,115 0 1,689
261 0 0
4 0 0
73 0 0
115 0 0
37 0 0
5 0 0
2 0 0
3 0 0
4 0 0
4 0 0
6 0 0
2 0 0
1 0 0
1 0 0
58 0 0
386 0 8
---------------- ---------------- ----------------

Unable to migrate WE8ISO8859P1 to ALUTF8 *Unrecognized convertible date*

Hi
..have followed all steps in migration guide
create CSMIG
take backup (used datapump)
run cs scan
stopped db
startup restrict
run csalter.plbthe script fails with error:
Unrecognized convertible date found in scanner result
database: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
scan output:
scan.err file:
Database Scan Individual Exception Report
[Database Scan Parameters]
Parameter Value
CSSCAN Version v2.1
Instance Name itempl
Database Version 10.2.0.1.0
Scan type Full database
Scan CHAR data? YES
Database character set WE8ISO8859P1
FROMCHAR WE8ISO8859P1
TOCHAR AL32UTF8
Scan NCHAR data? NO
Array fetch buffer size 10240
Number of processes 3
Capture convertible data? NO
[Data Dictionary individual exceptions]
[Application data individual exceptions]
scan.txt:
Database Scan Summary Report
Time Started : 2010-06-20 23:48:40
Time Completed: 2010-06-20 23:50:33
Process ID Time Started Time Completed
1 2010-06-20 23:48:41 2010-06-20 23:50:31
2 2010-06-20 23:48:41 2010-06-20 23:50:31
3 2010-06-20 23:48:43 2010-06-20 23:50:31
[Database Size]
Tablespace Used Free Total Expansion
SYSTEM 488.38M 21.63M 510.00M 984.00K
UNDOTBS1 20.94M 9.06M 30.00M .00K
SYSAUX 349.44M 10.56M 360.00M 9.52M
TEMP .00K .00K .00K .00K
USERS 22.69M 1.06M 23.75M 10.00K
EXAMPLE 68.25M 31.75M 100.00M 3.00K
Total 949.69M 74.06M 1,023.75M 10.50M
The size of the largest CLOB is 1625114 bytes
[Database Scan Parameters]
Parameter Value
CSSCAN Version v2.1
Instance Name itempl
Database Version 10.2.0.1.0
Scan type Full database
Scan CHAR data? YES
Database character set WE8ISO8859P1
FROMCHAR WE8ISO8859P1
TOCHAR AL32UTF8
Scan NCHAR data? NO
Array fetch buffer size 10240
Number of processes 3
Capture convertible data? NO
[Scan Summary]
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
[Data Dictionary Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 2,983,218 0 0 0
CHAR 1,097 0 0 0
LONG 149,525 0 0 0
CLOB 31,468 2,071 0 0
VARRAY 22,366 0 0 0
Total 3,187,674 2,071 0 0
Total in percentage 99.935% 0.065% 0.000% 0.000%
The data dictionary can be safely migrated using the CSALTER script
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 1,730,333 1,465 0 0
CHAR 59,586 0 0 0
LONG 0 0 0 0
CLOB 41 12 0 0
VARRAY 2,019 0 0 0
Total 1,791,979 1,477 0 0
Total in percentage 99.918% 0.082% 0.000% 0.000%
[Distribution of Convertible, Truncated and Lossy Data by Table]
USER.TABLE Convertible Truncation Lossy
ITEMPLDB.EMP 1 0 0
MDSYS.SDO_COORD_OP_PARAM_VALS 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE 1 0 0
MDSYS.SDO_STYLES_TABLE 78 0 0
MDSYS.SDO_XML_SCHEMAS 4 0 0
OE.WAREHOUSES 4 0 0
PM.PRINT_MEDIA 8 0 0
SYS.EXPIMP_TTS_CT$ 8 0 0
SYS.EXTERNAL_TAB$ 1 0 0
SYS.METASTYLESHEET 80 0 0
SYS.RULE$ 4 0 0
SYS.WRH$_SQLTEXT 607 0 0
SYS.WRH$_SQL_PLAN 532 0 0
SYS.WRI$_ADV_ACTIONS 22 0 0
SYS.WRI$_ADV_OBJECTS 418 0 0
SYS.WRI$_ADV_RATIONALE 7 0 0
SYS.WRI$_DBU_FEATURE_METADATA 90 0 0
SYS.WRI$_DBU_FEATURE_USAGE 2 0 0
SYS.WRI$_DBU_HWM_METADATA 17 0 0
SYSMAN.MGMT_HC_OS_COMPONENTS 8 0 0
SYSMAN.MGMT_HC_VENDOR_SW_COMPONENTS 8 0 0
[Distribution of Convertible, Truncated and Lossy Data by Column]
USER.TABLE|COLUMN Convertible Truncation Lossy
ITEMPLDB.EMP|ENAME 1 0 0
MDSYS.SDO_COORD_OP_PARAM_VALS|PARAM_VALUE_FILE 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE|XMLSCHEMA 1 0 0
MDSYS.SDO_STYLES_TABLE|DEFINITION 78 0 0
MDSYS.SDO_XML_SCHEMAS|XMLSCHEMA 4 0 0
OE.WAREHOUSES|SYS_NC00003$ 4 0 0
PM.PRINT_MEDIA|AD_FINALTEXT 4 0 0
PM.PRINT_MEDIA|AD_SOURCETEXT 4 0 0
SYS.EXPIMP_TTS_CT$|XMLINFO 8 0 0
SYS.EXTERNAL_TAB$|PARAM_CLOB 1 0 0
SYS.METASTYLESHEET|STYLESHEET 80 0 0
SYS.RULE$|CONDITION 4 0 0
SYS.WRH$_SQLTEXT|SQL_TEXT 607 0 0
SYS.WRH$_SQL_PLAN|OTHER_XML 532 0 0
SYS.WRI$_ADV_ACTIONS|ATTR5 11 0 0
SYS.WRI$_ADV_ACTIONS|ATTR6 11 0 0
SYS.WRI$_ADV_OBJECTS|ATTR4 418 0 0
SYS.WRI$_ADV_RATIONALE|ATTR5 7 0 0
SYS.WRI$_DBU_FEATURE_METADATA|INST_CHK_LOGIC 11 0 0
SYS.WRI$_DBU_FEATURE_METADATA|USG_DET_LOGIC 79 0 0
SYS.WRI$_DBU_FEATURE_USAGE|FEATURE_INFO 2 0 0
SYS.WRI$_DBU_HWM_METADATA|LOGIC 17 0 0
SYSMAN.MGMT_HC_OS_COMPONENTS|DESCRIPTION 8 0 0
SYSMAN.MGMT_HC_VENDOR_SW_COMPONENTS|DESCRIPTION 8 0 0
[Indexes to be Rebuilt]
USER.INDEX on USER.TABLE(COLUMN)
******* need help..

984437 wrote:
Hi Sergiusz,
I am also into a similar situation. CSALTER results into:
Pl post details of OS and database versions, along with the parameters passed to the csalter utility.
Checking data validity...
Unrecognized convertible data found in scanner result
PL/SQL procedure successfully completed.
Checking or Converting phase did not finish successfully
No database (national) character set will be altered
CSALTER finished unsuccessfully.
After this I tried altering the database character set:
SQL> ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8;
Database altered.
This command is undocumented/unsupported and should not be used - it will likely corrupt your database beyond repair - hopefully you have a good backup of the database that you can recover from.
https://forums.oracle.com/forums/search.jspa?threadID=&q=INTERNAL_USE&objID=f50&dateRange=all&userID=&numResults=15
>
Is this a correct way ?
I was able to convert the database character set but I still curious to know if it is the right way to do it.
Any suggestion would be a great help.
Thanks,Also, pl do not hijack an old post - pl post your issue in a new thread.
HTH
Srini

CSSCAN in 11g - Characterset not changing from WE8IMSWIN1252 to AL32UTF8

All,
We have installed a 11g database in Linux box and once after that we wanted to change the character set to AL32UTF8 from default WE8MSWIN1252.
We took the cs-alter approach and ran cs-scan utility, upon going through csscan.txt files generated by csscan utility we found that there are no lossy data but convertible data was found in data dictionary. Below is the output from csscan.txt
This is the Scan Summary
*[Scan Summary]*
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
Database Scan Summary Report
Time Started : 2012-10-17 21:42:17
Time Completed: 2012-10-17 21:42:47
Process ID         Time Started       Time Completed
         1 2012-10-17 21:42:18 2012-10-17 21:42:46
         2 2012-10-17 21:42:18 2012-10-17 21:42:46
         3 2012-10-17 21:42:18 2012-10-17 21:42:46
[Database Size]
Tablespace                           Used            Free           Total       Expansion
SYSTEM                            709.75M         256.00K         710.00M           2.42M
SYSAUX                            645.63M          34.38M         680.00M          12.52M
UNDOTBS1                           13.13M          16.88M          30.00M            .00K
TEMP                                 .00K            .00K            .00K            .00K
USERS                               1.31M           3.69M           5.00M            .00K
HYPE_DATA                       1,024.00K      19,999.00M      20,000.00M            .00K
HYPE_INDX                       1,024.00K      19,999.00M      20,000.00M            .00K
Total                           1,371.81M      40,053.19M      41,425.00M          14.94M
The size of the largest CLOB is 1625114 bytes
[Database Scan Parameters]
Parameter                      Value
CSSCAN Version                 v2.1
Instance Name                  dvhp081
Database Version               11.2.0.3.0
Scan type                      Full database
Scan CHAR data?                YES
Database character set         WE8MSWIN1252
FROMCHAR                       WE8MSWIN1252
TOCHAR                         al32utf8
Scan NCHAR data?               NO
Array fetch buffer size        10240
Number of processes            3
Capture convertible data?      NO
[Scan Summary]
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
[Data Dictionary Conversion Summary]
Data Dictionary Tables:
Datatype                    Changeless      Convertible       Truncation            Lossy
VARCHAR2                     5,408,302                0                0                0
CHAR                             4,261                0                0                0
LONG                           249,018                0                0                0
CLOB                            67,652            3,794                0                0
VARRAY                          49,807                0                0                0
Total                        5,779,040            3,794                0                0
Total in percentage             99.934%           0.066%           0.000%           0.000%
The data dictionary can be safely migrated using the CSALTER script
XML CSX Dictionary Tables:
Datatype                    Changeless      Convertible       Truncation            Lossy
VARCHAR2                           702                0                0                0
CHAR                                 0                0                0                0
LONG                                 0                0                0                0
CLOB                                 0                0                0                0
VARRAY                               0                0                0                0
Total                              702                0                0                0
Total in percentage            100.000%           0.000%           0.000%           0.000%
[Application Data Conversion Summary]
Datatype                    Changeless      Convertible       Truncation            Lossy
VARCHAR2                     2,550,581                0                0                0
CHAR                                 0                0                0                0
LONG                                 0                0                0                0
CLOB                            22,187            8,287                0                0
VARRAY                               0                0                0                0
Total                        2,572,768            8,287                0                0
Total in percentage             99.679%           0.321%           0.000%           0.000%
[Distribution of Convertible, Truncated and Lossy Data by Table]
Data Dictionary Tables:
USER.TABLE                                              Convertible       Truncation            Lossy
MDSYS.SDO_COORD_OP_PARAM_VALS                                   200                0                0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE                                    1                0                0
MDSYS.SDO_STYLES_TABLE                                           78                0                0
MDSYS.SDO_XML_SCHEMAS                                             5                0                0
SYS.METASTYLESHEET                                              179                0                0
SYS.RULE$                                                         1                0                0
SYS.SCHEDULER$_EVENT_LOG                                        356                0                0
SYS.WRH$_SQLTEXT                                                537                0                0
SYS.WRH$_SQL_PLAN                                               514                0                0
SYS.WRI$_ADV_DIRECTIVE_META                                       5                0                0
SYS.WRI$_ADV_OBJECTS                                             28                0                0
SYS.WRI$_ADV_SQLT_PLANS                                           2                0                0
SYS.WRI$_ADV_SQLT_PLAN_STATS                                      2                0                0
SYS.WRI$_DBU_FEATURE_METADATA                                   193                0                0
SYS.WRI$_DBU_FEATURE_USAGE                                        9                0                0
SYS.WRI$_DBU_HWM_METADATA                                        21                0                0
SYS.WRI$_REPT_FILES                                              27                0                0
SYSMAN.MGMT_IP_ELEM_DEFAULT_PARAMS                              130                0                0
SYSMAN.MGMT_IP_REPORT_ELEM_PARAMS                             1,475                0                0
SYSMAN.MGMT_IP_SQL_STATEMENTS                                    31                0                0
XML CSX Dictionary Tables:
USER.TABLE                                              Convertible       Truncation            Lossy
Application Data:
USER.TABLE                                              Convertible       Truncation            Lossy
APEX_030200.WWV_FLOW_BANNER                                      10                0                0
APEX_030200.WWV_FLOW_BUTTON_TEMPLATES                            12                0                0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS                          19                0                0
APEX_030200.WWV_FLOW_FLASH_CHART_SERIES                           5                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES                             298                0                0
APEX_030200.WWV_FLOW_PAGE_GENERIC_ATTR                           44                0                0
APEX_030200.WWV_FLOW_PAGE_PLUGS                               3,240                0                0
APEX_030200.WWV_FLOW_PAGE_PLUG_TEMPLATES                        254                0                0
APEX_030200.WWV_FLOW_PROCESSING                                  45                0                0
APEX_030200.WWV_FLOW_ROW_TEMPLATES                               66                0                0
APEX_030200.WWV_FLOW_SHORTCUTS                                   39                0                0
APEX_030200.WWV_FLOW_STEPS                                    1,795                0                0
APEX_030200.WWV_FLOW_STEP_PROCESSING                          2,238                0                0
APEX_030200.WWV_FLOW_TEMPLATES                                  192                0                0
APEX_030200.WWV_FLOW_WORKSHEETS                                  30                0                0
[Distribution of Convertible, Truncated and Lossy Data by Column]
Data Dictionary Tables:
USER.TABLE|COLUMN                                       Convertible       Truncation            Lossy
MDSYS.SDO_COORD_OP_PARAM_VALS|PARAM_VALUE_FILE                  200                0                0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE|XMLSCHEMA                          1                0                0
MDSYS.SDO_STYLES_TABLE|DEFINITION                                78                0                0
MDSYS.SDO_XML_SCHEMAS|XMLSCHEMA                                   5                0                0
SYS.METASTYLESHEET|STYLESHEET                                   179                0                0
SYS.RULE$|CONDITION                                               1                0                0
SYS.SCHEDULER$_EVENT_LOG|ADDITIONAL_INFO                        356                0                0
SYS.WRH$_SQLTEXT|SQL_TEXT                                       537                0                0
SYS.WRH$_SQL_PLAN|OTHER_XML                                     514                0                0
SYS.WRI$_ADV_DIRECTIVE_META|DATA                                  5                0                0
SYS.WRI$_ADV_OBJECTS|ATTR4                                       28                0                0
SYS.WRI$_ADV_SQLT_PLANS|OTHER_XML                                 2                0                0
SYS.WRI$_ADV_SQLT_PLAN_STATS|OTHER                                2                0                0
SYS.WRI$_DBU_FEATURE_METADATA|INST_CHK_LOGIC                     22                0                0
SYS.WRI$_DBU_FEATURE_METADATA|USG_DET_LOGIC                     171                0                0
SYS.WRI$_DBU_FEATURE_USAGE|FEATURE_INFO                           9                0                0
SYS.WRI$_DBU_HWM_METADATA|LOGIC                                  21                0                0
SYS.WRI$_REPT_FILES|SYS_NC00005$                                 27                0                0
SYSMAN.MGMT_IP_ELEM_DEFAULT_PARAMS|VALUE                        130                0                0
SYSMAN.MGMT_IP_REPORT_ELEM_PARAMS|VALUE                       1,475                0                0
SYSMAN.MGMT_IP_SQL_STATEMENTS|SQL_STATEMENT                      31                0                0
XML CSX Dictionary Tables:
USER.TABLE|COLUMN                                       Convertible       Truncation            Lossy
Application Data:
USER.TABLE|COLUMN                                       Convertible       Truncation            Lossy
APEX_030200.WWV_FLOW_BANNER|BANNER                               10                0                0
APEX_030200.WWV_FLOW_BUTTON_TEMPLATES|TEMPLATE                   12                0                0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS|AUTH_FUNC                 8                0                0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS|PAGE_SENT                10                0                0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS|POST_AUTH                 1                0                0
APEX_030200.WWV_FLOW_FLASH_CHART_SERIES|SERIES_QU                 5                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|ITEM_TEMPLATE                20                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|ITEM_TEMPLATE                20                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|LIST_TEMPLATE               105                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|LIST_TEMPLATE               105                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_LIST_ITEM                12                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_LIST_ITEM                12                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_TEMPLATE_                12                0                0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_TEMPLATE_                12                0                0
APEX_030200.WWV_FLOW_PAGE_GENERIC_ATTR|ATTRIBUTE_                44                0                0
APEX_030200.WWV_FLOW_PAGE_PLUGS|PLUG_SOURCE                   3,240                0                0
APEX_030200.WWV_FLOW_PAGE_PLUG_TEMPLATES|TEMPLATE               166                0                0
APEX_030200.WWV_FLOW_PAGE_PLUG_TEMPLATES|TEMPLATE                88                0                0
APEX_030200.WWV_FLOW_PROCESSING|PROCESS_SQL_CLOB                 45                0                0
APEX_030200.WWV_FLOW_ROW_TEMPLATES|ROW_TEMPLATE1                 54                0                0
APEX_030200.WWV_FLOW_ROW_TEMPLATES|ROW_TEMPLATE2                 10                0                0
APEX_030200.WWV_FLOW_ROW_TEMPLATES|ROW_TEMPLATE3                  2                0                0
APEX_030200.WWV_FLOW_SHORTCUTS|SHORTCUT                          39                0                0
APEX_030200.WWV_FLOW_STEPS|HELP_TEXT                          1,513                0                0
APEX_030200.WWV_FLOW_STEPS|HTML_PAGE_HEADER                     282                0                0
APEX_030200.WWV_FLOW_STEP_PROCESSING|PROCESS_SQL_             2,238                0                0
APEX_030200.WWV_FLOW_TEMPLATES|BOX                               64                0                0
APEX_030200.WWV_FLOW_TEMPLATES|FOOTER_TEMPLATE                   64                0                0
APEX_030200.WWV_FLOW_TEMPLATES|HEADER_TEMPLATE                   64                0                0
APEX_030200.WWV_FLOW_WORKSHEETS|SQL_QUERY                        30                0                0
[Indexes to be Rebuilt]
USER.INDEX on USER.TABLE(COLUMN)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00078$)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00079$)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00080$)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00081$)
APEX_030200.WWV_FLOW_WS_UNQ_ALIAS_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00082$)
APEX_030200.WWV_FLOW_WS_UNQ_ALIAS_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(ALIAS)
----------------------------------------------------------------------------------We followed few metalink documents *Solving Convertible or Lossy data in Data Dictionary objects reported by Csscan when changing the NLS_CHARACTERSET [ID 258904.1]* and found that we are good to go as convertible was found only in data dictionary and that too CLOB data. But while running csalter.plb csalter came out without changing the characterset. We ran the following query given the said document and it returned no rows which again confirms there is no problem and go ahead with running csalter.
SELECT DISTINCT z.owner_name
|| '.'
|| z.table_name
|| '('
|| z.column_name
|| ') - '
|| z.column_type
|| ' - '
|| z.error_type
|| ' ' NotHandledDataDictColumns
FROM csmig.csmv$errors z
WHERE z.owner_name IN
(SELECT DISTINCT username FROM csmig.csm$dictusers
) minus
SELECT DISTINCT z.owner_name
|| '.'
|| z.table_name
|| '('
|| z.column_name
|| ') - '
|| z.column_type
|| ' - '
|| z.error_type
|| ' ' DataDictConvCLob
FROM csmig.csmv$errors z
WHERE z.error_type ='CONVERTIBLE'
AND z.column_type = 'CLOB'
AND z.owner_name IN
(SELECT DISTINCT username FROM csmig.csm$dictusers
ORDER BY NotHandledDataDictColumns
/Sorry to have made the thread so big but to make sure and give a complete picture of the issue pasted the csscan contents. Request the PRO's to help us in this issue.

You have convertible data in the application tables. CLOB or not, such data prevents csalter.plb from changing the character set.
You are on 11.2.0.3, so use the DMU (http://www.oracle.com/technetwork/products/globalization/dmu/overview/index.html). It can cope with such data.
-- Sergiusz

VARBINARY problems in OBIEE 11g importing data from DB2 AS/400 V6R1

Hi all,
I have set up a connection between OBIEE 11g version 11.1.1.6.0 and DB2 AS/400 V6R1.
It is working fine for most of the data types, but we have the following cast sentence in a view:
CAST(
CASE WHEN A.RCATLY IN ( 1250 , 1000 ) THEN F.DESCRIPTION3 ELSE
CASE WHEN A.RCATLY=12 THEN 'AUM' ELSE
CASE WHEN F.KEYASL3='AL_EXCLUDED' THEN 'Other open items' ELSE
'AUM' END END END AS CHAR(50)) AS POS_CAT,
CAST(CASE WHEN F.DESCRIPTION3 IS NULL THEN 'Securities' ELSE F.DESCRIPTION3
END AS CHAR(50)) AS POS_DESCR
We are importing this view into OBIEE 11.1.1.6, the fileds POS_CAT and POS_DESCR are coming as BINARY, we also have tried to cast them to VARCHAR, they come as VARBINARY instead.
When we try to see the fields in a report we are getting the error below:
Error Codes: OAMP2OPY:Q4NU7XSN
Invalid Handle Of 'const saw::ExpressionBase*' Exception
I have tried to cast this fileds to VARCHAR in administration, no luck, error below:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 46035] Datatype(VARBINARY) nullable(1) unicode(1) external char(0) conversion to datatype(VARCHAR) nullable(1) unicode(0) external char(0) is not supported. (HY000)
SQL Issued: SELECT 0 s_0, "MI"."DWSPAIN01"."POS_CAT" s_1 FROM "MI" FETCH FIRST 65001 ROWS ONLY
Any suggestion?
Edited by: Ruben Alonso Ortega on 04-Mar-2013 07:23

Thanks for your quick response, I have tried to change it in the phisycal layer, to CHAR, VARCHAR, same error, it didn't work.

Problem in calling nested stored procedure

Hi,
I am using execute(), getMoreResults() and getResultSet() methods to call sybase stored proc. It is working fine when calling a simple stored proc. But it is giving following error when this stored proc calls another stored proc inside it.
<<
Error connecting: com.sybase.jdbc2.jdbc.SybSQLException: Implicit conversion from datatype 'INT' to 'CHAR' is not allowed. Use the CONVERT function to run this query
>>
It will be very helpful if somebody shares the experience of nested stored procs calls using JDBC.
-Subhendu

Vinay,
Thanks for replying...
Following is the excerpts from the parent procedure
create proc TEST_PARENT_sp
(@fundID char(5) = NULL)
as
begin
exec TEST_CHILD_sp @fundID
end
The code for CHILD proc is attached
create procedure TEST_CHILD_sp
(@fundID char(5) = NULL)
as
begin
insert #PV_funds_curr
(fundID,
curr_id,
curr_type,
tcurr_id,
in_xrate_id,
out_xrate_id,
display_seq)
select
pv.fund_id,
rl.curr_id,
rl.curr_type,
rl.curr_id,
null,
null,
pv.display_seq
from
#PV_funds pv,
RL_currencies rl,
#PV_currencies tmp_c
where
@fundID in (pv.fund_id, 'ALL') and
pv.fund_id = rl.fund_id and
tmp_c.curr_id in (rl.curr_id, 'ALL') and
tmp_c.curr_type in (rl.curr_type, 'ALL')
end
Regards,
Subhendu.
PS.- The Parent Stored proc works fine while calling from other applications,e.g., Rapid SQL, isql.

How to combine multiple MailAttachement-x payload to One -Help Please ?

Hi Friends ,
 In my scenario My Mail sender Adapter reading attachment . It works fine for 1 attachement but if more than one comes It is reading all attachements but it is converting the First attachement only to XML format , rest of files are left as it is.
 Can you please tell me how to combine all the Mailattachements and then covert into XML ?
 In our Mail Sender configurations , I am giving parameters for MessageTransFormBean like
 xml.documentName - MT_Row
 xml.documentNameSpace - http://com.test
 xml.fieldNames - Details
 xml.fieldSeparator - ' \n'
 xml.ProcessFieldNames - FromConfiguration
In PayLoadSwapBean
 i am giving propertieslike Content-Description , Content-Disposition , attachement;filename="MailAttchement-1.txt" and all other configuration i am giving.
 I am not clear as if will it WorkFor Multiple attachement ? I can understand as it wil work for Only one attachement . But if i can get multiple attachemnt 1 with proper XML conversion ( our DataType ) , rest of files are with out XML
conversion . How can i process those files also as XML converted ?
 Expecting your reply asap !
Regards .,
V.Rangarajan

> Can you please tell me how to combine all
> the Mailattachements and then covert into XML ?
This is not possible without a self-written adapter module.
Regards
Stefan

Report created results in Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P

Hi ,
I created a report and when I run I get the following error. Not sure where to concentrate in terms of the columns that I have selected. One column I suspected is reptno which return a number and so was cast with
cast(test.REPTNO as Varchar(20)) but not sure whether that is the true culprit. If anyone has any suggestion or anything that would help me over this situation will be of great help.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 46035] Datatype(VARCHAR) nullable(1) unicode(1) external char(0) conversion to datatype(VARBINARY) nullable(0) unicode(0) external char(0) is not supported. (HY000)
SQL Issued: SELECT test.PROGRAMMER saw_0, case WHEN test.PRODUCT_ID = '1162' then 'BPEL' WHEN test.PRODUCT_ID = '1669' then 'BPEL' else test.GROUP_NAME end saw_1, test.CLOSED_DATE saw_2, test.TEST_NAME saw_3, test.TEST_STATUS saw_4, CAST(test.REPTNO AS VARCHAR(20)) saw_5, test.SUBJECT saw_6, test.CUSTOMER saw_7 FROM DDR WHERE (test.OWNER_TYPE = 'DDR') AND (test.STATUS IN (80, 75)) AND (test.CLOSED_DATE > timestamp '2009-01-01 00:00:00') AND (test.CS_PRIORITY < 3) AND (test.GENERIC_OR_PORT_SPECIFIC IN ('G', 'P')) AND (test.PRODUCT_ID IN (1162, 1669, 1876, 1652, 355, 1318, 1978, 2025, 1771, 1773, 1980)) AND (test.GROUP_NAME <> 'Others') AND ((test.TEST_NAME IS NULL) OR ((test.TEST_NAME NOT LIKE 'AUTO%' AND test.TEST_NAME NOT LIKE '%MANUAL%' AND test.TEST_NAME NOT LIKE '%FEASIBLE%'))) AND (test.TEST_STATUS IS NULL) ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Thanks,
-vinod

Clearly the error is due to data type. You should get similar error if you run the SQL directly on your database.
Also, looks like you are missing operator in the following clause.
AND (test.GROUP_NAME 'Others')
hth,
Prakash

Using NVL for date

I am creating a view and one of the columns is this:
(b.startdate || ' To ' || b.enddate) salesDateRange
however when I was trying to handle the null value of date, I found the following problems,
case 1
(nvl(b.startdate, 'NA') || ' To ' || b.enddate) salesDateRange
when i use nvl, I am able to create the view, but when I retrieve the data, I get this error msg.
ORA-01858: a non-numeric character was found where a numeric was expected
01858. 00000 - "a non-numeric character was found where a numeric was expected"
*Cause: The input data to be converted using a date format model was
incorrect. The input data did not contain a number where a number was
required by the format model.
*Action: Fix the input data or the date format model to make sure the
elements match in number and type. Then retry the operation.
is nvl only available for numerical value?

user8944947 wrote:
I am creating a view and one of the columns is this:
(b.startdate || ' To ' || b.enddate) salesDateRange
however when I was trying to handle the null value of date, I found the following problems,
case 1
(nvl(b.startdate, 'NA') || ' To ' || b.enddate) salesDateRange
when i use nvl, I am able to create the view, but when I retrieve the data, I get this error msg.
ORA-01858: a non-numeric character was found where a numeric was expected
01858. 00000 - "a non-numeric character was found where a numeric was expected"
*Cause: The input data to be converted using a date format model was
incorrect. The input data did not contain a number where a number was
required by the format model.
*Action: Fix the input data or the date format model to make sure the
elements match in number and type. Then retry the operation.
is nvl only available for numerical value?In addition to the answers already given, you have to consider that NVL is an overloaded function, designed to deal with different datatypes. It accepts 2 arguments and the version of NVL that is used depends on the arguments given (that's the nature of overloading - look it up on the internet if you're not sure).
So, there is defined e.g.
NVL({noformat}<number arg>, <number arg>{noformat})
NVL({noformat}<varchar2 arg>, <varchar2 arg>{noformat})
NVL({noformat}<date arg>, <date arg>{noformat})
etc.In your example, as the first argument you are passing in is a date, Oracle is opting to use:
NVL({noformat}<date arg>, <date arg>{noformat})But your second argument is not a date, it's a varchar2.
However, Oracle is clever and can perform "implicit" conversions between datatypes i.e. it will try and convert datatypes without you actually telling it to. (It's generally good coding practice to do it yourself though).
So, in you case Oracle is taking your varchar2 string "NA" and trying to implicitly convert this to a date, using the only way it knows how, which is to apply a date format mask as defined by the NLS_DATE_FORMAT parameter for the session. For example, internally it will be trying to do the equivalent of:
TO_DATE('NA','DD-MON-YYYY')(assuming your NLS_DATE_FORMAT parameter is set to DD-MON-YYYY)
If we try that ourselves, we get...
SQL> select to_date('NA','DD-MON-YYYY') from dual;
select to_date('NA','DD-MON-YYYY') from dual
ERROR at line 1:
ORA-01858: a non-numeric character was found where a numeric was expected... which is the same error you were getting.
So, in order for your NVL to work you would either need to supply a DATE as the second argument (some default date to use if the first argument is null), or some varchar2 string that represents a date in the correct format as per your NLS_DATE_FORMAT setting (dangerous because if the NLS_ setting changes then your code can suddently error), or you provide the first argument as a VARCHAR2 string instead of a date (using TO_CHAR), so the the function overloading causes Oracle to choose the varchar2 argument version of NVL, for which 'NA' is a perfectly valid second argument.

Can both in-row and off-row LOBs be used in a where clause?

We are preparing to upgrade ASE from version 15.5 to 16.0. One of the features that is very appealing has to do with the changes made concerning the handling of LOBs. In particular, the ability to use a LOB column in search arguments (where clause) is something our developers have longed for since the retirement of the full-text search option. So, in version 16.0, can any column with a datatype of text be used as a search argument? Are there any restrictions.
Thanks in advance.

Hi Kevin,
The in-row LOB feature is mainly designed to save space when a text column has many short values, which is a particularly bad problem when the server uses a large page size (like 16K) as ASE would use a full 16K to store even a single bye "Y". I don't think the feature made any change in how text can be used in search arguments. i.e. you can still use LIKE and IS [NOT] NULL, but not others.
Example:
1> create table t (x text in row (8))
2> go
1> insert t values ("abc")
2> insert t values ("abcdefghijkl")
3> go
(2 rows affected)
1> select * from t where x like "%c%"
2> go
x
abc
abcdefghijkl
(2 rows affected)
1> select * from t where x !> "c"
2> go
Msg 257, Level 16, State 1:
Server 'redhead', Line 1:
Implicit conversion from datatype 'TEXT' to 'VARCHAR' is not allowed. Use the
CONVERT function to run this query.
Msg 306, Level 16, State 5:
Server 'redhead', Line 1:
TEXT, IMAGE and UNITEXT datatypes may not be used in a WHERE clause, except with
the LIKE expression and IS [NOT] NULL predicate on columns.

Conversion of datatypes

Similar Messages

Maybe you are looking for