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
Post a Comment
Post a Comment