6.2.7.1 lsdataset
List datasets.
Purpose
The lsdataset
command displays information about Exascale datasets. It can also list the files contained
in a specific dataset.
Syntax
lsdataset [ -l ] [ --detail ] [ --attributes attribute[,attribute] ... ]
[ --filter filter[,filter] ... ] [ --sort [-]attribute[,[-]attribute] ... ]
[ --count value ] [ --files [ --recursive ]] [ dataset-id ]
Command Options
The options for the lsdataset
command are:
-
dataset-id: The identifier for a dataset that you want to display information about.
Each system-defined dataset has a unique composite identifier, which contains unique identifiers for the associated entities. The dataset identifier has one of the following formats:
-
@Vault-name
: Identifies the vault-level dataset for a specific named vault. -
@Vault-name:GI-cluster-ID
: Identifies the dataset for a specific Oracle Grid Infrastructure (GI) cluster, which consumes storage space in the specified vault. -
@Vault-name:GI-cluster-ID:CDB-ID
: Identifies the dataset for a specific Oracle multitenant container database (CDB) that belongs to the specified GI cluster. -
@Vault-name:GI-cluster-ID:CDB-ID:PDB-ID
: Identifies the dataset for an Oracle pluggable database (PDB) that is associated with the specified CDB, GI cluster, and vault.
The asterisk (
*
) can be used for wildcard searches. For example,@Vault-name:GI-cluster-ID:*
displays information about all CDB datasets associated with the specified GI cluster and vault.If dataset-id is not specified, the command displays information about all datasets in all vaults.
-
-
-l
: Returns output in a long, tabular form. -
--detail
: Lists all attributes in a detailed form. -
--attributes
: Lists the specific attributes to display. -
--filter
: Used to specify conditions for filtering the list output. -
--sort
: Used to sort the output using the specified attributes. -
--count
: Specifies the maximum number of results to report. -
--files
: Lists files that are in the specified dataset. -
--recursive
: Also lists files that are in descendant datasets.
Usage Notes
Note the following information when using this command:
-
Filter conditions are specified as:
<attribute><operator><value>
.The allowed operators are =, !=, >=, <=, >, and <.
Multiple comma-separated filter conditions are combined using AND logic.
Dates can be specified using the following formats:
yyyy-MM-dd''T''HH:mm:ss
yyyy-MM-dd
(Time is assumed to be 00:00 AM)HH:mm:ss
(Date is assumed to be today)
A date can also be followed by a timezone specification.
Sizes can be specified using suffixes
K
,KB
,M
,MB
,G
,GB
,T
,TB
. The suffix is not case-sensitive. -
Sorting attributes are specified as:
[-]attribute
. Multiple sort attributes are comma-delimited. The default sort order is ascending. For descending sort order, prefix the attribute name with-
.For example, use the following to primarily sort by name in descending order, and use creation time in ascending order to further sort entries with the same name:
--sort -name,createTime
-
You must specify a dataset-id in conjunction with the
--files
option.
Examples
Example 6-69 Display All Datasets
You can use the lsdataset
command with no other options to
display a list of all datasets across all vaults.
@> lsdataset
id name
@MYDATA @MYDATA
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5 @MYDATA/cluster1
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301 @MYDATA/cluster1:mydb
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:1402749181 @MYDATA/cluster1:mydb.PDB$SEED
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:2132037342 @MYDATA/cluster1:mydb.CDB$ROOT
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:2164757665 @MYDATA/cluster1:mydb.MYDB_PDB1
@VAULT2 @VAULT2
...
Example 6-70 Display Additional Dataset Attributes
@> lsdataset --attributes id,name,fileUsageHC,datasetUsageHC
id name fileUsageHC datasetUsageHC
@MYDATA @MYDATA 0.0000 3.4961G
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5 @MYDATA/cluster1 294.5339M 3.4961G
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301 @MYDATA/cluster1:mydb 25.2656M 3.2085G
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:1402749181 @MYDATA/cluster1:mydb.PDB$SEED 650.6719M 650.6719M
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:2132037342 @MYDATA/cluster1:mydb.CDB$ROOT 1.9056G 1.9056G
@MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:2164757665 @MYDATA/cluster1:mydb.MYDB_PDB1 658.1719M 658.1719M
@VAULT2 @VAULT2 0.0000 110.8750M
...
Example 6-71 Display Files in a Dataset
@> lsdataset --files @MYDATA:a5b4997a027d6f91ffd9729702ff6ec5:1427076301:2164757665
DATAFILE/mydb_pdb1_db.f
DATAFILE/mydb_pdb1_tmp.f
DATAFILE/mydb_pdb1_xdb.f
DATAFILE/mydb_pdb1_ax.f
Example 6-72 Using the Recursive Display Option
The following examples illustrate using the --recursive
option.
Without the --recursive
option, the following example shows the files
belonging directly to the specified GI cluster dataset.
@> lsdataset --files @MYDATA:a5b4997a027d6f91ffd9729702ff6ec5
cluster1.ocr
cluster1/vfile1
With the --recursive
option, the following example shows the files belonging
to the specified GI cluster and all of the associated CDB and PDB datasets.
@> lsdataset --files --recursive @MYDATA:a5b4997a027d6f91ffd9729702ff6ec5
DATAFILE/mydb_pdb0_ax.f
dbs/xspfile.ora
DATAFILE/mydb_pdb0.xml
DATAFILE/mydb_pdb1_db.f
DATAFILE/t_ax1.f
DATAFILE/t_db1.f
CLUSTER1-A5B4997A027D6F91FFD9729702FF6EC5/MYDB/TEMPFILE/TEMP.OMF.2012709C
DATAFILE/t_xdb1.f
DATAFILE/mydb_pdb1_tmp.f
dbs/t_cf1.f
DATAFILE/mydb_pdb0_xdb.f
DATAFILE/mydb_pdb0_tmp.f
DATAFILE/t_undo1.f
cluster1.ocr
DATAFILE/mydb_pdb1_xdb.f
CLUSTER1-A5B4997A027D6F91FFD9729702FF6EC5/MYDB/PASSWORD/pwdMYDB.4ABC8604
cluster1/vfile1
DATAFILE/mydb_pdb0_db.f
DATAFILE/mydb_pdb1_ax.f
...
Parent topic: Dataset Management