Thursday 3 October 2019

ORA-02085: database link GOLD_TO_SILVER connects to SILVER


This post describes how to resolve "ORA-02085: database link GOLD_TO_SILVER connects to SILVER" issue.


Error:

SQL> select count(*) from dual@GOLD_TO_SILVER;
select count(*) from dual@GOLD_TO_SILVER
                          *
ERROR at line 1:
ORA-02085: database link GOLD_TO_SILVER connects to SILVER


SQL>


Solution:

This error may occurs when global_names set to "TRUE"

SQL> show parameter global_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
global_names                         boolean     TRUE

SQL> show parameter db_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_name                              string      GOLD


SQL> alter system set global_names=FALSE scope=both;

System altered.

SQL> show parameter global_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
global_names                         boolean     FALSE

SQL> select count(*) from dual@GOLD_TO_SILVER;

  COUNT(*)
----------
         1

SQL>







Thanks for going through this post..................

TNS-01151: Missing listener name, GOLD, in LISTENER.ORA


This document describes how to resolve "TNS-01151: Missing listener name, GOLD, in LISTENER.ORA" error.

Error:

[oracle@ebsdb GOLD_ebsdb]$ lsnrctl start GOLD
LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 03-OCT-2019 14:03:58
Copyright (c) 1991, 2014, Oracle.  All rights reserved.
Starting /u01/app/GOLD/12.1.0//bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 12.1.0.2.0 - Production
Log messages written to /u01/app/GOLD/12.1.0/log/diag/tnslsnr/ebsdb/gold/alert/log.xml
TNS-01151: Missing listener name, GOLD, in LISTENER.ORA

Listener failed to start. See the error message(s) above...
[oracle@ebsdb GOLD_ebsdb]$

This error occurs when service name or SID is incorrect or missing in listener.ora file which is under $TNS_ADMIN($ORACLE_HOME/network/admin).

                                                               (OR)

Incorrect environment settings of $TNS_ADMIN

Solution:

In my case listener.ora having correct entries. But got error due to incorrect settings of TNS_ADMIN.

listener.ora:

GOLD =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ebsdb.apps.com)(PORT = 1521))
       )
     )

SID_LIST_GOLD =
  (SID_LIST =
    (SID_DESC =
      (ORACLE_HOME= /u01/app/GOLD/12.1.0)
      (SID_NAME = GOLD)
        )
     )

STARTUP_WAIT_TIME_GOLD = 0
CONNECT_TIMEOUT_GOLD = 10
TRACE_LEVEL_GOLD = OFF

LOG_DIRECTORY_GOLD = /u01/app/GOLD/12.1.0/network/admin
LOG_FILE_GOLD = GOLD
TRACE_DIRECTORY_GOLD = /u01/app/GOLD/12.1.0/network/admin
TRACE_FILE_GOLD = GOLD
ADMIN_RESTRICTIONS_GOLD = ON
SUBSCRIBE_FOR_NODE_DOWN_EVENT_GOLD = OFF

Set TNS_ADMIN to correct path to fix the issue.

Ex:

$export TNS_ADMIN= /u01/app/GOLD/12.1.0/network/admin





Thanks for going to this post......


Thursday 26 September 2019

SEVERE: [FATAL] [INS-10102] Installer initialization failed.



Getting below error while installing EBS R12.2.0 in Linux server.


Click on warning button to see the error.


Installer logs having below error message. We can find error logs in inventory location. In my case "/u01/app/oraInventory/logs". 

Error 1:
SEVERE: [FATAL] [INS-10102] Installer initialization failed.
   CAUSE: An unexpected error occured while initializing the Installer.
   ACTION: Contact Oracle Support Services or refer logs
   SUMMARY:
       - [INS-21003] Installer has detected that an invalid inventory pointer location file was specified..
Refer associated stacktrace #oracle.install.commons.util.exception.DefaultErrorAdvisor:37
INFO: Advice is ABORT
SEVERE: Unconditional Exit
INFO: Adding ExitStatus FAILURE to the exit status set
INFO: Finding the most appropriate exit status for the current application
INFO: Exit Status is -1
INFO: Shutdown Oracle Database 12c Release 1 Installer
[root@ebsdb logs]# 

Error 2:

Found below error in "/tmp/OraInstall2019-09-26_02-55-57PM/oraInstall2019-09-26_02-55-57PM.err"

---# Begin Stacktrace #---------------------------
ID: oracle.install.commons.util.exception.DefaultErrorAdvisor:37
oracle.install.commons.base.driver.common.InstallerException: [INS-10102] Installer initialization failed.
        at oracle.install.commons.base.driver.common.Installer.run(Installer.java:324)
        at oracle.install.ivw.common.util.OracleInstaller.run(OracleInstaller.java:106)
        at oracle.install.ivw.db.driver.DBInstaller.run(DBInstaller.java:142)
        at oracle.install.commons.util.Application.startup(Application.java:921)
        at oracle.install.commons.flow.FlowApplication.startup(FlowApplication.java:181)
        at oracle.install.commons.flow.FlowApplication.startup(FlowApplication.java:198)
        at oracle.install.commons.base.driver.common.Installer.startup(Installer.java:355)
        at oracle.install.ivw.db.driver.DBInstaller.startup(DBInstaller.java:130)
        at oracle.install.ivw.db.driver.DBInstaller.main(DBInstaller.java:161)
Caused by: oracle.install.commons.base.driver.common.SetupDriverException: [INS-21003] Installer has detected that an invalid inventory pointer location file was specified.
        at oracle.install.driver.oui.OUIInstallDriver.load(OUIInstallDriver.java:393)
        at oracle.install.ivw.db.driver.DBSetupDriver.load(DBSetupDriver.java:225)
        at oracle.install.commons.base.driver.common.Installer.run(Installer.java:306)
        ... 8 more

---# End Stacktrace #-----------------------------


We will get below error if we ignore this error and proceed with the installation.



Solution:

Error is with some permissions and found group details are not present in "/etc/oraInst.loc".

[root@ebsdb logs]# cat /etc/oraInst.loc
inventory_loc=/u01/app/oraInventory
[root@ebsdb logs]#

Added group details and after adding "/etc/oraInst.loc" file looks like below.

[root@ebsdb logs]# cat /etc/oraInst.loc
inventory_loc=/u01/app/oraInventory
inst_group=dba
[root@ebsdb logs]#






Thanks for reviewing this post...............


Wednesday 17 July 2019

Decrypt Weblogic Admin password



This post describes how to decrypt weblogic password using python script.

Assumption: We have boot.properties file which contains encrypted password.

Step 1: Get encrypted password from boot.properties file.

Go to below location and cat boot.properties to get encrypted weblogic password.

cd $DOMAIN_HOME/servers/Adminserver/security

[oracle@server1 AdminServer]$ cd /u01/app/Middleware/user_projects/domains/base_domain/servers/AdminServer/security/

[oracle@server1 security]$ cat boot.properties
# Generated by Configuration Wizard on Thu Jul 11 13:11:09 IST 2019
username={AES}3Ryhu7KAt1t74cqx/UFhcwhq675U5gxfiChMAqgdCW8=
password={AES}s+0t9pgYnGBXRtLxtzp0grC7qbQDjobTZlLc/Tm/AwA=


Step 2: Create python script in the server with below parameters.

from weblogic.security.internal import *
from weblogic.security.internal.encryption import *

passwd = "<encrypted password from boot.properties file"
secPath = "security folder path under DOMAIN_HOME"
encService = SerializedSystemIni.getEncryptionService(secPath)
coeService = ClearOrEncryptedService(encService)
print "Password is : " + coeService.decrypt(passwd)


[oracle@server1 security]$ vi DecryptPassword.py

from weblogic.security.internal import *
from weblogic.security.internal.encryption import *

passwd = "{AES}s+0t9pgYnGBXRtLxtzp0grC7qbQDjobTZlLc/Tm/AwA="
secPath = "/u01/app/Middleware/user_projects/domains/base_domain/security"
encService = SerializedSystemIni.getEncryptionService(secPath)
coeService = ClearOrEncryptedService(encService)
print "Password is : " + coeService.decrypt(passwd)

:wq!


Step 3: Get decrypted password using wlst script.

execute below command.

[oracle@server1 security]$ /u01/app/Middleware/oracle_common/common/bin/wlst.sh DecryptPassword.py

 
Output: 

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Password is : welcome123
[oracle@server1 security]$







Thanks for your patience to view this post................



Saturday 1 June 2019

Find Concurrent Program Name using concurrent request ID.


This post describes how to find concurrent program name using concurrent request ID.

Query:

Use below query to find Concurrent Program Name using Concurrent Request ID.


SELECT PROGRAM FROM FND_CONC_REQ_SUMMARY_V WHERE REQUEST_ID = ‘Request ID;