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.
MOD-00060 PL/SQL error in compiling package specification → 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 specification file (it has a.pks extension). See the PL/SQL User's Guide and Reference for more information.
MOD-00048 cursor " string " was never opened. → Cause: No OPEN command exists in the module for the cursor named in this message. Action: Add an OPEN command or remove the cursor if it is not needed.
MOD-00059 INTO variable " string " is not listed as a formal parameter → Cause: The target of an INTO clause in a SELECT statement is not a parameter of the procedure. Action: Declare the parameter using the correct datatype in the procedure's parameter list.
MOD-00095 datatype " string " is not valid for this host language. → Cause: A datatype was used that is not supported for the host language. For example, NUMERIC is not a supported datatype for Ada and C. Action: Refer to your language-specific Precompiler Programmer's Guide for a list of the datatypes supported in each host language.
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-00085 [package specification compiled] → Cause: This is an informational message. Action: No action is required.
MOD-00069 Oracle error number while attempting to store package → Cause: SQL*Module's attempt to store the package in the database failed. Action: Look up the error number in this manual and correct the problem.
MOD-00007 unable to open a cursor at line number in file string → Cause: The syntax in the SQL statement is faulty. The module compiler was expecting a host variable, but found something else. Action: Check the syntax and the spelling, then correct the SQL statement.
MOD-00018 unable to disconnect from Oracle → Cause: An Oracle connection error occurred while the module was trying to log off, probably because Oracle has been shut down. Action: Check that Oracle is available, then retry.
MOD-00039 unable to open specifications file " string " → Cause: SQL*Module is not able to create the specifications (header) output file. This usually happens when write permissions on the current directory or on the directory specified for the SNAME option do not exist. It can also happen if the name or directory path is not legal, a directory on the path does not exist, or the disk or file system is full. Action: Check the permissions on the specified
MOD-00077 mandatory status parameter, such as SQLCODE or SQLSTATE,is missing → Cause: Include a status parameter -- SQLCODE, SQLSTATE, or both -- in every parameter definition. Action: Include SQLCODE or SQLSTATE.
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.
MOD-00023 invalid option " string " → Cause: The module compiler found an invalid module option name. Some possible causes follow: The option name is misspelled. The specified option does not exist. The equal sign (=) between the option name and value is missing or has space around it. Action: Check that the option exists and that its name is spelled correctly. To see an online display of the module options, enter the MODADA command (with
MOD-00045 a character string length of number is illegal → Cause: For a char[n] host variable, a length of less than 2 characters was specified. The length must be at least 2 characters. Action: Correct the declaration so that it specifies the length of at least 2 characters.
MOD-00003 invalid SQL Identifier at column number in line number of file string → Cause: The symbol in a SQL descriptor is invalid. Action: Check the statement syntax and spelling of the identifier and check that a reserved word was not accidentally used. If necessary, define the identifier in the declaration section of the module file.