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

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 ...

Difference between AWR, ADDM and ASH reports

AWR: Automatic Workload Repository gathers, processes and maintains performance stats used for problem detection and self-tuning the databases. Different Components that uses AWR are: Automatic Database Diagnostic Monitor Undo Advisor SQL Tuning Advisor Segment Advisor Different types of AWR Reports for different purposes: For Single Instance Environment: @$ORACLE_HOME/rdbms/admin/awrrpt.sql For Oracle RAC Environment : @$ORACLE_HOME/rdbms/admin/awrgrpt.sql For a particular SQL Statement : @$ORACLE_HOME/rdbms/admin/awrsqrpt.sql For Comparing the reports : @$ORACLE_HOME/rdbms/admin/awrddrpt.sql ADDM: Automatic Database Diagnostic Monitoring Report analyzes the AWR data on a regular basis, to give you overview of the root cause of the problem which is affecting your database’s performance. It also provides suggestions or recommendations for rectifying any problem identified and lists the areas which are having no issues. ADDM recommends multiple solutions for the DBA to choose from which...