Skip to main content

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded


ERROR:

I was Performing a full database import and during the import I faced the below error.


ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 6 with process name "DW07" prematurely terminated
ORA-31672: Worker process DW07 died unexpectedly.
Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40

ORA-39014: One or more workers have prematurely exited.


SOLUTION: 

Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully.

NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again.

NOTE 2: Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SGA sizes to increase the process, sessions & transaction parameters accordingly.


SQL> select * from v$resource_limit where RESOURCE_NAME in ('sessions','processes','transactions');

RESOURCE_NAME        CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_ALLOCATION             LIMIT_VALUE
-------------------- ------------------- --------------- ------------------------------ ------------------------------
processes                             31              78        150                            150
sessions                              34              87        170                            170

transactions                         267             389        187                      UNLIMITED


Example : alter system set processes=300 scope=spfile ;

- If we increase the PROCESS parameter it will automatically allocate/increase other two parameter values (sessions & transactions)

Here we are Done :)

Thank You !

Comments

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...

CHANGING DBID FOR ORACLE DATABASE 11G

C:\Users\computer>sqlplus SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:03:33 2013 Copyright (c) 1982, 2008, Oracle.  All rights reserved. Enter user-name: sys as sysdba Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select dbid from v$database;       DBID ---------- 2188161033 SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options C:\Users\computer>nid DBNEWID: Release 11.1.0.7.0 - Production on Thu Sep 10 21:04:44 2013 Copyright (c) 1982, 2007, Oracle.  All rights reserved. Keyword     Description                    (Default) ---------------------------------------------------- TARGET ...