Importing Full database wid Crrent production dumpfile on test Database

hi,
I have production database 9.2.0.4 on widows server.
I have Current Dumpfile of Production database.
I Have test Database on another server which is too 9.2.0.4 on windows server.
I need to Import full database on test Database with Current Production Dump file.
COuld u reply the complete procedure
I have tested on test Server But i am not getting all tables some tables are missing.
Thankx
Edited by: oradb on Nov 29, 2010 1:54 AM

which method are you using to take the dump ?
if you are using the imp/exp method ,
then simple create a parameter file with the following parameters :
indexes=y
rows=y
grants=y
buffer=500000
ignore=y
statistics=none
full=y
log=logfile.log
and then run the following command :
imp system/**** <parfilename>
Always refer to the logfile to see for successfull completion of the import.
hope this helps
- KKukreja-
that should help
Edited by: rattlesnake on Nov 29, 2010 3:15 AM

Similar Messages

Production vs. Testing Database

I double posted. Sorry.

JimKiser wrote:
> My local machine runs on Windows XP Pro SP2. I have PHP
5.1.6 and MySQL
> 5.0.24A installed and I am currently running IIS 5.1.
>
> The live site is running on "Windows NT WINHOST34 5.2
build 3790" and uses
> PHP.4.3.11 AND MySQL
That should be no problem. The code produced by Dreamweaver
MX 2004 is
compatible with both. However, the code created by the Log In
User
server behavior in MX 2004 breaks in recent versions of PHP.
I have
posted the workaround in the friends of ED forum at the
following address:
http://friendsofed.infopop.net/2/OpenTopic?a=tpc&s=989094322&f=8033053165&m=324102421
David Powers
Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
http://foundationphp.com/

Export/Import full database dump fails to recreate the workspaces

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

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

Importing full database and SYSTEM password

Hi,
I have a export dump of a database (full database dump). Want to import on my existing database.
I have create a database, with tablespaces matching names with source database (i.e. got a list of tablespaces from the dba of source database and created them). Now, I am ready to import with imp command (with FULL=Y option).
Will the full database import change my SYSTEM's password to the system's password on the source database ?
Reason for this question is, If you try to read the export of full database (using wordpad !!), you will find all commands creating tablespaces, users, roles etc etc etc. Also, you will see commands which alter the users SYS and SYSTEM to change the password !!!
Any past experiences ??
Thanks in advance.

Hi,
>>Will the full database import change my SYSTEM's password to the system's password on the source database ?
Yes, take a look at demonstration below:
C:\>exp system/pass file=test.dmp full=y statistics=none
Export: Release 10.2.0.1.0 - Production on Mon Apr 21 13:59:51 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases^C
C:\>findstr /C:"ALTER USER SYS" TESTE.DMP
ALTER USER SYS IDENTIFIED BY VALUES '5638228DAF52805F' TEMPORARY TABLESPACE "TEMP"
ALTER USER SYSTEM IDENTIFIED BY VALUES 'D4DF7931AB130E37' TEMPORARY TABLESPACE "TEMP"
Cheers
Legatti

Database refresh from production to test database

Dear All,
i want to refresh data on test database using production database.Test and production database has same backend structure.
i am using following steps.Please correct if i am wrong any where.
1)Take Full export from producion database
2)DROP SCHEMA ON test database.SKIP schema like sys,system and other oracle schemas.
3)do full import on test database.
is this correct way to refresh the data on other enviornmet.
Thanks.
rajesh

user12071799 wrote:
Dear All,
i want to refresh data on test database using production database.Test and production database has same backend structure.
i am using following steps.Please correct if i am wrong any where.
1)Take Full export from producion database
2)DROP SCHEMA ON test database.SKIP schema like sys,system and other oracle schemas.
3)do full import on test database.
is this correct way to refresh the data on other enviornmet.
Hi,
You can do one correction here :
Instead of taking full export backup , take export of only those schemas which you want to refresh.
You can use datapump to make it faster.
For improving speed please check
http://www.dba-oracle.com/oracle_tips_load_speed.htm
Regards
Rajesh

9i export file into 11GR2 - import full db or create users, roles.. first?

I'm moving several 9iR2 databases onto new hardware with 11GR2 64bit.
One of them has only a couple of users, roles etc. so I pre-create all the tablespaces, users, etc. then import with 11G imp utility using fromuser=user1,user2 etc. in the parfile.
Another has an application front end that creates a database user for all the application users, and assigns certain roles etc. So I have dozens of users on this database, along with various roles as well. I'm wondering what the best way to approach this one is, so I'm thinking:
Do I do a import full=y, and let the import create all the users roles etc. ? *I already pre-created all the tablespaces when I created the empty database with DBCA
Do I generate the ddl for all the users and roles, run it on the new db first, then import with fromuser=user1,user2..?
Do I import full=y for trial run, then when ready to import final production data, drop users that have data with cascade option, recreate these users and import their schemas only?
Keep in mind that I am doing several "rehearsals" on this, importing from full exp files on the current production database, for users to test the app against and also to debug my import commands,scripts etc. so this will be a one command process when I am ready to do the final import.
I'm asking all of this because I'm wondering if its just ok to do full=y when upgrading, (I usually don't)
I'm assuming all the system etc. tables in the 11G are just left alone when ignore=y parameter is used.

I tried importing the full database from the 11G gui's import from export files option, but it kept failing, so I imported just the schema's I wanted. That worked ok, and all the database users accounts and roles were also imported, not sure how that happened or if it was when I attempted the full import. In any case I got the database schemas I wanted over, but noticed a lot of invalid views that would not compile, so a further check showed that none of the applications public synonyms came over. Running a simple create script on dba_synonyms on the prod database fixed that and its all good now, but I'm wondering why the synonyms never came across with the import?

Is it possible to make PCTFREE 0 a database-wide default via init.ora ?

In our batch environment we drop/create lots of tables as follows - CREATE TABLE X NOLOGGING PCTFREE 0 PARALLEL AS SELECT .........
Since the tables get created from scratch every time and don't get updated - we use PCTFREE 0 to minimize space usage and speed up overall IO.
Today - we specify the PCTFREE 0 clause in every CTAS - so that Oracle won't use the default.
Is there a way to make the default "0" database wide so that we have one less clause to specify?
Thanks !

They really are Global Temporary Tables in functionality - they are part of a daily ETL cycle - but the users would like for them to stick around for 24 hours for "after the fact" analysis of issues - being able to step through table after table - long after the session / process are done. Hence - they are DROP/CREATed every day.
No - statistics aren't collected - it takes precious time. There are no indexes - so 99% of the time the tables are Full Table Scanned and the Hash Joined - which the optimizer is sensible enough to chose 99% of the time.
We run Nologging and NoArchivelogging - so we are spared the triple writes (Data/Log/arch) - so Billion row tables are ETLed very quickly on the modest hardware we can avail ourselves.
PCTFREE 0 saves space, reduces block count, and speeds up IO - and with tables DROP/CREATED it helps the cause.
Thanks for the tip about inheriting PCTFREE from the tablespace. I'll check it out.

Getting Error while importing FULL SLD in PRD Server

Hi Experts,
I am trying to import FULL SLD into Production server from QA server. I have exported full SLD from QA server and then try to import the same in the Production. But, while importing it gives me a warning "The selected ALL 1.0 full import belongs to the export line ALL which is not compatible with the export line(s) SAP_CR of previous imports. The data of the selected import may possibly interfere with the previously imported data."
And it shows two options: CANCEL IMPORT, IMPORT ANYWAY
**All the servers are on Xi 7.0 sp08
Kindly Help...

Hi Ajay,
These errors as mentioned are because of different CR versions and as mentioned in the blog:
1) the source system is not defined in the SLD 2) the target system is not defined in the SLD 3) the association already exist 4) the source system and the target system are in the system business system group
Regards
Vijaya

Insert into all tables on a Database on Test Server select from all tables on a database A from production server

hi Friends ,i need a suggestion from you on how to
insert data to all tables on a Database "A " on Test server
Select data from all tables on a Database "A" on Production Server
where id=123
Database A is same with Structures on Test and Production also all Tables will have Id column in common.
The purpose of this insert is ,as we all know Production has the latest data and i need to push to test server on request for particular ID only ( may be weekly once or twice a week )
I have a linked server setup name "LINQ"
Example for one table is below , like wise i need a script which does for 154 tables.
Insert into ABC( id, name)---insert to test server
Select Id, name from LINQ.ProdSerevrname.databasename.ABC where id = 123
Please help me ..
Thanks

Why not use export import wizard for this if you've read access to production?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Database refresh from production to test -how to clean existing test env

All,
My environment is
Both Production and Test databases are in two node RAC environment
Oracle version - 10.2.0.4.0
OS - RHEL5
Production database size 80GB
We need to refresh the test environment from production database. Complete objects, data etc should be refreshed.
We have a datapump export from production environment. With this export dump from production environment, I need to import into test environment.
So far, I have imported with this kind of dump to the fresh database only.
Now, we have already objects, data sitting in the test environment. How to clean the existing test environment and refresh the production datapump export dump.
I thought of dropping all the tablespaces in test (other than system,sysaux, undo and temp). But not able to drop few tablespaces, it is telling that index is available in other tablespaces, dependency errors etc.
Which is the best method to clean the existing test database. Management is not interested in dropping the test database and recreating it.

I understand that you are Newbie , let give me simple steps.
Follow the steps on testing envi.
1. Drop only Application users that you want to refresh from Prod(Do NOT drop users system,sysaux.. or tablespaces)
2. Create the users that you dropped.
3. using import or import data pump import the data.
In case you want to import user"A" data to "B" use REMAP_SCHEMA option.
See the below link for data pump export/import with examples.
http://oracleracexpert.blogspot.com/2009/08/oracle-data-pump-exportimport.html
Hope this helps.
Regards,
Satishbabu Gunukula
http://oracleracexpert.blogspot.com
Click here for [How to add and remove OCR|http://oracleracexpert.blogspot.com/2009/09/how-to-add-and-remove-ocr-oracle.html]
Click here in [ Making decisions and migrating your databases |http://oracleracexpert.blogspot.com/2009/08/download-sql-developer-migration.html]
Click here to lean [ Static parameters change in SPFILE and PFILE|http://oracleracexpert.blogspot.com/2009/09/how-to-change-static-parameters-in.html]
Edited by: Satishbabu Gunukula on Sep 14, 2009 5:09 PM
Edited by: Satishbabu Gunukula on Sep 18, 2009 10:35 AM

Migrating from Test Database to Production Database

Hi,
I have a situation where I created my Portal Pages on test database and now, I want to move everything from test database to my production database. The portal version on both the sites is same (3.0.9.8). I have content areas and applications in my existing test site. What is the best and easiest way to achieve this?
Thanks in advance.
Regards,
Jatinder

Hi,
the easiest way is to make an export of the portal schema en import it into you're production database.
greetings
<BLOCKQUOTE>quote:<HR>Originally posted by Jatinder:
Hi,
I have a situation where I created my Portal Pages on test database and now, I want to move everything from test database to my production database. The portal version on both the sites is same (3.0.9.8). I have content areas and applications in my existing test site. What is the best and easiest way to achieve this?
Thanks in advance.
Regards,
Jatinder<HR></BLOCKQUOTE>
null

Export full DB/Import full DB privilege

Hii,
How to grant export full database and import full database privilege to a user in 920720 DB.
SQL> grant export full database to almasar;
ORA-00990: missing or invalid privilege
But its working in 10.1.0.2.0
Thankx

Hi
What does catexp do? It "Creates internal views for Export/Import utility", says the script
Also, if I need to export import
just a few tables from another schema, do I still
need EXP_FULL_DATABASE and IMP_FULL_DATABASE role?Yes you need to have EXP_FULL_DATABASE and IMP_FULL_DATABASE role

Import Full Name and Emal Address

Hi,
I have successfully connected my BOE 3.1 to SAP and imported a role with 2,500 users.
The Account Names are successfully populated but the Full Name and Email fields are not. Further to this, if I click on any user, the "Import Full Name and Email Address" check box is actually disabled.
Is this a limitation of the integration kit?
Will it be supported soon?
Is there a work around such us a productivity pack where we can perform a bulk update via Excel and an API call?
Thanks,
Steve

While it is possible to include additional roles in SAP an import them, the preferred approach is to validate the users in SAP only and to use local groups and imported SAP users for internal application security so as not t clog up the SAP system with with security roles which don't apply to it.
Unfortunately, only the 8 digit SAP HR number is imported into BOE. Someone will now have to create an excel lookup spreadsheet for all users with their ESS number and full name, then manually add users to groups after looking refering to the excel spreadsheet for each name.
Also, in the future, publications will also need email addresses.
In R2, there was a migration / productivity pack where you could programatically add users to groups in bulk. This would assist us in adding SAP users to local BOE groups.
Cheers,
Steve

How to omport PLD from testing database to Production Database

i have designed PLD reports in testing database and now i want to import it to Production Database ? How should i do it ?

There are couple of ways to do this
Use Copy Express Addon of SAP to copy PLD from one DB to another.
Another way is to use SQL to copy from one DB to another.
I am not sure if the SAP still support the SQL way but I could give it to you and it will work.
insert into [TargetDB\].[dbo\].[RDOC\]
select [SourceDB\].[dbo\].[RDOC\].* FROM [SourceDB\].[dbo\].[RDOC\]
WHERE [SourceDB\].[dbo\].[RDOC\].DocCode = 'CHO10002'
insert into [TargetDB\].[dbo\].[RITM\]
select [SourceDB\].[dbo\].[RITM\].*
from [SourceDB\].[dbo\].[RITM\]
where [SourceDB\].[dbo\].[RITM\].DocCode = 'CHO10002' AND [SourceDB\].[dbo\].[RITM\].[Doccode\]
IN (SELECT Doccode from [SourceDB\].[dbo\].[RDOC\])
CHO10002 is shown as a sample DocCode. You can get the DocCode when you open the PLD in design mode and go to Print layout design menu on top and click on Display Document Properties - General tab
Let me know
Suda

Importing full schema except few tables

Hi all
I sthere any way to import full schema ,except few tables
in 9i.I want to import a full schema without few tables.I dont want to import later drop.Is there any way
with regards
ramya

You would have to provide the list of tables you do want to import at the command line in the TABLES argument.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Importing Full database wid Crrent production dumpfile on test Database

Similar Messages

Maybe you are looking for