ORA-28000, the account was unlocked in the primary database, but still locked in the Active Standby Database.

Situation:

The primary database is configured with Dataguard is returning an error ORA-28000, “the account is locked,” when the user tries to log in. 

The database administrator unlocked this user’s account in the primary database but still the user is unable to connect to the standby and receives the same error code, ORA-28000, for that specific user; nonetheless, the standby account status indicates that it is open.

Standby Situation:

SYS@DATABASE  > conn raheel/raheel123

ERROR:

ORA-28000: the account is locked

Warning: You are no longer connected to ORACLE.

SYS@DATABASE > select username,account_status from dba_users where username=’RAHEEL’;

USERNAME                      ACCOUNT_STATUS

——————————————————————————————

Raheel                               OPEN

SYS@DATABASE > @check_db

DbId Name      Log Mode     Open Mode            Database Role    Created             Resetlogs         Remote Archive

———– ——— ———— ——————– —————- ——————- ——————- ——————

603299473 RAHEEL   ARCHIVELOG   READ ONLY WITH APPLY PHYSICAL STANDBY 11/13/2019 20:16:17 11/13/2019 03:54:21 ENABLED

SOLUTION:
This is a result of the standby’s read-only access and inability to change any tables.  A user’s account is only locked in memory on the standby database when it has to be.

The database administrator, sysdba, is a privileged user who needs to log in to the standby and unlock the account.  The account is now unlocked in the standby database, as confirmed by the message ORA-28015 “Account unlocked, but the database is open for read-only access.”  After that, there are no more errors for the user to encounter when logging into the standby database.

Connect Standby Database and unlock the account:

SYS@DATABASE > ALTER USER RAHEEL ACCOUNT UNLOCK;

ALTER USER RAHEEL ACCOUNT UNLOCK;

ERROR at line 1:

ORA-28015: Account unlocked, but the database is open for read-only access

SYS@DATABASE > conn raheel/raheel123

Connected.

ISSUE:

/u01/ebs/fs1/EBSapps/10.1.2/bin/sqlplus: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory

While running adcfgclone appsTier single fs on EBS 12.2.10

FATAL ERROR

PROGRAM : (/u01/ebs/fs1/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkManageDBConnectionPool.pl)

TIME : Sun Nov 10 15:26:51 2024

FUNCTION: main::validateAppsSchemaCredentials [ Level 1 ]

ERRORMSG: Invalid APPS database user credentials. No updates Performed

.end err out.

Result : FAILED

sqlplus: error while loading shared libraries: libnsl.so.1 txkManageDBConnectionPool.pl Invalid APPS database user credentials

Adcfgclone Fails With “sqlplus: error while loading shared libraries: libnsl.so.1: wrong ELF class: ELFCLASS64” (Doc ID 2963649.1)

CAUSE:

The output of the query below indicated that the Linux 8 RPM -> libnsl 64 bits was installed only instead of required 32 bit RPM

rpm -qa –qf “%{n}-%{v}-%{r}.%{arch}\n” | grep libnsl

libnsl-2.28-225.0.3.el8.x86_64

libnsl2-1.2.0-2.20180605git4a062cf.el8.x86_64

SOLUTION:

With a valid backup,Please execute the below

1) Install libnsl RPM with 32 bit

[root@ebs (clone)]$ 02:28:29 > rpm -ivh /media/dvd/BaseOS/Packages/libnsl-2.28-251.0.2.el8.i686.rpm

Verifying… ################################# [100%]

Preparing… ################################# [100%]

Updating / installing…

1:libnsl-2.28-251.0.2.el8 ################################# [100%]

[root@ebs (clone)]$ 02:28:44 >

After installing 32 bit RPM adcfgclone appsTier ran successfully.

Verify whether your Primary Oracle Database is in sync with the Standby Database in a Data Guard configuration.

Solution:

To ensure synchronization, you need to check the Managed Recovery Process (MRP) and query relevant views that provide real-time status and logs. Below are the key SQL queries that help you confirm synchronization.

1. Check the Managed Standby Recovery Process (MRP)

Run the following query to check the status of the MRP process on the standby database:

SELECT thread#, sequence#, process, client_process, status, blocks 
FROM v$managed_standby;

• THREAD# – Identifies the thread number.
• SEQUENCE# – Displays the current sequence number being processed.
• PROCESS – Indicates the type of process running.
• CLIENT_PROCESS – Shows the client process (e.g., ARCH for archive or MRP for managed recovery).
• STATUS – Current status of the process (e.g., ACTIVE or WAITING).
• BLOCKS – Number of blocks being processed.

2. Check for Errors in Data Guard Status

Run this query to look for any critical errors (severity: Error or Fatal) in the Data Guard status log:

SELECT gvi.thread#, timestamp, message 
FROM gv$dataguard_status gvds, gv$instance gvi 
WHERE gvds.inst_id = gvi.inst_id 
AND severity IN ('Error', 'Fatal') 
ORDER BY timestamp, thread#;

This query will help you identify potential issues that could disrupt synchronization between the primary and standby databases.

3. Compare Last Received and Applied Archive Logs

Use this query to compare the last archive log received and applied on the standby:

SELECT ARCH.THREAD# "Thread", 
       ARCH.SEQUENCE# "Last Sequence Received", 
       APPL.SEQUENCE# "Last Sequence Applied", 
       (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference" 
FROM (SELECT THREAD#, SEQUENCE# 
      FROM V$ARCHIVED_LOG 
      WHERE (THREAD#, FIRST_TIME) IN 
            (SELECT THREAD#, MAX(FIRST_TIME) 
             FROM V$ARCHIVED_LOG 
             GROUP BY THREAD#)) ARCH, 
     (SELECT THREAD#, SEQUENCE# 
      FROM V$LOG_HISTORY 
      WHERE (THREAD#, FIRST_TIME) IN 
            (SELECT THREAD#, MAX(FIRST_TIME) 
             FROM V$LOG_HISTORY 
             GROUP BY THREAD#)) APPL 
WHERE ARCH.THREAD# = APPL.THREAD#;

• Last Sequence Received – The most recent archive log received by the standby.
• Last Sequence Applied – The most recent archive log applied on the standby.
• Difference – Shows the gap (if any) between the received and applied sequence numbers.

If the Difference is 0 (zero), your standby database is fully synchronized with the primary. Any positive value indicates lag that may require attention.

ISSUE:

I had to renew my customer’s EBS SSL certificate as it was about to expire soon
Since the EBS 12.2.7 wallet had the ability to open wallet in GUI mode , I tried to open wallet BUT was Not able to open it facing the below error.

! The new version of wallet I guess does not allow to perform this activity through OWM GUI.

owm &

Java HotSpot(TM) Server VM warning: You have loaded library /oracle/PROD/fs1/EBSapps/10.1.2/lib/libowm2.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It’s highly recommended that you fix the library with ‘execstack -c ‘, or link it with ‘-z noexecstack’.

SOLUTION:

In order to resolve the issue, do the following:
export PATH=$FMW_HOME/webtier/bin:$FMW_HOME/oracle_common/bin:$PATH

Run:

owm &

it works now.

Removed the expired certificates

Imported all fresh Trusted and User Certififcates.

Command to displayed the wallet to validate the certificate chain:
$FMW_HOME/oracle_common/bin/orapki wallet display -wallet .

[applprod@erpprod Apache]$ $FMW_HOME/oracle_common/bin/orapki wallet display -wallet .
Oracle PKI Tool : Version 11.1.1.9.0
Copyright (c) 2004, 2015, Oracle and/or its affiliates. All rights reserved.

Requested Certificates:
User Certificates:
Subject: CN=*****.gov.sa,O=****** ***,L=Riyadh,C=SA
Trusted Certificates:
Subject: CN=SSL.com TLS RSA Root CA 2022,O=SSL Corporation,C=US
Subject: CN=Entrust OV TLS Issuing RSA CA 1,O=SSL Corporation,C=US
Subject: CN=SSL.com EV Root Certification Authority RSA R2,O=SSL Corporation,L=Houst on,ST=Texas,C=US
[applprod@erpprod Apache]$

ERROR:

When we click on the home button on landing page after login on java applet we are facing this issue.
” You have encountered an unexpected error. Please contact the system administrator for assistance. “

when we click on ” click here for exception details “

SOLUTION: Compile jsps

1. If you are login to EBS, do a clean logout.
2. Stop the application.
3. After complete stop of application check the following processes to confirm that the application is completely stopped.
   ps -ef | grep PALIB
   ps -ef | grep FND
   ps -ef | grep OPP
   ps -ef | grep frmweb
4. After that,
   COMMAND:
   cd $FND_TOP/patch/115/bin
5. COMMAND:
   perl -x ojspCompile.pl –compile –flush -p 2

Once the compilation is done, restart the EBS Services.

Issue would be resolved.

ISSUE:

While migrating one of my client’s Core Oracle Database from an on-premises environment to Google Cloud VM Instance. I encountered an issue while transferring files via SCP from the source Linux server to the target and was unable to connect to Google Cloud VM’s Linux terminal with password using SSH?

ERROR:

[oraprd@core-db-prd ~]$ scp abc oradev@155.199.299.187:/u01/core_db/db/
The authenticity of host ‘155.199.299.187 (155.199.299.187)’ can’t be established.
ECDSA key fingerprint is SHA256:weCNN1YK6jubMLYRfRs2QVhJ5wPNZc7G8SWp/J+0tJ0.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added ‘155.199.299.187’ (ECDSA) to the list of known hosts.
oraprd@155.199.299.187: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
lost connection
[oraprd@core-db-prd ~]$

SOLUTION:

Steps to Transfer a Folder or File Between GCP VMs

1. Enable Password Authentication on the Target DR Server
   • Open the SSH configuration file:
     vi /etc/ssh/sshd_config
   • Update the following line:
     From: PasswordAuthentication no
     To: PasswordAuthentication yes
   • Restart the SSH service:
     systemctl restart sshd
   • Verify the SSH service status:
     systemctl status sshd
2. Transfer Files
   • Use a secure copy command (scp) to transfer the folder or file from the source (Prod Server) to the target (DR Server). You will be prompted to enter the password.
3. Revert Password Authentication Setting on the Target DR Server
   • Edit the SSH configuration file again:
     vi /etc/ssh/sshd_config
   • Change the line back:
     From: PasswordAuthentication yes
     To: PasswordAuthentication no
   • Restart the SSH service:
     systemctl restart sshd
   • Verify the SSH service status:
     systemctl status sshd

IMPORTANT ! : Always ensure you revert the PasswordAuthentication setting after the transfer to maintain server security.

ISSUE:

While running perl adcfgclone.pl dbTechStack, Cloning EBS integerated 19c Database TechStack Fails on supported OS Check with Red Hat Linux 8.10

CAUSE:

19c does not contain Pre-req checks specific to Oracle Linux 8 / Red Hat Linux 8.10
Silent Installer will fail with below Error,as there are no Pre-req checks specific to Linux 8.

SHOW STOPPER ERROR:

[WARNING] [INS-08101] Unexpected error while executing the action at state:’supportedOSCheck’
CAUSE: No additional information available.
ACTION: Contact Oracle Support Services or refer to the software manual.
SUMMARY:
– java.lang.NullPointerException

SOLUTION:

Hence,there is a need to direct the Installer to assume the installed OS to be OL 7 & perform related checks.
Therefore,the below Variable needs to be set,prior to launching Installer-

export CV_ASSUME_DISTID=OEL7.8

NOTE: As per Oracle Pre-req check file for OL/RHEL 8 is provided by 19c PSU 19.6 + but I faced this same issue in 19.22 still !

ISSUE:

After Adcfgclone appsTier for a newly cloned ebs 12.2.13 environment from an SSL-enabled ebs precloned stage backup prevents me from logging in to non-SSL EBS login URL, despite it was completed 100% successfully without any error.

CAUSE:

EBS Context file variable s_enable_sslterminator was empty and was required to be changed as shown below:

It was discovered that the EBS App Context file was having below entry only and
Even after changing the required parameters in the context file, Switching all https to http did not disable SSL and the URL still rerouted to https.

From – >>> http://ebsclone.aot.sa:8010/OA_HTML/AppsLogin
Redirecting to –>> https://ebsclone.aot.sa:4443/OA_HTML/AppsLocalLogin.jsp

SOLUTION:

The ssl_terminator variable value in the context value tags needs to be included as shown below:

From:
<sslterminator oa_var=”s_enable_sslterminator”/>
to
<sslterminator oa_var=”<s_enable_terminator”>#</sslterminator>

After updating Context file, stopped EBS App Services, run autoconfig and restart the App Services Resolved the NON SSL URL redirection.

—————————————

Official interrelated Oracle EBS SSL Documents:
Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID 1367293.1)
How to Completely Disable the SSL Listener for E-Business Suite R12.2 Using Fusion Middleware Control (Doc ID 2203482.1)03482.1)

Issue faced: Sudden Power shutdown of EBS 12.2 Application Server / Machine

cd $ADMIN_SCRIPTS_HOME
./adapcctl.sh status
Noticed that the http service shows STOP

SOLUTION:

cd /u01/ebiz_APRIL_2018/fs1/FMW_Home/webtier/instances/web_GEAPROD_OHS1/config/OPMN/opmn/states

ls -lrta

-rw-r—–. 1 applprod dba 14 Oct 26 10:58 .locale
-rw-r—–. 1 applprod dba 579 Oct 26 10:59 p1505039354
-rw-r—–. 1 applprod dba 20 Oct 26 11:00 .opmndat

rename this file “p1505039354” and started opmn and adapcctl
mv p1505039354 XX_OFF_p1505039354

ls -lrt
-rw-r—–. 1 applprod dba 578 Oct 26 10:53 XX_OFF_p1505039354

cd $ADMIN_SCRIPTS_HOME
./adapcctl.sh start

Symptoms/Problem Details :

Unable to connect apps user from a Recently cloned and EBS RUP 12.2.12 applied Application node
sqlplus apps/*****
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.[oracle@clone admin]$ sqlplus apps/****
SQL*Plus: Release 10.1.0.5.0 – Production on Mon Sep 2 11:25:55 2024
Copyright (c) 1982, 2005, Oracle.  All rights reserved.

ERROR:

ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus

================================
[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:53:30 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL>  Select name from v$active_services;
NAME
—————————————————————-
cdbclone
cdbcloneXDB
SYS$BACKGROUND
SYS$USERS
clone_ebs_patch
clone
7 rows selected.
SQL> exit
ebs_<PDB_SID> found missing in the above result
==================
root cause identified as below:
service name :      ebs_<PDB_SID> was not up and running
NOTE:  ebs_clone  :  is the service name in our case
====================

SOLUTION:

========

1. open a linux terminal
2. Source CDB env
Our pdb sid is: clone
3. export ORACLE_PDB_SID=clone     ( set the PDB env temporarily) 
4-a. sqlplus / as sysdba
4-b. Start the PDB service – ebs_clone
BEGIN
DBMS_SERVICE.START_SERVICE(
service_name => ‘ebs_clone’
);
END;
/
5. connect EBS node, source run fs environment and test now
sqlplus apps/*** OR sqlplus apps/***
connected to apps user successfully now.
===================================
Recorded session below:
[oracle@clone clone_clone]$ export ORACLE_PDB_SID=clone   (Having sourced CDB env)[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:52:49 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL>
BEGIN
DBMS_SERVICE.START_SERVICE(
service_name => ‘ebs_clone’
);
END;
/SQL>   2    3    4    5    6
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
[oracle@clone clone_clone]$
===================================
Now Make sure to save the PDB State with above ebs_clone service configured and running.
[oracle@clone clone_clone]$
[oracle@clone clone_clone]$
[oracle@clone clone_clone]$ export ORACLE_PDB_SID=clone
[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:54:12 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL> alter pluggable database “clone” save state;
Pluggable database altered.
SQL>
SQL>
================
Verify the service ebs_clone is now coming as active and running.
[oracle@clone clone_clone]$
[oracle@clone clone_clone]$ export ORACLE_PDB_SID=””
[oracle@clone clone_clone]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Mon Sep 2 11:53:30 2024
Version 19.19.0.0.0
Copyright (c) 1982, 2022, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
SQL>  Select name from v$active_services;
NAME
——————-
cdbclone
ebs_clone   <<<— service ebs_clone is now coming as active and running.
cdbcloneXDB
SYS$BACKGROUND
SYS$USERS
clone_ebs_patch
clone
7 rows selected.
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.19.0.0.0
[oracle@clone clone_clone]$
======================================