Concerns on pre upgrade log- EBS 19c upgrade

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Concerns on pre upgrade log- EBS 19c upgrade

satish
This post was updated on .
Dear Erman,

Our apps version R12.2.5
Db version 12.1.0.2

We need your expertise on below 2 concerns from pre upgrade log


1) We have below duplicate objects. Is it mandatory to drop below objects?

SQL> SELECT object_name, object_type
        FROM dba_objects
        WHERE object_name||'_'||object_type IN
          (SELECT object_name||'_'||object_type
           FROM dba_objects WHERE owner = 'SYS')
         AND owner = 'SYSTEM' AND object_name NOT IN ('AQ$_SCHEDULES',
          'AQ$_SCHEDULES_PRIMARY','DBMS_REPCAT_AUTH','DBMS_REPCAT_AUTH');
  2    3    4    5    6    7

OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE
-----------------------
HELP
TABLE

HELP_TOPIC_SEQ
INDEX

WPG_DOCLOAD
PACKAGE


OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE
-----------------------
WPG_DOCLOAD
PACKAGE BODY


SQL> SQL> desc system.help
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 TOPIC                                     NOT NULL VARCHAR2(50)
 SEQ                                       NOT NULL NUMBER
 INFO                                               VARCHAR2(80)




2)What action to be taken before upgrade.I can see applsyspub has 10g version.Pls correct


SQL> select username, password_versions from dba_users where account_status='OPEN';
USERNAME
SYS
SYSTEM
OUTLN
ORDSYS
ORDPLUGINS
MDSYS
CTXSYS
APPLSYS
APPLSYSPUB
ALR
AX

PASSWORD_VERSIONS
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G 12C HTTP
10G 11G-++++-----++++++++++++applsyspub 
10G 11G 12C HTTP
10G 11G 12C HTTP



Perform one of the following:
1) Expire user accounts that use only the old
10G password version and
follow the procedure recommended in Oracle
Database Upgrade Guide under
the section entitled, "Checking for Accounts Using Case-Insensitive Password Version".
2) Explicitly set
SQLNET.ALLOWED_LOGON_VERSION_SERVER
in the 19
SQLNET.ORA to a non-Exclusive Mode value, such as "11". (This is a short
term approach and is not recommended because it will retain known
securitv risks associated with the 10G password version.)
Your database system has at least one account with only the 10G password
version (see the PASSWORD_VERSIONS column of DBA_USERS).
Starting with Oracle Database release
12.2.0.1, Exclusive Mode is the new default password-based authentication
mode. All Exclusive Mode
login/authentication attempts will fail for preexisting user accounts
which only have the 10G password version and neither the 11G or 12C password version (see
DBA_USERS.PASSWORD_VERSIONS.)

Thanks,
Satish
Reply | Threaded
Open this post in threaded view
|

Re: Concerns on pre upgrade log- EBS 19c upgrade

ErmanArslansOracleBlog
Administrator
1)Let's operationalize it. See -> How to Clean Up Duplicate Objects Owned by SYS and SYSTEM Schema (Doc ID 1030426.6) -- HELP_TOPIC_SEQ for instance is documented there as well.

2) APPLSYS has 10G & 11G password versions according to your output.
Check -> EBS: What should be the value of SQLNET.ALLOWED_LOGON_VERSION_SERVER Parameter in 19c ? (Doc ID 2786414.1) ..
You will find your answer yourself after checking the document above:)