The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

Check that there are enough Output Post-processor service processes running.

More information may be found in the service process logfile.

Output Post Processor (OPP) issue



Solution:

Two profiles options actually control the timeouts of OPP.

             i.        Concurrent:OPP Response Timeout
            ii.        Concurrent:OPP Process Timeout

  1. OPP No Response: 
                      i.        Increase the value (in seconds) for the profile option 'Concurrent:OPP Response Timeout'. If the current value is 120 then set it to 7200. 
                     ii.        Increase the number of processes or threads (or both) of the OPP via System Administrator >Profile>
Find Both like that or set value 7200..
 %Concurrent%OPP%Process%Timeout%
7200
%Concurrent%OPP%Response%Timeout%
7200

Save it.

                    iii.        Bounce application services.

REP-0004 INVOKING THE ORACLE REPORTS BUILDER

REP-0004 INVOKING THE ORACLE REPORTS BUILDER (Doc ID 1013620.6)

APPLIES TO:

Oracle Reports Developer - Version 6.0 to 11.1.2.2.0 [Release 6 to 11g]
Oracle Application Object Library - Version 11.0.0 to 12.1 [Release 11 to 12.1]
Generic UNIX
Checked for relevance on 20-Oct-2015

SYMPTOMS

You are receiving the following error from Oracle Reports:

REP-0004 : Warning - Unable to open user preference file.

 There may also be other errors like:

REP-0003  - Warning - Unable to open global preference file.

REP-3000 - Internal error starting Oracle Toolkit.

CAUSE

 There are several causes of this error.

SOLUTION

Possible causes and solutions of REP-0004 include the following:

1.  No prefs.ora file in HOME directory:

Oracle Reports will look into the user's HOME directory for the prefs.ora preferences file.
 If a prefs.ora file does not exist in your HOME directory, you can copy the prefs.ora
file that came with the Oracle Tools.

A prefs.ora file is shipped with the Oracle Tools, and is located in:

$ORACLE_HOME/tools/admin/prefs.ora

You can also create a prefs.ora file the first time you are in the Reports Builder

To create a prefs.ora file from the Oracle Reports Builder

Oracle Reports 6.0.X:

Start the Oracle Reports Builder
Select Tools->Preferences
Select your preferences
Press the OK button
This will save a prefs.ora file in your HOME directory when you exit Reports Builder.
Oracle Reports 9.x / 10.x /11.x:

Start the Oracle Reports Builder
Select Edit->Preferences
Select your preferences
Press the OK button
This will save a prefs.ora file in your HOME directory when you exit Reports Builder.

2.  Location of the prefs.ora file:

If you want to use a prefs.ora file in a different directory than HOME (for versions < 11g) or
ORACLE_INSTANCE/config/FRComponent/frcommon/tools/admin/ for 11g, set the
 $ORACLE_LOCALPREFERENCE environment variable to that directory.

Example:  You want all users to access a common prefs.ora file located in /home/allusers/prefs.ora.

% setenv ORACLE_LOCALPREFERENCE /home/allusers

              OR

% export ORACLE_LOCALPREFERENCE=/home/allusers

3.  Insufficient privileges on the prefs.ora file:

The user invoking Oracle Reports must have read privileges on the prefs.ora file.  

4.  A system error made it impossible to open the file. 

The preferences file may have become corrupted.  If you suspect file corruption,
copy $ORACLE_HOME/tools/admin/prefs.ora and respecify your preferences.  

Note:
Oracle Forms and Oracle Graphics also read prefs.ora, thus you will have to respecify
all preferences that were set in the corrupted prefs.ora file.
Consult your operating system documentation or contact your system administrator for assistance
 setting environment variables or file privileges.

REP-0004

REP-0004: Warning: Unable to open user preference file

Metalink id:
R12: Request Logs Contain the Message "REP-0004: Warning: Unable to open user preference file" [ID 1120529.1]


Symptoms:

All concurrent requests that run REPORTS are printing the following warning in the request log.
REP-0004: Warning: Unable to open user preference file.

Cause:

This message occurs when the concurrent process attempts to open the Oracle Reports executable and your local preference file cannot be found or opened. This is just a warning, so the request will continue to run even if this occurs.

Solution:

To resolve the warning, copy the prefs.ora file from your Reports Builder $ORACLE_HOME/tools/admin/ directory into the Applications $HOME directory.

Example:

Copy of the file prefs.ora in the directory /apps/prod/apps/tech_st/10.1.2/tools/admin/ to the directory  /home/applprod/.

[applprod@sujeet ~]$ cd /apps/prod/apps/tech_st/10.1.2/tools/admin/

[applprod@sujeet  admin]$ ls
prefs.ora  

[applprod@sujeet  admin]$ cp prefs.ora /home/applprod/

Note: Bounce apache service.



Issue resolved.


NOTE:
For a report developed by xml publisher getting the same error, create /HDDATA/xml_tmp directory (environment dependent) on the system server after checking Administration from XML Publisher Administrator responsibility -> Configuration -> General -> Temporary directory column is /HDDATA/xml_tmp.

APP-FND-00362

"APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM,
 because the environment variable &BASEPATH is not set for the application to
which the concurrent program executable &EXECUTABLE belongs."


Cause :- 

The issue is caused by a custom executable name for the Invoice on Hold report: XXX_APXINROH


Solution :-

(R) : System Administrator
(N) : Concurrent > Program > Define

Search for short name : APXINROH
1 - Change the Executable Name from XXX_APXINROH to APXINROH
2 - Re-run the report and confirm the error is resolved.

If issue not resolved please try below steps.

OR

The error occurs when run only Thai Localization Reports.
And your customer confirms, the issue was solved after setting the basepath of $CLA_TOP in .env file.

Linux 7 installation steps

 Red Hat Enterprise Linux 7 (64 bit) Installation steps by steps

Once you insert and boot your machine with the RHEL DVD, you will get the below screen. 

Select "Install Red Hat Enterprise Linux 7 and Press "Enter".

Select the Language preference.

The Next screen contains almost all the configuration which has to be performed for the installation. Since we have already selected our Language and Keyboard preferences, we can skip that step here.

Lets start by setting the Date and Time.

Select your Location as for me it is Asia/Kolkata.

Next we will select the packages which we want to install. So Select "Software Installation" which will lead you to the below screen. In my case I will install the "Base Installation" package having "Server with GUI" and in case you want to add any extra Add On, you can select the same from the left panel as shown below.

Next we need to configure partitions. So select "Installation Destination"

Select the hard disk which you have used to install RHEL 7, as for my case as you can see 200 GB hard drive.

Also if you want the OS to automatically create the partition select the same or else for this article lets manually create the partitions.

I will create /boot, /, swap space 
note- swap space depend on RAM size if RAM-10 GB than Swap-20 GB.

Click on Done and select Accept Changes.

The last one is to Configure Network.

Change the Ethernet device name or else you can skip that part. Next configure you IP details as per your environment i.e IPv4 or IPv6. We are using IPv4 so selected the "IPv4 Settings" and added the IP, Netmask,Gateway and DNS details in the same.. Click on "Done" to save the configuration and go a step back.

So we are done here with all the options on this screen. Next we can "Begin Installation"

As you see the installation has begun in the mean time you can add a password for your root user. Also you can create additional user by using the "User Creation" thumbnail.

Provide a password for root account.

Create a user.(Optional).

In the mean time let the installation complete. Once done click on Reboot.

Once the machine reboots, next it will prompt the below screen. Click on "License Information"

Accept the Terms and Conditions.

Click on "Finish Configuration".

Next you will get the Kdump configuration page.

Let us enable the Kdump and let the machine decide the amount of memory required for the same.

I do not want to register my system to RHN as for now,also we can perform this step later so let us skip this part for now.

Next you get your Login Screen which means we have successfully installed our Operation System i.e. RHEL 7.0 (64 bit).





ORA-00942: table or view does not exist in 12c


ORA-00942: table or view does not exist in 12c database (Doc ID 1948487.1)


APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]

Information in this document applies to any platform.

SYMPTOMS

Creating the database manually as shown below:
CREATE DATABASE ORCL02
LOGFILE GROUP 1 ('/u022/oradata/ORCL02/ORCL02redo01a.log','/u023/oradata/ORCL02/ORCL02redo01b.log') SIZE 50M,
        GROUP 2 ('/u022/oradata/ORCL02/ORCL02redo02a.log','/u023/oradata/ORCL02/ORCL02redo02b.log') SIZE 50M
CHARACTER SET US7ASCII
NATIONAL CHARACTER SET AL16UTF16

....

ENABLE PLUGGABLE DATABASE
SEED
   FILE_NAME_CONVERT = ('/u011/oradata/ORCL02/CDB/','/u011/oradata/ORCL02/SEED/',
                        '/u005/oradata/ORCL02/CDB/','/u005/oradata/ORCL02/SEED/')
   USER_DATA TABLESPACE USERS DATAFILE '/u011/oradata/ORCL02/SEED/users01.dbf' size 1024m


the following errors are generated in both alert.log and trace files:

Errors in file /u021/app/oracle/admin/diag/rdbms/orcl02_rhd208/ORCL02/trace/ORCL02_cjq0_12527.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-12801: error signaled in parallel query server P001
ORA-00942: table or view does not exist

CAUSE

Multitenant created manually with these initialization parameters aq_tm_processes, job_queue_processes,events, parallel_... , etc


SOLUTION

  This has been discussed in unpublished Bug 20049142 ( closed in status 32- Not a bug)
where it mentioned that if the customer must create manually, please ensure as a minimum:
   - use a minimal init.ora without aq_tm_processes, job_queue_processes, events, parallel_... , etc
   - use a 8 bit character set as a minimum not US7ASCII
   - make sure the seed is created with "_oracle_script"=true
   - do not run cat scripts directly use the perl catcon system


 An alternative is to use DBCA to create the scripts and to run them manually.

VNC Server Configuringon Linux 7.1

Install & Configure VNC Server in RHEL 7

VNC (Virtual Network Computing) Server allows the remote Desktop sharing using remote VNC clients like VNC viewer.
In RHEL 7 package named “tigervnc-server” needs to be installed in order to setup the VNC server.

[root@sujeet /]# yum install tigervnc-server

Step:1 
Make Sure the Desktop Packages are installed

In order to setup VNC server first we make sure that Desktop is installed ,in My case i am using Gnome Desktop.
 If Gnome Desktop is not installed on your Linux machine then use the below command to install.

[root@sujeet /]# yum groupinstall GNOME Desktop


Step:2
Install Tigervnc and other dependency Package.

[root@sujeet /]# yum install tigervnc-server xorg-x11-fonts-Type1


Step:3
 Setup VNC Server Configuration File.

Copy the VNC config file “/lib/systemd/system/vncserver@.service” to the “/etc/systemd/system/vncserver@:<Port_Number>.service”.

While Copying the VNC config file we can mention the port number on which we want VNC service to be listen.
In my case i am using port 8 , it means VNC will listen on “5908”.

So while Connecting to the VNC server We can specify port number as <IP_Address_VNC_Server:8> or <IP_Address_VNC_Server:5908>


[root@sujeet /]# cp /lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@:8.service

Step:4 
Update the User’s Information in the Config File

[root@sujeet ~]# vi /etc/systemd/system/vncserver@:8.service

ExecStart=/usr/sbin/runuser -l oracle -c "/usr/bin/vncserver %i"
PIDFile=/home/oracle/.vnc/%H%i.pid

Replace the “oracle” user as per your requirement.
In my case oracle user will able to control and manage its desktop session using remote VNC clients.


Set the Firewall Rule if firewall is enabled on your linux box.

[root@sujeet~]# firewall-cmd --permanent --zone=public --add-port=5908/tcp
success
[root@sujeet ~]# firewall-cmd --reload
success

Step:5 
Set the VNC password for the User.
login with oracle User after that reset VNCSERVER password.

[oracle@sujeet ~]# vncpasswd
Password:******

Start and Enable the VNC Service at boot.

Execute below commands as root only.

[root@sujeet/]# systemctl daemon-reload
[root@sujeet /]# systemctl start vncserver@:8.service
[root@sujeet /]# systemctl enable vncserver@:8.service

[root@sujeet /]# ln -s '/etc/systemd/system/vncserver@:8.service' '/etc/systemd/system/multi-user.target.wants/vncserver@:8.service'
ln: failed to create symbolic link ‘/etc/systemd/system/multi-user.target.wants/vncserver@:3.service’: File exists

[root@sujeet/]# systemctl status vncserver@:8.service

Open VNC port using iptables:
[root@sujeet sysconfig]# iptables -I INPUT -p tcp --dport 5908 -j ACCEPT

[root@sujeet sysconfig]# firewall-cmd --add-rich-rule='rule family="ipv4" service name=vnc-server accept'

FirewallD is not running


Step:6
 Access Remote Desktop Session.


Now let's use netstat to check what ports VNC is listening on.

[root@sujeet ~]# netstat -tulp | grep vnc


Terminating a VNC Session

Similarly to enabling the vncserver service, you can disable the automatic start of the service at system start:
~]# systemctl disable vncserver@:8.service

Or, when your system is running, you can stop the service by issuing the following command as root:

~]# systemctl stop vncserver@:8.service


How to check whether particular port is open or closed on UNIX?
Login with root user.

[opc@b0f67e ~]$ lsof -i -P
and grep the output for the port you are looking for.

For example to check for port 80 do

[opc@b0f67e ~]$ lsof -i -P | grep :80

[opc@b0f67e ~]$ netstat -ano|grep 5908|grep LISTEN
[opc@b0f67e ~]$ lsof -i -P | grep :5908



ERROR 1396 (HY000): Operation ALTER USER failed for 'Mysql'@'%'

 This MySQL error — ERROR 1396 (HY000): Operation ALTER USER failed for 'Mysql'@'%' — means that MySQL cannot find the user ...