Home » RDBMS Server » Server Administration » Why does a database imported from a production dump not have the same csscan as the original db (11.2.0.3 SE, SLES 11)
Why does a database imported from a production dump not have the same csscan as the original db [message #626474] Tue, 28 October 2014 05:53 Go to next message
juniordbanewbie
Messages: 250
Registered: April 2014
Senior Member
Hi,

I've a production db having the following character set

SYS@orcl1>select * from gv$nls_parameters where parameter='NLS_CHARACTERSET';

   INST_ID PARAMETER
---------- ----------------------------------------------------------------
VALUE
----------------------------------------------------------------
         1 NLS_CHARACTERSET
WE8MSWIN1252


I have a dev db having the following character set


SYS@nowatz1>select * from gv$nls_parameters where parameter='NLS_CHARACTERSET';

   INST_ID PARAMETER
---------- ----------------------------------------------------------------
VALUE
----------------------------------------------------------------
         1 NLS_CHARACTERSET
WE8MSWIN1252

         2 NLS_CHARACTERSET
WE8MSWIN1252



for nowatz db the partial csscan.txt is as follow

Data Dictionary Tables:

Datatype                    Changeless      Convertible       Truncation            Lossy
--------------------- ---------------- ---------------- ---------------- ----------------
VARCHAR2                     4,741,147                0                0                0

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

The data dictionary can be safely migrated using the CSALTER script


for orcl partial cscan.txt output will be

Datatype                    Changeless      Convertible       Truncation            Lossy
--------------------- ---------------- ---------------- ---------------- ----------------
VARCHAR2                    21,263,330                1                0                0

The data dictionary can not be safely migrated using the CSALTER script


So Why does a database imported from a production dump not have the same csscan.txt as the original db? More importantly is using the proper rman backup and restore techniques the only way to guarantee that the auxiliary database will face the same character set problem as the source.

thanks a lot!

[Updated on: Tue, 28 October 2014 06:04]

Report message to a moderator

Re: Why does a database imported from a production dump not have the same csscan as the original db [message #626477 is a reply to message #626474] Tue, 28 October 2014 06:15 Go to previous messageGo to next message
Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator

First ideas:
* you imported in a not empty database
* you have not the same nls_length_semantics parameter value

Quote:
More importantly is using the proper rman backup and restore techniques the only way to guarantee that the auxiliary database will face the same character set problem as the source.


I think so.

Report message to a moderator

Re: Why does a database imported from a production dump not have the same csscan as the original db [message #626553 is a reply to message #626477] Wed, 29 October 2014 00:29 Go to previous messageGo to next message
juniordbanewbie
Messages: 250
Registered: April 2014
Senior Member
for orcl

SYS@orcl1>

SYS@orcl1>select * from gv$nls_parameters where parameter='NLS_LENGTH_SEMANTICS';

   INST_ID PARAMETER
---------- ----------------------------------------------------------------
VALUE
----------------------------------------------------------------
         1 NLS_LENGTH_SEMANTICS
BYTE


for nowatz

SYS@nowatz>select * from gv$nls_parameters where parameter='NLS_LENGTH_SEMANTI
CS';

   INST_ID PARAMETER
---------- ----------------------------------------------------------------
VALUE
----------------------------------------------------------------
         2 NLS_LENGTH_SEMANTICS
BYTE

         1 NLS_LENGTH_SEMANTICS
BYTE


i.e they have same NLS_LENGTH_SEMANTICS, i.e. BYTES

so I don't get what you mean when you said you have not the same nls_length_semantics parameter value.

Report message to a moderator

Re: Why does a database imported from a production dump not have the same csscan as the original db [message #626555 is a reply to message #626553] Wed, 29 October 2014 01:43 Go to previous messageGo to next message
Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator

It was just a hint to check.
Then the other one: "you imported in a not empty database"?

Report message to a moderator

Re: Why does a database imported from a production dump not have the same csscan as the original db [message #626560 is a reply to message #626553] Wed, 29 October 2014 02:59 Go to previous messageGo to next message
juniordbanewbie
Messages: 250
Registered: April 2014
Senior Member
yes not a empty database.

I just use DBCA to create a database with same character set and import the production dump from the production db.

Report message to a moderator

Re: Why does a database imported from a production dump not have the same csscan as the original db [message #626562 is a reply to message #626560] Wed, 29 October 2014 03:22 Go to previous message
Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...
Senior Member
Account Moderator

So if you have not the same data in both databases how could you expect that the result of csscan will be the same one?

Report message to a moderator

Previous Topic: Job scheduler issue
Next Topic: ORA-00060: deadlock detected while waiting for resource
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Jan 02 17:35:37 CST 2025
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.