Troubleshooting in Oracle Data Migration:

Troubleshooting in Oracle Data Migration:

1, after the data migration, there is garbled problem

Resolution process

A, use SELECT * from nls_database_parameters; command to view the character set in the source library, what the content might be. (This failure is resolved according to the following character set contents)

Sql> select * from Nls_database_parameters;

......

......

Nls_nchar_characterset

Al16utf16

Nls_language

AMERICAN

PARAMETER

-------------------------------

Nls_numeric_characters

.,

Nls_characterset

Zhs16gbk

Nls_calendar

Gregorian

PARAMETER

------------------------------

......

B. You can select the ZHS16GBK, Simplified Chinese character set in the installation DB instance.

C. Before exporting the data, use the following command in the shell first

Export Nls_lang=american_america. Zhs16gbk

Echo $NLS _lang

D, after executing the command in step c, then use exp to back up the data.

E. Execute the following command in the shell before importing the data to the new Oracle database.

export Nls_lang=american_america. Zhs16gbk

Echo $NLS _lang

F, execute the command in E, and then execute the IMG Import command

#####################################################################

2. The following error occurred in the Import database:

Fault Type 1,

Imp-00017:following statement failed with ORACLE error 1917:

"GRANT SELECT on" Commentd "to" Portal3_interaction ""

Imp-00003:oracle Error 1917 encountered

Ora-01917:user or role ' portal3_interaction ' does not exist

According to the above tips, it is easy to know that there is no portal3_interaction this user, so use the following command to create the user.

Create user portal3_interaction identified by portal3_interaction;

Grant CONNECT,RESOURCE,DBA to Portal3_interaction;

######################################

Fault Type 2,

Imp-00017:following statement failed with ORACLE error 1917:oms_source

"GRANT SELECT on" Content_dispatch "to" Content_stats ""

Imp-00003:oracle Error 1917 encountered

Ora-01917:user or role ' content_stats ' does not exist

According to the above fault hint: you can know that there is no content_stats this table space in the database.

Create tablespace content_stats logging datafile '/data/oracle/app/oradata/content_stats.dbf ' size 5000m autoextend on n Ext 5000m MaxSize Unlimited;

Note that the above command can resolve the current failure, but you may also continue to be prompted below that you have not created another tablespace.

Therefore, it is better to use the following command to see what table space exists in your source library, and then use the table space at once to create the above command, and then restore.

Select Name,status from V$datafile;

######################################

Fault Type 3,

Imp-00058:oracle Error 1691 encountered

Ora-01691:unable to extend LOB segment oms_basic. sys_lob0000067310c00011$$ by 1024x768 in Tablespace oms_basic

Imp-00018:partial Import of previous table completed:17188 rows imported

Imp-00017:following statement failed with ORACLE error 1658:

"CREATE INDEX" idx_tplcheck_fld "On" Template_check "(" tpl_fld_id ") Pctfre"

"E Initrans 2 Maxtrans 255 STORAGE (INITIAL 3145728 freelists 1 FREELIST G"

"Roups 1 buffer_pool DEFAULT" tablespace "Oms_basic" LOGGING "

Based on the above fault tip: You can know that this is due to a ORA-01691 error because tablespace cannot allocate new space to the table.

There are two possible reasons for this failure.

The first: The DataFile file is set to size, and the settings do not automatically grow. That is, the table space is created with the following type of command.

Create tablespace oms_basic logging datafile '/data/oracle/app/oradata/oms_basic.dbf ' size 5000m;

The second type: DataFile is set to the size, and is set to auto-grow, has reached the maximum of 32G file limit.

Create tablespace oms_basic logging datafile '/data/oracle/app/oradata/oms_basic.dbf ' size 5000m autoextend on next 5000m MaxSize Unlimited;

Workaround:

For the first reason. Our solution is to use the following command to let the database tablespace grow automatically

Create tablespace oms_basic logging datafile '/data/oracle/app/oradata/oms_basic.dbf ' size 5000m autoextend on next 5000m MaxSize Unlimited;

For the second reason. We can add several new data files to the table space.

Alter tablespace oms_basic add datafile '/data/oracle/app/oradata/oms_basic_01.dbf ' SIZE 1000M autoextend on NEXT 100M MAX SIZE UNLIMITED;

Alter tablespace oms_basic add datafile '/data/oracle/app/oradata/oms_basic_02.dbf ' SIZE 1000M autoextend on NEXT 100M MAX SIZE UNLIMITED;

This article is from the "Struggle Bar" blog, please be sure to keep this source http://lvnian.blog.51cto.com/7155281/1707968

Troubleshooting in Oracle Data Migration: