R12.1.3 upgrade to R12.2

[satish]

Dear Erman,

Environment:

Database 19.17
Apps R12.1.3

AD/TXL delta 12


ssscdba is CDB
SSSTTEST is PDB


We are upgrading application to R12.2. Not yet started

By default, service_names parameter is set to CDB which is ssscdba in our case as below. Do we need to add patch service name to service_names parameter prior to upgrade?

We are on AD/TXK delta 12. Preupgrade analyser says "Not to modify service_names parameter when using 19c"


SQL> sho pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 SSSTTEST                       READ WRITE NO


SQL> sho parameter service

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
service_names                        string      ssscdba

SQL> alter session set container=SSSTTEST;

Session altered.

SQL> sho parameter service

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
service_names                        string      ssscdba
SQL>


Active services in PDB

SQL> select NAME,CON_ID from v$services;
 

NAME                                                                 CON_ID
---------------------------------------------------------------- ----------
sssttest                                                                  3
ebs_SSSTTEST                                                              3



From preupgrade analyser:

18. Check Name : Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2
Refer: Chapter 4: Performing the upgrade => Performing the Upgrade to Release 12.2.0 => See Database Initialization Parameters for Oracle Applications Release 12.2 (Doc ID: 396009.1)

        Initialization parameters required at each stage of an upgrade may vary depending on when you upgrade your database.
        Set the appropriate parameters now.

        The important 12.2 specific parameters are:

        recyclebin = off
        service_names=%s_dbSid%,ebs_patch

        Some of the Additional Database Initialization parameters are not set or not valid. Please set the appropriate parameters now.
        Current set parameters are:
        recyclebin = on
        service_names = ssscdba


        Note:  For Oracle Database 19c with a single tenant (1 CDB:1 PDB) configuration : -
                service_names: The value for this parameter is auto-populated when CDB is created. This parameter should not be modified manually.

Please advice..

Thanks,
SG

[ErmanArslansOracleBlog]

Don't touch that. You are still on EBS 12.1.3.. You are on 19C, and you already created your CDB. It should be added during the upgrade process somewhere.. I checked my notes.. We didn't set that manually.


I mean, you are not aligned with the following  ->

--This is for EBS 12.2 , you are not there yet..
 
# Service Names parameter.
#
# To support online patching, Oracle E-Business Suite Release 12.2 introduces a
# new database service.
#
# The service_names parameter specifies one or more names by which clients can
# connect to an instance. The instance registers its service names with the
# listener. When a client requests a service, the listener determines which
# instances offer the requested service and then routes the client to the most
# appropriate instance.
#
# On codelevels lower than AD-TXK Delta 9, the service name is always 'ebs_patch'.
# From the AD-TXK Delta 9 codelevel, the service name is defined by the the value
# of the context variable 's_patch_service_name'.
#
# For Oracle Database 19c with a single tenant (1 CDB : 1 PDB) configuration, the
# value for the service_names parameter is auto-populated when the CDB is created.
# You should not modify this parameter manually.
#

[satish]

Dear Erman,

So,can we start upgrade from R12.1.3 to R12.2 without adding patch service ebs_patch to service_names parameter?

Before your update,i have added like

SQL>  alter system set service_names='ssscdba','ebs_patch' scope=both ;

System altered.

-bash-4.2$ lsnrctl status ssscdba

LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 17-APR-2023 13:38:52

Copyright (c) 1991, 2022, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=abc.dummy.org)(PORT=1111)))
STATUS of the LISTENER
------------------------
Alias                     ssscdba
Version                   TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date                16-APR-2023 16:08:44
Uptime                    0 days 21 hr. 30 min. 8 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u02/CRP/db/19chome/network/admin/listener.ora
Listener Log File         /u02/CRP/db/19chome/log/diag/tnslsnr/sssterpdev1/ssscdba/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=abc.dummy.org)(PORT=****)))
Services Summary...
Service "86b637b62fdf7a65e053f706e80a27ca" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ebs_SSSTTEST" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ebs_patch" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "f9355dee6dfab2bfe0530905000a3c6b" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ssscdba" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ssscdbaXDB" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "sssttest" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
The command completed successfully
-bash-4.2$

Please correct me,if i need to revert back service_names parameter to ssscdba.

Thanks,
Satish

[satish]

Thank you erman. We will revert back service_names parameter.
STATUS of the LISTENER
------------------------
Alias                     ssscdba
Version                   TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date                16-APR-2023 16:08:44
Uptime                    0 days 21 hr. 37 min. 23 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u02/CRP/db/19chome/network/admin/listener.ora
Listener Log File         /u02/CRP/db/19chome/log/diag/tnslsnr/sssterpdev1/ssscdba/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sssterpdev1.ssst.org)(PORT=1526)))
Services Summary...
Service "86b637b62fdf7a65e053f706e80a27ca" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ebs_SSSTTEST" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "f9355dee6dfab2bfe0530905000a3c6b" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ssscdba" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "ssscdbaXDB" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
Service "sssttest" has 1 instance(s).
  Instance "ssscdba", status READY, has 1 handler(s) for this service...
The command completed successfully

SQL>

[satish]

After reverting back service_names parameter to ssscdba,pre install checks failed with below error.

SQL> sho parameter service

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
service_names                        string      ssscdba
SQL>


DB service_names Check
DB service_names Check has failed.
Add ebs_patch as an entry in Database service_names parameter before proceeding.

Please guide

Thanks,
Satish

[ErmanArslansOracleBlog]

In our case(s), we ignored that.. We continued without adding ebs_patch, and we didn't touch it during the rest of the process.. It is set automatically during a phase of the upgrade. But! you may add that ebs_patch as the prereq checking mechanism suggests.. So, just add it and continue.