Connect String Specific For An Instance (RAC)

In cluster environments, if we connect using connect string or JDBC, we usually connect to a public address that leads us to some of the nodes in the cluster. Sometimes We need to go to a particular node, from applications (of course, you can do this by defining preferred affinity and services) or as in my case for administration issues, where You need to work on a particular node.

Since version 11, if I am not wrong, the connect string includes the parameter instance_name, an example we can see below for a cluster of three nodes, with this we can go directly to the node we need.

sap_1.domain.es =
(DESCRIPTION =
  (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = scan.public.com)(PORT = 5671))
  )
  (CONNECT_DATA =
    (SERVICE_NAME = SAP)
    (INSTANCE_NAME=SAP_1)
  )
)

sap_2.domain.es =
(DESCRIPTION =
  (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = scan.public.com)(PORT = 5671))
  )
  (CONNECT_DATA =
    (SERVICE_NAME = SAP)
    (INSTANCE_NAME=SAP_2)
  )
)

sap_3.domain.es =
(DESCRIPTION =
  (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = scan.public.com)(PORT = 5671))
  )
  (CONNECT_DATA =
    (SERVICE_NAME = SAP)
    (INSTANCE_NAME=SAP_3)
  )
)

HTH – Antonio NAVARRO

Advertisements

How To Find Out If TFA Is Installed And If So Which Version

TFA (Trace File Analyzer) is a very useful tool, mainly used by Oracle support, although we can always use it to extract information from a system. I also recommend taking a look at the information it contains. I am currently updating to the latest version of TFA so I post this post as an aid for those who do not know and also as a reminder for me.

To know if it is installed (in this case Solaris 11, varies depending on the platform);

Grep TFA_HOME = /etc/init.d/init.tfa

He would return something similar to this;

TFA_HOME = / app / oracle / grid / 121 / tfa / node-1 / tfa_home

If it is installed, then to know what version we have;

Export TFA_HOME = / app / oracle / grid / 121 / tfa / node-1 / tfa_home
$ TFA_HOME / bin / tfactl print status

I will return something like this


.-----------------------------------------------------------------------------------------------.
| Host | Status of TFA | PID | Port | Version | Build ID | Inventory Status |
+----------+---------------+------+------+------------+----------------------+------------------+
| node-1 | RUNNING | 1834 | 5000 | 12.1.2.7.0 | 12127020160304140533 | COMPLETE |
| node-2 | RUNNING | 1810 | 5000 | 12.1.2.7.0 | 12127020160304140533 | COMPLETE |
'----------+---------------+------+------+------------+----------------------+------------------'

HTH – Antonio NAVARRO

 

ORA-02065 Changing Max_Dump_File_Size Parameter

 

Yesterday I was generating some traces (1046) in a database in version 10g, when I went to see the dump, in row mode I appeared the hateful message

*** DUMP FILE SIZE IS LIMITED TO 25722880 BYTES ***

Of course, it’s my fault for not looking at it previously, to solve it you can extend it at the session or system level. In my case as I was tracing several sessions, I would like to change it to the system level, so I run;

Alter system set max_dump_file_size = 100m;

This gave me back the following error

ORA-02065: illegal option for ALTER SYSTEM

Doing some memory remember that it is a string of text and has to go in quotes, as in the following example;

alter system set max_dump_file_size= ‘100m’;

Better.
HTH – Antonio NAVARRO