tfactl ips

Use the tfactl ips command to collect Automatic Diagnostic Repository diagnostic data.

Syntax

tfactl ips
[ADD]
[ADD FILE]
[ADD NEW INCIDENTS]
[CHECK REMOTE KEYS]
[COPY IN FILE]
[COPY OUT FILE]
[CREATE PACKAGE]
[DELETE PACKAGE]
[FINALIZE PACKAGE]
[GENERATE PACKAGE]
[GET MANIFEST]
[GET METADATA]
[GET REMOTE KEYS]
[PACK]
[REMOVE]
[REMOVE FILE]
[SET CONFIGURATION]
[SHOW CONFIGURATION]
[SHOW FILES]
[SHOW INCIDENTS]
[SHOW PROBLEMS]
[SHOW PACKAGE]
[UNPACK FILE]
[UNPACK PACKAGE]
[USE REMOTE KEYS]
[options]

For detailed help on each topic use:

help ips topic

Parameters

tfactl ips Command Parameters

Parameter	Description
`ADD`	Adds incidents to an existing package.
`ADD FILE`	Adds a file to an existing package.
`ADD NEW INCIDENTS`	Finds new incidents for the problems and add the latest ones to the package.
`CHECK REMOTE KEYS`	Creates a file with keys matching incidents in specified package.
`COPY IN FILE`	Copies an external file into Automatic Diagnostic Repository, and associates it with a package and (optionally) an incident.
`COPY OUT FILE`	Copies an Automatic Diagnostic Repository file to a location outside Automatic Diagnostic Repository.
`CREATE PACKAGE`	Creates a package, and optionally select contents for the package.
`DELETE PACKAGE`	Drops a package and its contents from Automatic Diagnostic Repository.
`FINALIZE PACKAGE`	Gets a package ready for shipping by automatically including correlated contents.
`GENERATE PACKAGE`	Creates a physical package ( `zip` file) in target directory.
`GET MANIFEST`	Extracts the manifest from a package file and displays it.
`GET METADATA`	Extracts the metadata XML document from a package file and displays it.
`GET REMOTE KEYS`	Creates a file with keys matching incidents in specified package.
`PACK`	Creates a package, and immediately generates the physical package.
`REMOVE`	Removes incidents from an existing package.
`REMOVE FILE`	Removes a file from an existing package.
`SET CONFIGURATION`	Changes the value of an Incident Packaging Service configuration parameter.
`SHOW CONFIGURATION`	Shows the current Incident Packaging Service settings.
`SHOW FILES`	Shows the files included in the specified package.
`SHOW INCIDENTS`	Shows incidents included in the specified package.
`SHOW PROBLEMS`	Shows problems for the current Automatic Diagnostic Repository home.
`SHOW PACKAGE`	Shows details for the specified package.
`UNPACK FILE`	Unpackages a physical file into the specified path.
`UNPACK PACKAGE`	Unpackages physical files in the current directory into the specified path, if they match the package name.
`USE REMOTE KEYS`	Adds incidents matching the keys in the specified file to the specified package.

tfactl ips ADD

Use the tfactl ips ADD command to add incidents to an existing package.

Syntax

tfactl ips ADD [INCIDENT incid | PROBLEM prob_id | PROBLEMKEY prob_key | SECONDS seconds | TIME start_time TO end_time] PACKAGE package_id

Parameters

tfactl ips ADD Command Parameters

Parameter	Description
`incid`	Specify the ID of the incident to add to the package contents.
`prob_id`	Specify the ID of the problem to add to the package contents.
`prob_key`	Specify the problem key to add to the package contents.
`seconds`	Specify the number of seconds before now for adding package contents.
`start_time`	Specify the start of time range to look for incidents in.
`end_time`	Specify the end of time range to look for incidents in.

Example tfactl ips ADD

$ tfactl ips add incident 22 package 12

tfactl ips ADD FILE

Use the tfactl ADD FILE command to add a file to an existing package.

Syntax

The file must be in the same ADR_BASE as the package.

tfactl ips ADD FILE file_spec PACKAGE pkgid

Parameters

tfactl ips ADD FILE Command Parameters

Parameter	Description
`file_spec`	Specify the file with file and path (full or relative).
`package_id`	Specify the ID of the package to add the file to.

Example tfactl ips ADD FILE

$ tfactl ips add file ADR_HOME/trace/mydb1_ora_13579.trc package 12

tfactl ips ADD NEW INCIDENTS

Use the tfactl ips ADD NEW INCIDENTS command to find new incidents for the problems in a specific package, and add the latest ones to the package.

Syntax

tfactl ips ADD NEW INCIDENTS package_id

Parameters

tfactl ips ADD NEW INCIDENTS Command Parameters

Parameter	Description
`package_id`	Specify the ID of the package to add the incidents to.

tfactl ips CHECK REMOTE KEYS

Use the tfactl ips CHECK REMOTE KEYS command to create a file with keys matching incidents in a specified package.

Syntax

tfactl ips CHECK REMOTE KEYS file_spec PACKAGE package_id

Parameters

tfactl ips CHECK REMOTE KEYS Command Parameters

Parameter	Description
`file_spec`	Specify the file with file name and full path.
`package_id`	Specify the ID of the package to get the keys for.

tfactl ips COPY IN FILE

Use the tfactl ips COPY IN FILE command to copy an external file into Automatic Diagnostic Repository, and associate the file with a package and (optionally) an incident.

Syntax

tfactl ips COPY IN FILE file [TO new_name] [OVERWRITE] PACKAGE pkgid [INCIDENT incid]

Parameters

tfactl ips COPY IN FILE Command Parameters

Parameter	Description
`file`	Specify the file with file name and full path (full or relative).
`new_name`	Specify a name for the copy of the file.
`pkgid`	Specify the ID of the package to associate the file with.
`incid`	Specify the ID of the incident to associate the file with.

Options

OVERWRITE: If the file exists, then use the OVERWRITE option to overwrite the file.

Example tfactl ips COPY IN FILE

$ tfactl ips copy in file /tmp/key_file.txt to new_file.txt package 12 incident 62

tfactl ips COPY OUT FILE

Use the tfactl ips COPY OUT FILE command to copy an Automatic Diagnostic Repository file to a location outside Automatic Diagnostic Repository.

Syntax

tfactl IPS COPY OUT FILE source TO target [OVERWRITE]

Parameters

tfactl ips COPY OUT FILE Command Parameters

Parameter Description

Parameter	Description
`source`	Specify the file with file name and full path (full or relative). This file must be inside ADR.
`target`	Specify the file with file name and full path (full or relative). This file must be outside ADR.

source

Specify the file with file name and full path (full or relative).

This file must be inside ADR.

target

Specify the file with file name and full path (full or relative).

This file must be outside ADR.

Options

OVERWRITE: If the file exists, then use the OVERWRITE option to overwrite the file.

Example tfactl ips COPY OUT FILE

$ tfactl ips copy out file ADR_HOME/trace/ora_26201 to /tmp/trace_26201.txt

tfactl ips CREATE PACKAGE

Use the tfactl ips CREATE PACKAGE command to create a package, and optionally select the contents for the package.

Syntax

tfactl ips CREATE PACKAGE [INCIDENT inc_id | PROBLEM prob_id
| PROBLEMKEY prob_key | SECONDS seconds | TIME start_time TO end_time] [CORRELATE BASIC | TYPICAL | ALL] [MANIFEST file_spec]
[KEYFILE file_spec]

Parameters

tfactl ips CREATE PACKAGE Command Parameters

Parameter	Description
`incid`	Specify the ID of the incident to use for selecting the package contents.
`prob_id`	Specify the ID of the problem to use for selecting the package contents.
`prob_key`	Specify the problem key to use for selecting the package contents.
`seconds`	Specify the number of seconds before now for selecting the package contents.
`start_time`	Specify the start of time range to look for the incidents in.
`end_time`	Specify the end of time range to look for the incidents in.

Options

CORRELATE BASIC: The package includes the incident dumps and the incident process trace files. If the incidents share relevant correlation keys, then more incidents are included automatically.
CORRELATE TYPICAL: The package includes the incident dumps and all trace files that were modified in a time window around each incident. If the incidents share relevant correlation keys, or occurred in a time window around the main incidents, then more incidents are included automatically.
CORRELATE ALL: The package includes the incident dumps and all trace files that were modified between the first selected incident and the last selected incident. If the incidents occurred in the same time range, then more incidents are included automatically.
MANIFEST file_spec: Generates the XML format package manifest file.
KEYFILE file_spec: Generates the remote key file.

Note:

If you do not specify package contents, such as incident, problem, and so on, then Oracle Trace File Analyzer creates an empty package.

You can add files and incidents later.

If you do not specify the correlation level, then Oracle Trace File Analyzer uses the default level.

The default is normally TYPICAL, but you can change using the IPS SET CONFIGURATION command.

Example tfactl ips CREATE PACKAGE

$ tfactl ips create package incident 861

$ tfactl ips create package time '2006-12-31 23:59:59.00 -07:00' to '2007-01-01 01:01:01.00 -07:00'

tfactl ips DELETE PACKAGE

Use the tfactl ips DELETE PACKAGE command to drop a package and its contents from the Automatic Diagnostic Repository.

Syntax

tfactl ips DELETE PACKAGE package_id

Parameters

tfactl ips DELETE PACKAGE Command Parameters

Parameter	Description
`package_id`	Specify the ID of the package to delete.

Example tfactl ips DELETE PACKAGE

$ tfactl ips delete package 12

tfactl ips FINALIZE PACKAGE

Use the tfactl ips FINALIZE PACKAGE command to get a package ready for shipping by automatically including correlated contents.

Syntax

tfactl ips FINALIZE PACKAGE package_id

Example tfactl ips FINALIZE PACKAGE

$ tfactl ips finalize package 12

tfactl ips GENERATE PACKAGE

Use the tfactl ips GENERATE PACKAGE command to create a physical package (zip file) in the target directory.

Syntax

tfactl ips GENERATE PACKAGE package_id [IN path][COMPLETE | INCREMENTAL]

Parameters

tfactl ips GENERATE PACKAGE Command Parameters

Parameter	Description
`package_id`	Specify the ID of the package to create physical package file for.
`path`	Specify the path where the physical package file must be generated.

Options

COMPLETE: (Default) The package includes all package files even if a previous package sequence was generated.
INCREMENTAL: The package includes only the files that have been added or changed since the last package was generated.

Note:

If no target path is specified, then Oracle Trace File Analyzer generates the physical package file in the current working directory.

Example tfactl ips GENERATE PACKAGE

$ tfactl ips generate package 12 in /tmp

tfactl ips GET MANIFEST

Use the tfactl ips GET MANIFEST command to extract the manifest from a package file and view it.

Syntax

tfactl ips GET MANIFEST FROM FILE file

Parameters

tfactl ips GET MANIFEST FROM FILE Command Parameters

Parameter	Description
`file`	Specify the external file with file name and full path.

Example tfactl ips GET MANIFEST

$ tfactl ips get manifest from file /tmp/IPSPKG_200704130121_COM_1.zip

tfactl ips GET METADATA

Use the tfactl ips GET METADATA command to extract the metadata XML document from a package file and view it.

Syntax

tfactl ips GET METADATA [FROM FILE file | FROM ADR]

Parameters

tfactl ips GET METADATA Command Parameters

Parameter	Description
`file`	Specify the external file with file name and full path.

Example tfactl ips GET METADATA

$ tfactl ips get metadata from file /tmp/IPSPKG_200704130121_COM_1.zip

tfactl ips GET REMOTE KEYS

Use the tfactl ips GET REMOTE KEYS command to create a file with keys matching incidents in a specific package.

Syntax

tfactl ips GET REMOTE KEYS FILE file_spec PACKAGE package_id

Parameters

tfactl ips GET REMOTE KEYS FILE Command Parameters

Parameter	Description
`file_spec`	Specify the file with file name and full path (full or relative).
`package_id`	Specify the ID of the package to get keys for.

Example tfactl ips GET REMOTE KEYS

$ tfactl ips get remote keys file /tmp/key_file.txt package 12

tfactl ips PACK

Use the tfactl ips PACK command to create a package and immediately generate the physical package.

Syntax

tfactl ips PACK [INCIDENT incid | PROBLEM prob_id | PROBLEMKEY prob_key | SECONDS seconds | TIME start_time TO end_time]
[CORRELATE BASIC | TYPICAL | ALL] [MANIFEST file_spec] [KEYFILE file_spec]

Parameters

tfactl ips PACK Command Parameters

Parameter	Description
`incid`	Specify the ID of the incident to use for selecting the package contents.
`prob_id`	Specify the ID of the problem to use for selecting the package contents.
`prob_key`	Specify the problem key to use for selecting the package contents.
`seconds`	Specify the number of seconds before the current time for selecting the package contents.
`start_time`	Specify the start of time range to look for the incidents in.
`end_time`	Specify the end of time range to look for the incidents in.
`path`	Specify the path where the physical package file must be generated.

Options

**CORRELATE BASIC**: The package includes the incident dumps and the incident process trace files. If the incidents share relevant correlation keys, then more incidents are included automatically.
CORRELATE TYPICAL: The package includes the incident dumps and all trace files that were modified in a time window around each incident. If the incidents share relevant correlation keys, or occurred in a time window around the main incidents, then more incidents are included automatically.
CORRELATE ALL: The package includes the incident dumps and all trace files that were modified between the first selected incident and the last selected incident. If the incidents occurred in the same time range, then more incidents are included automatically.
MANIFEST file_spec: Generate the XML format package manifest file.
KEYFILE file_spec: Generate remote key file.

Note:

If you do not specify package contents, such as incident, problem, and so on, then Oracle Trace File Analyzer creates an empty package.

You can add files and incidents later.

If you do not specify the correlation level, then Oracle Trace File Analyzer uses the default level.

The default is normally TYPICAL, but you can change using the IPS SET CONFIGURATION command.

Example tfactl ips PACK

$ tfactl ips pack incident 861

$ tfactl ips pack time '2006-12-31 23:59:59.00 -07:00' to '2007-01-01 01:01:01.00 -07:00'

tfactl ips REMOVE

Use the tfactl ips REMOVE command to remove incidents from an existing package.

Syntax

The incidents remain associated with the package, but not included in the physical package file.

tfactl ips REMOVE [INCIDENT incid | PROBLEM prob_id | PROBLEMKEY prob_key] PACKAGE package_id

Parameters

tfactl ips REMOVE Command Parameters

Parameter	Description
`incid`	Specify the ID of the incident to add to the package contents.
`prob_id`	Specify the ID of the problem to add to the package contents.
`prob_key`	Specify the problem key to add to the package contents.

Example tfactl ips REMOVE

$ tfactl ips remove incident 22 package 12

tfactl ips REMOVE FILE

Use the tfactl ips REMOVE FILE command to remove a file from an existing package.

Syntax

The file must be in the same ADR_BASE as the package. The file remains associated with the package, but not included in the physical package file.

tfactl ips REMOVE FILE file_spec PACKAGE pkgid

Parameters

tfactl ips REMOVE FILE Command Parameters

Parameter	Description
`file_spec`	Specify the file with file name and full path (full or relative).
`package_id`	Specify the ID of the package to remove the file from.

Example tfactl ips REMOVE FILE

$ tfactl ips remove file ADR_HOME/trace/mydb1_ora_13579.trc package 12

tfactl ips SET CONFIGURATION

Use the tfactl ips SET CONFIGURATION command to change the value of an Incident Packaging Service configuration parameter.

Syntax

tfactl ips SET CONFIGURATION parameter_id value

Parameters

tfactl ips SET CONFIGURATION Command Parameters

Parameter	Description
`parameter_id`	Specify the ID of the parameter to change.
`value`	Specify the new value for the parameter.

tfactl ips SET CONFIGURATION

$ tfactl ips set configuration 6 2

tfactl ips SHOW CONFIGURATION

Use the tfactl ips SHOW CONFIGURATION command to view the current Incident Packaging Service settings.

Syntax

tfactl ips SHOW CONFIGURATION parameter_id

Example tfactl ips SHOW CONFIGURATION

$ tfactl ips show configuration

Multiple ORACLE HOMES were found, please select one ...

option[0] /scratch/app/oradb/product/11.2.0/dbhome_11204
option[1] /scratch/app/11.2.0.4/grid

Pls select an ORACLE_HOME to be used for the ADRCI binary [0] ?0
/scratch/app/oradb/product/11.2.0/dbhome_11204 was selected

Multiple ADR basepaths were found, please select one ...

( ) option[0] /scratch/app/oradb
( ) option[1] /scratch/app/oragrid

Pls select an ADR basepath [0..1] ?0
/scratch/app/oradb was selected

Multiple ADR homepaths were found for /scratch/app/oradb, please select one ...

( ) option[0] diag/rdbms/racone/racone_2
( ) option[1] diag/rdbms/rdb11204/rdb112041
( ) option[2] diag/rdbms/ogg11204/ogg112041
( ) option[3] diag/rdbms/apxcmupg/apxcmupg_1
( ) option[4] diag/rdbms/apxcmupg/apxcmupg_2
    option[5] Done

Pls select a homepath [5] ?0
diag/rdbms/racone/racone_2 was selected

PARAMETER INFORMATION:
   PARAMETER_ID           1
   NAME                   CUTOFF_TIME
   DESCRIPTION            Maximum age for an incident to be considered for inclusion
   UNIT                   Days
   VALUE                  90
   DEFAULT_VALUE          90
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0

PARAMETER INFORMATION:
   PARAMETER_ID           2
   NAME                   NUM_EARLY_INCIDENTS
   DESCRIPTION            How many incidents to get in the early part of the range
   UNIT                   Number
   VALUE                  3
   DEFAULT_VALUE          3
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0

PARAMETER INFORMATION:
   PARAMETER_ID           3
   NAME                   NUM_LATE_INCIDENTS
   DESCRIPTION            How many incidents to get in the late part of the range
   UNIT                   Number
   VALUE                  3
   DEFAULT_VALUE          3
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0

PARAMETER INFORMATION:
   PARAMETER_ID           4
   NAME                   INCIDENT_TIME_WINDOW
   DESCRIPTION            Incidents this close to each other are considered correlated
   UNIT                   Minutes
   VALUE                  5
   DEFAULT_VALUE          5
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0

PARAMETER INFORMATION:
   PARAMETER_ID           5
   NAME                   PACKAGE_TIME_WINDOW
   DESCRIPTION            Time window for content inclusion is from x hours before first included incident to x hours after last incident
   UNIT                   Hours
   VALUE                  24
   DEFAULT_VALUE          24
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0

PARAMETER INFORMATION:
   PARAMETER_ID           6
   NAME                   DEFAULT_CORRELATION_LEVEL
   DESCRIPTION            Default correlation level for packages
   UNIT                   Number
   VALUE                  2
   DEFAULT_VALUE          2
   MINIMUM                1
   MAXIMUM                4
   FLAGS                  0

tfactl ips SHOW FILES

Use the tfactl ips SHOW FILES command to view the files included in a specific package.

Syntax

tfactl ips SHOW FILES PACKAGE package_id

Example tfactl ips SHOW FILES

$ tfactl ips show files package 12

tfactl ips SHOW INCIDENTS

Use the tfactl ips SHOW INCIDENTS command to view the incidents included in a specific package.

Syntax

tfactl ips SHOW INCIDENTS PACKAGE package_id

Example tfactl ips SHOW INCIDENTS

$ tfactl ips show incidents package 12

tfactl ips SHOW PROBLEMS

Use the tfactl ips SHOW PROBLEMS command to view the problems for the current Automatic Diagnostic Repository home.

Syntax

tfactl ips SHOW PROBLEMS

Example tfactl ips SHOW PROBLEMS

tfactl ips show problems

Multiple ADR basepaths were found, please select one ...

( ) option[0] /scratch/app/oradb
( ) option[1] /scratch/app/oragrid

Pls select an ADR basepath [0..1] ?0
/scratch/app/oradb was selected

ADR Home = /scratch/app/oradb/diag/rdbms/racone/racone_2:
*************************************************************************
0 rows fetched

ADR Home = /scratch/app/oradb/diag/rdbms/rdb11204/rdb112041:
*************************************************************************
PROBLEM_ID           PROBLEM_KEY                                                 LAST_INCIDENT        LASTINC_TIME
-------------------- ----------------------------------------------------------- -------------------- ----------------------------------------
2                    ORA 700 [kgerev1]                                           42605                2016-07-05 07:53:28.578000 -07:00
1                    ORA 600                                                     42606                2016-07-05 07:53:30.427000 -07:00

ADR Home = /scratch/app/oradb/diag/rdbms/ogg11204/ogg112041:
*************************************************************************
PROBLEM_ID           PROBLEM_KEY                                                 LAST_INCIDENT        LASTINC_TIME
-------------------- ----------------------------------------------------------- -------------------- ----------------------------------------
3                    ORA 4030                                                    51504                2017-09-26 10:03:03.922000 -07:00
2                    ORA 700 [kgerev1]                                           54401                2017-09-26 10:03:10.371000 -07:00
1                    ORA 600                                                     54402                2017-09-26 10:03:11.446000 -07:00
6                    ORA 600 [gc_test_error]                                     54691                2017-10-23 03:03:40.599000 -07:00
5                    ORA 4031                                                    64277                2017-12-13 04:48:16.035000 -08:00
4                    ORA 7445                                                    96286                2018-05-29 08:26:11.326000 -07:00

ADR Home = /scratch/app/oradb/diag/rdbms/apxcmupg/apxcmupg_1:
*************************************************************************
0 rows fetched

ADR Home = /scratch/app/oradb/diag/rdbms/apxcmupg/apxcmupg_2:
*************************************************************************
0 rows fetched

tfactl ips SHOW PACKAGE

Use the tfactl ips SHOW PACKAGE command to view the details of a specific package.

Syntax

tfactl ips SHOW PACKAGE package_id [BASIC | BRIEF | DETAIL]

Note:

It is possible to specify the level of detail to use with this command.

BASIC : Shows a minimal amount of information. It is the default when no package ID is specified.

BRIEF : Shows a more extensive amount of information. It is the default when a package ID is specified.

DETAIL : Shows the same information as BRIEF, and also some package history and information on included incidents and files.

Example tfactl ips SHOW PACKAGE

$ tfactl ips show package

Multiple ADR basepaths were found, please select one ...

( ) option[0] /scratch/app/oradb
( ) option[1] /scratch/app/oragrid

Pls select an ADR basepath [0..1] ?0
/scratch/app/oradb was selected

Multiple ADR homepaths were found for /scratch/app/oradb, please select one ...

( ) option[0] diag/rdbms/racone/racone_2
( ) option[1] diag/rdbms/rdb11204/rdb112041
( ) option[2] diag/rdbms/ogg11204/ogg112041
( ) option[3] diag/rdbms/apxcmupg/apxcmupg_1
( ) option[4] diag/rdbms/apxcmupg/apxcmupg_2
    option[5] Done

Pls select a homepath [5] ?1
diag/rdbms/rdb11204/rdb112041 was selected

   PACKAGE_ID             1
   PACKAGE_NAME           IPSPKG_20160731165615
   PACKAGE_DESCRIPTION
   DRIVING_PROBLEM        N/A
   DRIVING_PROBLEM_KEY    N/A
   DRIVING_INCIDENT       N/A
   DRIVING_INCIDENT_TIME  N/A
   STATUS                 Generated (4)
   CORRELATION_LEVEL      Typical (2)
   PROBLEMS               0 main problems, 0 correlated problems
   INCIDENTS              0 main incidents, 0 correlated incidents
   INCLUDED_FILES         27

   PACKAGE_ID             2
   PACKAGE_NAME           IPSPKG_20160731170111
   PACKAGE_DESCRIPTION
   DRIVING_PROBLEM        N/A
   DRIVING_PROBLEM_KEY    N/A
   DRIVING_INCIDENT       N/A
   DRIVING_INCIDENT_TIME  N/A
   STATUS                 Generated (4)
   CORRELATION_LEVEL      Typical (2)
   PROBLEMS               0 main problems, 0 correlated problems
   INCIDENTS              0 main incidents, 0 correlated incidents
   INCLUDED_FILES         27

   PACKAGE_ID             3
   PACKAGE_NAME           ORA700kge_20160731211334
   PACKAGE_DESCRIPTION
   DRIVING_PROBLEM        2
   DRIVING_PROBLEM_KEY    ORA 700 [kgerev1]
   DRIVING_INCIDENT       42605
   DRIVING_INCIDENT_TIME  N/A
   STATUS                 Generated (4)
   CORRELATION_LEVEL      Typical (2)
   PROBLEMS               2 main problems, 0 correlated problems
   INCIDENTS              2 main incidents, 0 correlated incidents
   INCLUDED_FILES         84

   PACKAGE_ID             4
   PACKAGE_NAME           IPSPKG_20160801203518
   PACKAGE_DESCRIPTION
   DRIVING_PROBLEM        N/A
   DRIVING_PROBLEM_KEY    N/A
   DRIVING_INCIDENT       N/A
   DRIVING_INCIDENT_TIME  N/A
   STATUS                 Generated (4)
   CORRELATION_LEVEL      Typical (2)
   PROBLEMS               0 main problems, 0 correlated problems
   INCIDENTS              0 main incidents, 0 correlated incidents
   INCLUDED_FILES         27

$ tfactl ips show package 4 detail

Multiple ADR basepaths were found, please select one ...

( ) option[0] /scratch/app/oradb
( ) option[1] /scratch/app/oragrid

Pls select an ADR basepath [0..1] ?0
/scratch/app/oradb was selected

Multiple ADR homepaths were found for /scratch/app/oradb, please select one ...

( ) option[0] diag/rdbms/racone/racone_2
( ) option[1] diag/rdbms/rdb11204/rdb112041
( ) option[2] diag/rdbms/ogg11204/ogg112041
( ) option[3] diag/rdbms/apxcmupg/apxcmupg_1
( ) option[4] diag/rdbms/apxcmupg/apxcmupg_2
    option[5] Done

Pls select a homepath [5] ?1
diag/rdbms/rdb11204/rdb112041 was selected

DETAILS FOR PACKAGE 4:
   PACKAGE_ID             4
   PACKAGE_NAME           IPSPKG_20160801203518
   PACKAGE_DESCRIPTION
   DRIVING_PROBLEM        N/A
   DRIVING_PROBLEM_KEY    N/A
   DRIVING_INCIDENT       N/A
   DRIVING_INCIDENT_TIME  N/A
   STATUS                 Generated (4)
   CORRELATION_LEVEL      Typical (2)
   PROBLEMS               0 main problems, 0 correlated problems
   INCIDENTS              0 main incidents, 0 correlated incidents
   INCLUDED_FILES         27
   SEQUENCES              Last 1, last full 1, last base 0
   UNPACKED               FALSE
   CREATE_TIME            2016-08-01 20:35:18.684231 -07:00
   UPDATE_TIME            N/A
   BEGIN_TIME             2016-08-01 13:59:04.000000 -07:00
   END_TIME               2016-08-01 20:34:50.000000 -07:00
   FLAGS                  0

HISTORY FOR PACKAGE 4:
   SEQUENCE               1
   BASE_SEQUENCE          1
   MODE                   Complete (0)
   STATUS                 Generated (4)
   FILENAME               /scratch/app/oragrid/tfa/repository/suptools/srdc/user_oradb/IPSPKG_20160801203518_COM_1.zip
   ARCHIVE_TIME           2016-08-01 20:35:21.899095 -07:00
   UPLOAD_TIME            N/A
   UNPACK_TIME            N/A
   FORCE                  FALSE
   GENERATE_FLAGS         0
   UNPACK_FLAGS           0

MAIN INCIDENTS FOR PACKAGE 4:
CORRELATED INCIDENTS FOR PACKAGE 4:

FILES FOR PACKAGE 4:
   FILE_ID                1
   FILE_LOCATION          /trace
   FILE_NAME              alert_rdb112041.log
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2087
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_CONFIGURATION.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2088
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_PACKAGE.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2089
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_PACKAGE_INCIDENT.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2090
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_PACKAGE_FILE.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2091
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_PACKAGE_HISTORY.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2092
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_FILE_METADATA.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2093
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              IPS_FILE_COPY_LOG.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2094
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              DDE_USER_ACTION_DEF.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2095
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              DDE_USER_ACTION_PARAMETER_DEF.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2096
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              DDE_USER_ACTION.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2097
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              DDE_USER_ACTION_PARAMETER.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2098
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              DDE_USER_INCIDENT_TYPE.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2099
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              DDE_USER_INCIDENT_ACTION_MAP.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2100
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              INCIDENT.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2101
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              INCCKEY.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2102
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              INCIDENT_FILE.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2103
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              PROBLEM.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2104
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              HM_RUN.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2105
   FILE_LOCATION          /incpkg/pkg_4/seq_1/export
   FILE_NAME              EM_USER_ACTIVITY.dmp
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2106
   FILE_LOCATION          /incpkg/pkg_4/seq_1
   FILE_NAME              config.xml
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2107
   FILE_LOCATION          /incpkg/pkg_4/seq_1/opatch
   FILE_NAME              opatch.log
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2108
   FILE_LOCATION          /incpkg/pkg_4/seq_1/opatch
   FILE_NAME              opatch.xml
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2109
   FILE_LOCATION          /incpkg/pkg_4/seq_1
   FILE_NAME              metadata.xml
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2110
   FILE_LOCATION          /incpkg/pkg_4/seq_1
   FILE_NAME              manifest_4_1.xml
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2111
   FILE_LOCATION          /incpkg/pkg_4/seq_1
   FILE_NAME              manifest_4_1.html
   LAST_SEQUENCE          1
   EXCLUDE                Included

   FILE_ID                2112
   FILE_LOCATION          /incpkg/pkg_4/seq_1
   FILE_NAME              manifest_4_1.txt
   LAST_SEQUENCE          1
   EXCLUDE                Included

tfactl ips UNPACK FILE

Use the tfactl ips UNPACK FILE command to unpack a physical file into a specific path.

Syntax

Running the following command automatically creates a valid ADR_HOME structure. The path must exist and be writable.

tfactl ips UNPACK FILE file_spec [INTO path]

Parameters

tfactl ips UNPACK FILE Command Parameters

Parameter	Description
`file_spec`	Specify the file with file name and full path.
`path`	Specify the path where the physical package file should be unpacked.

Example 9-120 tfactl ips UNPACK FILE

$ tfactl ips unpack file /tmp/IPSPKG_20061026010203_COM_1.zip into /tmp/newadr

tfactl ips UNPACK PACKAGE

Use the tfactl ips UNPACK PACKAGE command to unpack physical files in the current directory into a specific path, if they match the package name.

Syntax

Running the following command automatically creates a valid ADR_HOME structure. The path must exist and be writable.

tfactl ips UNPACK PACKAGE pkg_name [INTO path]

Parameters

tfactl ips UNPACK PACKAGE Command Parameters

Parameter	Description
`pkg_name`	Specify the name of the package.
`path`	Specify the path where the physical package files should be unpacked.

Example tfactl ips UNPACK PACKAGE

$ tfactl ips unpack package IPSPKG_20061026010203 into /tmp/newadr

tfactl ips USE REMOTE KEYS

Use the tfactl ips USE REMOTE KEYS command to add incidents matching the keys in a specific file to a specific package.

Syntax

tfactl ips USE REMOTE KEYS FILE file_spec PACKAGE package_id

Parameters

tfactl ips USE REMOTE KEYS Command Parameters

Parameter	Description
`file_spec`	Specify the file with file name and full path.
`package_id`	Specify the ID of the package to add the incidents to.

Example tfactl ips USE REMOTE KEYS

$ tfactl ips use remote keys file /tmp/key_file.txt package 12