Oracle Discoverer Administrator Administration Guide 10g (9.0.4) Part Number B10270-01 |
|
This chapter introduces the Oracle Discoverer command line interface and contains the following topics:
Discoverer has the following command line interfaces:
For more information, see "What is the Oracle Discoverer command line interface?".
For more information, see the Oracle Discoverer EUL Command Line for Java User's Guide .
The Oracle Discoverer command line interface is a set of text based commands that enable you to create and manipulate Discoverer EULs created on both Oracle databases and non-Oracle databases.
Note: You use Heterogeneous Services to connect to non-Oracle databases, although the EUL is stored in the Oracle database. For more information about using non-Oracle databases, see "Discoverer support for non-Oracle databases and Oracle Rdb".
The Discoverer command line interface runs only on a Windows platform.
The Discoverer command line interface enables you to perform tasks without running the Discoverer Administrator or Discoverer Desktop graphical user interface (GUI). For example, using the Discoverer command line interface you can:
In addition, you can create command files that contain multiple commands (much like MS-DOS batch files or Unix script files) to perform groups of administrative tasks automatically.
The figure below shows three different ways in which you can manipulate Discoverer EULs:
Much of the Discoverer command line interface is compatible with the Discoverer EUL command line for Java. If you have commands and scripts written for the Discoverer command line interface, you can easily convert them to run on the Discoverer EUL command line for Java.
The Discoverer command line interface and the Discoverer EUL command line for Java differ as follows:
Note: You do not need to have Oracle Discoverer Administrator installed to run the Discoverer EUL Command Line for Java interface.
A Discoverer command line interface command is an instruction that manipulates a Discoverer EUL in some way. For example:
dis51adm.exe /connect myname/mypassword@database
dis51adm.exe /connect myname/mypassword@database /import c:\data\sales.eex
Note: Commands are not case-sensitive (for more information, see also "Notes on using commands").
A Discoverer command line interface command modifier is an instruction that qualifies or refines a command. For example:
dis51adm.exe /connect myname/mypassword@database /import c:\data\sales.eex
/log sales_import_logfile
dis51adm.exe /connect myname/mypassword@database /delete /item sales.profit
You can run Discoverer commands in the following ways:
Text description of the illustration comfile.gif
To run the above command file, you might type the following in the command line:
dis51adm.exe /cmdfile import.txt
To use the Discoverer command line interface, you require the same Discoverer privileges as you do to use the Discoverer graphical user interface.
If you want to perform an operation on an EUL using the Discoverer command line interface, you must have the correct privileges. If you do not have the correct privileges, the operation will fail.
When using the Discoverer command line interface, you can explicitly specify an EUL using the modifier /eul (for more information, see "/eul" ) or if you do not specify an EUL, Discoverer will identify the default EUL for the database user.
When using the Discoverer command line interface, the following rules apply:
dis51adm.exe
/? in the Windows Run dialog
.
For more information about identifiers, see Chapter 3, "What are identifiers?".
When specifying an object's display name or identifier that contains a special character (e.g. a space), enclose the entire string in double quotation marks (" "). For example, enter the name of the folder object Sales Figures as /folder "Sales Figures".
/REFRESH_SUMMARY
command line option only works in conjunction with Oracle databases.
/connect "/[@<dbname>]"
This guide uses the following command syntax conventions:
Use this syntax for the Discoverer command line interface (typed in a single line with no line breaks or carriage returns):
Where:
To delete the Sales folder and Sum1 summary from the eul31 EUL you would use the following command:
dis51adm.exe /connect me/mypassword /delete /folder "Sales" /summary "Sum1" /eul eul31 /log del.log
To refresh the Sales1 and Sales2 folders you would use the following command:
dis51adm.exe /connect me/mypassword /refresh_folder "Sales1, Sales2" /log refsum.log
To create an Applications Mode EUL in the database and grant access to it you would use the following command:
dis51adm.exe /connect eul_owner:appsresp/appspwd /create_eul /apps_mode /apps_grant_details apps/apps
Command files are text files that contain one or more Discoverer commands that can be run automatically from the command line. Command files work in a similar way to MS-DOS batch files and UNIX script files.
The commands in a command file are treated as though they were entered directly on the command line. Carriage returns embedded in the text file are ignored.
A command file can in turn invoke other command files. This provides a convenient work around for the Microsoft Windows imposed limitation of restricting a command line to not more than 255 characters in length.
You can create a command file using a text editor. Type the command into the text editor and save the file using the extension .txt.
To run a command file, start the Discoverer Administrator executable (for example, dis51adm.exe) with the name of the command file as an argument to the /cmdfile command. For example, to run commands stored in the text file Import.txt, type:
dis51adm.exe /cmdfile Import.txt
You can also run more than one command file by repeating the /cmdfile command. For example, to run commands stored in the text file Login.txt, then commands in Import.txt, type:
dis51adm.exe /cmdfile Login.txt /cmdfile Import.txt
Command files are a convenient way to store modular commands, which can then be used in different combinations. For example, the following three command files contain the following commands:
contains the line /connect me/mypassword@mydatabase
contains the line /create eul /log create.log
contains the line /delete eul /log delete.log
These three files can then be run from the command line in any of the following three combinations:
dis51adm.exe /cmdfile connect.txt
This would be a simple connect from the command line.
dis51adm.exe /cmdfile connect.cmd /cmdfile create.txt
This would connect and create an EUL for the connected user, storing all output into a log file named create.log.
dis51adm.exe /cmdfile connect.cmd /cmdfile delete.txt
This would connect and delete the EUL owned by the connected user, storing all output into a log file named delete.log .
Use the table below to find a brief description of a Discoverer Administrator command:
Command | Description |
---|---|
"/?" |
Display online help. |
"/apps_fndnam" <foundation name> |
Override connection details. |
"/apps_user" |
Connect as Oracle Applications user. |
"/asm" <modifier(s)> |
Automate summary management ASM |
"/cmdfile" |
Run command files |
"/connect" <user-name>/<password> [@<database>] |
Connect to an EUL. |
"/create_eul" |
Create an EUL. |
"/create_eul /apps_mode" |
Create an APPS EUL. |
"/delete" <modifier(s)> |
Delete EUL objects. |
"/delete_bus_area" <business area> |
Delete a business area. |
"/delete_eul" |
Delete an EUL. |
"/export (EUL objects)" <export file> <modifier(s)> |
Export EUL objects. |
"/import (Business Area)" <business area> |
Import a business area. |
"/import (EUL objects)" <import file(s)> <modifier(s)> |
Import EUL objects. |
"/load" <business_area> |
Load a business area. |
"/refresh_bus_area" <bus area name(s)> |
Refresh business areas. |
"/refresh_folder" <folder name(s)> |
Refresh folders. |
"/refresh_summary" <summary name(s)> <bus area name> |
Refresh summary folders. |
Use the table below to find out which command to use for a particular task:
How to: | Use this command |
---|---|
Automate summary management (ASM) |
"/asm" <modifier(s)> |
Connect as Oracle Apps user. |
"/apps_user" |
Connect to an EUL. |
"/connect" <user-name>/<password> [@<database>] |
Create an EUL. |
"/create_eul" |
Create an APPS EUL. |
"/create_eul /apps_mode" |
Delete a Business Area. |
"/delete_bus_area" <business area> |
Delete an EUL. |
"/delete_eul" |
Delete EUL objects. |
"/delete" <modifier(s)> |
Display on-line help. |
"/?" |
Export EUL objects. |
"/export (EUL objects)" <export file> <modifier(s)> |
Import a Business Area. |
"/import (Business Area)" <business area> |
Import EUL objects. |
"/import (EUL objects)" <import file(s)> <modifier(s)> |
Load a Business Area. |
"/load" <business_area> |
Override connection details. |
"/apps_fndnam" <foundation name> |
Refresh Business Areas. |
"/refresh_bus_area" <bus area name(s)> |
Refresh Folders. |
"/refresh_folder" <folder name(s)> |
Refresh Summaries. |
"/refresh_summary" <summary name(s)> <bus area name> |
Run command files |
"/cmdfile" <command file name(s)> |
This section contains detailed reference information about each command in the Discoverer Administrator command line interface. Note the following:
This command displays a list of Discoverer commands and their syntax and arguments.
Information | Details |
---|---|
"/?" |
|
None |
|
None |
|
None |
|
dis51adm.exe /? |
This command overrides the values for both the fields GWYUID (including Gateway User ID password) and FNDNAM in the Connection tab of the Options dialog.
Information | Details |
---|---|
/apps_fndnam <foundation name> |
|
/apps_gwyuid <gateway user id>/<password> |
|
dis51adm.exe /connect appsuser:appsresp/appspwd /apps_ fndnam apps /apps_gwyuid applsyspub/pub |
This command enables you to connect to Discoverer as an Oracle Applications user.
Information | Details |
---|---|
/apps_user |
|
"/apps_responsibility" "/apps_security_group" |
|
dis51adm.exe /connect appsuser/appspwd /apps_user /apps_responsibility "UK_Purchasing" /apps_security_ group "UK_Managers" Or dis51adm.exe /connect appsuser:UK_Purchasing/appspwd /apps_user /apps_security_group "UK_Managers" |
This command enables you to execute Discoverer's Automated Summary Management facility (ASM).
Information | Details |
---|---|
/asm [/asm_space <bytes> | |
|
"/asm_space, /asm_tablespace" |
|
If you specify an /asm_tablespace argument, you must specify an asm_space argument. |
|
dis51adm.exe /connect me/mypassword /asm /asm_space 2182 /asm_tablespace user_data |
This command enables you to run Discoverer commands stored in a text file automatically.
Information | Details |
---|---|
/cmdfile <file name> |
|
To create a command file, create a text file containing one or more Discoverer commands using a standard text editor. To run the command(s) in the text file, at the command line enter: dis51adm.exe /cmdfile <file name> For more information, see "What is a command file?". |
|
To run command(s) stored in the text file myFile, type the following command at the command line: dis51adm.exe /connect me/mypassword /cmdfile myFile |
This command enables you to connect to an EUL without having to enter a user name and password at the "Connect dialog".
Information | Details |
---|---|
|
|
"/eul" <eul> |
|
See also Chapter 16, "Using Discoverer with Oracle Applications" |
|
dis51adm.exe /connect user/password@datatbase |
This command enables you to create a Discoverer EUL.
Information | Details |
---|---|
/create_eul |
|
/apps_mode "/apps_grant_details" /default_tablespace "/eul_language" <language> "/log" "/overwrite" "/password" "/private" "/show_progress" /temporary_tablespace "/user" |
|
When using the /create_eul command, note the following:
For more information about the creation and deletion of End User Layers, see Chapter 3, "Creating and maintaining End User Layers" . |
|
To create a private EUL for a user named, "Bob", whose password is welcome, overwriting any existing EUL and recording all log entries in a file named create.log, enter: dis51adm.exe /connect me/mypassword /create_eul /overwrite /user bob /password welcome /private /log create.log |
This command enables you to create an Oracle Applications Mode EUL using the Discoverer command line interface. This command starts Discoverer Administrator (in Oracle Applications mode), creates the Applications Mode EUL in the database, and connects you to it. The example also includes the specification of schema/password.
Information | Details |
---|---|
/create_eul /apps_mode |
|
"/apps_grant_details" |
|
dis51adm.exe /connect system/manager /create_eul /apps_ mode /apps_grant_details apps/apps |
This command enables you to remove EUL objects from the database. You can also remove an entire EUL using the "/delete_eul" command.
Information | Details |
---|---|
/delete <modifier(s)> [/identifier] |
|
Modifiers for configuring the deletion: "/log" <log file name> ["/log_only"] "/show_progress" Modifiers for defining which EUL object(s) to delete: /asm_policy <asm policy> |
|
You can delete one or more EUL objects at a time, (see examples below). Parameters (e.g. business areas, folders) must be named explicitly, wildcards are not allowed. |
|
To delete two Business Areas named Test BA and Final BA, residing in an EUL named eul31, and write to a log file named delba.log, enter: dis51adm.exe /connect me/mypassword /delete /business_area "Test BA, Final BA" /eul eul31 /log delba.log To delete a Folder named "Sales", and a Summary named "Sum1", residing in an EUL named eul31, and write to a log file named del.log, enter: dis51adm.exe /connect me/mypassword /delete /folder Sales /summary Sum1 /eul eul31 /log del.log |
This command enables you to remove a Discoverer business area from the database. See also "/delete_eul" and "/delete".
Information | Details |
---|---|
/delete_bus_area <business area> |
|
Modifiers for configuring the deletion: "/keep_folder" "/log" <log file name> ["/log_only"] "/show_progress" |
|
This command has been superceded by the "/delete" command, and is included for backwards compatibility. For more information about the /delete command, see "/delete". |
|
To delete the Business Areas named Test BA and Final BA, and write to a log file named delba.log, enter: dis51adm.exe /connect me/mypassword /delete_bus_area "Test BA, Final BA" /log delba.log |
This command enables you to delete the current Discoverer EUL. You can also selectively remove individual EUL objects using the "/delete" command.
Information | Details |
---|---|
/ |
|
"/log" "/show_progress" |
|
You can only delete EULs for which you are the registered owner. |
|
dis51adm.exe /connect me/mypassword /delete_eul /log "c:\my log dir\delete_eul.log" |
This command enables you to export EUL objects to a Discoverer export file (EEX file). You can selectively export individual EUL objects (e.g. folders, business areas, functions) or entire EULs (using the /all modifier). When you import multiple files, Discoverer automatically resolves references between the files. For example, you can export the Emp folder in fileA.eex and the Dept folder in fileB.eex. If Emp and Dept are joined, the join information will actually be in both files, but neither file contains the information for both folders. If you import both files, the join will be recreated when the second file is processed.
Information | Details |
---|---|
/ |
|
"/all" /asm_policy <asm policy> "/audit_info" <audit details> "/business_area" <business area> "/external_element" <filename> (this filename refers to an xml file, not the export filename) "/folder" <folder> "/function" <function> "/hierarchy" <hierarchy> "/identifier" "/item_class" <item_class> "/log" <log file name> [log_only] "/summary" <summary> /set_created_by <creator name> /set_updated_by <updated name> "/show_progress" "/workbook" <workbook> [XML_workbook] "/xmlworkbook" (takes no parameters) |
|
<filename> - The name of the target *.EEX file. If a directory path is not specified, the target file is created in the default Discoverer folder. To override the default target directory setting, specify a directory path for the file, for example c:\data\sales.eex . Note that the directory path must be an absolute path, not a relative path. Wildcards are not allowed for parameters (e.g. business areas, folders) these must be named explicitly. [<bus_area_name>] - Use this option to export an entire business area and its contents (i.e. all EUL objects in the business area). If you only want to export the business area definition and metadata for the contents, use the /business_area modifier. When you export a business area using the /business_area modifier, Discoverer exports only business area definitions (e.g. business area name and description) and links to the folders in the business area. Discoverer will export the folders and workbooks only when they are specified by name. <modifiers> - When specifying parameters, you can use either their Display Name or Identifier. To maintain data relationships, you must also export linked (or joined) objects. |
|
To export two business areas named Test BA and Final BA, residing in an EUL named eul31, into a file named export.eex, and write to a log file named export.log, enter: dis51adm.exe /connect me/mypassword /export export.eex /business_area "Test BA" /business_area "Final BA" /all /eul eul41 /log import.log |
This command enables you to import a Discoverer business area into the database from an EEX file. For more information about selectively importing Discoverer EUL objects, see "/import (EUL objects)".
Information | Details |
---|---|
/import <file name> |
|
"/log" <log file name> [log_only] "/rename" <rename-policy> "/show_progress" |
|
This command has been superseded by the / |
|
To import the business area in the file myBA.eex, and write to a log file named impba.log, enter: dis51adm.exe /connect me/mypassword /import myBA.eex /log impba.log |
This command enables you to import EUL objects from one or more Discoverer export files (EEX files). Discoverer export files are created using the /export
command, and contain EUL objects (e.g. folders, business areas, functions, or an entire EUL).
Information | Details |
---|---|
/ |
|
"/eul"<EUL> "/identifier" "/keep_format_properties" "/log" <log file name> [log_only] /preserve_workbook_owner "/refresh" | "/rename" "/show_progress" |
|
<source filename(s)> - the name(s) of the source *.EEX file(s). You must specify the full path name for the file (e.g. 'c:\data\sales.eex'). Note that the directory path must be an absolute path, not a relative path. Wildcards are not allowed for parameters (e.g. business areas, folders) these must be named explicitly. Where multiple files are being imported, all files must be encapuslated in one pair double quotes and separated by spaces (for example, see syntax above). |
|
dis51adm.exe /connect <userid>/<password>@<dbalias> /import "file1.eex file2.eex" |
This enables you to bulk load data from a database into a Discoverer business area.
Information | Details |
---|---|
/ |
|
"/aggregate"<aggregate> "/capitalize" "/date_hierarchy" <date_hier> "/db_link" <db_link> "/description" <descrip> "/eul" <eul_name> "/insert_blanks" "/join" <join_policy> "/log" <log_file> "/lov" <lov> "/object" <obj_name> "/remove_prefix" "/show_progress" "/sort_folders" /sort_items "/source" <source> "/user" <user_id> |
|
When using the /load command, note the following:
|
|
You want to bulk load into an EUL named eul31 from an Oracle Designer source on the current connection, creating a new business area named Test BA that:
To perform the above bulk load, enter: dis51adm.exe /connect me/mypassword /load "Test BA" /source "Designer 6i - bobsworkarea" /eul eul31 /user bob /object test% /capitalize /remove_prefix /replace_ blanks /date_hierarchy "" /lov "CHAR, INTEGER, DECIMAL" /aggregate AVG /log load.log /description "Test BA" |
This command enables you to refresh one or more Discoverer Business Areas, by retrieving an up-to-date EUL structure from the database.
Information | Details |
---|---|
/ |
|
"/db_link" "/eul" "/log" "/schema" "/source" "/show_progress" |
|
When using the
|
|
To refresh two Business Areas named Test BA and Final BA that reside in an EUL named eul31, from an Oracle Designer source on the current connection that contains tables matching the pattern test% owned by user Bob, and summarize information in a log file named refba.log, enter: dis51adm.exe /connect me/mypassword /refresh_bus_area "Test BA, Final BA" /source "Designer 6i - bobsworkarea" /eul eul31 /user bob /log refba.log |
This command enables you to refresh one or more Discoverer folders. The query on which the folder is based is re-run in order to retrieve up-to-date data.
Information | Details |
---|---|
/ |
|
"/log" "/show_progress" "/source" "/user" <username> |
|
When using the |
|
To refresh two folders named Sales1 and Sales2, residing in a Business Area named Test BA, found in an EUL named eul31, and write to a log file named reffol.log, enter: dis51adm.exe /connect me/mypassword /refresh_folder "Sales1, Sales2" /log reffol.log |
This command enables you to refresh one or more Discoverer Summary folders. The query on which the summary is based is re-run in order to retrieve up-to-date data.
Information | Details |
---|---|
/ |
|
"/log" "/show_progress" |
|
When using the
|
|
To refresh two summaries named Summary1 and Summary2, residing in a Business Area named Test BA, found in an EUL named eul31, and write to a log file named refsum.log, enter: dis51adm.exe /connect me/mypassword /refresh_summary "Summary1, Summary2" "Test BA" /log refsum.log /eul eul31 |
This section contains detailed reference information about optional Discoverer Administrator command modifiers available in the Discoverer command line interface. Command modifiers are used to refine or qualify commands. Note the following:
The /aggregate
modifier enables you to specify the default aggregate to be used by a command.
Information | Details |
---|---|
/ |
The /all
modifier enables you to select every object in an EUL for import, export or deletion.
Information | Details |
---|---|
/ |
The modifier /apps_grant_details enables you to specify an Oracle Applications schema and password when creating an Oracle Applications mode EUL. For example, to specify the Oracle Applications foundation name and password (<fndnam>/<password>).
Information | Details |
---|---|
/apps_grant_details |
The modifier /apps_responsibility enables you to specify an Oracle Applications responsibility when connecting as an Oracle Applications database user. This can also be included immediately following a colon (:) placed after the Oracle Applications user name but before the password.
Information | Details |
---|---|
/apps_responsibility |
The /apps_security_group modifier enables you to specify an Oracle Applications security group when connecting as an Oracle Applications database user.
Information | Details |
---|---|
/apps_security_group |
The /asm_tablespace modifier ignores any tablespace value set in the ASM policy and uses this tablespace constraint instead. The /asm_space modifier ignores any space value set in the ASM policy and uses this space constraint instead. The following are valid combinations of tablespace and space values:
Information | Details |
---|---|
/asm [/asm_space <bytes> | |
The /audit_info modifier enables you to export audit fields with every object, (Created By, Created Date, Updated By, Updated Date). You can override the Created By and Updated By fields using the additional modifiers /set_created_by and /set_updated_by.
Information | Details |
---|---|
/ |
The /ba_link modifier enables you to specify a business area and folder for deletion.
Information | Details |
---|---|
/ |
The /business_area modifier enables you to specify a business area for import, export or deletion
The /capitalize modifier enables you to request that folder names have initial capital letters when they are generated from their respective column names during a bulk load.
Information | Details |
---|---|
/ |
The /condition modifier enables you to specify a condition for deletion.
Information | Details |
---|---|
/ |
The /date_hierarchy modifier enables you to specify the date hierarchy to be used during a bulk load.
Information | Details |
---|---|
/ |
|
Any valid date hierarchy name or "". If you set < |
The /db_link modifier enables you to specify the database link to be used by a command.
Information | Details |
---|---|
/ |
|
<db_link> can be any valid database link. |
The /description modifier enables you to specify a description for an object.
Information | Details |
---|---|
/ |
|
<description> can be any string. |
The /eul modifier enables you to specify an EUL on which to run a command. You must have access privileges to the specified EUL. If not specified, the default EUL for the database user is used.
Information | Details |
---|---|
/ |
|
<EUL> must be the name of a valid EUL. |
Note that this does not change the default EUL for the user.
The /eul_language modifier used (currently by Oracle Applications) with the /create_eul command, enables you to specify a language for the EUL
.
Information | Details |
---|---|
/ |
The /external_element modifier is used only with the /export command. The external_element modifier enables you to place XML code from a specified file at the top of the export file.
The /folder modifier enables you to specify a folder for import, export or deletion.
Information | Details |
---|---|
/ |
The /function modifier enables you to specify a function for import, export or deletion.
Information | Details |
---|---|
/ |
The /hier_node modifier enables you to specify a node in a hierarchy for deletion.
Information | Details |
---|---|
/ |
The /hierarchy modifier enables you to specify a hierarchy.
Information | Details |
---|---|
/ |
The /identifier modifier enables you to specify EUL objects by identifier, rather than by display name. If not specified, the object is identified by display name by default.
Information | Details |
---|---|
/ |
The /insert_blanks modifier enables you to request that folder names have spaces instead of underscore characters when they are generated from their respective column names during a bulk load.
Information | Details |
---|---|
/ |
The /item modifier enables you to specify an item for deletion.
Information | Details |
---|---|
/ |
The /item_class modifier enables you to specify an item class for import, export or deletion.
Information | Details |
---|---|
/ |
The /join modifier has two applications depending on which command you use it with:
Information | Details |
---|---|
Used with the /load command: /join <NONE|COLUMN_NAME|PRIMARY_KEY> Used with the /delete command: /join <join name> |
The /keep_folder modifier enables you to leave the folders in place when deleting a business area. If not specified, the folders are removed along with the business area.
Information | Details |
---|---|
/ |
The /keep_format_properties modifier enables you to keep existing format properties (e.g. display names, descriptions) on import. The default is to change format properties.
Information | Details |
---|---|
/ |
The /log modifier enables you to specify a name for the log file that stores command status messages. After each command is executed, Discoverer Administrator writes a status message indicating whether the command was successful. You can override the name and location of the log file using the /log modifier.
Information | Details |
---|---|
/ |
|
Any valid filename (dependent on the operating system). |
The /log_only modifier enables you to simulate a command and generate a log, without changing your data. This option enables you to check for errors and exceptions before changing your data.
The /lov modifier enables you to specify the data types for which a list of values should be generated during a bulk load.
Information | Details |
---|---|
/ |
The /object modifier enables you to specify an object for bulk load, import, export or deletion.
Information | Details |
---|---|
/ |
|
Any valid object name. You can use wildcard characters. |
The /overwrite modifier enables you to overwrite an existing EUL owned by the intended owner. If omitted, the default is to not overwrite an existing EUL.
Information | Details |
---|---|
/overwrite |
The /parameter modifier enables you to specify a parameter for deletion. When specifying parameters, you can use either their Display Name or Identifier.
Information | Details |
---|---|
/ |
The /password modifier enables you to specify the password to be used by the operation.
Information | Details |
---|---|
/ |
|
Any valid password associated with the value specified by the user. |
When you create an EUL, the /private modifier enables you to define its status as private to the Discoverer manager. If omitted, the status defaults to `public'.
Information | Details |
---|---|
/ |
The /refresh modifier enables you to merge imported objects with existing objects. By default, merged objects are matched on display name. Use the "/identifier" modifier to match on identifier.
Information | Details |
---|---|
/ |
The /remove_prefix modifier enables you to request that item names do not include the column name prefix when they are generated from their respective column names during a bulk load.
Information | Details |
---|---|
/ |
|
EMPNO |
The /rename modifier enables you to specify which objects are renamed when importing objects that match existing objects.
The /schema modifier enables you to specify a schema (user) for the operation.
Information | Details |
---|---|
/ |
The /show_progress modifier enables you to monitor a command in operation.
Information | Details |
---|---|
/ |
The /sort_folders modifier enables you to specify that Discoverer will alphabetically sort folders during a bulk load.
Information | Details |
---|---|
/ |
|
ON is the default |
The /sort_items modifier enables you to specify that Discoverer will alphabetically sort items during a bulk load.
Information | Details |
---|---|
/ |
|
OFF is the default |
The /source modifier enables you to specify the source for the operation.
The /summary modifier enables you to specify a summary for import, export or deletion.
Information | Details |
---|---|
/ |
The /user modifier enables you to specify the user ID to be used for the operation.
Information | Details |
---|---|
/ |
|
Any valid user ID. |
The /workbook modifier enables you to specify a workbook for import, export or deletion.
Information | Details |
---|---|
/ |
The /xmlworkbook modifier (used with the /export command) forces all workbooks to be exported both in XML format and binary large object (BLOB) format. The /xmlworkbook modifier enables you to view exported workbooks in an XML browser.
Information | Details |
---|---|
/xml |
This section contains detailed reference information about each command in the Discoverer Desktop command line interface. Note that commands are listed in alphabetical order.
This command displays a list of Discoverer Desktop commands.
Information | Details |
---|---|
/? |
|
None |
|
None |
|
None |
|
dis5usr.exe /? |
This command enables you to run workbooks without delaying the processing of subsequent workbooks.
This command enables you to connect directly to Discoverer Desktop without having to use the Connect dialog.
This command enables you to export the results of a workbook to a specified file.
This command enables you to open a workbook from a .dis file.
Information | Details |
---|---|
/open <file-workbook> |
|
None |
|
dis5usr.exe /open workbook1.dis |
This command enables you to open a workbook from the database.
Information | Details |
---|---|
/opendb <db-workbook> |
|
None |
|
dis5usr.exe /opendb workbook1.dis |
This command enables you to set a specified parameter to a specified value.
This command enables you to print a workbook from a file to a default printer.
Information | Details |
---|---|
/p <file> |
|
None |
|
Print options are saved as part of the workbook. |
This command enables you to print a workbook from a file to a specified printer with specified printer driver and port.
Information | Details |
---|---|
/pt <file> <printer> <driver> <port> |
|
None |
This command enables you to copy a workbook from the filesystem to the database.
This command enables you execute a query for the specified sheet(s).
Information | Details |
---|---|
/sheet {<sheet-name>|<sheet-number>|ALL} |
|
None |
|
Discoverer executes a query for : |
|
![]() Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
|