libsqlplus.so: cannot open shared object file

Error

libsqlplus.so: cannot open shared object file: No such file or directory

Cause

LD_LIBRARY_PATH is not set.

Solution

set the LD_LIBRARY_PATH environment variable to the folder where the “libsqlplus.so” file resides.

For example, 

export LD_LIBRARY_PATH=/DB/app/oracle/product/1124/dbhome_1/lib/

bash-3.2$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on 

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

SQL> 

ORA-01000: maximum open cursors

Error

Retrieving Snapshot Target Data (1) - 14:48:59
Error: Snapshot Get Target Data routine failed. ORA-01000: maximum open cursors
exceeded
ORA-06512: at "SYS.DBMS_SYS_SQL", line 909
ORA-06512: at "SYS.DBMS_SQL", line 39
Running: CREATE TABLE snapshot_temp_data_764_1

Cause

Maximum open cursors limit exhausted.

Solution

If the value of the database parameter "open_cursors" is not set sufficiently high, then it causes the "ORA-01000: maximum open cursors exceeded" error.

SQL> alter  system set open_cursors=600 scope=both sid='*';

If you are using SPFILE to set database parameter, you can change this value by doing the following while logged into SQL*Plus as SYSDBA:

SQL> alter system set open_cursors=<new_value> scope=both;

In case you are not using SPFILE and are instead using init<SID>.ora file, you should change the value for open_cursors by adding a line to that file or changing any existing setting to look like:

OR

If open_cursors values is much enough then involve your developer to validate the code and ask them to close the cursor after processing statements which were left not closed.

ORA-00600: internal error code, arguments: [729]

Error

ORA-00600: internal error code, arguments: [729], [408], [space leak], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/tabsdr/TABS2/incident/incdir_33266/TABS2_ora_5348_i33266.trc

Cause

Memory leak problems generally occur when Oracle is trying to free memory allocated to a process. The memory leak dump is generally discovered during session logoff, when Oracle frees the heaps that are allocated for the user process.

Solution

When a user connects to Oracle, a user process is created and at that time the heap is allocated. Every process will have its own memory heap.

If there are no other errors reported at the same time, this may be a case where the error was a rare occurrence and can be safely ignored. As a rule of thumb, leaks less than 90,000 bytes in size are considered to be of low significance.

In this case the space leak is very very low i.e 408 which can be very safely ignored.

Reference

ORA-00600: Internal Error Code, Arguments: [729], [40], (Doc ID 2102971.1)

ORA-46268: Conflicting operation on audit table(s)

Error

SQL> BEGIN
  DBMS_AUDIT_MGMT.set_audit_trail_location(
    audit_trail_type           => DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD,
    audit_trail_location_value => 'TABS_DATA');
END;
/    2    3    4    5    6
BEGIN
*
ERROR at line 1:
ORA-46268: Conflicting operation on audit table(s)
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 61
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 1530

ORA-06512: at line 2

Cause

Session was interrupted by CTRL+C

Solution

No action required and nothing to worry, allow some time to API completion and retry it.

SQL> BEGIN

  DBMS_AUDIT_MGMT.set_audit_trail_location(

    audit_trail_type           => DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD,

    audit_trail_location_value => 'TABS_DATA');

END;

/     2    3    4    5    6

PL/SQL procedure successfully completed.