Posts

Showing posts from June, 2019

Tnsping Net Service Name fails with TNS-12537: TNS:connection closed or Sqlplus connection errors out with Ora-12537

Tnsping Net Service Name fails with TNS-12537: TNS:connection closed or Sqlplus connection errors out with Ora-12537     Cause:     * In the Sqlnet.ora file the parameter TCP.VALIDNODE_CHECKING is enabled and TCP.INVITEDNODES is set to some specific IP's of the Client Machine.     * If trying to connect to the Apps database, by default, with Oracle Apps Installation the parameter TCP.VALIDNODE_CHECKING is enabled and TCP.INVITEDNODES is set to Server Machines IP or Hostname.     Solution     (i)  You can disable these parameters in the Sqlnet.ora as following, then lsnrctl reload listener_name #tcp.validnode_checking = yes #tcp.invited_nodes=(xxx.domain.com) or    (ii) add the client machines ip address in the TCP.INVITEDNODES list, then lsnrctl reload listener_name

adop phase=prepare [ERROR] META:18:03:58.800: bad stylesheet: kustrigc (Tested on R12.2.5 by me)

Initializing.     Run Edition context  : /oradev/oracle/r12/uat/fs1/inst/apps/sid_hostname/appl/admin/sid_hostname.xml     Patch edition context: /oradev/oracle/r12/uat/fs2/inst/apps/sid_hostname/appl/admin/sid_hostname.xml     Patch file system free space: 222.29 GB Validating system setup.     Node registry is valid.     [ERROR]     META:18:03:58.800: bad stylesheet: kustrigc     Encountered the above errors when performing database validations.     Resolve the above errors and restart adop. [STATEMENT] Please run adopscanlog utility, using the command "adopscanlog -latest=yes" to get the list of the log files along with snippet of the error message corresponding to each log file. adop exiting with status = 1 (Fail) $ Solution: 1. To find the current version of the adgrants.sql script on the instance, do the following:   a. Source the database environ...