Installed Apache on Suse Linux 10. Configured httpd.conf including a rewrite rule in a virtual host.
No configuration errors, but it did not work at all! After a while I discovered that the mod-rewrite module had been installed, but not enabled with this version of Apache (2.2.x). This URL gives a pretty good hand-out how to do this. Because I’m not sure this link will last for ever, a copy of (part of) the text in it with a small addition of my side:
- Edit the file /etc/sysconfig/apache2 as root:
- search for APACHE_MODULES, you should find a line like this
APACHE_MODULES="suexec access actions alias auth auth_dbm autoindex cgi dir env expires include log_config mime negotiation setenvif userdir ssl php4"
- Add rewrite to the content in the list between the “
- Save the changes and quit
- run /etc/init.d/apache2 restart to restart the Apache server
- run SuSEconfig to update the apache configuration files
Now, the mod_rewrite is enabled and integrated.
Helped a collegae who was migrating a discoverer configuration to another node with a different version (from 10.1.2 to 10.1.4) with now a 10.2 – infrastructure database in a separate home. The OID-users were already successfully migrated, with a little help of the example-script here, but one of the problems was that discoverer didn’t use the single-sign on. The other was that the private and public connection users had made, had disappeared.
By enabling Single Sign-On for Discoverer (is not default when installed) the first problem had been solved:
What to do about the ever growing files on Oracle Application Server as:
These files are not logrotated (at least in the ‘older versions’ of OAS) and cannot always be deleted or renamed manually on a ‘normal’ way (I know, there is a way..), and it must be scripted to avoid extraordinary large log-files.
Quite annoying, until Frits Hoogland pointed me at a standard Linux-functionality, ‘logrotate’.
For example, to logrotate the files default-web-acces.log and server.log in the directory $ORACLE_HOME/j2ee/home/log/home_default_island_1, create a script like this:
(an explenation of these parameters follows at the bottom of this post, pay special attention to ‘copytruncate’, which is very suitable for several files of the application server.)
This script should be (on Linux) in /etc/logrotate.d/ (as root). Call it ‘ora_logrotate’ for example.
The Linux-program ‘logrotate’ is daily executed (from /etc/cron.daily/) and will run the scripts in /etc/logratate.d .
You can test this manually by running it like ‘/etc/cron.daily/logrotate ora_logrotate’. The file ora_logrotate will be executed when it is place in /etc/logrotate.d .
When there is a standardised environment you can also make a script like this:
Apex, version 3.2.1.00.10, on a 10.2.0.3-database is working fine for some time.
Then, while clicking the ‘application builder’ home-page, we got the ‘page not found’-error in the browser.
Logging of Apache shows:
mod_plsql: /pls/apex_schd/f HTTP-404 ORA-03113: end-of-file on communication channel\n
mod_plsql: Unable to reset state for mode 0: Err 3114 url=>/pls/apex_schd/f
Problem: A report, designed for generating PDF with the true-type font Univers in it, does not work while deployed on the web, and uses other fonts instead.
Cause: there’s no Univers installed in the Reports Services on Unix.
Solution: install the font and configure the Reports Service! Sounds simple…
In the process of figuring this out, I had several error-messages, like rep-1352 (The fonts specified for this report cannot be found for the character set specified by NLS_LANG) , and rep-1 (nothing else…).
Took a lot of time to eliminate those errors, partly because there was a feature in the specified report what did’nt speed up the process of resolving this issue: embedded html. This caused for example the “rep-1”-error.
Creating a reports server and integrate it with Enterprise Manager / iasconsole
– Under control of opmn (wil be automatically restarted)
– Visible and manageable under Enterprise Manager.
1. Create/start a new reports server : “$ORACLE_HOME/bin/rwserver.sh repproject
2. A small window will pop-up, showing that the reports server is starting up.
3. After it’s status is ready, stop this server.
4. Register this new reports server (you can do this also by hand, in the section of deleting this, you can also see what files you will have to update to insert or delete a reports server).