Perform the expdp (fulldb/schema/table) by using the ASM Storage

-
Perform the expdp (fulldb/schema/table) by using the ASM Storage

Step 1 - Create the Directory in ASM location (Example - +DATA/mir_exp)

[grid@asmdb ~]$ asmcmd

ASMCMD> ls
CRS/
DATA/
FRA/

ASMCMD> cd DATA

ASMCMD> mkdir mir_exp

ASMCMD> cd DATA

ASMCMD> ls

ASM/
ASMDB1/
bck/
mir_exp/

ASMCMD> exit

 Step 2: Create the directory & give the require privileges

SQL> create directory mir_exp as '+DATA/mir_exp';
Directory created.

SQL> grant read,write on directory mir_exp to system;
Grant succeeded.

SQL> grant exp_full_database to system;
Grant succeeded.

 Step 3: Execute the expdp

[oracle@asmdb ~]$ expdp system/(Password) directory=mir_exp dumpfile=mir.dmp logfile=mir.log schemas=mir

Export: Release 11.2.0.4.0 - Production on Wed Jan 25 12:23:33 2017
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation

 Once we get the above error – Try to use the default directory for the logfile (Default directory is data_pump_dir) or   An alternative option is to use the parameter nologfile=yes

[oracle@asmdb ~]$ expdp system/stmtasm directory=mir_exp dumpfile=mir.dmp logfile=data_pump_dir:mir.log schemas=mir

Export: Release 11.2.0.4.0 - Production on Wed Jan 25 12:25:47 2017
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_01":  system/******** directory=mir_exp dumpfile=mir.dmp logfile=data_pump_dir:mir.log schemas=mir
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 64 KB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TABLE/TABLE
. . exported "MIR"."TEST"                                5.132 KB      13 rows
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
  +DATA/mir_exp/mir.dmp
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully completed at Wed Jan 25 12:26:28 2017 elapsed 0 00:00:39

 Step 4: Verify the dumpfile in asm location:

[root@asmdb ~]# su - grid

[grid@asmdb ~]$ asmcmd

ASMCMD> ls

CRS/
DATA/
FRA/

ASMCMD> cd DATA

ASMCMD> ls
ASM/
ASMDB1/
bck/
mir_exp/

ASMCMD> cd mir_exp

ASMCMD> ls

 mir.dmp
Hence Tested in our ENV

Comments

Post a Comment

Popular posts from this blog

RAC Failure Scenario - Testing in our RAC Test DB - Node 1 & Node 2

-
RAC Failure Scenario - Testing in our RAC Test DB - Node 1 & Node 2 Testing Various RAC Failure scenario like: 1 - Node Failure 2 - DB Instance Failure 3 - ASM Instance Failure 4 - Listener failure 5 - Public Network Failure 6 - Private Network Failure 7 - OCR & Voting Disk Failure 8 - ASM Disk Failure ============== 1 - Node Failure ============== It can be planned, unplanned or all the nodes it could be any scenario Let us start the workload & shutdown the node The expected result will be: Resources will go offline Instance recovery will be performed Node vip & scan vip fail to surviving node Scan listener will fail over surviving node Client connection are moved to surviving instance Now shutdown Node 1 in OS Level intentionally or due to some reason the node 1 is shutdown #Shutdown –h now Check the node 2 status [oracle@test-rac2 ~]$ crs_stat -t Name           Type           Target    State     Host ----------------------------
Read more

ORA-01110: data file 1: '/oradata/datafiles/system01.dbf'

-
ORA-01110: data file 1: '/oradata/datafiles/system01.dbf' Error occur while restoring the database from the backup of RMAN RMAN> alter database open resetlogs; using target database control file instead of recovery catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of alter db command at 09/03/2017 16:05:14 ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/oradata/datafiles/system01.dbf' To resolve this error fallow the below procedure – Hopefully you will succeed If you’re primary database is flashback & it has the standby – Fallow below procedure RMAN> run { 2> recover database; 3> } ORA-00283: recovery session canceled due to errors RMAN-11003: failure during parse/execution of SQL statement: alter datab
Read more

Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4)

-
Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4) Export on 12c (12.1.0.2)   – Tested in our env : 10.20.0.82 ==================== SQL> select instance_name,version from v$instance; INSTANCE_NAME    VERSION ---------------- ----------------- ora12c           12.1.0.2.0 SQL> conn sys/sys as sysdba Connected. SQL> conn hassan/( password ); Connected. SQL> select table_name from user_tables; TABLE_NAME -------------------------------------------------------------------------------- TEST SQL> select * from test; COLUMN1              NAME -------------------- -------------------- 1                    abc 2                    xyz [oracle@ora12c u02]$ mkdir dump [oracle@ora12c u02]$ chmod -R 777 dump/ [oracle@ora12c u02]$ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Wed Jan 25 16:22:46 2017 Copyright (c) 1982, 2014, Oracle.  All
Read more