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.
Wednesday, April 22, 2009
Friday, March 13, 2009
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 !!!!
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 !!!!
Friday, December 5, 2008
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.
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.
Wednesday, October 1, 2008
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 .
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 .
So you are fed up with Oracle Configuration Manager
This little beastie gets installed when you run opatch now. Most of you have no need whatsoever for it. So let's get rid of it :
Metalink Note 369111.1 has the answer but in True Oracle Fashion they didn't test it properly on all platforms
They did it on Linux, but the answer they give on Windows fails for me [ they wrote up something for Windows in cscript vbs ]
however it works quite nicely if you do
cd %ORACLE_HOME%\ccr\bin
deploypackages -d %ORACLE_HOME%\ccr\inventory\core.jar
And no more OCM.
Metalink Note 369111.1 has the answer but in True Oracle Fashion they didn't test it properly on all platforms
They did it on Linux, but the answer they give on Windows fails for me [ they wrote up something for Windows in cscript vbs ]
however it works quite nicely if you do
cd %ORACLE_HOME%\ccr\bin
deploypackages -d %ORACLE_HOME%\ccr\inventory\core.jar
And no more OCM.
Installing Audit Vault on Windows 2003
10.1.2.2.1 install :
All went well for the initial phase but failed 80% of the way through. The message it complains of is being unable to find or lock ewallet.p12 in the installation log, and you can spend a very long time trying to debug this. In fact it is completely misleading, the actual problem was that I had selected avadmin as the Audit Vault Administrator name, when this comes to run the installer it conflicts much much later with a predefined username; to fix this it's necessary to remove every trace of that install
by :
1: sc delete all the services just installed
2: regedit to delete all oracle keys
3: edit path and PERL5lib to remove all oracle references
4: remove c:\program files\oracle
5: remove the oracle home, flash and data directories.
Now you can run the installer again !
this time I picked avaultadmin as the admin name and it went through just fine !
BRGDS
Chris
All went well for the initial phase but failed 80% of the way through. The message it complains of is being unable to find or lock ewallet.p12 in the installation log, and you can spend a very long time trying to debug this. In fact it is completely misleading, the actual problem was that I had selected avadmin as the Audit Vault Administrator name, when this comes to run the installer it conflicts much much later with a predefined username; to fix this it's necessary to remove every trace of that install
by :
1: sc delete all the services just installed
2: regedit to delete all oracle keys
3: edit path and PERL5lib to remove all oracle references
4: remove c:\program files\oracle
5: remove the oracle home, flash and data directories.
Now you can run the installer again !
this time I picked avaultadmin as the admin name and it went through just fine !
BRGDS
Chris
Subscribe to:
Posts (Atom)