Skip to main content

Forms giving Invalid Username Password for EBS R12 after upgrade to 19c Database

Forms giving Invalid Username Password for EBS R12 after upgrade to 19c Database


After Upgrade to 19c database for my EBS environment getting invalid username/password error when opening forms.


Error:

ORA-1017 when opening Forms and ORA-1017 Invalid username/password; logon denied FRM-41352 failed to create a new session


Cause: 

Mis-configuration with the listener and registration of services:

Solution:

1. In 19c database service_name parameter should be set to container name

     Connect to the CDB and run the following commands:

        alter System set SERVICE_NAMES='<CDBNAME>' SCOPE=BOTH;
        alter system register;

2. Verify that the PDB database is registered with the  listener

      Connect to PDB and check value of local_listener parameter. It should be not be set at PDB level and should be same as CDB value.

3. PDB should have at a minimum of these services in 12.1 and 12.2.

  select name from v$active_services;

12.1:

  ebs_<PDB NAME>
 <PDB NAME>

12.2:

  ebs_<PDB NAME>
  <PDB NAME>
  <PDB_NAME>_ebs_patch

4. Listener should be started using CDB environment file

      cd $ORACLE_HOME

        .CDB_funebs.env

         lsnrcrt stop CDBNAME

       lsnrctl start CDBNAME

5. You should see something similar to the following:

$ lsnrctl status

LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 22-APR-2021 19:23:43

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

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=funebs.lab)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias VISCDB
Version TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date 22-APR-2021 19:23:43
Uptime 6 days 19 hr. 5 min. 17 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/oracle/db/tech/19.3/network/admin/listener.ora
Listener Log File /u01/oracle/db/tech/19.3/admin/PDB_funebs/diag/tnslsnr/funebs/cdb/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=funebs.lab)(PORT=1521)))
Services Summary...
Service "2809740d20a4db6" has 1 instance(s).
Instance "CDB", status READY, has 1 handler(s) for this service...
Service "PDB" has 2 instance(s). -----> PDB service. Started when PDB is started
Instance "PDB", status UNKNOWN, has 1 handler(s) for this service...
Instance "CDB", status READY, has 1 handler(s) for this service...
Service "PDB_ebs_patch" has 1 instance(s). ----> Created during post PDB steps , needed for ADOP patching
Instance "CDB", status READY, has 1 handler(s) for this service...
Service "CDB" has 1 instance(s). ---> CDB service , not used by EBS but needed for connections to CDB
Instance "CDB", status READY, has 1 handler(s) for this service...
Service "CDBXDB" has 1 instance(s). --> optional XDB service
Instance "CDB", status READY, has 1 handler(s) for this service...
Service "ebs_PDB" has 1 instance(s). ---> Created during post PDB steps , needed for EBS
Instance "CDB", status READY, has 1 handler(s) for this service...
The command completed successfully







If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more