ERROR: ORA-12560: TNS:protocol adapter error: No listener.

Posted on by Leave a comment

Problem: You are trying to access oracle database using sqlplus, or using forms builder, or using oracle reports builder and Toad.

ERROR: ORA-12560: TNS:protocol adapter error: No listener.

Solution: check the status of the Database listener by Running the Command Prompt with this code : lsnrctl status
if the command completed unsuccessfully start the Listener by running the Command Prompt with this code : lsnrctl start

if the above does not work.
go to C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\ADMIN on your local machine

check if the host name of the listener and tnsnames are the same as to your pc name.
Eg: Tns LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(ADDRESS = (PROTOCOL = TCP)(HOST = Example_PC or IP_ADDRESS)(PORT = 1521))
)
)

DEFAULT_SERVICE_LISTENER = (XE)

Eg: Tnsnames XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = Example_PC or IP_ADDRESS)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
)
)

 

Oracle Appliaction Express Access denied by Application Security Check

Posted on by Leave a comment

Problem: You are trying to access oracle apex internal admin. oracle database will validate
,check if the version being used is 3.0 and above. in this case, there`s a problem with the version being used.

Solution: Check your Apex Version, if it is 3.0 up to 3.9

Login as sys or system with sqlplus (sqlplus sys as sysdba )on the database and run this script:

alter session set current_schema = APEX_030000;
update APEX_030000.wwv_flow_fnd_user
set change_password_on_first_use =’N’
where lower(user_name) = ‘admin’
/
commit;

if your Apex Version is 4.0 up to 4.9

Login as sys or system with sqlplus (sqlplus sys as sysdba )on the database and run this script:

alter session set current_schema = APEX_040000;
update APEX_040000.wwv_flow_fnd_user
set change_password_on_first_use =’N’
where lower(user_name) = ‘admin’
/
commit;

 

Error REP-0756 Unable to find PL/SQL library ‘inv.pll’ when Opening a Report in Oracle Reports Builder

Posted on by Leave a comment

You are trying to open a Report in Oracle Reports Builder and you are getting an error:

Error REP-0756 Unable to find PL/SQL library ‘inv.pll’…

  1. Login to the Application Server under $AU_TOP/plsql.
  2. Copy the file inv.pll to your PC.
  3. Open the report again in Oracle Reports Builder.
  4. When the error pops up … open the inv.pll file from the folder you saved it on your PC.
  5. The error will now disappear.
 

Oracle Views return no data due to NLS LANGUAGE Settings

Posted on by Leave a comment

In Oracle E-Business Suite, and if there are multiple languages installed, and if you are not able accesses data from tables like fnd_lookup_values_vl or any other VL tables. Usually views with a condition of: LANGUAGE = USERENV (‘LANG’)in the where clause will not return data if the NLS LANGUAGE is not setup correctly.

Set USERENV(‘LANG’) in SQL*Plus

Check what language is set, using following query you can set the NLS LANGUAGE as follows:

SELECT USERENV(‘LANGUAGE’) “Language” FROM DUAL;

Set it to ‘AMERICAN’ using following alter command, you definitely get

ALTER session SET nls_language=’AMERICAN’

Set USERENV(‘LANG’) for SQL Developer

As SQL Developer doesn’t require an Oracle client, it doesn’t look at the Oracle registry settings to get your default NLS settings (where TOAD looks) – it picks up defaults from the OS (i.e. Regional and Language Settings on Windows).

To fix this (i.e.to make USERENV (‘lang’) return US), change your SQL Developer NLS settings (Tools > Preferences > Database > NLS Parameters) to have Language = AMERICAN and Territory = AMERICA

Set USERENV(‘LANG’) For TOAD

Access NLS Parameters, from the Database menu, -> select Administer| -> NLS Parameters

Set the NLS_LANGUAGE to ‘AMERICAN’

There some times org specific tables for that you need to setup org_id, you can use any of the following

fnd_global.apps_initialize

OR fnd_client_info.set_org_context

OR dbms_application_info.set_client_info