Export/Import full database dump fails to recreate the workspaces

Question

Hi,
We are studying the possibility of using Oracle Workspace to maintain multiple versions of our business data. I recently did some tests with the import/export of a dump that contains multiple workspaces. I'm not able to import the dump successfully because it doesn't recreate the workspaces on the target database instance, which is an empty Oracle database freshly created. Before to launch the import with the Oracle Data Pump utility, I have the "LIVE" workspace that exists in the WMSYS.WM$WORKSPACES_TABLE table. After the import is done, there is nothing in that table...
The versions of the Oracle database and Oracle Workspace Manager are the same on source and target database:
Database version (from the V$VERSION view):
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Workspace Manager version (from the WM_INSTALLATION view):
OWM_VERSION: 10.2.0.4.3
In order to recreate the tablespaces successfully during the full import of the dump, the directory structure for the tablespaces is the same on the target database's computer. I used the instructions given in this document, section "1.6 Import and Export Considerations" at page 1-19:
http://www.wyswert.com/documentation/oracle/database/11.2/appdev.112/e11826.pdf
Considering that the release of Oracle database used is version 10.2.0.4, I use the following command to import the dump since it doesn't contain the WMSYS schema:
impdp system/<password>@<database> DIRECTORY=data_pump_dir DUMPFILE=expfull.dmp FULL=y TABLE_EXISTS_ACTION=append LOGFILE=impfull.log
The only hints I have in the import log file are the following block of lines:
1st one:
==============================
Traitement du type d'objet DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Echec de la création du type d'objet PROCACT_SYSTEM avec erreur :
ORA-01843: ce n'est pas un mois valide
SQL en échec :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Traitement du type d'objet DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Echec de la création du type d'objet PROCACT_SCHEMA avec erreur :
ORA-20000: Workspace Manager Not Properly Installed
SQL en échec :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
The target operating system is in french... here is a raw translation:
1st one:
==============================
Treatment of object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39083: Object type creation failed PROCACT_SYSTEM with error :
ORA-01843: invalid month
failed SQL :
BEGIN
if (system.wm$_check_install) then
return ;
end if ;
begin execute immediate 'insert into wmsys.wm$workspaces_table
values(''LIVE'',
''194'',
''-1'',
2nd one at the end of the import process:
==============================
Treatment of object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type creation failed PROCACT_SCHEMA with error :
ORA-20000: Workspace Manager Not Properly Installed
failed SQL :
BEGIN
declare
compile_exception EXCEPTION;
PRAGMA EXCEPTION_INIT(compile_exception, -24344);
begin
if (system.wm$_check_install) then
return ;
end if ;
execute immediate 'alter package wmsys.ltadm compile';
execute immediate 'alter packag
By the way, the computer of the source database is Vista 64 in english and the destination computer is Vista 64 in french, do you think this has anything to do with these error messages? The parameters of the NLS_SESSION_PARAMETERS view are the same in the source and target database...
Thanks in advance for your help!
Joel Autotte
Lead Developer
Edited by: 871007 on Jul 13, 2011 7:31 AM

Answer 1

I tried to import the full database dump with the "imp" command and I had the same error message with more detail:
. Import d'objets SYSTEM dans SYSTEM
IMP-00017: Echec de l'instruction suivante avec erreur ORACLE 1843 :
"BEGIN "
"if (system.wm$_check_install) then"
" return ;"
" end if ;"
" begin execute immediate 'insert into wmsys.wm$workspaces_ta"
"ble"
" values(''LIVE'',"
" ''194'',"
" ''-1'',"
" ''SYS'',"
" *to_date(''09-DEC-2009 00:00:00'', ''DD-MON-YYYY HH"*
*"24:MI:SS''),"*
" ''0'',"
" ''UNLOCKED'',"
" ''0'',"
" ''0'',"
" ''37'',"
" ''CRS_ALLNONCR'',"
" to_date(''06-APR-2011 14:24:57'', ''DD-MON-YYYY HH"
"24:MI:SS''),"
" ''0'',"
" '''')'; end;"
"COMMIT; END;"
IMP-00003: Erreur ORACLE 1843 rencontrée
ORA-01843: ce n'est pas un mois valide
ORA-06512: à ligne 5
The call to the TO_DATE function with the string of the date format is incompatible with the format and language set in the NLS parameters of my database. Since I know that the "imp" and "exp" commands work client side (unlike "impdp" and "expdp"), I did a full export of the source database from the computer on which I try to import the dump to have the same language exported in the dump and I was able to import the dump successfully.
But, I would like to use the Data Pump tool instead of the old import and export tools. How would it be possible to set the NLS parameters that "impdp" must use before to launch the import of the dump?
The NLS parameters are set to the "AMERICAN" settings in both source and destination database when I validate that with the "NLS_DATABASE_PARAMETERS" view. The dump I did with "expdp" on the source database exported the data with the "AMERICAN" settings as well...
On the destination database, the computer language is in french and I guess it is considered by the Data Pump import tool since it outputs the log in the language of the computer and it tries to do a TO_DATE with the wrong date format because it works with the "CANADIAN FRENCH" settings...
Any suggestions? I'll continue to read on my side and re-post if I find the solution.
Thanks!
Edited by: 871007 on Jul 19, 2011 8:42 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM
Edited by: 871007 on Jul 19, 2011 8:43 AM