ORA-12712 error while changing nls character set to AL32UTF8

Hi,
It is strongly recommend to use database character set AL32UTF8 when ever a database is going to used with our XML capabilities. The database character set in the installed DB is WE8MSWIN1252. For making use of XML DB features, I need to change it to AL32UTF8. But, when I try doing this, I'm getting ORA-12712: new character set must be a superset of old character set. Is there a way to solve this issue?
Thanks in advance,
Divya.

Hi,
a change from we8mswin1252 to al32utf8 is not directly possible. This is because al32utf is not a binary superset of we8mswin1252.
There are 2 options:
- use full export and import
- Use of the Alter in a sort of restricted way
The method you can choose depends on the characters in the database, is it only ASCII then the second one can work, in other cases the first one is needed.
It is all described in the Support Note 260192.1, "Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)". Get it from the support/metalink site.
You can also read the chapters about this issue in the Globalization Guide: [url http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430]Change characterset.
Herald ten Dam
http://htendam.wordpress.com

Similar Messages

Getting ORA-01429 error while changing character set

When I am changing character set from WE8DEC to AL32UTF8, I am getting ORA-01429 error
SQL> ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8 ;
ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces

Chockalingam wrote:
I am using above steps as per oracle doc only.
http://docs.oracle.com/cd/B10500_01/server.920/a96529/ch10.htm
No, you are not.
- You are not using the correct version doc vs. Oracle server version. Try to find the same suggestion in the relevant doc.
- The doc you reference specifically says "... it can be used only under special circumstances. The ALTER DATABASE CHARACTER SET statement does not perform any data conversion, so it can be used +if and only if the new character set is a strict superset of the current character set+." (emphasis is mine)
You do not have a strict superset.
- Also the special clauses you have used are not documented - for a reason.
Please edit your posts above to remove the ill-advice (steps with internal use only clauses) that does not belong on a forum.
Edited by: orafad on Mar 16, 2012 9:47 PM

How to change the Character Set from AL32UTF8 to WE8DEC

Hello!!
I want to know how to change the character set in the database from AL32UTF8 to WE8DEC.
I tried to use the comand ALTER DATABASE CHARACTER SET but I got an error because WE8DEC is not a superset of AL32UTF8.
I need to import tables from a server that uses WE8DEC. So when I do the import to my server, wich has AL32UTF8 , I can't import the rows that include an Ñ.
So I want to change the caracter set to WE8DEC. How can I do it?
Is it needed to change the language configuration? The remote server has AMERICAN_AMERICA, and my server has MEXICAN SPANISH_MEXICO (both uses text in spanish).
Thanks a lot!!

When you export from WE8DEC server what did you use
for NLS_LANG char set? And when importing?
The export was done in another computer because I can't do the export in the server (I have 10g, and the remote server has 9i and the export is not working). In my server, when I tried to do the import, the NS_LANG value was MEXICAN SPANISH_MEXICO.WE8MSWIN1252.
When I try to import to my database I got the error:
import done in WE8DEC character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses WE8MSWIN1252 character set (possible charset conversion)
. importing USRMCR06's objects into PRIMARIZACION
. . importing table "CHG_FONDOS_MARZO_CD_MOR"
IMP-00019: row rejected due to ORACLE error 12899
IMP-00003: ORACLE error 12899 encountered
ORA-12899: value too large for column "PRIMARIZACION"."CHG_FONDOS_MARZO_CD_MOR".
"NOMBRE" (actual: 41, maximum: 40)
Column 1 16623436
Column 2
Column 3 Pymes_1
Column 4

NLS character set non AL32UTF8 versus AL32UTF8

Good morning Gurus,
RCU utility strongly recommends to have this parameter set to AL32UTF8.
My database by default was set as WE8MSWIN1252.
I have read a lot about these settings. and like to have exact steps to take to accomplish this. I posted this problem in "Problem with RCU utility' but did not get any response.
My question is why oracle makes things difficult. I only use american language, if both are good for that then why do RCU requires to change it.
I have seen people who have ignored this message had trouble down the road of installation process.
I appreciate if some one can explain to me the implications of not changing versus changing.
Is that means, my database has to be kept with AL32UTF8 parameter all the time after installation is done?
Also another question
I have 3 meg RAM on my laptop, Oracle requires 4, will this cause the problem during installation?
Thank you
j

Hi,
a change from we8mswin1252 to al32utf8 is not directly possible. This is because al32utf is not a binary superset of we8mswin1252.
There are 2 options:
- use full export and import
- Use of the Alter in a sort of restricted way
The method you can choose depends on the characters in the database, is it only ASCII then the second one can work, in other cases the first one is needed.
It is all described in the Support Note 260192.1, "Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)". Get it from the support/metalink site.
You can also read the chapters about this issue in the Globalization Guide: [url http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430]Change characterset.
Herald ten Dam
http://htendam.wordpress.com

Changing database character set from US7ASCII to AL32UTF8

Our database is running on Oracle database 10.1.0.4.0 (AIX) The following are its parameters:
SQL> select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';
VALUE
US7ASCII
We would like to change the database character set to AL32UTF8. After following Metalink notes: 260192.1 (which helped us resolve "Lossy" and "Truncated" data, the final output of the CSSCAN utility is:
[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]
The data dictionary can be safely migrated using the CSALTER script
We have no (0) Truncation and Lossy entries on the .txt file. We only have Changeless and Convertible. Now accdg to the documentation, we can do a FULL EXP and FULL IMP. But it did not detail how to do the conversion on the same database. The discussion on the document tells how to do it from one database to another database. But how about on the same database?
We cannot use CSALTER as stated on the document.
(Step 6
Step 12
12.c) When using Csalter/Alter database to go to AL32UTF8 and there was NO "Truncation" data, only "Convertible" and "Changeless" in the csscan done in point 4:)
After performing a FULL export of the database, how can we change its character set? What do we need to do the the existing database to change its character set to AL32UTF8 before we import back our dump file into the same database?
Please help.

There you are! Thanks! Seems like I am right in my understanding about the Oracle Official Documentation. Thanks!
Hmmmmm...when you say:
*"you can do selective export of only convertible tables, truncate the tables, use CSALTER, and re-import."*
This means that:
1. After running csscan on database PROD, i will take note of the convertible tables in the .txt output file.
2. Perform selective EXPORT on PROD (EXP the convertible tables)
3. Truncate the convertible tables on PROD database
4. Use CSALTER on PROD database
5. Re-import the tables into PROD database
6. Housekeeping.
Will you tell me if these steps are the correct one? Based on our scenario: This is what i have understood referring to the Official Doc.
Am i correct?
I really appreciate your help Sergiusz.

ORA-12709: error while loading create database character set after upgrade

Dear All
i m getting ORA-12709: error while loading create database character set, After upgraded the database from 10.2.0.3 to 11.2.0.3 in ebusiness suit env.
current application version 12.0.6
please help me to resolve it.
SQL> startup;
ORACLE instance started.
Total System Global Area 1.2831E+10 bytes
Fixed Size 2171296 bytes
Variable Size 2650807904 bytes
Database Buffers 1.0133E+10 bytes
Redo Buffers 44785664 bytes
ORA-12709: error while loading create database character set
-bash-3.00$ echo $ORA_NLS10
/u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
export ORACLE_BASE=/u01/oracle
export ORACLE_HOME=/u01/oracle/PROD/db/tech_st/11.2.0
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH
export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/site_perl/5.10.0
export ORA_NLS10=/u01/oracle/PROD/db/teche_st/11.2.0/nls/data/9idata
export ORACLE_SID=PROD
-bash-3.00$ pwd
/u01/oracle/PROD/db/tech_st/11.2.0/nls/data/9idata
-bash-3.00$ ls -lh |more
total 56912
-rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx00001.nlb
-rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00002.nlb
-rw-r--r-- 1 oracle oinstall 959 Jan 15 16:05 lx00003.nlb
-rw-r--r-- 1 oracle oinstall 984 Jan 15 16:05 lx00004.nlb
-rw-r--r-- 1 oracle oinstall 968 Jan 15 16:05 lx00005.nlb
-rw-r--r-- 1 oracle oinstall 962 Jan 15 16:05 lx00006.nlb
-rw-r--r-- 1 oracle oinstall 960 Jan 15 16:05 lx00007.nlb
-rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00008.nlb
-rw-r--r-- 1 oracle oinstall 940 Jan 15 16:05 lx00009.nlb
-rw-r--r-- 1 oracle oinstall 939 Jan 15 16:05 lx0000a.nlb
-rw-r--r-- 1 oracle oinstall 1006 Jan 15 16:05 lx0000b.nlb
-rw-r--r-- 1 oracle oinstall 1008 Jan 15 16:05 lx0000c.nlb
-rw-r--r-- 1 oracle oinstall 998 Jan 15 16:05 lx0000d.nlb
-rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx0000e.nlb
-rw-r--r-- 1 oracle oinstall 926 Jan 15 16:05 lx0000f.nlb
-rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00010.nlb
-rw-r--r-- 1 oracle oinstall 958 Jan 15 16:05 lx00011.nlb
-rw-r--r-- 1 oracle oinstall 956 Jan 15 16:05 lx00012.nlb
-rw-r--r-- 1 oracle oinstall 1005 Jan 15 16:05 lx00013.nlb
-rw-r--r-- 1 oracle oinstall 970 Jan 15 16:05 lx00014.nlb
-rw-r--r-- 1 oracle oinstall 950 Jan 15 16:05 lx00015.nlb
-rw-r--r-- 1 oracle oinstall 1.0K Jan 15 16:05 lx00016.nlb
-rw-r--r-- 1 oracle oinstall 957 Jan 15 16:05 lx00017.nlb
-rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00018.nlb
-rw-r--r-- 1 oracle oinstall 932 Jan 15 16:05 lx00019.nlb
-rw-r--r-- 1 oracle oinstall 951 Jan 15 16:05 lx0001a.nlb
-rw-r--r-- 1 oracle oinstall 944 Jan 15 16:05 lx0001b.nlb
-rw-r--r-- 1 oracle oinstall 953 Jan 15 16:05 lx0001c.nlb
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/oracle/PROD/db/tech_st/11.2.0
System name: SunOS
Node name: proddb3.zakathouse.org
Release: 5.10
Version: Generic_147440-19
Machine: sun4u
Using parameter settings in server-side spfile /u01/oracle/PROD/db/tech_st/11.2.0/dbs/spfilePROD.ora
System parameters with non-default values:
processes = 200
sessions = 400
timed_statistics = TRUE
event = ""
shared_pool_size = 416M
shared_pool_reserved_size= 40M
nls_language = "american"
nls_territory = "america"
nls_sort = "binary"
nls_date_format = "DD-MON-RR"
nls_numeric_characters = ".,"
nls_comp = "binary"
nls_length_semantics = "BYTE"
memory_target = 11G
memory_max_target = 12G
control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl01.dbf"
control_files = "/u01/oracle/PROD/db/tech_st/10.2.0/dbs/cntrl02.dbf"
control_files = "/u01/oracle/PROD/db/apps_st/data/cntrl03.dbf"
db_block_checksum = "TRUE"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_dest_1 = "LOCATION=/u01/oracle/PROD/db/apps_st/data/archive"
log_archive_format = "%t_%s_%r.dbf"
log_buffer = 14278656
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1200
db_files = 512
db_file_multiblock_read_count= 8
db_recovery_file_dest = "/u01/oracle/fast_recovery_area"
db_recovery_file_dest_size= 14726M
log_checkpoints_to_alert = TRUE
dml_locks = 10000
undo_management = "AUTO"
undo_tablespace = "APPS_UNDOTS1"
db_block_checking = "FALSE"
session_cached_cursors = 500
utl_file_dir = "/usr/tmp"
utl_file_dir = "/usr/tmp"
utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound"
utl_file_dir = "/u01/oracle/PROD/db/tech_st/10.2.0/appsutil/outbound/PROD_proddb3"
utl_file_dir = "/usr/tmp"
plsql_code_type = "INTERPRETED"
plsql_optimize_level = 2
job_queue_processes = 2
cursor_sharing = "EXACT"
parallel_min_servers = 0
parallel_max_servers = 8
core_dump_dest = "/u01/oracle/PROD/db/tech_st/10.2.0/admin/PROD_proddb3/cdump"
audit_file_dest = "/u01/oracle/admin/PROD/adump"
db_name = "PROD"
open_cursors = 600
pga_aggregate_target = 1G
workarea_size_policy = "AUTO"
optimizer_secure_view_merging= FALSE
aq_tm_processes = 1
olap_page_pool_size = 4M
diagnostic_dest = "/u01/oracle"
max_dump_file_size = "20480"
Tue Jan 15 16:16:02 2013
PMON started with pid=2, OS id=18608
Tue Jan 15 16:16:02 2013
PSP0 started with pid=3, OS id=18610
Tue Jan 15 16:16:03 2013
VKTM started with pid=4, OS id=18612 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Tue Jan 15 16:16:03 2013
GEN0 started with pid=5, OS id=18616
Tue Jan 15 16:16:03 2013
DIAG started with pid=6, OS id=18618
Tue Jan 15 16:16:03 2013
DBRM started with pid=7, OS id=18620
Tue Jan 15 16:16:03 2013
DIA0 started with pid=8, OS id=18622
Tue Jan 15 16:16:03 2013
MMAN started with pid=9, OS id=18624
Tue Jan 15 16:16:03 2013
DBW0 started with pid=10, OS id=18626
Tue Jan 15 16:16:03 2013
LGWR started with pid=11, OS id=18628
Tue Jan 15 16:16:03 2013
CKPT started with pid=12, OS id=18630
Tue Jan 15 16:16:03 2013
SMON started with pid=13, OS id=18632
Tue Jan 15 16:16:04 2013
RECO started with pid=14, OS id=18634
Tue Jan 15 16:16:04 2013
MMON started with pid=15, OS id=18636
Tue Jan 15 16:16:04 2013
MMNL started with pid=16, OS id=18638
DISM started, OS id=18640
ORACLE_BASE from environment = /u01/oracle
Tue Jan 15 16:16:08 2013
ALTER DATABASE MOUNT
ORA-12709 signalled during: ALTER DATABASE MOUNT...

ORA-12709 signalled during: ALTER DATABASE MOUNT...Do you have any trace files generated at the time you get this error?
Please see these docs.
ORA-12709: WHILE STARTING THE DATABASE [ID 1076156.6]
Upgrading from 9i to 10gR2 Fails With ORA-12709 : Error While Loading Create Database Character Set [ID 732861.1]
Ora-12709 While Trying To Start The Database [ID 311035.1]
ORA-12709 when Mounting the Database [ID 160478.1]
How to Move From One Database Character Set to Another at the Database Level [ID 1059300.6]
Thanks,
Hussein

ORA-12709: error while loading create database character set

I installed Oracle 8.05 on Linux successfully: was able to login
whith SQLPlus, start and stop the db whith svrmgrl etc.
During this install I chose WE8ISO8859P9 as the database
characterset when prompted.
After that I installed Oracle Application Server 3.02, and now
I'm getting the
ORA-12709: error while loading create database character set
message when I try to start up the database, and the database
won't mount.
Platform is RedHat Linux 5.2.
NLS_LANG set to different settings,
e.g. AMERICAN_AMERICA.WE8ISO8859P9
but without success.
Anyone any clue?
Thanks!
null

Jogchum Reitsma (guest) wrote:
: I installed Oracle 8.05 on Linux successfully: was able to
login
: whith SQLPlus, start and stop the db whith svrmgrl etc.
: During this install I chose WE8ISO8859P9 as the database
: characterset when prompted.
: After that I installed Oracle Application Server 3.02, and now
: I'm getting the
: ORA-12709: error while loading create database character set
: message when I try to start up the database, and the database
: won't mount.
: Platform is RedHat Linux 5.2.
: NLS_LANG set to different settings,
: e.g. AMERICAN_AMERICA.WE8ISO8859P9
: but without success.
: Anyone any clue?
: Thanks!
You can create the database with WE8DEC character set
and to use the WE8ISO8859P9 on the client or even on Linux.
The NLS_LANG setting doesn't effect the database, but the
interface with the database. The same setting can be used in de
windows 95/98/NT registry.
null

Change existing character set

Hi All,
I want to change current character set of my DB.
My DB version is 8.1.7 and character set is US7ASCII.
This character set does not support to store Euro symbol (â¬). So I want to change to another charset.
Currently I also have another DB, version 9.2.0 and charset is AL32UTF8 and National charset is AL16UTF16. This charset supports â¬ symbol.
But when I tried change chatset of 8i US7ASCII to AL32UTF8, an error happened: "ORA-12712 new character set must be a supersetof old character set".
Character set WE8ISO8859P1 support â¬ symbol.
I tried to change character set of 8i from US7ASCII to WE8ISO8859P1 successfully but change character set of 9i from AL32UTF8 to WE8ISO8859P1 unsuccessfully, error is "ORA-12712 new character set must be a supersetof old character set".
Please let me know which character set is superset of US7ASCII and AL32UTF8.
I want to change character set of 8i and 9i to the same another character set that support â¬ symbol.
Thanks in advanced,
Thi Nguyen

This is from Oracle metalink documentation.Hope this helps:
=========================================
This note defines character set combinations which are valid for the 'ALTER DATABASE CHARACTER SET xxxx;' command. A superset, in this context, is a character set where every character in the subset character set is defined and is defined at the same code point. Changing the Database Character Set or the Database National Character Set . If the change you want to do (change from <current> -> <new> characterset) is not listed here, then you need to use Export/Import. Export/Import and NLS Considerations for more info. SCOPE & APPLICATION ------------------- This note is relevant to anyone wishing to change the database character set or the database national character set. Note : this note is relevant from 8.1.6 to 9.2.0. Changing Database Character set - valid superset definitions ------------------------------------------------------------ Where the current character set does not have a corresponding match in the new character set column, it is not possible to change the definition by the above command alone; export / import into a new database with the new character set (not in the following list) will be required. 8.1.6 Subset/Superset Pairs =========================== A. Current Char set B. New Char set (Superset of A.) ------------------- -------------------------------- US7ASCII WE8DEC US7ASCII US8PC437 US7ASCII WE8PC850 US7ASCII IN8ISCII US7ASCII WE8PC858 US7ASCII WE8ISO8859P1 US7ASCII EE8ISO8859P2 US7ASCII SE8ISO8859P3 US7ASCII NEE8ISO8859P4 US7ASCII CL8ISO8859P5 US7ASCII AR8ISO8859P6 US7ASCII EL8ISO8859P7 US7ASCII IW8ISO8859P8 US7ASCII WE8ISO8859P9 US7ASCII NE8ISO8859P10 US7ASCII TH8TISASCII US7ASCII BN8BSCII US7ASCII VN8VN3 US7ASCII VN8MSWIN1258 US7ASCII WE8ISO8859P15 US7ASCII WE8NEXTSTEP US7ASCII AR8ASMO708PLUS US7ASCII EL8DEC US7ASCII TR8DEC US7ASCII LA8PASSPORT US7ASCII BG8PC437S US7ASCII EE8PC852 US7ASCII RU8PC866 US7ASCII RU8BESTA US7ASCII IW8PC1507 US7ASCII RU8PC855 US7ASCII TR8PC857 US7ASCII CL8MACCYRILLICS US7ASCII WE8PC860 US7ASCII IS8PC861 US7ASCII EE8MACCES US7ASCII EE8MACCROATIANS US7ASCII TR8MACTURKISHS US7ASCII EL8MACGREEKS US7ASCII IW8MACHEBREWS US7ASCII EE8MSWIN1250 US7ASCII CL8MSWIN1251 US7ASCII ET8MSWIN923 US7ASCII BG8MSWIN US7ASCII EL8MSWIN1253 US7ASCII IW8MSWIN1255 US7ASCII LT8MSWIN921 US7ASCII TR8MSWIN1254 US7ASCII WE8MSWIN1252 US7ASCII BLT8MSWIN1257 US7ASCII N8PC865 US7ASCII BLT8CP921 US7ASCII LV8PC1117 US7ASCII LV8PC8LR US7ASCII LV8RST104090 US7ASCII CL8KOI8R US7ASCII BLT8PC775 US7ASCII WE8DG US7ASCII WE8NCR4970 US7ASCII WE8ROMAN8 US7ASCII WE8MACROMAN8S US7ASCII TH8MACTHAIS US7ASCII HU8CWI2 US7ASCII EL8PC437S US7ASCII LT8PC772 US7ASCII LT8PC774 US7ASCII EL8PC869 US7ASCII EL8PC851 US7ASCII CDN8PC863 US7ASCII HU8ABMOD US7ASCII AR8ASMO8X US7ASCII AR8NAFITHA711T US7ASCII AR8SAKHR707T US7ASCII AR8MUSSAD768T US7ASCII AR8ADOS710T US7ASCII AR8ADOS720T US7ASCII AR8APTEC715T US7ASCII AR8NAFITHA721T US7ASCII AR8HPARABIC8T US7ASCII AR8NAFITHA711 US7ASCII AR8SAKHR707 US7ASCII AR8MUSSAD768 US7ASCII AR8ADOS710 US7ASCII AR8ADOS720 US7ASCII AR8APTEC715 US7ASCII AR8MSAWIN US7ASCII AR8NAFITHA721 US7ASCII AR8SAKHR706 US7ASCII AR8ARABICMACS US7ASCII LA8ISO6937 US7ASCII JA16VMS US7ASCII JA16EUC US7ASCII JA16SJIS US7ASCII KO16KSC5601 US7ASCII KO16KSCCS US7ASCII KO16MSWIN949 US7ASCII ZHS16CGB231280 US7ASCII ZHS16GBK US7ASCII ZHT32EUC US7ASCII ZHT32SOPS US7ASCII ZHT16DBT US7ASCII ZHT32TRIS US7ASCII ZHT16BIG5 US7ASCII ZHT16CCDC US7ASCII ZHT16MSWIN950 US7ASCII AL24UTFFSS US7ASCII UTF8 US7ASCII JA16TSTSET2 US7ASCII JA16TSTSET 8.1.7 Additions =============== US7ASCII ZHT16HKSCS US7ASCII KO16TSTSET WE8DEC TR8DEC WE8DEC WE8NCR4970 WE8PC850 WE8PC858 D7DEC D7SIEMENS9780X I7DEC I7SIEMENS9780X WE8ISO8859P1 WE8MSWIN1252 AR8ISO8859P6 AR8ASMO708PLUS AR8ISO8859P6 AR8ASMO8X IW8EBCDIC424 IW8EBCDIC1086 IW8EBCDIC1086 IW8EBCDIC424 LV8PC8LR LV8RST104090 DK7SIEMENS9780X N7SIEMENS9780X N7SIEMENS9780X DK7SIEMENS9780X I7SIEMENS9780X I7DEC D7SIEMENS9780X D7DEC WE8NCR4970 WE8DEC WE8NCR4970 TR8DEC AR8SAKHR707T AR8SAKHR707 AR8MUSSAD768T AR8MUSSAD768 AR8ADOS720T AR8ADOS720 AR8NAFITHA711 AR8NAFITHA711T AR8SAKHR707 AR8SAKHR707T AR8MUSSAD768 AR8MUSSAD768T AR8ADOS710 AR8ADOS710T AR8ADOS720 AR8ADOS720T AR8APTEC715 AR8APTEC715T AR8NAFITHA721 AR8NAFITHA721T AR8ARABICMAC AR8ARABICMACT AR8ARABICMACT AR8ARABICMAC KO16KSC5601 KO16MSWIN949 WE16DECTST2 WE16DECTST WE16DECTST WE16DECTST2 9.0.1 Additions =============== US7ASCII BLT8ISO8859P13 US7ASCII CEL8ISO8859P14 US7ASCII CL8ISOIR111 US7ASCII CL8KOI8U US7ASCII AL32UTF8 BLT8CP921 BLT8ISO8859P13 US7ASCII AR8MSWIN1256 UTF8 AL32UTF8 (added in patchset 9.0.1.2) Character Set Subset/Superset Pairs Obsolete from 9.0.1 ======================================================= US7ASCII AR8MSAWIN AR8ARABICMAC AR8ARABICMACT 9.2.0 Additions =============== US7ASCII JA16EUCTILDE US7ASCII JA16SJISTILDE US7ASCII ZHS32GB18030 US7ASCII ZHT32EUCTST WE8ISO8859P9 TR8MSWIN1254 LT8MSWIN921 BLT8ISO8859P13 LT8MSWIN921 BLT8CP921 BLT8CP921 LT8MSWIN921 AR8ARABICMAC AR8ARABICMACT ZHT32EUC ZHT32EUCTST UTF8 AL32UTF8 Character Set Subset/Superset Pairs Obsolete from 9.2.0 ======================================================= LV8PC8LR LV8RST104090

NLS CHARACTER SET 변경 방법 (ORACLE 7)

제품 : ORACLE SERVER
작성날짜 : 2004-11-09
NLS CHARACTER SET 변경 방법 (ORACLE 7)
======================================
PURPOSE
이 자료는 Oracle RDBMS SERVER에서 NLS CHARACTER SET 변경 방법에 대한
내용을 소개한다.
[ ORACLE 7 에서만 가능 ]
데이타베이스의 CHARACTER SET은 데이타 딕셔너리 테이블인 sys.props$에
들어 있다.
SQL>desc sys.props$
Name Null? Type
NAME NOT NULL VARCHAR2(30)
VALUE$ VARCHAR2(2000)
COMMENT$ VARCHAR2(2000)
SQL>column c1 format a30
SQL>select name c1, value$ c1 from sys.props$;
C1 C1
DICT.BASE 2
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_DATE_FORMAT DD-MON-YY
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET US7ASCII
NLS_SORT BINARY
GLOBAL_DB_NAME NLSV7.WORLD
여기서 NLS_CHARACTERSET에 현재 DB의 CHARACTER SET이 들어 있는데
이 값을 변경하여 DB의 CHARACTER SET을 변경할 수 있다.
여기서는 US7ASCII에서 KO16KSC5601로 옮기는 경우를 알아보자.
우선 바꾸고자 하는 CHRACTER SET이 지원되는 지를 다음 명령으로
확인한다.
select convert('a','KO16KSC5601','US7ASCII') from dual;
만약 이 Select 문에서 ORA-01482 에러가 발생하면 지정한 CHARACTER
SET이 지원되지 않는 경우이며 에러가 발생하지 않으면 CHARACTER
SET을 변경할 수 있다.
작업을 하기 전에는 만약을 위해서 DB 전체를 백업 받아두도록 한다.
CHARACTER SET 을 잘못 변경하면 DB 를 OPEN 할 수가 없기 때문이다.
1. 다음의 Update문을 실행하여 CHARACTER SET을 변경한다.
UPDATE sys.props$
SET value$ = 'KO16KSC5601'
WHERE name = 'NLS_CHARACTERSET';
Update 시에 NLS_CHARACTERSET을 지원되지 않는 값으로 잘못 설정하거나
실수로 콘트롤 문자 같은 것이 들어가게 되면 DB가 Shutdown 된 다음에는
Startup 이 안되므로 Update 후에 다음 명령으로 확인을 한 다음에
Commit을 하도록 한다.
select name, value$
from sys.props$
where value$ = 'KO16KSC5601';
Select가 제대로 출력되면 Commit 하고 Shutdown 했다가 Startup 하게
되면 새로운 CHARACTER SET 값을 갖게 된다. SELECT가 안 되면 ROLLBACK
하고 UPDATE부터 다시 하도록 한다.
2. 환경 변수 NLS_LANG 을 변경한다.
.profile 에서
NLS_LANG=American_America.KO16KSC5601; export NLS_LANG
또는 .cshrc 에서.
setenv NLS_LANG American_America.KO16KSC5601
*** win95 및 winnt의 client에서는 registry editor에서 NLS_LANG 값을
맞추어준다.
주의 !!!
: 위의 작업을 하기 전에 발생할 가능성이 있는 문제점
1) update 중 KO16KSC5601 이나 US7ASCII 등에서 철자를 잘못 입력하시면,
db 재기동 후에, 다음과 같은 에러가 발생합니다.
ora-12708
12708, 00000, "error while loading create database NLS parameter %s"
2) KO16KSC5601과 US7ASCII의 비교
Character set : KO16KSC5601 인 경우
===================================
: double byte encoding schema 이므로, 한글의 경우 2 bytes 를 크기 1로
계산하는 함수들이 있습니다.
그리고, table , column name에 한글을 double quote 없이 사용할 수 있습니다.
예)
SQL> create table 시험1
2 (컬럼1 varchar(10));
가
a
홍길동
SQL> select length(컬럼1) from 시험1;
1
1
3
SQL> select lengthb(컬럼1) from 시험1;
2
1
6
Character set : US7ASCII 인 경우
=================================
: single byte 7 bit encoding 을 사용합니다.
한글로 된 table, column 이름 사용 시 double quote를 반드시 사용해야 한다.
예)
SQL> create table "사원"
2 ("사원이름" varchar2(10));
가
a
홍길동
SQL> select length("사원이름") from "사원";
2
1
6
SQL> select lengthb("사원이름") from "사원";
2
1
6
US7ASCII일 때에는 vsize, lengthb function의 결과가 length 함수와 모두
동일합니다.
cf) substr, substrb 함수도 위의 length, lengthb의 관계와 같음.

제품 : ORACLE SERVER
작성날짜 : 2004-11-09
NLS CHARACTER SET 변경 방법 (ORACLE 7)
======================================
PURPOSE
이 자료는 Oracle RDBMS SERVER에서 NLS CHARACTER SET 변경 방법에 대한
내용을 소개한다.
[ ORACLE 7 에서만 가능 ]
데이타베이스의 CHARACTER SET은 데이타 딕셔너리 테이블인 sys.props$에
들어 있다.
SQL>desc sys.props$
Name Null? Type
NAME NOT NULL VARCHAR2(30)
VALUE$ VARCHAR2(2000)
COMMENT$ VARCHAR2(2000)
SQL>column c1 format a30
SQL>select name c1, value$ c1 from sys.props$;
C1 C1
DICT.BASE 2
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_DATE_FORMAT DD-MON-YY
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET US7ASCII
NLS_SORT BINARY
GLOBAL_DB_NAME NLSV7.WORLD
여기서 NLS_CHARACTERSET에 현재 DB의 CHARACTER SET이 들어 있는데
이 값을 변경하여 DB의 CHARACTER SET을 변경할 수 있다.
여기서는 US7ASCII에서 KO16KSC5601로 옮기는 경우를 알아보자.
우선 바꾸고자 하는 CHRACTER SET이 지원되는 지를 다음 명령으로
확인한다.
select convert('a','KO16KSC5601','US7ASCII') from dual;
만약 이 Select 문에서 ORA-01482 에러가 발생하면 지정한 CHARACTER
SET이 지원되지 않는 경우이며 에러가 발생하지 않으면 CHARACTER
SET을 변경할 수 있다.
작업을 하기 전에는 만약을 위해서 DB 전체를 백업 받아두도록 한다.
CHARACTER SET 을 잘못 변경하면 DB 를 OPEN 할 수가 없기 때문이다.
1. 다음의 Update문을 실행하여 CHARACTER SET을 변경한다.
UPDATE sys.props$
SET value$ = 'KO16KSC5601'
WHERE name = 'NLS_CHARACTERSET';
Update 시에 NLS_CHARACTERSET을 지원되지 않는 값으로 잘못 설정하거나
실수로 콘트롤 문자 같은 것이 들어가게 되면 DB가 Shutdown 된 다음에는
Startup 이 안되므로 Update 후에 다음 명령으로 확인을 한 다음에
Commit을 하도록 한다.
select name, value$
from sys.props$
where value$ = 'KO16KSC5601';
Select가 제대로 출력되면 Commit 하고 Shutdown 했다가 Startup 하게
되면 새로운 CHARACTER SET 값을 갖게 된다. SELECT가 안 되면 ROLLBACK
하고 UPDATE부터 다시 하도록 한다.
2. 환경 변수 NLS_LANG 을 변경한다.
.profile 에서
NLS_LANG=American_America.KO16KSC5601; export NLS_LANG
또는 .cshrc 에서.
setenv NLS_LANG American_America.KO16KSC5601
*** win95 및 winnt의 client에서는 registry editor에서 NLS_LANG 값을
맞추어준다.
주의 !!!
: 위의 작업을 하기 전에 발생할 가능성이 있는 문제점
1) update 중 KO16KSC5601 이나 US7ASCII 등에서 철자를 잘못 입력하시면,
db 재기동 후에, 다음과 같은 에러가 발생합니다.
ora-12708
12708, 00000, "error while loading create database NLS parameter %s"
2) KO16KSC5601과 US7ASCII의 비교
Character set : KO16KSC5601 인 경우
===================================
: double byte encoding schema 이므로, 한글의 경우 2 bytes 를 크기 1로
계산하는 함수들이 있습니다.
그리고, table , column name에 한글을 double quote 없이 사용할 수 있습니다.
예)
SQL> create table 시험1
2 (컬럼1 varchar(10));
가
a
홍길동
SQL> select length(컬럼1) from 시험1;
1
1
3
SQL> select lengthb(컬럼1) from 시험1;
2
1
6
Character set : US7ASCII 인 경우
=================================
: single byte 7 bit encoding 을 사용합니다.
한글로 된 table, column 이름 사용 시 double quote를 반드시 사용해야 한다.
예)
SQL> create table "사원"
2 ("사원이름" varchar2(10));
가
a
홍길동
SQL> select length("사원이름") from "사원";
2
1
6
SQL> select lengthb("사원이름") from "사원";
2
1
6
US7ASCII일 때에는 vsize, lengthb function의 결과가 length 함수와 모두
동일합니다.
cf) substr, substrb 함수도 위의 length, lengthb의 관계와 같음.

Creating database problem with ORA-01519: error while processing file '' ne

Dear all,
I am having rough time with creating database manually. can anyone help me with the following errors.
ALERT LOGFILE:-
Sun May 31 12:00:39 2009
Errors in file d:\oracle\product\10.1.0\admin\oracle5\udump\oracle5_ora_3444.trc:
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '%ORACLE_HOME%\RDBMS\ADMIN\SQL.BSQ' near line 5744
ORA-00604: error occurred at recursive SQL level 1
ORA-01119: error in creating database file 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\undotbs1.dbf'
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Error 1519 happened during db open, shutting down database
USER: terminating instance due to error 1519
Sun May 31 12:00:39 2009
Errors in file d:\oracle\product\10.1.0\admin\oracle5\bdump\oracle5_reco_3416.trc:
ORA-01519: error while processing file '' near line
CREATE DATABASE SCRIPT:-
create database ORACLE5
user sys identified by bala
user system identified by bala
logfile
group 1 ('D:\oracle\product\10.1.0\oradata\ORACLE5\logfile\redo01.log') SIZE 50M,
group 2 ('D:\oracle\product\10.1.0\oradata\ORACLE5\logfile\redo02.log') SIZE 50M,
group 3 ('D:\oracle\product\10.1.0\oradata\ORACLE5\logfile\redo03.log') SIZE 50M
maxlogfiles 5
maxlogmembers 5
maxloghistory 1
maxdatafiles 50
maxinstances 1
datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5\datafile\system01.dbf' size 200m autoextend on maxsize unlimited extent management local
undo tablespace UNDOTBS1 datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\undotbs1.dbf' size 10m autoextend on maxsize unlimited
sysaux datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5\datafile\sysaux01.dbf' size 100m autoextend on maxsize unlimited
default temporary tablespace temp tempfile 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\temp01.dbf' size 10m autoextend on maxsize unlimited
character set US7ASCII
NATIONAL CHARACTER SET AL16UTF16
INIT.ORA FILE:-
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Archive
log_archive_format=ARC%S_%R.%T
# Cache and I/O
db_block_size=8192
db_cache_size=25165824
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=300
# Database Identification
db_domain=""
db_name=oracle5
# Diagnostics and Statistics
background_dump_dest=D:\oracle\product\10.1.0\admin\oracle5\bdump
core_dump_dest=D:\oracle\product\10.1.0\admin\oracle5\cdump
user_dump_dest=D:\oracle\product\10.1.0\admin\oracle5\udump
# File Configuration
#db_create_file_dest=D:\oracle\product\10.1.0\oradata
db_recovery_file_dest=D:\oracle\product\10.1.0\flash_recovery_area
db_recovery_file_dest_size=2147483648
# Job Queues
job_queue_processes=10
# Miscellaneous
compatible=10.1.0.2.0
# Pools
java_pool_size=50331648
large_pool_size=8388608
shared_pool_size=83886080
# Processes and Sessions
processes=150
# Security and Auditing
remote_login_passwordfile=EXCLUSIVE
# Shared Server
dispatchers="(PROTOCOL=TCP) (SERVICE=oracle5XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=25165824
sort_area_size=65536
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_tablespace=UNDOTBS1
control_files=("D:\ORACLE\PRODUCT\10.1.0\ORADATA\ORACLE5\CONTROLFILE\control01.CTL", "D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORACLE5\CONTROLFILE\control02.CTL")

Hi,
undo tablespace UNDOTBS1 datafile 'D:\oracle\product\10.1.0\oradata\ORACLE5 \datafile\undotbs1.dbf' size 10m autoextend on maxsize unlimited
After ORACLE5 there is a space character. Typo? Create proper directory or delete this character.
Bartek

ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 401

I receive the following error by creating dataabse as below sql:
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 401
ORA-00604: error occurred at recursive SQL level 1
ORA-01119: error in creating database file '/sisdev04/dbs/users01.dbf'
ORA-27039: create file failed, file size limit reached
Additional information: 1
CREATE DATABASE SISDEV04
     LOGFILE GROUP 1 ('/sisdev04/dbs/log01a.dbf','/sisdev04/dbs/log01b.dbf') SIZE 10M,
          GROUP 2 ('/sisdev04/dbs/log02a.dbf','/sisdev04/dbs/log02b.dbf') SIZE 10M
     NOARCHIVELOG
     CHARACTER SET ZHT16BIG5
     NATIONAL CHARACTER SET ZHT16BIG5
     DATAFILE '/sisdev04/dbs/system01.dbf'
          SIZE 210M AUTOEXTEND OFF
     , '/sisdev04/dbs/rbs01.dbf'
SIZE 105M AUTOEXTEND OFF
     , '/sisdev04/dbs/temp01.dbf'
SIZE 105M AUTOEXTEND OFF
     , '/sisdev04/dbs/users01.dbf'
SIZE 1050M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_index_ivr01.dbf'
SIZE 105M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_ivr01.dbf'
SIZE 21M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_ems01.dbf'
SIZE 21M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_index_ems01.dbf'
SIZE 21M AUTOEXTEND OFF
I have issue df to check the directory sisuat04
/ >df
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 98304 45664 54% 2446 10% /
/dev/hd2 2097152 78992 97% 30280 12% /usr
/dev/hd9var 65536 20536 69% 308 4% /var
/dev/hd3 294912 262432 12% 147 1% /tmp
/dev/hd1 49152 5712 89% 1290 21% /home
/dev/mfcobol 81920 25520 69% 608 6% /mfcobol
/dev/magiclv 81920 22304 73% 346 4% /usr/magic
/dev/sispro02lv 6553600 6347792 4% 18 1% /sisdev02
/dev/sispro03lv 6553600 6347784 4% 19 1% /sisdev03
/dev/sisappllv 229376 173288 25% 1846 7% /sisappl
/dev/lvbaklog 98304 85552 13% 68 1% /app/bak_log
/dev/noteslv0 1048576 541352 49% 2195 2% /notes
/dev/noteslv1 4194304 1479304 65% 5269 2% /notesrv
/dev/noteslv2 2097152 898128 58% 51 1% /notesrv/sitesch
/dev/lvoracle 2097152 237240 89% 8280 4% /opt/oracle
/dev/u01lv 4194304 128720 97% 11697 3% /u01
/dev/sisdev01lv 4096000 3021552 27% 27 1% /sisdev04
Is is still a not enough space problem?

I receive the following error by creating dataabse as below sql:
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 401
ORA-00604: error occurred at recursive SQL level 1
ORA-01119: error in creating database file '/sisdev04/dbs/users01.dbf'
ORA-27039: create file failed, file size limit reached
Additional information: 1
CREATE DATABASE SISDEV04
     LOGFILE GROUP 1 ('/sisdev04/dbs/log01a.dbf','/sisdev04/dbs/log01b.dbf') SIZE 10M,
          GROUP 2 ('/sisdev04/dbs/log02a.dbf','/sisdev04/dbs/log02b.dbf') SIZE 10M
     NOARCHIVELOG
     CHARACTER SET ZHT16BIG5
     NATIONAL CHARACTER SET ZHT16BIG5
     DATAFILE '/sisdev04/dbs/system01.dbf'
          SIZE 210M AUTOEXTEND OFF
     , '/sisdev04/dbs/rbs01.dbf'
SIZE 105M AUTOEXTEND OFF
     , '/sisdev04/dbs/temp01.dbf'
SIZE 105M AUTOEXTEND OFF
     , '/sisdev04/dbs/users01.dbf'
SIZE 1050M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_index_ivr01.dbf'
SIZE 105M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_ivr01.dbf'
SIZE 21M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_ems01.dbf'
SIZE 21M AUTOEXTEND OFF
     , '/sisdev04/dbs/ts_index_ems01.dbf'
SIZE 21M AUTOEXTEND OFF
I have issue df to check the directory sisuat04
/ >df
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 98304 45664 54% 2446 10% /
/dev/hd2 2097152 78992 97% 30280 12% /usr
/dev/hd9var 65536 20536 69% 308 4% /var
/dev/hd3 294912 262432 12% 147 1% /tmp
/dev/hd1 49152 5712 89% 1290 21% /home
/dev/mfcobol 81920 25520 69% 608 6% /mfcobol
/dev/magiclv 81920 22304 73% 346 4% /usr/magic
/dev/sispro02lv 6553600 6347792 4% 18 1% /sisdev02
/dev/sispro03lv 6553600 6347784 4% 19 1% /sisdev03
/dev/sisappllv 229376 173288 25% 1846 7% /sisappl
/dev/lvbaklog 98304 85552 13% 68 1% /app/bak_log
/dev/noteslv0 1048576 541352 49% 2195 2% /notes
/dev/noteslv1 4194304 1479304 65% 5269 2% /notesrv
/dev/noteslv2 2097152 898128 58% 51 1% /notesrv/sitesch
/dev/lvoracle 2097152 237240 89% 8280 4% /opt/oracle
/dev/u01lv 4194304 128720 97% 11697 3% /u01
/dev/sisdev01lv 4096000 3021552 27% 27 1% /sisdev04
Is is still a not enough space problem? i think you have specified 1050m for users01.dbf file, your file system /sisdev04 has something like
1.5gb of free space. it failed because of lack of free space. may be you can reduce your datafile size or try to
create in another filesystem.

ORA-2002 : error while writing to audit trail

Hi all ,
I am oracle 11g and on SPARC OS.
I enabled audit in my database by setting the parameter audit_trail=DB and then i restarted my instance.
On doing so the database started but whenever i am trying to connect using pl/sql developer , i am getting the following list of errors :
ORA-00604 : error occured at recursive SQL level 1
ora-00904 : "DBID" invalid identifier
Ora-02002 : error while writing to audit trail
ORA-00604 : error occured at recursive SQL level 1
ora-00904 : "DBID" invalid identifier
I checked on the net for ora-02002 and increased the size of the system tablespace from 750 M to 1000M.
My system tablespace is dictionary managed.
bounced the database also , but still getting the same errors.
please help
regards
KKukreja
Edited by: ~JuniorDBA~ on Dec 20, 2010 8:59 PM

Hi Nicolas,
here is the output
SQL> desc sys.aud$
Name                                      Null?    Type
SESSIONID                                 NOT NULL NUMBER
ENTRYID                                   NOT NULL NUMBER
STATEMENT                                 NOT NULL NUMBER
TIMESTAMP#                                         DATE
USERID                                             VARCHAR2(30)
USERHOST                                           VARCHAR2(128)
TERMINAL                                           VARCHAR2(255)
ACTION#                                   NOT NULL NUMBER
RETURNCODE                                NOT NULL NUMBER
OBJ$CREATOR                                        VARCHAR2(30)
OBJ$NAME                                           VARCHAR2(128)
AUTH$PRIVILEGES                                    VARCHAR2(16)
AUTH$GRANTEE                                       VARCHAR2(30)
NEW$OWNER                                          VARCHAR2(30)
NEW$NAME                                           VARCHAR2(128)
SES$ACTIONS                                        VARCHAR2(19)
SES$TID                                            NUMBER
LOGOFF$LREAD                                       NUMBER
LOGOFF$PREAD                                       NUMBER
LOGOFF$LWRITE                                      NUMBER
LOGOFF$DEAD                                        NUMBER
LOGOFF$TIME                                        DATE
COMMENT$TEXT                                       VARCHAR2(4000)
CLIENTID                                           VARCHAR2(64)
SPARE1                                             VARCHAR2(255)
SPARE2                                             NUMBER
OBJ$LABEL                                          RAW(255)
SES$LABEL                                          RAW(255)
PRIV$USED                                          NUMBER
SESSIONCPU                                         NUMBERsince i took over the database , no one did anything ... i only truncated the aud$ table today.
But while going through the files i came across a SQL file that had this content :
more move_audit.sql
create table system.aud$
tablespace AUD_TSP
as select * from aud$;
create index system.i_aud1 on system.aud$(sessionid, ses$tid);
rename aud$ to aud$_temp;
create view aud$ as
select * from system.aud$;
connect system/XXXXX
grant all on aud$ to sys with grant option;
grant delete on aud$ to delete_catalog_role;Now I am not sure what has happened and who has done what,but when i checked on TOAD, system tablespace had aud$ table and there was no table in tablespace AUD_TSP.
thanks and regards
Kkukreja
Edited by: ~JuniorDBA~ on Dec 21, 2010 12:55 AM

ORA-19870: error while restoring backup piece -- file exists in ASM

[oracle@rs1pre92dvdbsa01 ~]$ rman target sys/c9nv9sd9t9f11e@mdm11 auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Oct 29 10:41:38 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: MDM (DBID=1485385044)
connected to auxiliary database: MDM (not mounted)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 29-OCT-10
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=13 device type=DISK
contents of Memory Script:
restore clone standby controlfile;
executing Memory Script
Starting restore at 29-OCT-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece +MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607
channel ORA_AUX_DISK_1: ORA-19870: error while restoring backup piece +MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607
ORA-19505: failed to identify file "+MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607"
ORA-17503: ksfdopn:2 Failed to open file +MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607
ORA-15012: ASM file '+MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607' does not exist
failover to previous backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/29/2010 10:42:00
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN>
ASMCMD [+mdmdg2] > cd mdm1
ASMCMD [+mdmdg2/mdm1] > ls
CONTROLFILE/
FLASHBACK/
ONLINELOG/
arch/
autobackup/
ASMCMD [+mdmdg2/mdm1] > cd autobackup
ASMCMD [+mdmdg2/mdm1/autobackup] > ls
2010_10_29/
ASMCMD [+mdmdg2/mdm1/autobackup] > cd 2010_10_29
ASMCMD [+mdmdg2/mdm1/autobackup/2010_10_29] > ls
s_733654605.283.733654607
As seen in asmcmd "s_733654605.283.733654607" file exists in +mdmdg2/mdm1/autobackup/2010_10_29 then why it is complaning that it can't find the file.
and also How to open/view file in asmcmd

[oracle@rs1pre91dvdbaa01 utl]$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Fri Oct 29 13:11:44 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup;
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
I have rebooted both the RAC servers and I can't start database?
I was under the impression that Database should be automatically started as part of Clusterware
Please help urgent.

Want to change Database Character set

I have installed Oracle 10g in my system.
But while installing Oracle 10g i have selected the Database Character set as English but now i want it to change it to West European WE8MSWIN1252
can anyboby suggest how to modify it.

http://oracle.ittoolbox.com/documents/popular-q-and-a/changing-the-character-set-of-an-oracle-database-1601
Best Practices
http://www.oracle.com/technology/tech/globalization/pdf/TWP_Character_Set_Migration_Best_Practices_10gR2.pdf

How to change the character set of the D/b

Hello All,
When i issue the command
ALTER DATABASE CHARACTER SET UTF8
It gives me the error that I can only change the character set to a superset of the existing character set.
Is there any way i can change the character set without recreating the database.
TIA
Naveen

The existing character set is the basis for the new character set. This is fair enough, because the character set determines how the actual data is stored in the database. Allowing new characters is a minor change: completely re-encoding your entire database is not.
I'm afraid export, recreate and import is your only option.
Cheers, APC

ORA-12712 error while changing nls character set to AL32UTF8

Similar Messages

Maybe you are looking for