Oracle Database Vault was configured on RAC database v11.2.0.3 and appropriate permissions given to allow the regular duties, such as data pump export/import etc.
However, when classical/traditional import (a dump file from v9 database) was performed, the import on 11.2.0.3 database failed with the following errors:
Data pump jobs were successfully executing without any issues. The only problem is with traditional export/import . According to below Oracle notes, it is an expected behavior in 11.2.0.3 with DB Vault in place.
The option would be to upgrade the database to higher than 11.2.0.3.
Will apply the patch and update this blog if the issue is fixed or not.
However, when classical/traditional import (a dump file from v9 database) was performed, the import on 11.2.0.3 database failed with the following errors:
Import: Release 11.2.0.3.0 - Production on Tue May 29
16:56:23 2018
Copyright (c) 1982, 2011, Oracle and/or its
affiliates. All rights reserved.
IMP-00058: ORACLE error 1031 encountered
ORA-01031: insufficient privilegesUsername: Data pump jobs were successfully executing without any issues. The only problem is with traditional export/import . According to below Oracle notes, it is an expected behavior in 11.2.0.3 with DB Vault in place.
Classic Export/Import Fail With ORA-01031 in Database
Vault Environment Starting Release 11.2.0.3 (Doc ID 1419687.1)
Bug 13615338 - EXP/IMP disabled in Database Vault
environment (Doc ID 13615338.8)
According to the notes,
Export and Import tools are no longer recommended to be used,
especially in Database Vault environments.
When it is not possible to use data pump (for instance when the export has been created from a pre-10g database),
the patch 13615338 must be installed to allow the usage of classic export/import utilities.
When it is not possible to use data pump (for instance when the export has been created from a pre-10g database),
the patch 13615338 must be installed to allow the usage of classic export/import utilities.
The option would be to upgrade the database to higher than 11.2.0.3.
Will apply the patch and update this blog if the issue is fixed or not.
No comments:
Post a Comment