Skip to main content

SQLException: ORA-02020: too many database links in use.



You can limit the number of connections from a user process to remote databases using the static initialization parameter OPEN_LINKS. This parameter controls the number of remote connections that a single user session can use concurrently in distributed transactions.

If you are not sure how many database links are opened up concurrently by your session's database application, you can query v$dblink

select in_transaction, count(*) from v$dblink group by in_transaction;

To Increase the Database Links limit.  Follow the below.

SQL> select name from v$database;

NAME
---------------------------
ORCL


SQL> show parameter open_links;

NAME                                 TYPE                                         value
------------------------------------ --------------------------------- ------------------------------
open_links                           integer                                         4  


Default Value is > 4

Here have changed from 4 To 60.

SQL> ALTER SYSTEM SET OPEN_LINKS=60 SCOPE=SPFILE;

System altered.

NOTE: Parameter 'OPEN_LINKS' its static parameter. Hence database bounce is required, once change is made. Then only the new value will be effected.

SQL> select name from v$database;

NAME
---------------------------
ORCL

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size                  2101808 bytes
Variable Size             377490896 bytes
Database Buffers          687865856 bytes
Redo Buffers                6283264 bytes
Database mounted.
Database opened.

SQL> show parameter open_links;

NAME                                 TYPE                                         value
------------------------------------ --------------------------------- ------------------------------
open_links                           integer                                         60


Thank You!

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...
Post a Comment
Read more

Difference between AWR, ADDM and ASH reports

AWR: Automatic Workload Repository gathers, processes and maintains performance stats used for problem detection and self-tuning the databases. Different Components that uses AWR are: Automatic Database Diagnostic Monitor Undo Advisor SQL Tuning Advisor Segment Advisor Different types of AWR Reports for different purposes: For Single Instance Environment: @$ORACLE_HOME/rdbms/admin/awrrpt.sql For Oracle RAC Environment : @$ORACLE_HOME/rdbms/admin/awrgrpt.sql For a particular SQL Statement : @$ORACLE_HOME/rdbms/admin/awrsqrpt.sql For Comparing the reports : @$ORACLE_HOME/rdbms/admin/awrddrpt.sql ADDM: Automatic Database Diagnostic Monitoring Report analyzes the AWR data on a regular basis, to give you overview of the root cause of the problem which is affecting your database’s performance. It also provides suggestions or recommendations for rectifying any problem identified and lists the areas which are having no issues. ADDM recommends multiple solutions for the DBA to choose from which...
Post a Comment
Read more