Migrating Database from Oracle 8.0.5 for NT to Oracle 8.1.7 for Unix.

Hello!
Please help me in Migrating Database(Including Data,Stored
Procdures, Views, Indexes,Forms, Triggers etc.) from Oracle 8.0.5 for NT to Oracle 8.1.7 for Unix.

Check the installation option that you chose.
Not all of the options will install a database.
P.S.
I have a similar problem on NT.
Where I am able to access the database after the 8i Enterprise
Install. I can not access the database from a Developer or
Designer Installation. I am trying to run these tools locally.
How do I configure NET8 to access the local 8i Database?
Any ideas??
Regards, Jim
Emeka (guest) wrote:
: I just installed the Oracle 8 Enterprise Edition for windows NT
: and i can't find the Oracle database to support the tables.
Also
: the username and password of scott and tiger didn't work for
the
: SQL Plus.ERROR' ORA-12203: TNS: unable to connect to
destination'
: was the message when i try getting into SQL. Could someone
please
: tell me how to install the database and how to get the user
name
: and password for the SQL Plus.
null

Similar Messages

  • Migrating database from PostgreSql to Oracle 10g

    Hi
    can anybody help me by providing steps to migrating database from PostgreSql to Oracle 10g. its very urgent requirement. so please let me know if anyone know about this setps.
    thanks in advance.
    jayesh
    cignex technology pvt ltd

    NPD wrote:
    Hi Guys,
    Can one migrate database from sql2005 to Oracle.
    Thanx.You can use [Oracle Migration Tool |http://www.oracle.com/technology/tech/migration/workbench/index.html]
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com
    [Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

  • Migrating database from sql2005 to Oracle 9i

    Hi Guys,
    Can one migrate database from sql2005 to Oracle.
    Thanx.

    NPD wrote:
    Hi Guys,
    Can one migrate database from sql2005 to Oracle.
    Thanx.You can use [Oracle Migration Tool |http://www.oracle.com/technology/tech/migration/workbench/index.html]
    Kamran Agayev A. (10g OCP)
    http://kamranagayev.wordpress.com
    [Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

  • How To Migrate Databases From Windows 2003 32 bit to windows 2003 64 bit?

    Hi,
    How To Migrate Databases From Windows 2003 32 bit to windows 2003 64 bit?
    Db Version: 10.2.0.2
    Thanks,
    Yusuf

    Also see MOS Doc 403522.1 (How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows)
    HTH
    Srini

  • How to migrate  database from oracle10g to mysql

    how to migrate database from oracle10g to mysql

    Assuming you're actually using any of the features of Oracle at present, this will be an impossible task, since MySql has such narrower set of supported SQL.

  • Migrate database from IBM DB2 to ORACLE

    Hi oracle professionals,
    Currently database resides in IBM DB2...
    We need to migrate Database to oracle ...
    Thanks in advance
    Pawan

    Hi,
    Kindly refer
    Oracle SQL*Developer - which is free to use and download -
    http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/index.html
    Oracle Database Migration Technology -
    http://www.oracle.com/technetwork/database/migration/index-084442.html
    Migrating from IBM DB2 LUW to Oracle -
    http://www.oracle.com/technetwork/database/migration/db2-084087.html
    IBM DB2/400 V4R3 & V4R5 can be migrated using the original Migration Workbench v10.1.0.4 available from here -
    http://www.oracle.com/technetwork/topics/index-095746.html
    Also article
    Migrating From IBM DB2 UDB to Oracle (Doc ID 1148493.1)
    Thanks,
    Krishna

  • Migrating database from server (OS: IBM AIX 5.1 Oracle: 9.2.0.4) to server

    Dear All,
    In order to migrate one database from server (OS: IBM AIX 5.1 Oracle: 9.2.0.4) to another server (OS: IBM AIX 5.3 Oracle: 9.2.0.6)
    I am performing the cold backup and taking the below files backup.
    Datafiles
    Redologfiles
    Archive log file
    Backup of control file from trace
    I just wanted to know
    a) Is there any other files do I need to take backup which may be required to bring the database up on another server?
    b) Upper version of OS and oracle can create any issue or do I need to perform any extra activities?
    I know after restoration the above files to the destination server, what procedure I would require to follow.
    I have doubt with version of OS and oracle.
    Request your advice on this.
    Regards,

    I dont think higher version especially 5.1-5.3 will make any difference but oracle 9.2.0.4 will definitely will have an issue. If i am not wrong you need to startup the database with startup MIGRATE option after moving all the files to the new server
    May be password file (missed out, but you can always create one)
    Init.ora file
    make note on Entries in ORATAB

  • How to migrate database from oracle9i on solaris to windows Itanium?

    How step I can do?
    I try to use export tool of oracle 9i export full database from solaris.
    by use command:
    export ORACLE_SID=dbtest
    export NLS_LANG=AMERICAN_AMERICA.TH8TISASCII
    exp system/password@dbtest full=y file= /u02/dump/dbtestfull.dmp log=/u02/dump/exp_dbtest.log
    My result is "Export terminated successfully without warnings."
    I had ftp dump file in binary mode from solaris to windows.
    create same database name on widnows (dbca --general purpose) set oracle_sid and NLS_lang
    and then import database by use command:
    imp system/password@dbtest file=e:\dumpfile\dbtestfull.dmp log=e:\dumpfile\imp_dbtestfull.log full=y
    I got error:
    "CREATE TABLESPACE "DRSYS" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradata"
    "/dbtest/drsys01.dbf' SIZE 20971520 AUTOEXTEND ON NEXT 655360 MAXSIZE"
    " 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGING "
    "SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00015: following statement failed because the object already exists:
    "CREATE TABLESPACE "EXAMPLE" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/orada"
    "ta/dbtest/example01.dbf' SIZE 156631040 AUTOEXTEND ON NEXT 655360 MA"
    "XSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOG"
    "GING SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00015: following statement failed because the object already exists:
    "CREATE TABLESPACE "INDX" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradata/"
    "dbtest/indx01.dbf' SIZE 26214400 AUTOEXTEND ON NEXT 1310720 MAXSIZE "
    "32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGING S"
    "EGMENT SPACE MANAGEMENT AUTO"
    IMP-00015: following statement failed because the object already exists:
    "CREATE TABLESPACE "ODM" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradata/d"
    "btest/odm01.dbf' SIZE 20971520 AUTOEXTEND ON NEXT 655360 MAXSIZE 327"
    "67M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGING SEGM"
    "ENT SPACE MANAGEMENT AUTO"
    IMP-00015: following statement failed because the object already exists:
    "CREATE TABLESPACE "TOOLS" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradata"
    "/dbtest/tools01.dbf' SIZE 10485760 AUTOEXTEND ON NEXT 327680 MAXSIZE"
    " 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGING "
    "SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00015: following statement failed because the object already exists:
    "CREATE TABLESPACE "USERS" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradata"
    "/dbtest/users01.dbf' SIZE 26214400 AUTOEXTEND ON NEXT 1310720 MAXSIZ"
    "E 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGING"
    " SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00015: following statement failed because the object already exists:
    "CREATE TABLESPACE "XDB" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/oradata/d"
    "btest/xdb01.dbf' SIZE 39976960 AUTOEXTEND ON NEXT 655360 MAXSIZE 327"
    "67M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGING SEGM"
    "ENT SPACE MANAGEMENT AUTO"
    IMP-00017: following statement failed with ORACLE error 1119:
    "CREATE TABLESPACE "TESTTBS" BLOCKSIZE 8192 DATAFILE '/u01/app/oracle/orada"
    "ta/dbtest/testtbs.dbf' SIZE 33554432 AUTOEXTEND ON NEXT 33554432 MAX"
    "SIZE 2048M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT NOLOGGI"
    "NG"
    IMP-00003: ORACLE error 1119 encountered
    ORA-01119: error in creating database file '/u01/app/oracle/oradata/dbtest/testt
    bs.dbf'
    ORA-27040: skgfrcre: create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "OUTLN" IDENTIFIED BY VALUES '4A3BA55E08595C81' TEMPORARY TABLE"
    "SPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "DBSNMP" IDENTIFIED BY VALUES 'E066D214D5421CCC' TEMPORARY TABL"
    "ESPACE "TEMP""
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "WMSYS" IDENTIFIED BY VALUES '7C9BA362F8314299' TEMPORARY TABLE"
    "SPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "ANONYMOUS" IDENTIFIED BY VALUES 'anonymous' DEFAULT TABLESPACE"
    " "XDB" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "WKSYS" IDENTIFIED BY VALUES '69ED49EE1851900D' DEFAULT TABLESP"
    "ACE "DRSYS" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "WKPROXY" IDENTIFIED BY VALUES 'B97545C4DD2ABE54' DEFAULT TABLE"
    "SPACE "DRSYS" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "ODM" IDENTIFIED BY VALUES 'C252E8FA117AF049' DEFAULT TABLESPAC"
    "E "ODM" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "ODM_MTR" IDENTIFIED BY VALUES 'A7A32CD03D3CE8D5' DEFAULT TABLE"
    "SPACE "ODM" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "OLAPSYS" IDENTIFIED BY VALUES '3FB8EF9DB538647C' DEFAULT TABLE"
    "SPACE "CWMLITE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "HR" IDENTIFIED BY VALUES '6399F3B38EDF3288' DEFAULT TABLESPACE"
    " "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "OE" IDENTIFIED BY VALUES '9C30855E7E0CB02D' DEFAULT TABLESPACE"
    " "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "PM" IDENTIFIED BY VALUES '72E382A52E89575A' DEFAULT TABLESPACE"
    " "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "SH" IDENTIFIED BY VALUES '9793B3777CD3BD1A' DEFAULT TABLESPACE"
    " "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_ADM" IDENTIFIED BY VALUES '991CDDAD5C5C32CA' DEFAULT TABLES"
    "PACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS" IDENTIFIED BY VALUES '8B09C6075BDF2DC4' DEFAULT TABLESPACE"
    " "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_WS" IDENTIFIED BY VALUES '24ACF617DD7D8F2F' DEFAULT TABLESP"
    "ACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_ES" IDENTIFIED BY VALUES 'E6A6FA4BB042E3C2' DEFAULT TABLESP"
    "ACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_OS" IDENTIFIED BY VALUES 'FF09F3EB14AE5C26' DEFAULT TABLESP"
    "ACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_CBADM" IDENTIFIED BY VALUES '7C632AFB71F8D305' DEFAULT TABL"
    "ESPACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_CB" IDENTIFIED BY VALUES 'CF9CFACF5AE24964' DEFAULT TABLESP"
    "ACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "QS_CS" IDENTIFIED BY VALUES '91A00922D8C0F146' DEFAULT TABLESP"
    "ACE "EXAMPLE" TEMPORARY TABLESPACE "TEMP" PASSWORD EXPIRE ACCOUNT LOCK"
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "SCOTT" IDENTIFIED BY VALUES 'F894844C34402B67' TEMPORARY TABLE"
    "SPACE "TEMP""
    IMP-00015: following statement failed because the object already exists:
    "CREATE USER "APITHA" IDENTIFIED BY VALUES '71B848C6F0AAC4F6' DEFAULT TABLES"
    "PACE "TESTTBS" TEMPORARY TABLESPACE "TEMP""
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "SELECT_CATALOG_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "SELECT_CATALOG_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "EXECUTE_CATALOG_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "EXECUTE_CATALOG_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "DELETE_CATALOG_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "DELETE_CATALOG_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "RECOVERY_CATALOG_OWNER""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "RECOVERY_CATALOG_OWNER" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "GATHER_SYSTEM_STATISTICS""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "GATHER_SYSTEM_STATISTICS" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "LOGSTDBY_ADMINISTRATOR""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "LOGSTDBY_ADMINISTRATOR" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "AQ_ADMINISTRATOR_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "AQ_ADMINISTRATOR_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "AQ_USER_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "AQ_USER_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "GLOBAL_AQ_USER_ROLE" IDENTIFIED GLOBALLY "
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "OEM_MONITOR""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "OEM_MONITOR" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "HS_ADMIN_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "HS_ADMIN_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "WKUSER""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "WKUSER" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "WM_ADMIN_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "WM_ADMIN_ROLE" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "JAVAUSERPRIV""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "JAVAUSERPRIV" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "JAVAIDPRIV""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "JAVAIDPRIV" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "JAVASYSPRIV""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "JAVASYSPRIV" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "JAVADEBUGPRIV""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "JAVADEBUGPRIV" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "EJBCLIENT""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "EJBCLIENT" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "JAVA_ADMIN""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "JAVA_ADMIN" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "JAVA_DEPLOY""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "JAVA_DEPLOY" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "CTXAPP""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "CTXAPP" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "XDBADMIN""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "XDBADMIN" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "AUTHENTICATEDUSER""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "AUTHENTICATEDUSER" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "OLAP_DBA""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "OLAP_DBA" FROM SYSTEM"
    IMP-00015: following statement failed because the object already exists:
    "CREATE ROLE "SALES_HISTORY_ROLE""
    IMP-00015: following statement failed because the object already exists:
    "REVOKE "SALES_HISTORY_ROLE" FROM SYSTEM"
    IMP-00017: following statement failed with ORACLE error 3113:
    "BEGIN "
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_EVALUATIO"
    "N_CONTEXT_OBJ, 'SYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_EVALUATIO"
    "N_CONTEXT_OBJ, 'DBA',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_EVALUATIO"
    "N_CONTEXT_OBJ, 'AQ_ADMINISTRATOR_ROLE',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_EVALUATIO"
    "N_CONTEXT_OBJ, 'MDSYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_EVALUATIO"
    "N_CONTEXT_OBJ, 'CTXSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_EVALUATIO"
    "N_CONTEXT_OBJ, 'WKSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_ANY_EVALU"
    "ATION_CONTEXT, 'SYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_ANY_EVALU"
    "ATION_CONTEXT, 'DBA',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_ANY_EVALU"
    "ATION_CONTEXT, 'MDSYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_ANY_EVALU"
    "ATION_CONTEXT, 'CTXSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.CREATE_ANY_EVALU"
    "ATION_CONTEXT, 'WKSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.ALTER_ANY_EVALUA"
    "TION_CONTEXT, 'SYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.ALTER_ANY_EVALUA"
    "TION_CONTEXT, 'DBA',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.ALTER_ANY_EVALUA"
    "TION_CONTEXT, 'MDSYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.ALTER_ANY_EVALUA"
    "TION_CONTEXT, 'CTXSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.ALTER_ANY_EVALUA"
    "TION_CONTEXT, 'WKSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.DROP_ANY_EVALUAT"
    "ION_CONTEXT, 'SYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.DROP_ANY_EVALUAT"
    "ION_CONTEXT, 'DBA',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.DROP_ANY_EVALUAT"
    "ION_CONTEXT, 'MDSYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.DROP_ANY_EVALUAT"
    "ION_CONTEXT, 'CTXSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.DROP_ANY_EVALUAT"
    "ION_CONTEXT, 'WKSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.EXECUTE_ANY_EVAL"
    "UATION_CONTEXT, 'SYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.EXECUTE_ANY_EVAL"
    "UATION_CONTEXT, 'DBA',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.EXECUTE_ANY_EVAL"
    "UATION_CONTEXT, 'MDSYS',TRUE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.EXECUTE_ANY_EVAL"
    "UATION_CONTEXT, 'CTXSYS',FALSE);"
    "SYS.DBMS_RULE_ADM.GRANT_SYSTEM_PRIVILEGE(SYS.DBMS_RULE_ADM.EXECUTE_ANY_EVAL"
    "UATION_CONTEXT, 'WKSYS',FALSE);"
    "COMMIT; END;"
    IMP-00003: ORACLE error 3113 encountered
    ORA-03113: end-of-file on communication channel
    IMP-00003: ORACLE error 3114 encountered
    ORA-03114: not connected to ORACLE
    How to solve this problem?
    I want to migrate whole database, it'can be?

    Hi
    I was able to find only two types of error in this.
    1)
    IMP-00015: following statement failed because the object already exists:Use ignore=y along with import because the tablespace for which it failed already exist in the database. So with ignore=y it would ignore the objects which already exist and would go to next step.
    2)
    IMP-00003: ORACLE error 1119 encounteredThis is because full export do include tablespace defination also. Since the tablespaces which it is trying to create does not exist in the system and the source database from where the exp dump was taken was Unix flavour so the file structure between them was different and as a result it was not able to create it.
    Suggestion.: Manually create the tablespace at your desired location. And then run the imp again with ignore=y
    Regards
    Anurag

  • Migration databases from one server to another

    Hi All
    I want to migrate our 8 production databases from one server to another server. these are in RAC .Details are below
    OLD SERVER: -
    OS: REDHAT LINUX 3
    ORACLE: ORACLE 10gR1
    FILE SYSTEM : OCFS
    STORAGE: SAN
    Its a RAC databases
    NEW SERVER: -
    OS: REDHAT LINUX 5
    ORACLE: ORACLE 11g R2
    FILE SYSTEM:ASM
    STORAGE:SAN ( fresh one)
    Its also RAC DATABASES
    So please tell me the best method to migrate 8 databases from old server to another server . all databases size are not more than 50 GB.
    All servers details are above .please let me know if you require any other details
    please reply soon we have to do it on urgent basis

    Since all your databases are small (< 50G), I would recommend using expdp/impdp - http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/expimp.htm - as this will provide several advantages as listed in the document.
    Different Upgrade Methods For Upgrading Your Database (Doc ID 419550.1)
    HTH
    Srini

  • Migrated database from 2008 R2 to 2012 getting wrong decimal precisions

    Migrated SQL Server database from 2008R2 to 2012 using backup and restore option
    When I do aggregate sum on both the databases 2008 and 2012 decimal precision is coming different. Because of this measure value in SSAS cube browser is calculated wrongly compared to 2008 R2 vs 2012
    select SUM(rate) from [InfoDB]
    2008 R2 Result
    3029520.583895
    2012 Result
    3029520.58389499
    Rate column is float data type Length 8, Precision 53, Scale is null
    Please suggest if any work around for this.

    Hello,
    Does changing the underlying data to decimal possible? Instead of using float. Please try that.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Migrating database from windows to linux using dbca templates

    Hi every one,
    Is it possible to migrate Oracle10g database from Windows to Linux by using DBCA templates?????????????
    If yes please guide me, as i tried it and am getting error while creating database on linux using DBCA templates of Windows server.
    Warm regards,
    Veeresh.S
    (Oracle DBA)

    With DBCA you can create a new database, delete a database, create ASM, and manage templates.
    There's no option of migrating a database from one platform to the other. If you want to migrate your database from Windows to Linux you have 2 ways of doing it:
    1 using IMP/EXP Export you db on windows and Import it on Linux.
    2 Use across platform transportable tablespace if you db is already on 10g.
    Regards,
    Tony

  • Migrating database from 10g to 11g

    Hi gurus,
    how we can migrate the database from 10gr2 to 11gr2 using rman.
    thank you!

    Pl see these MOS Docs
    Upgrading Database Version Online Using Streams and RMAN [ID 782444.1]
    RMAN Restore of Backups as Part of a Database Upgrade [ID 790559.1]
    The recommended method is to use DBUA as outlined in the link posted above
    HTH
    Srini

  • Migrating database from solaris to linux

    I am not sure if there is a migration section here. However, I would like to migrate a 9.2.0.8 database from Solaris to linux and upgrade it to 11g. I reckon that both platforms have different endian format and using rman convert+transportable database and so on will be work if I can upgrade the database to 10 or 11g.
    My question is that since the database is small around 35GB, can I use just exp/imp? If yes but can someone outline what will be needed to take care of the endian format and other hidden hints.
    I believe someone must have done this ------> 9i to 10g or 9i to 11g across platform.
    Thanks.

    It just depends on what how you define 'large'. Generally speaking exp/imp is slow when compared to Data Pump or transportable tablespaces (but both cannot be used in your case).
    I don't think that 16 GB is large but you have to test in your environment how much time import is going to take: import needs always more time than export.

  • Migrating database from windows to unix

    Can anyone, please suggest me some reading on migrating a database from windows to unix? Thanks

    Yes an export import is the most likely migration path you have. There is another option. You may install, just temporarily a 10g environment on the windows platform, then upgrade using the DBUA from 8i to 10g on the same platform. This way you will make sure you don't miss a piece of data during the migration process.
    Once your database is at the 10g platform, you may proceed with a transport tablespace from 10g win to 10g unix. Violà, your database will be on the 10g platform.
    Next, deinstall the windows temporary 10g installation.
    Notes:
    1. Make sure your 8i db is at the latest patchset available at 8i (8.1.7.4.0)
    2. Define which unix platform you are referring to. It's because of endian issues.
    ~ Madrid.

  • Migrate database from UTF-8 to AL32UTF8

    We've heard that support for the UTF-8 characterset is going to peter out. Our databases are all in the UTF-8 characterset, so we are considering migrating to AL32UTF8. Any issues we need to consider, or is it simply a case of switching the database characterset? The globalization whitepapers I've read don't seem to address this kind of migration.

    Doc ID: Note:123670.1
    Subject: Use Scanner Utility before Altering the Database Character Set
    Type: BULLETIN
    Status: PUBLISHED
    Content Type: TEXT/PLAIN
    Creation Date: 02-NOV-2000
    Last Revision Date: 30-OCT-2003
    A) Purpose. ----------- Before altering the character set of a database, check the convertibility of the data before converting. Character set conversions can cause data loss or data corruption. The Character Set Scanner utility provides this 2 features: 1) convertibility check of existing data and potential issues. The Scanner checks all character data in the database including the data dictionary and tests for the effects and problems of changing the character set encoding (characterset). At the end of the scan, it generates a summary and exception report of the database scan. 2) from csscan V1.1 onwards it allows you also to do a check if there is no data in the database that is incorrectly stored. This is used in [NOTE:225938.1] Database Character Set Healthcheck This note gives an example on how the output of the csscan tool looks like and some live examples of how to convert the characterset. Please use the following note: [NOTE:225912.1] Changing the Database Character Set - an Overview as a complete guide to plan the change of the database character set. B) Installation and setup. -------------------------- IMPORTANT: Check for the latest version on technet of the csscan tool for your platform: http://technet.oracle.com/software/tech/globalization/content.html and use this. ( [NOTE:179843.1] Versioning of the Character Set Scanner ) There is one know problem with the characterset scanner for 817: see [BUG:3043474] To install the Character Set Scanner, you must have DBA privileges on the Oracle database. If you encounter "CSS-0xxxx" type errors, first look in the "Character Set Scanner Error Messages " section of above docset. Run csminst.sql to create the needed user and tabels, You can modify the default tablespace for CSMIG by editing the csminst.sql script. Modify the following statement in csminst.sql to assign your preferred tablespace to CSMIG as follows: ALTER USER csmig DEFAULT TABLESPACE tablespace_name; Then run csminst.sql using these commands and SQL statements: cd $ORACLE_HOME/rdbms/admin set oracle_sid=<your SID> sqlplus "system/manager" SQL>spool csminst.log SQL> START csminst.sql check the csminst.log for errors. or for 9i: cd $ORACLE_HOME/rdbms/admin set oracle_sid=<your SID> sqlplus "/ as sysdba" SQL>spool csminst.log SQL> START csminst.sql check the csminst.log for errors. [NOTE:232242.1] Character set migration utility schema not installed in 9i / ORA-942 during csminst.sql Now you can run the scanner against this database. C:\>csscan help=y gives the help screen, we will show here some sample outputs of full database scans using the command line. See also Chapter 11 "Character Set Scanner" of the Oracle9i Database Globalization Support Guide Release 2 (9.2) Part Number A96529-01 C) Character Set Scanner Compatibility. --------------------------------------- see [NOTE:179843.1] Versioning of the Character Set Scanner D) There are 3 possible conversion statuses possible ---------------------------------------------------- *** ***************** *** Scanner statuses *** ***************** The Scanner utility reports 3 types of conversion status for each table and row: 1/ CHANGELESS which leads to consider that the object needs no conversion, the codepoint dous not change between the two charactersets for those characters. 2/ CONVERTIBLE which leads to consider that the object needs conversion by export/import. (the target charactersets is NO binary superset of the source characterset) The character itself is know in both charactersets but has another codepoint This is why the ALTER DATABASE CHARACTER SET <new_character_set>; command is enforcing that the NEW characterset needs to be a BINARY superset of the old one. So you wan't be allowed to use ALTER DATABASE CHARACTER SET <new_character_set>; 3/ EXCEPTIONAL which leads to consider that the data needs manual updates before conversion or that you have invalid data in the database. Note that the scanner cannot "see" what type of character is stored. It can only compare codepoints and look them up in in the characterset conversion lists of oracle. The scanner checks if in the target characterset the codepoint of the source characterset is a valid codepoint, or that there are mappings to another codepoint it has no knowlegde of the character it suppose to represent. This is a problem if you have stored incorrect data in the database by bypassing the NLS layers. But normally this will lead to the reporting of exceptional data. This information is clearly reported in the 2 following reports automatically generated by the Scanner utility. *** *********************************** *** Reports SCAN.TXT and SCAN.ERR *** *********************************** 1/ SCAN.TXT => objects in the data dictionary requiring an action such as renaming a table => application data requiring an action such exporting/importing data to be converted, updating data, rebuilding indexes, modifying column sizes Example [Data Dictionary Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- -------------- VARCHAR2 608,343 0 1 608,344 CHAR 2 0 0 2 LONG 29,756 0 0 29,756 CLOB ---------------- -------------- -------------- -------------- -------------- Total 638,101 0 1 638,102 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- -------------- VARCHAR2 16 0 0 16 CHAR 2 1 1 4 LONG 0 0 0 0 CLOB 0 0 0 0 ---------------- -------------- -------------- -------------- -------------- Total 18 1 1 20 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional ----------------------------------------- ---------------- ---------------- SYS.OBJ$ 0 1 U1.T_EXCEPTIONAL 0 1 U1.T_CONVERTIBLE 1 0 ----------------------------------------- ---------------- ---------------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional ----------------------------------------- ---------------- ---------------- SYS.OBJ$|NAME 0 1 U1.T_EXCEPTIONAL|C1 0 1 U1.T_CONVERTIBLE|C1 1 0 ----------------------------------------- ---------------- ---------------- [Indexes to be Rebuilt] USER.INDEX on USER.TABLE(COLUMN) ---------------------------------------------------------------------------- SYS.I_OBJ2 on SYS.OBJ$(NAME) U1.I_T_CONVERTIBLE on U1.T_CONVERTIBLE(C1) --------------------------------------------------------------------------- 2/ SCAN.ERR => lists rowids of rows for which data is to be updated because of an EXCEPTIONAL status Example User : SYS Table : OBJ$ Column: NAME Type : VARCHAR2(30) Number of Exceptions : 1 Max Post Conversion Data Size: 33 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAASAABAAAAXjABF exceed column size 33 table_M-H_gM-Erer_drM-Bles_franM-5ais ------------------ ------------------ ----- ------------------------------ User : U1 Table : T_EXCEPTIONAL Column: C1 Type : CHAR(12) Number of Exceptions : 1 Max Post Conversion Data Size: 24 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAxDAAFAAAABDAAA exceed column size 24 M-EM-IM-HM-KM-LM-]M-NM-OM-AM-BM-QM-@ ------------------ ------------------ ----- ------------------------------ *** *************************** *** 3 statuses => 3 approaches *** *************************** 1/ When objects are in CHANGELESS status, they need not be converted. Issue the ALTER DATABASE CHARACTER SET statement on the database. This is possible when, and only when, the new character set is a strict superset of the current character set. 2a/ When a lot of objects are in CONVERTIBLE status, the data can be converted, and must be converted by Export: FULL Export + creation of a new database + FULL Import 2b/ When the database is large and only a few tables are in CONVERTIBLE status, whereas all the others are CHANGELESS, prefer the following method: Export selected tables + ALTER DATABASE CHARACTER SET if possible + Import the selected convertible tables (import will convert appropriately) 3/ However, if there are some cases in EXCEPTIONAL status reported, these exceptions must be handled one by one, and fixed first before using any of the above methods to do the conversions. This involves modifying data and/or modify structures to eliminate those exceptions. Again, see [NOTE:225912.1] Changing the Database Character Set - an Overview for more info en on how to deal with exceptional data. E) This are some sample outputs and live examples: -------------------------------------------------- *** Test1 on a WE8ISO8859P9 character set database to be converted to UTF8 1/ Create 4 tables : Table "table_� _gérer_drôles_français": table name is to be converted Table T_STANDARD: no data change required Table T_CONVERTIBLE: data are to be converted Table T_EXCEPTIONAL: data are to be updated before conversion $ NLS_LANG=american_america.WE8ISO8859P9 SQL> connect u1/u1 Connected. SQL> create table "table_� _gérer_drôles_français" (c1 char(16)); Table created. SQL> insert into "table_� _gérer_drôles_français" values ('A'); 1 row created. SQL> create table T_STANDARD (c1 char(12)) ; Table created. SQL> insert into T_STANDARD values ('aeiouaieou'); 1 row created. SQL> create table T_CONVERTIBLE (c1 CHAR(12)); Table created. SQL> create index i_t_convertible on t_convertible(c1) ; Index created. SQL> insert into T_CONVERTIBLE values ('éè� '); 1 row created. SQL> create table T_EXCEPTIONAL (c1 char(12)); Table created. SQL> insert into T_EXCEPTIONAL values ('éè� ùäöüêôîâ'); 1 row created. SQL> select * from T_EXCEPTIONAL; C1 ------------ éè� ùäöüêôîâ SQL> commit; Commit complete. 2/ Run the Character Set Scanner utility to provide report. ----------------------------------------------------------- Before running csscan, be aware of the following parameters: CAPTURE=Y records the ROWID for each cell of data that is problematic; use it only when there are small amounts of problem data because it might "flood" the database if lots of problematic data is expected. The ARRAY and PROCESS parameters for large databases are vital: * ARRAY can be set to a size in bytes which best represents the available real memory at scanner run time; the higher the better. * PROCESS spawns a process for parallel scanning and should be set to the number of available CPU's on the system which is hosting the database. $ csscan system/manager FULL=Y FROMCHAR=WE8ISO8859P9 TOCHAR=UTF8 CAPTURE=Y Character Set Scanner: Release 8.1.7.0.0 - Production on Thu Nov 9 10:36:15 2000 (c) Copyright 2000 Oracle Corporation. All rights reserved. Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production With the Partitioning option JServer Release 8.1.7.0.0 - 64bit Production Enter array fetch buffer size: 10240 > Enter number of scan processes to utilize(1..32): 1 > 4 Enumerating tables to scan... . process 1 scanning SYS.SOURCE$[AAAABAAABAAAADAAAA] . process 2 scanning SYS.SOURCE$[AAAABAAABAAAA8/AAA] . process 3 scanning SYS.TAB$ ...... . process 4 scanning U1.T_EXCEPTIONAL . process 4 scanning U1.table_� gérerdrôles_français . process 4 scanning U1.T_STANDARD . process 4 scanning U1.T_CONVERTIBLE . process 4 scanning SYS.SYN$ .... . process 3 scanning SYS.FILE$ Creating Database Scan Summary Report... Creating Individual Exception Report... Scanner terminated successfully. 3/ Examine the 2 provided reports : scan.txt and scan.err. ---------------------------------------------------------- Report scan.txt --------------- Database Scan Summary Report ... [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 Exceptional Total ---------------- -------------- -------------- -------------- ---------------- VARCHAR2 608,343 0 1 608,344 CHAR 2 0 0 2 LONG 29,756 0 0 29,756 ---------------- -------------- -------------- -------------- ---------------- Total 638,101 0 1 638,102 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- ---------------- VARCHAR2 18 0 0 18 CHAR 1 1 1 3 LONG 0 0 0 0 ---------------- -------------- -------------- -------------- ---------------- Total 19 1 1 21 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional -------------------------------------------- ---------------- ---------------- SYS.OBJ$ 0 1 U1.T_CONVERTIBLE 1 0 U1.T_EXCEPTIONAL 0 1 -------------------------------------------- ---------------- ---------------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional -------------------------------------------- ---------------- ---------------- SYS.OBJ$|NAME 0 1 U1.T_CONVERTIBLE|C1 1 0 U1.T_EXCEPTIONAL|C1 0 1 -------------------------------------------- ---------------- ---------------- [Indexes to be Rebuilt] USER.INDEX on USER.TABLE(COLUMN) ------------------------------------------------------------------------------ SYS.I_OBJ2 on SYS.OBJ$(NAME) U1.I_T_CONVERTIBLE on U1.T_CONVERTIBLE(C1) ------------------------------------------------------------------------------ Report scan.err --------------- Database Scan Individual Exception Report ... [Application data individual exceptions] User : SYAR2(30) Number of Exceptions : 1 Max Post Conversion Data Size: 33 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAASAABAAAAXjABF exceed column size 33 table_M-H_gM-Erer_drM-Bles_franM-5ais ------------------ ------------------ ----- ------------------------------ User : U1 Table : T_EXCEPTIONAL Column: C1 Type : CHAR(12) Number of Exceptions : 1 Max Post Conversion Data Size: 22 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAxDAAFAAAABDAAA exceed column size 22 M-EM-IM-HM-KM-LM-NM-OM-AM-BM-QM-@ ------------------ ------------------ ----- ------------------------------ 4/ Actions to take before character set conversion. --------------------------------------------------- a/ The table named "table_� _gérer_drôles_français" needs to be recreated with another name. SQL> alter table "table_� _gérer_drôles_français" rename to table_a_gerer_droles_francais; Table altered. b/ Export table U1.T_CONVERTIBLE: $ NLS_LANG=american_america.WE8ISO8859P9 $ exp userid=U1/U1 tables=T_CONVERTIBLE . . exporting table T_CONVERTIBLE 1 rows exported Export terminated successfully without warnings. c/ Since the exception refers to a too small column size, enlarge the column size of U1.T_EXCEPTIONAL.C1: SQL> alter table t_exceptional modify (c1 char(24)); Table altered. 5/ Perform another scan check before character set conversion. -------------------------------------------------------------- $ csscan system/manager FULL=Y FROMCHAR=WE8ISO8859P9 TOCHAR=UTF8 CAPTURE=Y => reports scan.txt: Datatype Changeless Convertible Exceptional Total --------------- -------------- -------------- ---------------- ---------------- VARCHAR2 608,344 0 0 608,344 CHAR 2 0 0 2 LONG 29,756 0 0 29,756 --------------- -------------- -------------- ---------------- ---------------- Total 638,102 0 0 638,102 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- ---------------- -------------- -------------- ---------------- VARCHAR2 18 0 0 18 CHAR 1 2 0 3 LONG 0 0 0 0 ---------------- ---------------- -------------- -------------- ---------------- Total 19 2 0 21 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional ---------------------------------------------- ---------------- ---------------- U1.T_CONVERTIBLE 1 0 U1.T_EXCEPTIONAL 1 0 ---------------------------------------------- ---------------- ---------------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional ---------------------------------------------- ---------------- ---------------- U1.T_CONVERTIBLE|C1 1 0 U1.T_EXCEPTIONAL|C1 1 0 ---------------------------------------------- ---------------- ---------------- => in scan.err, no more exception 6/ Last actions to take before character set conversion ------------------------------------------------------- Export table U1.T_EXCEPTIONAL: $ exp U1/U1 tables=T_CONVERTIBLE,T_EXCEPTIONAL Export: Release 8.1.7.0.0 - Production on Thu Nov 9 13:06:53 2000 About to export specified tables via Conventional Path ... . . exporting table T_CONVERTIBLE 1 rows exported . . exporting table T_EXCEPTIONAL 1 rows exported Export terminated successfully without warnings. 7/ Perform character set conversion ------------------------------------ Follow the steps in: [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set but you will get: SQL> alter database character set UTF8; alter database character set UTF8 * ERROR at line 1: ORA-12712: new character set must be a superset of old character set Since the character set UTF8 is not allowed in alter database, use FULL EXPORT , recreate the database with UTF8 character set, FULL IMPORT. See [NOTE:15095.1] Export/Import and NLS Considerations for more info on these steps. 8/ Actions to take after character set conversion. -------------------------------------------------- a/ Check the imported data of tables U1.T_CONVERTIBLE and U1.T_EXCEPTIONAL: Import: Release 8.1.7.0.0 - Production on Thu Nov 9 14:27:54 2000 import done in WE8ISO8859P9 character set and US7ASCII NCHAR character set import server uses UTF8 character set (possible charset conversion) . importing U1's objects into U1 . . importing table "T_CONVERTIBLE" IMP-00019: row rejected due to ORACLE error 1401 IMP-00003: ORACLE error 1401 encountered ORA-01401: inserted value too large for column Column 1 éè� 0 rows imported . . importing table "T_EXCEPTIONAL" IMP-00019: row rejected due to ORACLE error 1401 IMP-00003: ORACLE error 1401 encountered ORA-01401: inserted value too large for column Column 1 éè� ùäöüêôîâ 0 rows imported See [NOTE:119119.1] UTF8 Database Character Set Implications section "2.2.1 Example Export / Import into a UTF-8 Database" why this happens. b/ Change the column width of the tables and reimport the data: SQL> alter table U1.T_CONVERTIBLE modify (C1 CHAR(16)); Table altered. SQL> alter table U1.T_EXCEPTIONAL modify (C1 CHAR(36)); Table altered. $ imp U1/U1 FULL=Y IGNORE=Y Import: Release 8.1.7.0.0 - Production on Thu Nov 9 14:23:18 2000 import done in WE8ISO8859P9 character set and US7ASCII NCHAR character set import server uses UTF8 character set (possible charset conversion) . importing U1's objects into U1 . . importing table "T_CONVERTIBLE" 1 rows imported . . importing table "T_EXCEPTIONAL" 1 rows imported Import terminated successfully without warnings. c/ Check integrity for all CONVERTIBLE and EXCEPTIONAL objects: SQL> select * from U1.TABLE_A_GERER_DROLES_FRANCAIS; C1 ---------------- A SQL> select * from U1.T_CONVERTIBLE; C1 ---------------- éè� SQL> select * from U1.T_EXCEPTIONAL; C1 ------------------------------------ éè� ùäöüêôîâ *** on an US7ASCII database containing WE8ISO8859P1 characters *** to be altered to WE8ISO8859P9 Steps 1 and 2 are identical 3/ Run the Character Set Scanner utility to provide report. ----------------------------------------------------------- The database is US7ASCII but contains some WE8ISO8859P1 characters; then by setting FROMCHAR=WE8ISO8859P1, the scanner treats all cells as if they are from WE8ISO8859P1 and gives a more acurate result. $ csscan USERID=system/manager FULL=Y CAPTURE=Y FROMCHAR=WE8ISO8859P1 TOCHAR=WE8ISO8859P9 ...... . process 4 scanning U1.table_� gérerdrôles_français . process 4 scanning U1.T_STANDARD . process 4 scanning U1.T_CONVERTIBLE . process 4 scanning U1.T_EXCEPTIONAL ......t... Creating Individual Exception Report... Scanner terminated successfully. $ 4/ Examine the 2 provided reports : scan.txt and scan.err. ---------------------------------------------------------- Report scan.txt --------------- Database Scan Summary Report [Data Dictionary Conversion Summary] Datatype Changeless Convertible Exceptional Total --------------- -------------- -------------- -------------- -------------- VARCHAR2 608,314 0 0 608,314 CHAR 2 0 0 2 LONG 29,754 0 0 29,754 --------------- -------------- -------------- -------------- -------------- Total 638,070 0 0 638,070 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- -------------- VARCHAR2 14 0 0 14 CHAR 4 0 0 4 LONG 0 0 0 0 ---------------- -------------- -------------- -------------- -------------- Total 18 0 0 18 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional ---------------------------- ------------ ----------- ---------------------------- ------------ ----------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional ---------------------------- ------------ ----------- ---------------------------- ------------ ----------- [Indexes to be Rebuilt] USER.INDEX on USER.TABLE(COLUMN) -------------------------------------------------- -------------------------------------------------- Report scan.err --------------- Database Scan Individual Exception Report [Application data individual exceptions] 5/ Actions to take before character set conversion. --------------------------------------------------- In this case, execute the ALTER DATABASE CHARACTER SET which does not change the actual character codes, but only changes the character set declaration. To prevent any possible data loss, perform a FULL database backup before altering the database character set. 6/ Perform character set conversion. ------------------------------------ Follow the steps in: [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set 7/ Actions to take after character set conversion. -------------------------------------------------- Check integrity for all EXCEPTIONAL objects: SQL> select * from U1."table_� _gérer_drôles_français"; C1 ---------------- A SQL> select * from U1.T_CONVERTIBLE; C1 ------------ éè� SQL> select * from U1.T_EXCEPTIONAL; C1 ------------ éè� ùäöüêôîâ RELATED DOCUMENTS ----------------- [NOTE:15095.1] Export/Import and NLS Considerations [NOTE:119119.1] UTF8 Database Character Set Implications [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set [NOTE:119119.1] UTF8 database character set implications [BUG:1611255] CHARACTER SET SCANNER GETS SEGMENTATION FAULT WHEN ARRAY AND PROCESS ARE LARGE [NOTE:232242.1] Character set migration utility schema not installed in 9i / ORA-942 during csminst.sql
    Joel P�rez

Maybe you are looking for

  • Inits

    Hi, What is diff between init without data transfer and init with data transfer? What are the benefits? Can anybody exlain in detail? Thanks

  • Are the dimensions of a 2014 macbook air the same as the 2012 model?

    I want to buy a full body protector for my 2014 macbook air  but the only one advertised on a particular website I'm looking is for the 2012 model. Will it fit?

  • How to delete derivation rule - COPA (KEA5)

    Hi All, Could you please inform me how to delete derivation rule(COPA_KOSTL) in  KEA5 transaction code ? when we try to delete the system displaying  the following message : Message No K6430 Diagnosis you are trying to delete a field delivered by SAP

  • Time dependent HR master data question

    Hello, I want to compare the two records ( Current record with the  most recent delimited record) for pay rate for an employee. 0EMPLOYEE does not have DATETO or DATEFROM in its attribute list. Furthermore, I can not add DATETO as an attribute since

  • Photoshop Files Displayed in FCE

    When I import layered Photoshop files into FCE to be used in a slideshow, they appear compressed at the sides, whereas jpegs display normally (both are sized 4:3). That being said, when I save the very same Photoshop files as jpegs and import them in