Configing AWS for E-Business Basic settings.

So we have to build a templated E-Business suite

Firs this

symptom : enabling APXS support for Apache2, no apxs2

solution : yum install httpd-devel

Building PHP with OCI8

problems occur because when configuring for build you get

checking libxml2 install dir... no
checking for xml2-config path...
configure: error: xml2-config not found. Please check your libxml2 installation.
How to solve :
yum install libxml2-devel

and then it works.

Oracle BIP publisher throws nasty errors if you don't have the sample datasets installed. Can only trace this with wireshark !

Adding the Examples Tables back into a database.


With 11g they are not just a DDL create, there is a special RMAN pl/sql call and everything.

The best thing to do is :

1: $OH/demo/schemas/mkplug.sql copy to m2.sql and edit.

remove all defines and set the variables to hardcode.

The missing DFB files can be found at $OH/assistants/dbca/templates, as can the hotplug example.dmp, also fill in the output DBF file in the normal oradata location.


Make sure the log file location has a / at the end for Linux, as the spool won't work properly otherwise.

Then it just runs !!!!

database vault install.

Just installed DB Vault at a customer site. Had to do 12 reinstalls before we found the cause of the error.

symptom : 10.2.0.4

AUD$ was owned by SYS. This is wrong. In 10.2 AUD$ is owned by SYSTEM and a synonym points to it. [ Yes I know it's all unsupported ]

Theoretically there is no recreate for AUD$, so only supported solution is to export, recreate DB, import, re run vault config [ As If ]

Hacked by obtaining AUD$ DDL from a known good 10.2.0.4 and recreating the table

Database vault then went in without a worry....

So there you are !

Edit : found out later there is something wrong somewhere for this to have been caused.

Audit Vault Agent Config Part 1

When running the verifier you are asked to export an env variable = testdba/password

of course it should be

SET AVORCLDB=SYSTEM/

and now avorcldb verify works

otherwise you get a username invalid error. Small typo, but reinforces the "just-out-the-door" thinking behind it .