Tuesday, 21 June 2016

Datapump expdp error

[oracle@rac1 Desktop]$ expdp attach=j2
 
Export: Release 11.2.0.4.0 - Production on Tue Jun 21 23:27:01 2016Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Job: J2
  Owner: SYSTEM                        
  Operation: EXPORT                        
  Creator Privs: TRUE                          
  GUID: 35CE1BA27BA432CCE0530100007F9B40
  Start Time: Tuesday, 21 June, 2016 22:55:38
  Mode: FULL                          
  Instance: orcl1
  Max Parallelism: 1
  EXPORT Job Parameters:
  Parameter Name      Parameter Value:
     CLIENT_COMMAND        system/******** directory=datapump dumpfile=full.dmp logfile=full.log full=y job_name=j2
  State: EXECUTING                     
  Bytes Processed: 0
  Current Parallelism: 1
  Job Error Count: 0
  Dump File: /u02/datapump/full.dmp
    bytes written: 4,096
 
Worker 1 Status:
  Process Name: DW00
  State: EXECUTING                     
  Object Type: DATABASE_EXPORT/SCHEMA/TABLE/
POST_INSTANCE/PROCACT_INSTANCE
  Completed Objects: 61
  Total Objects: 61
  Worker Parallelism: 1

Export> stop_job
Are you sure you wish to stop this job ([yes]/no): yes

[oracle@rac1 Desktop]$ expdp attach=j2

Export: Release 11.2.0.4.0 - Production on Tue Jun 21 23:30:07 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Job: J2
  Owner: SYSTEM                        
  Operation: EXPORT                        
  Creator Privs: TRUE                          
  GUID: 35CE1BA27BA432CCE0530100007F9B40
  Start Time: Tuesday, 21 June, 2016 23:30:30
  Mode: FULL                          
  Instance: orcl1
  Max Parallelism: 1
  EXPORT Job Parameters:
  Parameter Name      Parameter Value:
     CLIENT_COMMAND        system/******** directory=datapump dumpfile=full.dmp logfile=full.log full=y job_name=j2
  State: IDLING                        
  Bytes Processed: 0
  Current Parallelism: 1
  Job Error Count: 0
  Dump File: /u02/datapump/full.dmp
    bytes written: 4,096
 
Worker 1 Status:
  Process Name: DW00
  State: UNDEFINED                  
   
Export> start_job
Export> exit
 
[oracle@rac1 Desktop]$
 
 
Question:  I am getting an ORA-39181 error when tying an export as the SYSTEM user. 
       ORA-39181: Only partial table data may be exported due to fine grain access control on "xxxxx"
How to fix this ORA-39181 error?
 
      Answer: The oerr utility show this for the ORA-39101 error:
Cause This is expected behavior. ORA-39181 is caused by an unprivileged user who tries to export a table with a fine grain access control policiy applied. The table owner is subject to access control and may not be able to export all rows in the table.
Action: Only the rows that can be seen by that user are exported. In order to preserve integrity of the table, the user importing the table should have enough privilege to recreate the table with the security policies at import time. Action: It is strongly recommended that the database administrator handles the export of this table.
This is an informational message and may be ignored.

It has a workaround of using the following gran statement:

GRANT EXEMPT ACCESS POLICY to System;
 

No comments:

Post a Comment

Optimizer Access Paths using Indexes

Introduction In this tutorial you will use the Optimizer Access Paths for the following cases (scenarios): Case 1: With and Without Index Ca...