How to Start/Open 11g Form Builder and Report Builder in Unix

Open Oracle Forms Builder:

Starting the builder using frmbld executable directly rather than through the frmbld.sh wrapper script will result in FRM-10039
FRM-10039: Unable to start up the Form Builder

Hence, Open Oracle Forms Builder using the following command:

$ORACLE_INSTANCE/bin/frmbld.sh 

This will set required environment settings.

 
Open Oracle Reports Builder:

Oracle Report Builder should be open using the following command:

$ORACLE_INSTANCE/config/reports/bin/rwbuilder.sh

Note:
It is Not Supported to Execute frmbld.sh & rwbuilder.sh As Non-Oracle User.
One workaround is to use a UNIX utility called 'sudo'.

ORA-16019: cannot use LOG_ARCHIVE_DEST_1 with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Issue:

Below error encountered when trying to set LOG_ARCHIVE_DEST_1 while configuring Oracle Data Guard Parameters on Primary Database.

SQL> startup mount
ORA-16019: cannot use LOG_ARCHIVE_DEST_1 with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Cause:

We cannot use the LOG_ARCHIVE_DEST at the same time with LOG_ARCHIVE_DEST_1

Solution:

If you are using spfile then you can use the following:

SQL> alter system set log_archive_dest=' ' scope=spfile;
SQL> alter system set log_archive_dest_1='<archive log location>' scope=spfile;

Set other standby releated parameters and then Bounce Database to reflect the parameters.

If you are using pfile then follow below steps:

1) Comment out the LOG_ARCHIVE_DEST parameter in pfile
2) Shutdown the database

3) Startup with new pfile and mount the database
    SQL> startup mount pfile='<pfilename>';
   
4) check for the parameter log_archive_dest in not used

5) If parameters are ok, then create spfile from this pfile
    SQL> create spfile from pfile='<pfilename>';
   
6) Shut down the database and start it again so that it will use the spfile newly created
7) Set LOG_ARCHIVE_DEST_1 and other standby related parameters then bounce the database
    SQL> alter system set log_archive_dest_1='<archive log location>' scope=spfile;


 

Large number of job history (c*) and job files (d*) accumulated in /var/spool/cups in Linux

Issue:

Unable to print requests output from Oracle EBS.
There are large number of files accumulated in /var/spool/cups in Linux
Some begins with "d" example d00010 and others begin with "c" c00016

Cause:

cups is not cleaning up the "c" file after the job completes and printing gets stuck due to this.
They are retained until explicitly removed by Administrator.

Solution:

Configure cups to remove the job files (d*) and the job history (c*) files from /var/spool/cups/ after successful jobs have been sent to printer queues.

Configure cups to remove the job files beginning with "c"

The files whose names begin with a "c" are "job history" files.
If you would like to not retain job history, then you have to add the directive to /etc/cups/cupsd.conf

Action plan would be :

1. As a root – take backup of /etc/cups/cupsd.conf
2. Add the parameter below the maxlogsize line in /etc/cups/cupsd.conf –

    PreserveJobHistory Off

3. Then restart CUPS with the command:

    $ service cups restart

When PreserveJobHistory is set to Off, the job history (c*) files should be removed automatically approximately 30 seconds after a print job is completed.


Controlling the number of files stored in /var/spool/cups

The number of files stored in /var/spool/cups is controlled with the MaxJobs directive in /etc/cups/cupsd.conf.
The default value for MaxJobs is 500