Error while running aiaconfig.sh - The command line argument(s) "weblogicConfig"

Question

Hi.
We are Configuring PIP on AIA 11.1.1.7 after installing AIA PIP release. we we run ./aiaconfig.sh we are getting below error message,
$./aiaconfig.sh
Starting Oracle Universal Installer...
Checking swap space: must be greater than 500 MB.   Actual 169130 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 16777216    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-11-20_04-11-10AM. Please wait ...adevaia                                                        @soa-odi-dev1:/u02/app/Oracle/Middleware/AIAHOME/bin$ [WARN ][jrockit] MaxPermSize=256m ignored: Not a valid opt                                                        ion for JRockit
Log: /u01/app/oraInventory/logs/install2013-11-20_04-11-10AM.log
The command line argument(s) "weblogicConfig" or the install mode specified is not valid.
Copyright (c) 1999, 2011, Oracle and/or its affiliates. All rights reserved.
Usage:
config.sh [-mode] [-options] [(<CommandLineVariable=Value>)*]
Where mode include:
[Mode is a mandatory parameter. Only one mode can be specified.]
     -silent For silent mode operations, the inputs can be a response file or a list of
              command line variable value pairs.
Where options include:
     -help, --help, --usage
              Displays above usage.
     -invPtrLoc <inventory pointer file>
              Launches the installer with a custom inventory location. The invPtrLoc
              should point to a file which contains the following information.
              inventory_loc=<inventory_location>
              inst_group=<group_name>
     -response, -responseFile <response file>
              Specifies the response file and path to use.
     -jreLoc <location>
              Path where Java Runtime Environment is installed. OUI cannot be run without
              it.
     -logLevel <level>
              To filter log messages that have a lesser priority level than <level>.
              Valid options are: severe, warning, info, config, fine, finer, finest,
              basic, general, detailed, trace. The use of basic, general, detailed, trace
              is deprecated.
     -debug  For getting the debug information from OUI.
     -force  Allowing silent mode installation into a non-empty directory.
     -printdiskusage
              Log debug information for disk usage.
     -printmemory
              Path where Java Runtime Environment is installed. OUI cannot be run without
              it.
     -printtime
              Log debug information for time usage.
     -waitforcompletion
              For windows. setup.exe will wait for completion instead of spawning the
              java engine and exiting.
     -noconsole
              For suppressing display of messages to console. Console is not allocated.
     -ignoreSysPrereqs
              For ignoring the results of the system pre-requisite checks.
     -executeSysPrereqs
              Execute system pre-requisite checks and exit.
     -paramFile <location of file>
              Specify location of oraparam.ini file to be used by OUI.
     -novalidation
              Disables the validations, can be invoked along with GUI or silent mode.
     -nodefaultinput
              Disables the default computation of values (pre-populating of values when
              screen is loaded) in GUI install.
     -nocheckForUpdates
              To disable all updates checking
     -updatesDir
              To specify the directory where latest updates are downloaded. This could be
              used in disconnected mode.
Command Line Variables Usage:
          Command line variables are specified using <name=value>; for example:
              [ session: | session:compName: | session:compName:version: ]variableName=" valueOfVariable"]
          Installer variables are specified using:
              varName=value
              Ex: ORACLE_HOME=<value>
          OUI Session variables are specified using:
              session:varName=value
              Ex: session:VARIABLE_NAME=<value>
          OUI Component variables are specified using:
              session:compInternalName:[Version:]varName
              Ex 1: session:oracle.comp1:1.0.1:varName=<value>
              Ex 2: session:oracle.comp1:varName=<value>
              The lookup order is compInternalName:Version:varName, then compInternalName:varName
do anyone had any idea on this.
Thanks a lot,
RR.

Answer 1

try checking relevant environment variables like the CLASSPATH.... a major source of failures in Windows is when in the classpath there is a path containing SPACES.... also enabling some "debug" or "verbose" flag (not sure how to do it) would provide more insight...