dezwart's questions

Reading through the BEA WebLogic 9.2 Deployment Descriptor Elements documentation, there are a few parameters that we already use in our web applications weblogic.xml to decrease the time it takes to run continuous integration tests against WebLogic 9.2:

• jsp-descriptor, precompile, false
• jsp-descriptor, page-check-seconds, -1
• container-descriptor, servlet-reload-check-secs, -1

This is what our weblogic.xml looks like:

<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                  xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <jsp-descriptor>
        <page-check-seconds>-1</page-check-seconds>
        <precompile>false</precompile>
    </jsp-descriptor>

    <container-descriptor>
        <servlet-reload-check-secs>-1</servlet-reload-check-secs>
    </container-descriptor>
</weblogic-web-app>

Are there are any other usual suspects that we could consider to squeeze out some more life from our build servers?

Does anyone know the magic incantation to disable the annoying blue led on the front of a LaCie 1TB High-Speed USB 2.0 external drive?

The manual for that model doesn't mention the ability to disable it, but for the NAS model; there is the option.

After reading the Linux installation guide for Oracle 11g, taking particular note of the pre-installation requirements; I have been able to record a response file for a silent installation based off a successful manual installation.

The issue is when performing the silent installation based off the recorded response file, the installation procedure will fail when executing the generate shell script for manually executing any steps that require intervention.

Further digging (read strace) shows the following exception in an out of the way logfile:

INFO: oracle.assistants.server:Internal PlugIn for {Micro Step state:step:1:configuration in CfmAggregateInstance: oracle.assistants.server:11.1.0.6.0:common:family=CFM:oh=/oracle/app/oracle/product/11.1.0/db_1:label=0} failed with an unhandled exception:
oracle.sysman.emCfg.common.CfwExceptionUninitializedParameter: {Parameter:S_SYSPASS in {Aggregate:oracle.assistants.server:11.1.0.6.0:common}}: parameter value has never been set and no default is present.
        at oracle.sysman.emCfg.core.CfmParameterState.expressData(CfmParameterState.java:720)
        at oracle.sysman.emCfg.core.CfmParameterState.expressDataAsArgv(CfmParameterState.java:541)
        at oracle.sysman.emCfg.core.CfmParameterPair.appendDataAsArgv(CfmParameterPair.java:372)
        at oracle.sysman.emCfg.core.CfmArguments.expandOneArgv(CfmArguments.java:92)
        at oracle.sysman.emCfg.core.CfmArguments.expand(CfmArguments.java:61)
        at oracle.sysman.emCfg.core.CfmArguments.expandAsArgv(CfmArguments.java:107)
        at oracle.sysman.emCfg.core.PerformMicroStep.runJavaClass(PerformMicroStep.java:540)
        at oracle.sysman.emCfg.core.PerformMicroStep.executeMicroStep(PerformMicroStep.java:120)
        at oracle.sysman.emCfg.core.ActionPerformer.performMicroStep(ActionPerformer.java:917)
        at oracle.sysman.emCfg.core.ActionPerformer$Performer.run(ActionPerformer.java:1038)

My suspicion is that the recorded response file is missing parameters that were supplied during the manual installation from which it was derived. Notably S_SYSPASS.

However, even manually setting all password fields in the response file doesn't fix this issue.

The question that I need answered is where can I look to perform further diagnosis of this installation failure.