APP-FND-01542 : This Application Server is not authorized to access this system. Please contact your system administrator

https://dbissues.blogspot.com/2017/10/app-fnd-01542-this-application-server.html

This error message pops-up when value for profile “s_appserverid_authentication” is set to “SECURE“ in Application Context file.

This profile value can be set to three different values, “SECURE, PARTIAL, OFF”.

To over come this issue set check profile value “s_appserverid_authentication” from “SECURE” to “OFF”.

Then.
Stop the middle tiers
Run autoconfig
Startup the middle tier services
Retest direct login to forms

How to compile invalid objects in an APPS Environment

https://dbissues.blogspot.com/2017/10/how-to-compile-invalid-objects-in-apps.html

Compiling Objects Manually Through SQL Commands

First find the Invalid Objects in the Database by below given query.

SELECT COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = ‘INVALID’;

For a more detailed query, use the following script :

SELECT OWNER, OBJECT_TYPE, COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = ‘INVALID’
GROUP BY OWNER, OBJECT_TYPE;

To recompile an individual object, connect to SQL*PLUS as the owner of the object (generally apps) and use oneof the following depending on the object type :

alter package <package_name> compile; (package specification)
alter package <package_name> compile body; (package body)
alter view <view_name> compile; (view)

If the object compiles with warnings, use either of the following to see the errors that caused the warnings :

show errors
OR
select * from user_errors where name = ‘<OBJECT_NAME>’;
Compiling Objects Through ADADMIN Utility

1. Login OS with APPS owner.

2. Start the ADADMIN Utility from the Unix prompt with this command :

$adadmin

3. Under the Maintain Applications Database Objects Menu, select Compile APPS schema(s)

Tablespace Growth Query

https://dbissues.blogspot.com/2017/09/tablespace-growth-query.html

  SELECT  TO_CHAR(SYSDATE,'MON-YYYY') period , a.tablespace_name,
                  ROUND (((c.BYTES - NVL (b.BYTES, 0)) / c.BYTES) * 100,2) percentage_used,
                            c.BYTES / 1024 / 1024 space_allocated,
                            ROUND (c.BYTES / 1024 / 1024 - NVL (b.BYTES, 0) / 1024 / 1024,2) space_used,
                            ROUND (NVL (b.BYTES, 0) / 1024 / 1024, 2) space_free,
                            c.DATAFILES
                          FROM dba_tablespaces a,
                               (    SELECT   tablespace_name,
                                          SUM (BYTES) BYTES
                                   FROM   dba_free_space
                               GROUP BY   tablespace_name
                               ) b,
                              (    SELECT   COUNT (1) DATAFILES,
                                          SUM (BYTES) BYTES,
                                          tablespace_name
                                   FROM   dba_data_files
                               GROUP BY   tablespace_name
                            ) c
                          WHERE b.tablespace_name(+) = a.tablespace_name
                            AND c.tablespace_name(+) = a.tablespace_name

Delete Interface/Integrator/Component - Web ADI

--Delete an Interface/Integrator Details

SELECT biv.application_id

       ,biv.integrator_code

       ,biv.user_name

       ,bib.interface_code

   FROM bne_integrators_vl biv

       ,bne_interfaces_b   bib

  WHERE upper(user_name) like '%XXAK%'

    AND bib.integrator_code = biv.integrator_code ;

---------------------------------------------

--Delete an Interface

DECLARE

   vn_number   NUMBER;

BEGIN

   vn_number := bne_integrator_utils.delete_interface

                (p_application_id => 20003,

        p_interface_code  => 'XXAKTESTUPADI_XINTG_INTF1');

                

   DBMS_OUTPUT.put_line ('ADI Interface Deleted '||vn_number);

   COMMIT;

   --

EXCEPTION  

   WHEN OTHERS THEN

      DBMS_OUTPUT.put_line('Error: '||sqlerrm);

      ROLLBACK;

END;

----------------------------

--Delete an Intergrator

DECLARE

   vn_number number:=0;

BEGIN

   vn_number:= bne_integrator_utils.delete_integrator

               (p_application_id => 20003,

                p_integrator_code => 'XXAKTESTUPADI_XINTG');

               

   dbms_output.put_line(' ADI Deleted : '||vn_number);

   COMMIT;

   --

EXCEPTION  

   WHEN OTHERS THEN

      DBMS_OUTPUT.put_line('Error: '||sqlerrm);

      ROLLBACK;

END;

---------------------------

--Delete a Component

DECLARE

   vn_number number:=0;

BEGIN

   vn_number:=BNE_INTEGRATOR_UTILS.DELETE_COMPONENT(p_application_id => 200,

                p_COMPONENT_CODE => 'HUBINV_XINTG_INTF1_C9_COMP');

              

   dbms_output.put_line(' ADI Deleted : '||vn_number);

   COMMIT;

   --

EXCEPTION 

   WHEN OTHERS THEN

      DBMS_OUTPUT.put_line('Error: '||sqlerrm);

      ROLLBACK;

END;

How To Clear BNE Cache

https://dbissues.blogspot.com/2017/08/how-to-clear-bne-cache.html

To Clear BNE cache:

Using System Administrator responsibility:

Login to the application as a user with System Administrator Responsibility.

Select the System Administrator Responsibility.
Bring up the AdminServlet by changing the URL in the browser where you are logged into the applications keeping the appropriate hostname.domain and port number.

Release 11i:
http://hostname.domain:portnumber/oa_servlets/oracle.apps.bne.framework.BneAdminServlet
On the new web page that loads, scroll down and click the "clear-cache" link

Release 12:
http://hostname.domain:portnumber/OA_HTML/BneAdminServlet
On the new web page that loads, scroll down to the Cache Name section.
Clear the cache for the following by clicking the "(clear)" link:

Cache Name
============
Default Cache
Generic SQL Statements
Web ADI Repository Objects
Web ADI Parameter Lists
Web ADI Parameter Definitions


The BNE cache is now cleared.

PDF Output is being sent in .out format as mail attachment through Oracle

https://dbissues.blogspot.com/2017/08/pdf-output-is-being-sent-in-out-format.html

Attachment is being sent in .out format for PDF file

Currently, there is no such function in EBS to generate report output file extension in the mail as anything other than .out.

Workaround:

The delivery option is coming from xml publisher API , and if the report is generated by xml publisher, it will generate two output file, one is the output of the request, an .out file and the other one is generated by bi publisher, which may be a .pdf file or an .xls file. The API then attach  the correct file in the mail, but when the report is generated by oracle report, though it is a pdf file, it is an .out file in the file system and API attach it in the mail.

Simple is, If the report is generated by xml publisher , the pdf format output will have a output file as .pdf. In the case, the delivery API would send the pdf output in the email as the attachment with .pdf . So you may need to generate the report output from Oracle*Report by xml publisher.

----------------------------------

Register Report in XML Publisher in .rtf format and make Default Output view & Preview Format to PDF.

In concurrent Program, select Output Format as XML and run the Report. Email will be sent in .pdf format

How to make a .tar file on Linux

https://dbissues.blogspot.com/2017/07/how-to-make-tar-file-on-linux.html

tar -czvf tt_new.tar tt