ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Upgrade Readiness Tool Fails while running the "sandbox" upgrade

book

Article ID: 173509

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

When attempting to run the "sandbox" upgrade portion of the Upgrade Readiness Tool (URT), it fails and you see a similar message to the below error in the URT details output file.

Import: Release 12.2.0.1.0 - Production on Sun Jan 27 01:38:16 2019

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 12c Standard Edition Release 12.2.0.1.0 - 64bit Production
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_IMPORT_FULL_01 for user DLPBRUN
ORA-06512: at "SYS.KUPV$FT", line 1140
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 1748
ORA-39062: error creating master process DM00
ORA-39105: Master process DM00 failed during startup. Master error:
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
ORA-06512: at "SYS.KUPP$PROC", line 57
ORA-06512: at "SYS.KUPP$PROC", line 275
ORA-06512: at "SYS.KUPV$FT", line 1690
ORA-06512: at "SYS.KUPV$FT", line 1101



Import: Release 12.2.0.1.0 - Production on Sun Jan 27 01:38:18 2019

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

UDI-02391: operation generated ORACLE error 2391
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

Username: 

Cause

By default both the "protect" and the "upgrade user" Oracle accounts use the default profile when they are created. There are not enough Oracle sessions available to the URT "upgrade" user's profile and thus the export/import function fails.

Resolution

Log into the DLP Oracle database via SQLPlus from a command line:

1. sqlplus /nolog

2. connect [email protected] as sysdba

3. Enter your sys password when prompted.

4. Run the following SQL statement. You should see that only SESSIONS_PER_USER is set to 1.

col username for a12
col profile for a19
col limit for a12
set lines 299
select a.username,b.PROFILE,b.RESOURCE_NAME,b.limit from dba_users a , dba_profiles b where a.profile=b.profile and b.RESOURCE_NAME='SESSIONS_PER_USER' and a.username='YOUR_UPGRADE_USER';

5. Run the following statement to increase the number of sessions for the default profile. No commit is needed.
 
ALTER PROFILE DEFAULT LIMIT SESSIONS_PER_USER 10;

6. It will show "Profile Altered" if successful.

7. Run the statement again from step 4 above to make sure the change to the SESSIONS_PER_USER parameter took place.

col username for a12
col profile for a19
col limit for a12
set lines 299
select a.username,b.PROFILE,b.RESOURCE_NAME,b.limit from dba_users a , dba_profiles b where a.profile=b.profile and b.RESOURCE_NAME='SESSIONS_PER_USER' and a.username='YOUR_UPGRADE_USER';

8. Run the Upgrade Readiness Tool again and it should get beyond the step where it was previously failing.

 

Keep in mind that by running the above alter statement it will increase the SESSIONS_PER_USER value from the current level to 10. This will change the value for all other Oracle accounts who use the default profile.