CMDSCA Messages 100-199
|
|
105
ERROR: Command commandname is not named mkfldfromschema, mkfld32fromschema, mkviewfromschema, or mkview32fromschema
Description
The mkfldfromschema, mkfld32fromschema, mkviewfromschema, and mkview32fromschema commands share the same executable, and use the command name to determine which functionality should be provided. This executable has been copied or linked to another name and invoked using that name.
Action
Use one of the four allowable command names to invoke the command.
See Also
mkfldfromschema(1), mkfld32fromschema(1), mkviewfromschema(1), mkview32fromschema(1)
107
ERROR: Expected numeric argument to -b option
Description
The -b option to the mkfldfromschema or mkfld32fromschema command causes a * base basenumber line to be added to the generated field table. This option requires a numeric option argument basenumber, but no such option argument was provided.
Action
Supply a numeric option argument for the -b option and rerun the command.
See Also
mkfldfromschema(1), mkfld32fromschema(1)
108
ERROR: -b basenumber value must be nonnegative
Description
The -b option to the mkfldfromschema or mkfld32fromschema command causes a * base basenumber line to be added to the generated field table. basenumber must be non-negative, but the value specified by the user was negative.
Action
Supply a non-negative value for the basename and rerun the command.
See Also
mkfldfromschema(1), mkfld32fromschema(1)
109
ERROR: basenumber value of basenumber leaves no space for fields below limit of maxbase
Description
The -b option to the mkfldfromschema or mkfld32fromschema command causes a * base basenumber line to be added to the generated field table. The maximum allowable field number is maxbase, but basenumber was bigger than that.
Action
Ensure that basenumber is within the allowable range.
See Also
mkfldfromschema(1), mkfld32fromschema(1)
110
ERROR: Cannot specify the -i and -u options together
Description
The -i option to the mkfldfromschema, mkfld32fromschema, mkviewfromschema, and mkview32fromschema commands specifies an input file containing an XML schema, and the -u option specifies a URL where the input schema is located. These options are mutually exclusive.
Action
Specify at most one of the -i and -u options.
See Also
mkfldfromschema(1), mkfld32fromschema(1), mkviewfromschema(1), mkview32fromschema(1)
111
ERROR: Cannot open input file filename
Description
The input file specified by the -i option to the
mkfldfromschema, mkfld32fromschema, mkviewfromschema, or mkview32fromschema command
could not be opened for reading.
Action
Ensure that filename exists and that the file permissions permit this user to read the file.
See Also
mkfldfromschema(1), mkfld32fromschema(1), mkviewfromschema(1), mkview32fromschema(1)
112
ERROR: Cannot open output file filename
Description
The output file specified by the -o option to the mkfldfromschema, mkfld32fromschema, mkviewfromschema, or mkview32fromschema command could not be opened for writing.
Action
Ensure that file and directory permissions permit this user to write to filename.
See Also
mkfldfromschema(1), mkfld32fromschema(1), mkviewfromschema(1), mkview32fromschema(1)
113
WARN: Type fieldtype specified for field fieldname is not valid; ignoring this field
Description
The type fieldtype specified for field fieldname in the XSD file used as input to
mkfldfromschema or mkfld32fromschema
does not correspond to a valid Tuxedo type.
Action
Specify an XML schema conforming to the guidelines described in the SDO Mapping section of the Oracle Salt Programming Guide, or determine that this field will not be mapped to Tuxedo and that the error can be ignored.
See Also
Oracle Service Architecture Leveraging Tuxedo Programming Guide, mkfldfromschema(1), mkfld32fromschema(1)
114
WARN: Field fieldname redefined as type newtype after previous defintion as type originaltype; ignoring the redefinition
Description
Field fieldname was specified using different types in two or more locations in the schema file used as input to the
mkfldfromschema(1) or mkfld32fromschema(1) command. Only the first definition is used.
Action
Edit the schema file so that the same field is not specified multiple times using different types and rerun the
mkfldfromschema(1) or mkfld32fromschema(1) command.
See Also
mkfldfromschema(1), mkfld32fromschema(1)
115
WARN: Type typename specified for view member membername is not valid; ignoring this member
Description
The type typename specified for view member membername in the XSD file used as input to
mkviewfromschema, mkview32fromschema
does not correspond to a valid Tuxedo type.
Action
Specify an XML schema conforming to the guidelines described in the SDO Mapping section of the Oracle Salt Programming Guide, or determine that this field will not be mapped to Tuxedo and that the error can be ignored.
See Also
Oracle Service Architecture Leveraging Tuxedo Programming Guide, mkviewfromschema(1), mkview32fromschema(1)
116
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating memory for a field lookup table.
Action
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
See Also
mkfldfromschema(1), mkfld32fromschema(1), mkviewfromschema(1), mkview32fromschema(1)
117
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating memory for a field lookup table.
Action
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
See Also
mkfldfromschema(1), mkfld32fromschema(1), mkviewfromschema(1), mkview32fromschema(1)
118
WARN: Replacing maxOccurs value of unbounded for field fieldname with newvalue. Edit the output manually if this is not appropriate.
Description
Field fieldname
was specified a maxOccurs value ofunbounded in the input to
mkviewfromschema(1) or mkview32fromschema(1).
Since Tuxedo views cannot have an unlimited number of occurrences, this value has been replaced with a value newvalue, which is equal to the minimum number of occurrences specified or is 1.
Action
If the default action taken by Oracle SALT is not appropriate, edit the input or output of mkviewfromschema or mkview32fromschema to specify the desired value.
See Also
mkviewfromschema(1), mkview32fromschema(1)
119
WARN: Replacing non-numeric maxOccurs value of nonnumericvalue for field fieldname with newvalue. Edit the output manually if this is not appropriate.
Description
Field fieldname
was specified a maxOccurs value of nonnumericvalue in the input tomkviewfromschema(1) or mkview32fromschema(1).
This value has been replaced with a value newvalue, which is equal to the minimum number of occurrences specified or is 1.
Action
If the default action taken by Oracle SALT is not appropriate, edit the input or output of mkviewfromschema or mkview32fromschema to specify the desired value.
See Also
mkviewfromschema(1), mkview32fromschema(1)
120
WARN: Replacing non-positive maxOccurs value of nonpositivevalue for field fieldname with newvalue. Edit the output manually if this is not appropriate.
Description
Field fieldname
was specified a maxOccurs value of nonpositivevalue in the input tomkviewfromschema(1) or mkview32fromschema(1).
This value has been replaced with a value newvalue, which is equal to the minimum number of occurrences specified or is 1.
Action
If the default action taken by Oracle SALT is not appropriate, edit the input or output of mkviewfromschema or mkview32fromschema to specify the desired value.
See Also
mkviewfromschema(1), mkview32fromschema(1)
121
WARN: Unable to open directory: directoryname
Description
The buildscaclient(1) command was unable to open directory directoryname.
Action
Ensure that directory directoryname exists and that the user has permission search this directory.
See Also
buildscaclient(1)
122
WARN: Unable to stat entry: filename
Description
The stat(2) system call failed for filename while buildscaclient(1) was searching all files in the directory where filename is located.
Action
Verify that filename was not removed while buildscaclient(1) was executing. Try re-executing the buildscaclient(1) command. Contact the Unix or Linux administrator to ask if there are any filesystem problems on the machine.
See Also
buildscaclient(1)
123
ERROR: Command line option "optionname" missing required argument!
Description
The buildscaclient(1) option optionname requires an option argument but no such option argument was specified.
Action
Supply the required option argument and re-execute buildscaclient(1)>.
See Also
buildscaclient(1)
124
ERROR: Command line argument "optionname" missing required argument!
Description
The buildscaclient(1) option optionname requires an option argument but no such option argument was specified.
Action
Supply the required option argument and re-execute buildscaclient(1)>.
See Also
buildscaclient(1)
125
ERROR: Command line option "optionname" missing required argument!
Description
The buildscaclient(1) option optionname requires an option sub-argument but no such option argument was specified.
Action
Supply the required option argument and re-execute buildscaclient(1)>.
See Also
buildscaclient(1)
126
ERROR: Command line option "optionname" contains unsupport sub option
Description
An unsupported option sub-argument was specified for the buildscaclient(1) option optionname.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
127
ERROR: Command line option "optionname" contains unsupported property
Description
An unsupported option sub-argument was specified for the buildscaclient(1) option optionname.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
128
ERROR: Command line option "optionname" missing required argument.
Description
A required option sub-argument was not specified for the buildscaclient(1) option optionname.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
129
ERROR: Command line option "optionname" has syntax error.
Description
buildscaclient(1) detected a syntax error in the specification of the optionname option.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
130
ERROR: Command line option "optionname" has duplicate sub option.
Description
A duplicated option sub-argument was detected in the processing of the buildscaclient(1) optionname option.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
131
ERROR: Command line option "optionname" has duplicated property.
Description
A duplicated option sub-argument was detected in the processing of the buildscaclient(1) optionname option.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
132
ERROR: Command line option "optionname" missing required sub option.
Description
A required option sub-argument was not specified for the buildscaclient(1) option optionname.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
133
ERROR: Command line option "optionname" missing required property.
Description
A required option sub-argument was not specified for the buildscaclient(1) option optionname.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
134
ERROR: Command line option "optionname" already exists.
Description
The buildscaclient(1) option optionname was specified multiple times and is allowed to be specified only once.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
135
ERROR: Command line option "optionname" only allows single sub option.
Description
Multiple option sub-arguments were specified for the buildscaclient(1) option optionname but only one option sub-argument is allowed.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
136
ERROR: Command line option "optionname" is not supported!
Description
The optionname option was specified to buildscaclient(1) but this is not a valid option name.
Action
Consult the buildscaclient(1) manual page for the proper syntax and re-execute the command.
See Also
buildscaclient(1)
137
WARN: Method name 'methodname' and reference name 'referencename' make up a too long identifier (totallength > maxlen). Make sure a \
Description
During the processing of the buildscaclient(1) command, the length of methodname plus the length of a separator character plus the length of referencename totaled totallength, which is larger than the maximum allowable length for a Tuxedo service name, which is maxlen.
Action
There are two different ways to fix this problem. One way is to use a \
See Also
Oracle Service Architecture Leveraging Tuxedo Administration Guide,
buildscaclient(1)
138
WARN: <elementType> target 'targetname' not found in interface for reference 'referencename'. Check SCDL code.
Description
The target of targetname was not found among the interfaces for reference referencename. elementType is "inputBufferType", "outputBufferType", "errorBufferType", or "serviceType" and indicates which type of target was not found.
Action
Examine the SCDL files under the SCA root directory and make sure that all targets are defined in the appropriate interfaces.
See Also
buildscaclient(1)
139
ERROR: Cannot execute compilercommand, rc = returncode
Description
An error occurred while buildscaclient was compiling source files.
Action
Examine the syntax of the compilercommand and any error messages reported by the compiler as well as the operating system returncode.
See Also
buildscaclient(1)
140
ERROR: Component is not specified.
Description
buildscaclient(1) was invoked without the required parameter -c default-component
Action
Fix the command syntax and re-invoke buildscaclient(1).
See Also
buildscaclient(1)
141
ERROR: TUXDIR environment variable not set.
Description
The required environment variable TUXDIR was not set when invoking buildscaclient(1).
Action
Set TUXDIR to the directory where Tuxedo is installed and re-invoke buildscaclient(1).
See Also
buildscaclient(1)
142
ERROR: Failed to allocate memory.
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while executing the buildscaclient(1) command.
Action
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
See Also
buildscaclient(1)
143
ERROR: TUSCANY_SCACPP_ROOT Environment variable not set
Description
The buildscaclient(1) command was invoked without the -s scaroot option. In addition, neither the APPDIR environment variable nor the TUSCANY_SCACPP_ROOT environment variable was set.
Action
Set APPDIR or invoke buildscaclient(1) with the -s scaroot option.
(The TUSCANY_SCACPP_ROOT environment variable is deprecated and its use is discouraged.)
See Also
buildscaclient(1)
144
ERROR: SystemConfigurationException: exception_information
Description
An exception occurred during the execution of
buildscaclient(1).
Action
Examine the exception_information to determine the proper action to take.
See Also
buildscaclient(1)
145
INFO: No reference found in defaultcomponent.
Description
No SCA component files were found in the directory specifed by the
buildscaclient(1) -c defaultcomponent option.
Action
No action is required. However, if it was intended for there to be component files in the
defaultcomponent directory, then the
buildscaclient(1) should be re-executed.
See Also
buildscaclient(1)
146
ERROR: Unable to find directory for component defaultcomponent.
Description
The buildscaclient(1) command was unable to change its current direcory to the directory specified by the -c defaultcomponent option.
Action
Verify that defaultcomponent exists, is a directory, and that the current user has permission to change directory to this directory.
See Also
buildscaclient(1)
147
ERROR: Open file filename failed(errno).
Description
The buildscaclient(1) command was unable to open file filename due to operating system error errno.
Action
Verify that filename exists and that the current user has permission to open this file.
See Also
buildscaclient(1)
148
ERROR: Read file filename error(errno).
Description
The buildscaclient(1) command was unable to read file filename due to operating system error errno.
Action
Verify that filename exists and that the current user has permission to read this file.
See Also
buildscaclient(1)
149
INFO: No ATMI binding reference, skip library generation.
Description
No ATMI binding reference file was found, so
buildscaclient(1) will not build any libraries.
Action
No action required.
See Also
buildscaclient(1)
150
INFO: build complete.
Description
buildscaclient(1) has finished building the requested SCA client.
Action
No action required.
See Also
buildscaclient(1)
151
ERROR: Unable to load file compositefile.
Description
buildscaclient(1) was unable to load SCA composite file
compositefile because no root data object was found in this file.
Action
Verify that compositefile has the proper syntax for an SCA composite file.
See Also
buildscaclient(1)
152
ERROR: Unable to load composite: exceptiontext
Description
An exception occureed while buildscaclient(1) was attempting to load an SCA composite file.
Action
Consult the exceptiontext to determine the correct action to take.
See Also
buildscaclient(1)
153
ERROR: Unsupported binding type: typename
Description
This message no longer occurs in the Oracle SALT 10gR3 codebase.
Action
Contact Oracle Technical Support.
See Also
buildscaclient(1)
154
ERROR: Memory allocation failure.
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed during the processing of the buildscaclient(1) command.
Action
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
See Also
buildscaclient(1)
156
WARN: Unable to open directory: directoryname
Description
The buildscacomponent(1) or buildscaserver(1)
command was unable to read the contents of directory directoryname.
Action
Verify that directoryname exists, is a directory, and that the current user has permission to read this directory.
See Also
buildscacomponent(1), buildscaserver(1)
157
WARN: Unable to stat entry: filename
Description
The buildscacomponent(1) or buildscaserver(1)
command encountered an error while executing the stat() system call on file filename.
Action
Verify that filename exists and that the current user has search permission on directories above the directory where filename is located.
See Also
buildscacomponent(1), buildscaserver(1)
159
ERROR: buildscaserver cannot open the temporary output file, filename.
Description
An error occured when trying to open temporary file filename for writing.
Action
Verify that the current user has permission to create files in the directory where filename is located, that a file with the same name had not been previously created, and that the filesystem where filename is located is not out of space.
See Also
buildscaserver(1)
160
ERROR: Open file filename failed(errno_string).
Description
The buildscacomponent(1) or buildscaserver(1)
was unable to open file filename for reading due to operating system error errno_string.
Action
Consult errno_string to determine the specific nature of the error, which might be related to a nonexistent file, file permissions, or some other cause.
See Also
buildscacomponent(1), buildscaserver(1)
161
ERROR: Read file filename error(errno_string).
Description
The buildscacomponent(1) or buildscaserver(1)
encountered an error while reading
file filename due to operating system error errno_string.
Action
Consult errno_string to determine the specific nature of the error.
See Also
buildscacomponent(1), buildscaserver(1)
162
WARN: no WSDL for composite compositename
Description
No Web Services Definition Language files were associated with composite compositename.
Action
Define WSDL associated with composite compositename if this is what is intended.
See Also
buildscacomponent(1), buildscaserver(1)
163
WARN: Unable to load or parse WSDL: WSDLfile
Description
An error occurred while opening or parsing WSDL file WSDLfile.
Action
Verify that WSDLfile exists and has valid syntax.
See Also
buildscacomponent(1), buildscaserver(1)
164
WARN: Method name 'methodname' and service name 'referencename' make up too long an identifier (totallength > maxlen). Make sure a \
Description
The length of methodname plus the length of a separator character plus the length of referencename totaled totallength, which is larger than the maximum allowable length for a Tuxedo service name, which is maxlen.
Action
There are two different ways to fix this problem. One way is to use a \
See Also
buildscacomponent(1), buildscaserver(1)
165
WARN: \
Description
THe target for map method mapmethod is not one of the defined interfaces for service servicename.
Action
Fix the SCDL code so that map methods specify only valid interfaces.
See Also
buildscacomponent(1), buildscaserver(1)
166
WARN: \
Description
Target targetname is not one of the defined interfaces for service servicename.
Action
Fix the SCDL code so that the \
See Also
buildscacomponent(1), buildscaserver(1)
167
WARN: \
Description
Target targetname is not one of the defined interfaces for service servicename.
Action
Fix the SCDL code so that the \
See Also
buildscacomponent(1), buildscaserver(1)
168
WARN: No signature loaded for composite compositename
Description
No service signatures were loaded during the processing of SCA component compositename
Action
If this component is intended for processing SCA services, the administrator should add the missing signature(s) to the composite.
See Also
buildscacomponent(1), buildscaserver(1)
169
WARN: No composite processed
Description
No SCA composite files were processed during this invocation of buildscaserver(1).
Action
Investigate whether the proper files and options were given to the command.
See Also
buildscacomponent(1), buildscaserver(1)
170
WARN: No shared library created for composite compositename
Description
No shared library was created by
buildscacomponent(1) during the processing of composite compositename.
Action
Add a service binding to the composite so that a corresponding library is generated.
See Also
buildscacomponent(1)
171
WARN: No composite processed
Description
No composite file was processed during execution of the
buildscacomponent(1) command.
Action
Investigate whether the proper files and options were given to the command.
The -c option may be used to specify one or more components to be processed.
See Also
buildscacomponent(1)
172
ERROR: Command line option "optionname" missing required argument!
Description
The buildscacomponent(1) or buildscaserver option optionname requires an option sub-argument but no such option argument was specified.
Action
Supply the required option argument and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
173
ERROR: Command line argument "optionname" missing required argument!
Description
The buildscacomponent(1) or buildscaserver option optionname requires an option sub-argument but no such option argument was specified.
Action
Supply the required option argument and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
174
ERROR: Command line option "optionname" missing required argument!
Description
The buildscacomponent(1) or buildscaserver option optionname requires an option sub-argument but no such option argument was specified.
Action
Supply the required option argument and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
175
ERROR: Command line option "optionname" contains unsupported sub option
Description
The buildscacomponent(1) or buildscaserver option optionname contained an unsupported sub option.
Action
Fix the command line options and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
176
ERROR: Command line option "optionname" contains unsupported property
Description
The buildscacomponent(1) or buildscaserver
option optionname contained an unsupported property.
Action
Fix the command line options and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
177
ERROR: Command line option "optionname" missing required argument.
Description
The buildscacomponent(1) or buildscaserver
option optionname requires an option sub-argument but no such option argument was specified.
Action
Supply the required option argument and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
178
ERROR: Command line option "optionname" has syntax error.
Description
buildscacomponent(1) or buildscaserver
detected a syntax error in the specification of the optionname option.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
179
ERROR: Command line option "optionname" has duplicate sub option.
Description
A duplicated option sub-argument was detected in the processing of the buildscacomponent(1) or buildscaserver(1) optionname option.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
180
ERROR: Command line option "optionname" has duplicated property.
Description
A duplicated option sub-argument was detected in the processing of the buildscacomponent(1) or buildscaserver(1) optionname option.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
181
ERROR: Command line option "optionname" missing required sub option.
Description
A required option sub-argument was not specified for the buildscacomponent(1) or buildscaserver(1) option optionname.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
182
ERROR: Command line option "optionname" missing required property.
Description
A required option sub-argument was not specified for the buildscacomponent(1) or buildscaserver(1) option optionname.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
183
ERROR: Command line option "optionname" already exists.
Description
The buildscacomponent(1) or buildscaserver(1) option optionname was specified multiple times and is allowed to be specified only once.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
184
ERROR: Command line option "optionname" only allows single sub option.
Description
Multiple option sub-arguments were specified for the
buildscacomponent(1) or buildscaserver(1) option optionname but only one option sub-argument is allowed.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
185
ERROR: Command line option "optionname" is not supported!
Description
The optionname option was specified to buildscacomponent(1) or buildscaserver(1) but this is not a valid option name.
Action
Consult the buildscacomponent(1) or buildscaserver(1) manual page for the proper syntax and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
186
INFO: Executing command: commandline
Description
buildscacomponent(1) or buildscaserver(1)
is about to execute the command commandline.
Action
No action required.
See Also
buildscacomponent(1), buildscaserver(1)
187
ERROR: cannot execute commandline
Description
buildscacomponent(1) or buildscaserver(1)
encountered an error while executing
the command commandline.
Action
Examine the commandline for possible syntax errors or bad filenames.
See Also
buildscacomponent(1), buildscaserver(1)
188
ERROR: Memory allocation failure. (:)
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while cleaning the Bulletin Board.
Action
Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
See Also
buildscacomponent(1), buildscaserver(1)
189
ERROR: Unrecognized file type in the file list: filename
Description
The file filename specified as an input file to
buildscacomponent(1) or buildscaserver(1)
did not have a suffix of ".cpp", ".c", or a suffix associated with a library file on this operating system.
Action
Specify only C++ source files, C source files, or library files as input files to
buildscacomponent(1) or buildscaserver(1).
See Also
buildscacomponent(1), buildscaserver(1)
190
ERROR: Command line option "-t" is not supported by programname.
Description
"-t" is not a valid option for buildscacomponent, although it is a valid option for buildscaserver.
Action
Fix the command syntax and re-execute buildscacomponent.
See Also
buildscacomponent(1), buildscaserver(1)
191
ERROR: Command line option "-o outname" is not supported by programname.
Description
"-o outname" is not a valid option for buildscacomponent, although it is a valid option for buildscaserver.
Action
Fix the command syntax and re-execute buildscacomponent.
See Also
buildscacomponent(1), buildscaserver(1)
192
ERROR: Command line option "-o outname" is required by programname.
Description
"-o outname" is a required option for buildscaserver.
Action
Fix the command syntax and re-execute buildscaserver.
See Also
buildscaserver(1)
193
ERROR: Command line option "-r RM" is not supported by programname.
Description
"-r RM" is not a valid option for buildscacomponent, although it is a valid option for buildscaserver.
Action
Fix the command syntax and re-execute buildscacomponent.
See Also
buildscacomponent(1), buildscaserver(1)
194
INFO: APPDIR not set, use parent directory dirname as SCA ROOT.
Description
The APPDIR environment variable was not set when executing
buildscacomponent(1),
so the parent directory dirname is used as the SCA root directory.
Action
No action required.
See Also
buildscacomponent(1)
195
INFO: APPDIR not set, use current working directory dirname as SCA ROOT.
Description
The APPDIR environment variable was not set when executing
buildscaserver(1),
so the current directory dirname is used as the SCA root directory.
Action
No action required.
See Also
buildscaserver(1)
196
ERROR: Command line option "-f filelist" is not supported by programname.
Description
"-f filelist" is not a valid option for buildscaserver, although it is a valid option for buildscacomponent.
Action
Fix the command syntax and re-execute buildscaserver.
See Also
buildscacomponent(1), buildscaserver(1)
197
ERROR: Command line option "-l filelist" is not supported by .
Description
"-l filelist" is not a valid option for buildscaserver, although it is a valid option for buildscacomponent.
Action
Fix the command syntax and re-execute buildscaserver.
See Also
buildscacomponent(1), buildscaserver(1)
198
ERROR: "-f" and "-l" can not be specified with "-o" option.
Description
This message should no longer occur in the current Oracle SALT release.
Action
Check the proper syntax of
buildscacomponent(1) or buildscaserver(1)
and re-execute the command.
See Also
buildscacomponent(1), buildscaserver(1)
199
ERROR: required composite name option '-c' not specified.
Description
The required -c compositelist argument to the buildscaservercommand was not specified.
Action
Fix the command syntax and re-execute buildscaserver.
See Also
buildscaserver(1)
 |
 |
 |