• Blog
  • Get Help Now!
  • Customer Portal

BlueGecko Denmark

  • Why you need us
    • Why act now
    • Why are we unique
  • What we do
    • Products Supported 24/7
      • MySQL
      • Postgres
      • SQL Server
      • Open Source
      • OS & Storage
  • How we do it
    • Consulting
    • System Monitoring
    • Security
  • Support
    • Blog
      • Oracle
      • MySQL
      • News & Events
      • Oracle Applications
      • Amazon Web Services
      • Jeremiah Wilton’s Oradeblog
      • OurSQL Community Podcast
      • Remote DBA
    • Team viewer
    • Whitepapers
  • About Us
    • Philosophy
    • The Blue Gecko Teams
    • Employment Opportunities
    • Partners
    • News
    • Press
  • Contact Us

February 1, 2010 by cedwards

Oracle Correction to Export/Import

If you don’t get alerts regularly from Oracle Support you may have missed this notice:

If you conducted an import or export of an Oracle10g Release 2 or 11g Release 1 database prior to September 11, 2009, you should follow the instructions in My Oracle Support Knowledge Document 1055539.1 to verify the privileges in your database. This is because a missing step in several OracleMetaLink notes published before 11 September 2009 means that target instance schemas created by following the instructions in them may have an additional privilege that was not present in the source instance, and which may therefore need to be removed. See Knowledge Document 985520.1 for full Critical Patch Update Information.

Anyone who has performed an export or an import recently should absolutely read this note.  Below, I have included Oracle’s test to see if you may be affected by the issue.  This is straight off of note 1055539.1 mentioned above:


Possible Symptoms

To determine whether this extra privilege exists on your target system, use SQL*Plus to connect to the database as SYSDBA and run the following command:

[code language=”plain”]SQL> select grantee, privilege from dba_sys_privs where privilege = ‘EXEMPT ACCESS POLICY’;[/code]

The following output indicates that the SYSTEM account has the additional privilege:

[code]
GRANTEE                  PRIVILEGE
———————— ————————————-
SYSTEM                   EXEMPT ACCESS POLICY
[/code]

Workaround or Resolution

To remove the exempt access policy privilege from your target instance schema, connect to the database as SYSDBA from SQL*Plus and run the following command:

[code language=”plain”]SQL> revoke EXEMPT ACCESS POLICY from system;[/code]

Please contact Oracle Support Services if you have any questions or concerns.

Filed Under: Oracle Tagged With: export/import, Metalink, Oracle DBA

Categories

  • Amazon Web Services
  • Configuration Management
  • downtime
  • Drizzle
  • ebs
  • Education
  • elastic block store
  • elastic compute cloud
  • hosting
  • hot backup
  • ignorance
  • Infrastructure
  • IOUG
  • Jeremiah Wilton's Oradeblog
  • misconception
  • misconceptions
  • Monocle
  • MySQL
  • MySQL Council
  • News & Events
  • Oracle
  • Oracle Applications
  • Oracle Data Guard
  • Oracle Database
  • Oracle Database Appliance
  • Our People
  • OurSQL Community Podcast
  • outage
  • parallel
  • performance
  • podcast
  • proof
  • Remote DBA
  • replication
  • S3
  • Security
  • SQL Server
  • System monitoring
  • Uncategorized

Contact Blue Gecko

  • This field is for validation purposes and should be left unchanged.

Get Our Newsletter

  • This field is for validation purposes and should be left unchanged.

The Fine Print

  • Privacy Policy
  • Terms of Use
  • When is remote DBA the right solution
  • What are remote DBA services
  • Get Help

Blog Categories

  • 24/7 support
  • Blue Gecko 360° Services
  • Products Supported 24/7

Virtual runs

Contact Blue Gecko

Blue Gecko A/S
Slotsgade 21
DK – 4200 Slagelse
Denmark
Phone: (DK) +45 70 60 51 20

Networks

  • Email
  • Twitter

© Blue Gecko Group