How do I narrow my search results?
After you submit your search query:
- On the Refine Search results page, select one or more categories of products or services from the left sidebar.
- Then for a category with search results, click Select to choose your product and release filters, and then click OK.
For search queries that contain multiple words, surround the query with quotes, and then resubmit your query. Example: "database cloud service"
How do I find the documentation for my product or service?
From the home page, click the technology categories for your products or services. If you do not know which category to pick, try the following features:
- Click the Find a product tab and search for your product or service.
- Click Browse All Products & Services at the bottom of the home page to view an alphabetical listing of products and services.
- Apple Safari: Version 6
- Google Chrome: Version 29 and later
- Mozilla Firefox: Version 24 and later
- Microsoft Internet Explorer: Version 9 and later
MOD → Syntax mod::= Text description of mod Purpose MOD returns the remainder of m divided by n. Returns … m if n is 0. Examples The following example returns the remainder of 11 divided by 4: SELECT MOD … mathematical modulus function when m is negative. The classical modulus can be expressed using the MOD
Mod (OraNumber) Method → Feedback Mod (OraNumber) Method Applies To OraNumber Description Gets the modulus from the division of … value. Usage OraNumber. Mod operand Remarks The result of the operation is stored in OraNumber
WM_ERROR_187 the parameter session_duration must be true for the 1WRITER_SESSION mod → Cause: An attempt was made to invoke the FreezeWorkspace procedure with an invalid session_duration parameter. Action: The session_duration parameter of the FreezeWorkspace must be TRUE when attempting to freeze a workspace in 1WRITER_SESSION mode. Ensure that FreezeWorkspace is invoked with the correct parameters.
MOD-00081 failed assertion → Cause: Some part of the input to SQL*Module caused an error or warning condition. This message always follows a specific error or warning message. Action: No action required for this message. Correct the previous errors.
39 SQL*Module Messages (MOD) → MOD-00001 unable to open file string Cause: SQL*Module was unable to open a temporary file for
MOD-00004 unsupported datatype in line number of file string → Cause: A host variable defined in the procedure definition of the module file has an unsupported datatype or has a scale or precision outside the supported range. Action: Redefine the host variable using a supported datatype. Check that the scale and precision of a numeric variable are in the accepted range.
MOD-00010 unable to open listing file " string " → Cause: SQL*Module is not able to create the listing output file. This usually happens when write permissions do not exist on the current directory or on the directory specified for the LNAME option. It can also happen if the name or directory path is not legal or a directory on the path does not exist. Action: Check the permissions on the specified path and file, or on the current directory if the
MOD-00014 unable to obtain bind variables at line number in file string → Cause: The module compiler was unable to find information about an input host variable (bind variable) used in a SQL statement. Action: Check that the input host variable is declared in the procedure definition of the module file and used properly in the SQL statement.
MOD-00046 cursor " string " has not been declared → Cause: In the module file, an OPEN, FETCH, or CLOSE was attempted on a cursor that had not yet been declared. Action: Insert an appropriate cursor declaration in the module file. Remember that cursors must be declared in the file before they are acted upon.
MOD-00055 preprocessor directive is not understood → MOD-00056 array bound must be greater than 0 Cause: Incorrect array index was specified. Cause
MOD-00061 PL/SQL error in compiling package body → Cause: A semantic error occurred in the PL/SQL parse phase when running SQL*Module. Action: Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code file (it has a.pkb extension). See the PL/SQL User's Guide and Reference for more information.
MOD-00065 interface definition missing for procedure string → Cause: An attempt was made to generate stubs for a package that does not contain a WITH INTERFACE clause for one or more procedures. Action: Add the WITH INTERFACE clause to the package specification.
MOD-00070 procedure string interface is missing declaration for string → Cause: An indicator variable was specified in the WITH INTERFACE clause, but the associated main variable was not declared there. Action: Modify the WITH INTERFACE clause. Either remove the indicator variable or declare a host variable for it.
MOD-00074 ONAME option is specified but not meaningful → Cause: The ONAME option was used when it was not required. For example, the ONAME option is not required when RPC_GENERATE=NO, and STORE_PACKAGE=YES, or the OUTPUT values list does not contain the CODE value. Action: Do not use the ONAME option.
MOD-00083 [package body compiled] → Cause: This is an informational message. Action: No action is required.
MOD-00088 feature not implemented yet → Cause: SQL*Module encountered a SQL statement that it can compile, but that uses a feature not yet implemented. Action: Contact Oracle Languages Product Management.
MOD-00097 with-interface must be specified for this host language → Cause: A PL/SQL package or function specification did not have a WITH INTERFACE clause. Currently, MODADA requires the WITH INTERFACE clause to be present in order to create calls to a PL/SQL function or package. Action: Rewrite PL/SQL package or function specification to include a WITH INTERFACE clause. Alternatively, write a PL/SQL package or function specification which has a WITH INTERFACE clause
MOD-00005 invalid include file name at column number in line number of file string → MOD-00006 invalid host variable at column number in line number of file string Cause: A host
MOD-00019 indicator variable " string " has wrong type or length at line number in file string → Cause: An indicator variable was not declared in the procedure definition as a 2-byte integer. Indicator variables must be defined as 2-byte integers. Action: Redefine the indicator variable as a 2-byte integer.