Entries Tagged 'Legacy' ↓

By Jon Griffin
I have added my documents related to ArsDigita, OpenACS and ACS (ArsDigita Community System). They are relevant for anyone wanting to understand OpenACS, it’s history and why some design decisions were made. There are also some pearls of database programming (specifically Oracle) in these documents.

Originally ACS was only meant to run on Oracle and AOLserver (formerly naviserver). When ACS changed to it’s new version (4.0) back in 2000 (if I remember correctly), they added a hook for multiple database backends. Originally this was for the ACS/pg (later OpenACS) project.

Caution: May be gentoo specific

Scenario:

1 Master Server
Many clients
LAN

Installing on the Master Server

1. Install clockserver package on server.
2. get script from http://www.guinix.com/software/clocksd.html - appears dead.
   or the one local which has been changed for gentoo gentoo diff for clocksd.

Please Note this post is for archival purposes. I don’t know if Oracle after 8.x needs this. Hopefully it will still be of use to someone.

---

So your programmer decided to create a query that had a little syntax error. Say, a typo and it became an endless loop. Now your temporary tablespace is hosed because it is bigger than 2 gigs.Note that this is really only a solution for temp files because they don’t have any data that needs saving.Here is how to fix it:

By Jon Griffin

Please Note this post is for archival purposes. I don’t know if Oracle after 8.x needs this. Hopefully it will still be of use to someone.

• Your temporary tablespace is hosed - Salvaging your programmers big syntax error.
• analyze - Using analyze to speed up Oracle.

Some useful queries

The below query shows all tables that have more than one index with the same leading column. These indexes can cause queries to use an inappropriate indexes; in other words, Oracle will use the index that was created most recently if two indexes are of equal ranking. This can cause different indexes to be used from one environment to the next (e.g., from DEV to TEST to PROD).