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

Registering The Database to RMAN catalog database:

Registering The Database to RMAN catalog database: Need to start RMAN as follows: RMAN target=sys/password@database_to_backup rcvcat=sys/password@recovery_catalog_database Another variation on the command, if the recovery catalog and the database were on the same server, might be as shown: oraenv ORACLE_SID = [KKUY] ? KKUY RMAN rcvcat=sys/password@recovery_catalog_database RMAN> connect target Recovery Manager: Release 8.0.5.1.0 - Production RMAN-06005: connected to target database: KKUY RMAN-06008: connected to recovery catalog database Use the below command to register the database. RMAN>register database; Want to verify if a database is registered in the recovery catalog. To do this, connect to RMAN and issue the command LIST INCARNATION OF DATABASE. RMAN> list incarnation of database; RMAN-03022: compiling command: list RMAN-06240: List of Database Incarnations RMAN-06241: DB Key Inc Key DB Name DB ID      CUR Reset SCN   Reset Time RMAN