ASP.NET Web PDF Document Viewer/Editor Control Library

he technique I am about to discuss allows you to have a single script that can be called in several ways by different names. The script itself contains all the code necessary to perform a number of tasks, but you may want to determine the specific task to be performed at runtime by calling the script by a specific name. This lets users invoke an individual task by name without having to learn specialized command-line switches for the options they want. There are two of ways of specifying the precise behavior of a script. One way is to have the script accept command-line options telling it how to act. This method is covered in 5, which dealt with the use of getopts. This chapter illustrates the second method: calling a script by giving it multiple names. Sometimes you want to have multiple scripts perform tasks that are related in some way but have slight differences. An example, albeit a silly one, is a script that monitors disk consumption of the / file system. The script will determine the disk utilization percentage from the output of the df command. The following is a sample of df output:

how to make barcodes in excel 2011, convert text to barcode in excel 2003, ean barcode excel macro, install barcode font excel 2007, download free barcode font for excel 2007, barcode plugin excel free, how to change font to barcode in excel, barcode add in excel 2010 free, free barcode add in for word and excel, how to make barcodes in excel 2013,

The EXCLUDE and INCLUDE parameters are two mutually exclusive parameters that you can use to perform what is known as metadata filtering. Metadata filtering enables you to selectively leave out or include certain types of objects during a Data Pump Export or Import job. In the old export utility, you used the CONSTRAINTS, GRANTS, and INDEXES parameters to specify whether you wanted to export those objects. Using the EXCLUDE and INCLUDE parameters, you now can include or exclude many other kinds of objects besides the four objects you could filter previously. For example, if you don t wish to export any packages during the export, you can specify this with the help of the EXCLUDE parameter.

If you use the CONTENT=DATA_ONLY option (same as the old ROWS=Y parameter), you aren t exporting any objects just table row data. Naturally, in this case, you can t use either the EXCLUDE or INCLUDE parameter.

Summary

Simply put, the EXCLUDE parameter helps you omit specific database object types from an export or import operation. The INCLUDE parameter, on the other hand, enables you to include only a specific set of objects. Following is the format of the EXCLUDE and INCLUDE parameters: EXCLUDE=object_type[:name_clause] INCLUDE=object_type[:name_clause] For both the EXCLUDE and INCLUDE parameters, the name clause is optional. As you know, several objects in a database such as tables, indexes, packages, and procedures have names. Other objects, such as grants, don t. The name clause in an EXCLUDE or an INCLUDE parameter lets you apply a SQL function to filter named objects. Here s a simple example that excludes all tables that start with EMP: EXCLUDE=TABLE:"LIKE 'EMP%'" In this example, "LIKE 'EMP%'" is the name clause.

The name clause in an EXCLUDE or INCLUDE parameter is optional. It s purely a filtering device, allowing you finer selectivity within an object type (index, table, and so on). If you leave out the name clause component, all objects of the specified type will be excluded or included. In the following example, Oracle excludes all indexes from the export job, since there is no name clause to filter out only some of the indexes: EXCLUDE=INDEX You can also use the EXCLUDE parameter to exclude an entire schema, as shown in the following example: EXCLUDE=SCHEMA:"='HR'" The INCLUDE parameter is the precise opposite of the EXCLUDE parameter: it forces the inclusion of only a set of specified objects in an export. As in the case of the EXCLUDE parameter, you can use a name clause to qualify exactly which objects you want to export. Thus, you have the ability to selectively choose objects at a fine-grained level. The following three examples show how you can use the name clause to limit the selection of objects: INCLUDE=TABLE:"IN ('EMPLOYEES', 'DEPARTMENTS')" INCLUDE=PROCEDURE INCLUDE=INDEX:"LIKE 'EMP%'" The first example is telling the Data Pump job to include only two tables: employees and departments. In the second example, the INCLUDE parameter specifies that only procedures should be included in this export job. The third example shows how you can specify that only those indexes that start with EMP should be part of the export job. The following example shows how you must use slashes (\) to escape the double quotation marks: $ expdp scott/tiger DUMPFILE=dumphere:file%U.dmp schemas=SCOTT EXCLUDE=TABLE:\"='EMP'\", EXCLUDE=FUNCTION:\"='MY_FUNCTION''\",

Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 18334940 13019804 4383768 75% / /dev/hda1 256666 25241 218173 11% /boot none 257300 0 257300 0% /dev/shm /dev/hdb1 16577308 11732468 4002760 75% /snapshot