System Messages: CMDSCA Catalog 100-199
|
105 |
ERROR: Command commandname is not named mkfldfromschema, mkfld32fromschema, mkviewfromschema, or mkview32fromschema | |
|
Description |
The |
Action |
Use one of the four allowable command names to invoke the command. | |
See Also |
| |
107 |
ERROR: Expected numeric argument to -b option | |
|
Description |
The |
Action |
Supply a numeric option argument for the | |
See Also |
| |
108 |
ERROR: -b basenumber value must be nonnegative | |
|
Description |
The |
Action |
Supply a non-negative value for the basename and rerun the command. | |
See Also |
| |
109 |
ERROR: basenumber value of basenumber leaves no space for fields below limit of maxbase | |
|
Description |
The |
Action |
Ensure that basenumber is within the allowable range. | |
See Also |
| |
110 |
ERROR: Cannot specify the -i and -u options together | |
|
Description |
The |
Action |
Specify at most one of the | |
See Also |
| |
111 |
ERROR: Cannot open input file filename | |
|
Description |
The input file specified by the |
Action |
Ensure that filename exists and that the file permissions permit this user to read the file. | |
See Also |
| |
112 |
ERROR: Cannot open output file filename | |
|
Description |
The output file specified by the |
Action |
Ensure that file and directory permissions permit this user to write to filename. | |
See Also |
| |
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
|
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, | |
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
|
Action |
Edit the schema file so that the same field is not specified multiple times using different types and rerun the
| |
See Also |
| |
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
|
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, | |
116 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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 |
| |
117 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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 |
| |
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 | |
See Also |
| |
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 | |
See Also |
| |
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 | |
See Also |
| |
121 |
WARN: Unable to open directory: directoryname | |
|
Description |
The |
Action |
Ensure that directory directoryname exists and that the user has permission search this directory. | |
See Also |
| |
122 |
WARN: Unable to stat entry: filename | |
|
Description |
The |
Action |
Verify that filename was not removed while | |
See Also |
| |
123 |
ERROR: Command line option "optionname" missing required argument! | |
|
Description |
The |
Action |
Supply the required option argument and re-execute | |
See Also |
| |
124 |
ERROR: Command line argument "optionname" missing required argument! | |
|
Description |
The |
Action |
Supply the required option argument and re-execute | |
See Also |
| |
125 |
ERROR: Command line option "optionname" missing required argument! | |
|
Description |
The |
Action |
Supply the required option argument and re-execute | |
See Also |
| |
126 |
ERROR: Command line option "optionname" contains unsupport sub option | |
|
Description |
An unsupported option sub-argument was specified for the |
Action |
Consult the | |
See Also |
| |
127 |
ERROR: Command line option "optionname" contains unsupported property | |
|
Description |
An unsupported option sub-argument was specified for the |
Action |
Consult the | |
See Also |
| |
128 |
ERROR: Command line option "optionname" missing required argument. | |
|
Description |
A required option sub-argument was not specified for the |
Action |
Consult the | |
See Also |
| |
129 |
ERROR: Command line option "optionname" has syntax error. | |
|
Description |
|
Action |
Consult the | |
See Also |
| |
130 |
ERROR: Command line option "optionname" has duplicate sub option. | |
|
Description |
A duplicated option sub-argument was detected in the processing of the |
Action |
Consult the | |
See Also |
| |
131 |
ERROR: Command line option "optionname" has duplicated property. | |
|
Description |
A duplicated option sub-argument was detected in the processing of the |
Action |
Consult the | |
See Also |
| |
132 |
ERROR: Command line option "optionname" missing required sub option. | |
|
Description |
A required option sub-argument was not specified for the |
Action |
Consult the | |
See Also |
| |
133 |
ERROR: Command line option "optionname" missing required property. | |
|
Description |
A required option sub-argument was not specified for the |
Action |
Consult the | |
See Also |
| |
134 |
ERROR: Command line option "optionname" already exists. | |
|
Description |
The |
Action |
Consult the | |
See Also |
| |
135 |
ERROR: Command line option "optionname" only allows single sub option. | |
|
Description |
Multiple option sub-arguments were specified for the |
Action |
Consult the | |
See Also |
| |
136 |
ERROR: Command line option "optionname" is not supported! | |
|
Description |
The optionname option was specified to |
Action |
Consult the | |
See Also |
| |
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 |
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,
| |
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 |
| |
139 |
ERROR: Cannot execute compilercommand, rc = returncode | |
|
Description |
An error occurred while |
Action |
Examine the syntax of the compilercommand and any error messages reported by the compiler as well as the operating system returncode. | |
See Also |
| |
140 |
ERROR: Component is not specified. | |
|
Description |
|
Action |
Fix the command syntax and re-invoke | |
See Also |
| |
141 |
ERROR: TUXDIR environment variable not set. | |
|
Description |
The required environment variable TUXDIR was not set when invoking |
Action |
Set TUXDIR to the directory where Tuxedo is installed and re-invoke | |
See Also |
| |
142 |
ERROR: Failed to allocate memory. | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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 |
| |
143 |
ERROR: TUSCANY_SCACPP_ROOT Environment variable not set | |
|
Description |
The |
Action |
Set APPDIR or invoke | |
See Also |
| |
144 |
ERROR: SystemConfigurationException: exception_information | |
|
Description |
An exception occurred during the execution of
|
Action |
Examine the exception_information to determine the proper action to take. | |
See Also |
| |
145 |
INFO: No reference found in defaultcomponent. | |
|
Description |
No SCA component files were found in the directory specifed by the
|
Action |
No action is required. However, if it was intended for there to be component files in the
defaultcomponent directory, then the
| |
See Also |
| |
146 |
ERROR: Unable to find directory for component defaultcomponent. | |
|
Description |
The |
Action |
Verify that defaultcomponent exists, is a directory, and that the current user has permission to change directory to this directory. | |
See Also |
| |
147 |
ERROR: Open file filename failed(errno). | |
|
Description |
The |
Action |
Verify that filename exists and that the current user has permission to open this file. | |
See Also |
| |
148 |
ERROR: Read file filename error(errno). | |
|
Description |
The |
Action |
Verify that filename exists and that the current user has permission to read this file. | |
See Also |
| |
149 |
INFO: No ATMI binding reference, skip library generation. | |
|
Description |
No ATMI binding reference file was found, so
|
Action |
No action required. | |
See Also |
| |
150 |
INFO: build complete. | |
|
Description |
|
Action |
No action required. | |
See Also |
| |
151 |
ERROR: Unable to load file compositefile. | |
|
Description |
|
Action |
Verify that compositefile has the proper syntax for an SCA composite file. | |
See Also |
| |
152 |
ERROR: Unable to load composite: exceptiontext | |
|
Description |
An exception occureed while |
Action |
Consult the exceptiontext to determine the correct action to take. | |
See Also |
| |
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 |
| |
154 |
ERROR: Memory allocation failure. | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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 |
| |
156 |
WARN: Unable to open directory: directoryname | |
|
Description |
The |
Action |
Verify that directoryname exists, is a directory, and that the current user has permission to read this directory. | |
See Also |
| |
157 |
WARN: Unable to stat entry: filename | |
|
Description |
The |
Action |
Verify that filename exists and that the current user has search permission on directories above the directory where filename is located. | |
See Also |
| |
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 |
| |
160 |
ERROR: Open file filename failed(errno_string). | |
|
Description |
The |
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 |
| |
161 |
ERROR: Read file filename error(errno_string). | |
|
Description |
The |
Action |
Consult errno_string to determine the specific nature of the error. | |
See Also |
| |
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 |
| |
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 |
| |
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 |
| |
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 |
| |
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 |
| |
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 |
| |
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 |
| |
169 |
WARN: No composite processed | |
|
Description |
No SCA composite files were processed during this invocation of |
Action |
Investigate whether the proper files and options were given to the command. | |
See Also |
| |
170 |
WARN: No shared library created for composite compositename | |
|
Description |
No shared library was created by
|
Action |
Add a service binding to the composite so that a corresponding library is generated. | |
See Also |
| |
171 |
WARN: No composite processed | |
|
Description |
No composite file was processed during execution of the
|
Action |
Investigate whether the proper files and options were given to the command.
The | |
See Also |
| |
172 |
ERROR: Command line option "optionname" missing required argument! | |
|
Description |
The |
Action |
Supply the required option argument and re-execute the command. | |
See Also |
| |
173 |
ERROR: Command line argument "optionname" missing required argument! | |
|
Description |
The |
Action |
Supply the required option argument and re-execute the command. | |
See Also |
| |
174 |
ERROR: Command line option "optionname" missing required argument! | |
|
Description |
The |
Action |
Supply the required option argument and re-execute the command. | |
See Also |
| |
175 |
ERROR: Command line option "optionname" contains unsupported sub option | |
|
Description |
The |
Action |
Fix the command line options and re-execute the command. | |
See Also |
| |
176 |
ERROR: Command line option "optionname" contains unsupported property | |
|
Description |
The |
Action |
Fix the command line options and re-execute the command. | |
See Also |
| |
177 |
ERROR: Command line option "optionname" missing required argument. | |
|
Description |
The |
Action |
Supply the required option argument and re-execute the command. | |
See Also |
| |
178 |
ERROR: Command line option "optionname" has syntax error. | |
|
Description |
|
Action |
Consult the | |
See Also |
| |
179 |
ERROR: Command line option "optionname" has duplicate sub option. | |
|
Description |
A duplicated option sub-argument was detected in the processing of the |
Action |
Consult the | |
See Also |
| |
180 |
ERROR: Command line option "optionname" has duplicated property. | |
|
Description |
A duplicated option sub-argument was detected in the processing of the |
Action |
Consult the | |
See Also |
| |
181 |
ERROR: Command line option "optionname" missing required sub option. | |
|
Description |
A required option sub-argument was not specified for the |
Action |
Consult the | |
See Also |
| |
182 |
ERROR: Command line option "optionname" missing required property. | |
|
Description |
A required option sub-argument was not specified for the |
Action |
Consult the | |
See Also |
| |
183 |
ERROR: Command line option "optionname" already exists. | |
|
Description |
The |
Action |
Consult the | |
See Also |
| |
184 |
ERROR: Command line option "optionname" only allows single sub option. | |
|
Description |
Multiple option sub-arguments were specified for the
|
Action |
Consult the | |
See Also |
| |
185 |
ERROR: Command line option "optionname" is not supported! | |
|
Description |
The optionname option was specified to |
Action |
Consult the | |
See Also |
| |
186 |
INFO: Executing command: commandline | |
|
Description |
|
Action |
No action required. | |
See Also |
| |
187 |
ERROR: cannot execute commandline | |
|
Description |
|
Action |
Examine the commandline for possible syntax errors or bad filenames. | |
See Also |
| |
188 |
ERROR: Memory allocation failure. (:) | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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 |
| |
189 |
ERROR: Unrecognized file type in the file list: filename | |
|
Description |
The file filename specified as an input file to
|
Action |
Specify only C++ source files, C source files, or library files as input files to
| |
See Also |
| |
190 |
ERROR: Command line option "-t" is not supported by programname. | |
|
Description |
"-t" is not a valid option for |
Action |
Fix the command syntax and re-execute | |
See Also |
| |
191 |
ERROR: Command line option "-o outname" is not supported by programname. | |
|
Description |
"-o outname" is not a valid option for |
Action |
Fix the command syntax and re-execute | |
See Also |
| |
192 |
ERROR: Command line option "-o outname" is required by programname. | |
|
Description |
"-o outname" is a required option for |
Action |
Fix the command syntax and re-execute | |
See Also |
| |
193 |
ERROR: Command line option "-r RM" is not supported by programname. | |
|
Description |
"-r RM" is not a valid option for |
Action |
Fix the command syntax and re-execute | |
See Also |
| |
194 |
INFO: APPDIR not set, use parent directory dirname as SCA ROOT. | |
|
Description |
The APPDIR environment variable was not set when executing
|
Action |
No action required. | |
See Also |
| |
195 |
INFO: APPDIR not set, use current working directory dirname as SCA ROOT. | |
|
Description |
The APPDIR environment variable was not set when executing
|
Action |
No action required. | |
See Also |
| |
196 |
ERROR: Command line option "-f filelist" is not supported by programname. | |
|
Description |
"-f filelist" is not a valid option for |
Action |
Fix the command syntax and re-execute | |
See Also |
| |
197 |
ERROR: Command line option "-l filelist" is not supported by . | |
|
Description |
"-l filelist" is not a valid option for |
Action |
Fix the command syntax and re-execute | |
See Also |
| |
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
| |
See Also |
| |
199 |
ERROR: required composite name option '-c' not specified. | |
|
Description |
The required |
Action |
Fix the command syntax and re-execute | |
See Also |
|