- « Oracle SqlDeveloper java.lang.OutOfMemoryError: Java heap space - fix
- Oracle 12c - DG - ORA-16598: Oracle Data Guard broker detected a mismatch in configuration »
DataPump - Export - Import - 12.1 - ORA-31623: a job is not attached to this session via the specified handle
Exporting..... takes time in some case :)
If you are running export or import process
expdp \"sys@SID as sysdba\"
There are a different resolution of this issue and you have to try with first metalink or second - please read it and try to execute some of the recommendations like to unset NLS environments
try to unset or set correct NLS_DATE_FORMAT as per information from the database - >
i try a lot of changes but without success and finally, resolution appear in metalink -> How to resolve the Data Pump error ORA-31623 UDE-31623 (a job is not attached to this session via the specified handle) ? (Doc ID 1907256.1)
Errors are received at expdp or impdp using LOGTIME parameter
Data Pump export/import with LOGTIME parameter crashes if the environment variable NLS_DATE_FORMAT is set. In some cases, the errors are seen if both NLS_DATE_FORMAT and NLS_LANG are set.
The problem is addressed in
Bug 18920652 - DATAPUMP WITH LOGTIME CRASHES WHEN NLS_LANG IS SET AT O/S LEVEL
closed as a duplicate of
Bug 17714887 - ORA-31623 ON IMPDP WITH DBLINK
Please note that Bug 17714887 has been superseded by unpublished Bug 21094393
Unpublished Bug 21094393 is fixed in 12.2.
To solve the issue, use any of below alternatives:
Apply interim patch 21094393, if available for your platform and Oracle version.
To check for conflicting patches, please use the MOS Patch Planner Tool
Please refer to Note 1317012.1 - How To Use MOS Patch Planner To Check And Request The Conflict Patches?
If no patch exists for your version, please contact Oracle Support for a backport request.
- OR -
As possible workarounds:
Do not use the LOGTIME parameter, as it is not essential to the export/import functionality as such.
- OR -
Unset the NLS_DATE_FORMAT and NLS_LANG environment variables
In my case, i just remove parameter LOGTIME=all because I am not able to patch database :(
have fun with oracle
No feedback yet
Form is loading...