Updates the Call‑Home settings.
call_home ‑modify [{‑enableEventTrigger |‑disableEventTrigger}] [{‑enableLargeFile | ‑disableLargeFile}] [{‑enableStandardPeriodic | ‑disableStandardPeriodic}] [{‑enableLargerPeriodic | ‑disableLargerPeriodic}] [‑numberOfEvents number‑of‑events‑to‑include] [{ ‑callHomeDestination https‑server_ip_or_dns [{‑proxy ‑proxyIp proxy_ip ‑proxyPort proxy_port ‑proxyConnection {http | socks4 | socks5} | ‑noProxy}] | ‑localDestination local_server_ip_or_dns ‑directory local_directory ‑userName user_name }] [ ‑schedulePeriodic {standard | large} ‑interval { daily | weekly | monthly} ‑frequency interval_frequency ‑startTime date‑time ] [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}] [{‑outputformat | ‑o} { text | xml }] [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]
Use the call_home ‑modify command to configure or update the Call‑Home options. You can use the command to add a proxy server that resolves the name of the destination Oracle server.
You can enable or disable the Call‑Home feature that are triggered by system events. Some options disable the Auto Service Request (ASR) feature. If you disable ASR configure the ‑localDestination Call‑Home server and implement some other means to monitor the Oracle FS System.
Specifies that the Call‑Home data is to be sent to the Oracle server. The data must be sent using the HTTPS protocol.
‑proxyIp
‑proxyPort
‑proxyConnection
If you omit the ‑proxy option, or if you specify the ‑noProxy option, no proxy server is used.
Identifies the full directory path on the local Call‑Home server in which to store the Call‑Home log bundles.
Disables the Call‑Home feature for system events. This feature, when enabled, disables ASR functionality.
Specifies that Call‑Home log bundles only include the header information, resulting in smaller file size. Selecting this option disables the system from sending any event or manual logs to the Oracle server.
If ‑disableLargeFile is enabled and a system event occurs, you will need to manually download the logs and upload them to My Oracle Support (MOS).
When the ‑disableLargeFile option and the ‑disableLargerPeriodic option are used together, the effect is the same as using the ‑enableStandardPeriodic option.
Disables the periodic transmission of a larger amount of Call‑Home data to the designated destination server.
Disables the periodic sending of the Call‑Home header data to the designated destination server.
Enables the Call‑Home feature to send status messages for selected system events to the designated server. Enable ‑enableEventTrigger option to support the ASR feature.
You can also designate a local server by using the ‑localDestination option. Using a local Call‑Home server disables all ASR functionality.
Enables the transmission of diagnostic logs to the designated server.
During a system event, if this option is not enabled, the system does not send debug or other diagnostic logs to the Oracle server. Instead, you would need to manually send the diagnostic logs to a specific service request (SR) on My Oracle Support (MOS).
Enables the periodic transmission of a larger amount of Call‑Home data to the designated destination server.
If the transmission of larger Call‑Home files is disabled by specifying the ‑disableLargeFile option, enabling the periodic transmission of larger amounts of data has the same effect as enabling standard periodic transfers by means of the ‑enableStandardPeriodic option.
Define the time interval and the frequency for this data transmission by specifying the ‑schedulePeriodic large option.
‑interval weekly
‑frequency 1
Enables the periodic transmission of the Call‑Home data to the designated destination server.
Define the time interval and the frequency for this data transmission by specifying the ‑schedulePeriodic standard option.
‑interval daily
‑frequency 1
Defines the number of time units as specified by the ‑interval option between the time when one task is run and the time when the next task is run. The value must be a positive integer.
Specifies that the interval is in days.
Specifies that the interval is in weeks.
Specifies that the interval is in months.
Specifies the IP address or DNS address of the local server where the Call‑Home logs should be sent.
Using a local server disables all Auto Service Request (ASR) functionality, which means that Oracle Customer Support is not notified of any system events.
Specifies that Call‑Home does not use a proxy server.
Specifies that Call‑Home uses a proxy server to provide the connection to the Oracle server.
‑proxyIp
‑proxyPort
‑proxyConnection
Identifies the routing protocol to use.
http
socks4
socks5
Identifies the IP address of the proxy server.
Identifies the TCP port on the proxy server to use.
Specifies that the system sends standard sized log bundles to the designated server.
‑interval daily
‑frequency 1
Specifies that the system sends large sized log bundles to the designated server.
‑interval weekly
‑frequency 1
Defines the time and the date of when the task is to begin.
YYYY-MM-DD[THH[:mm[:SS[.xxx]]]][+|-HH:mm]
where:
Designates a 4‑digit year, a 2‑digit month, and a 2‑digit day. If the remaining values are omitted, the time is set to 12:00:00.000+00:00.
A separator that designates the start of the time portion of the string.
Designates the hours, the minutes, and the seconds (to three decimals) in terms of a 24-hour clock. If only HH is defined, the remaining values default to 00.
Designates the time zone as an offset from Coordinated Universal Time (UTC) in hours and minutes.
Specifies the user log in name to the ‑localDestination server.
Change the Call‑Home settings for the Oracle FS System.
The size of the periodic log bundles: standard
The interval at which to send the log bundles: weekly
The frequency at which to send the log bundles: 2
The start time at which to begin the process of sending the log bundles: 2014-08-01
$ fscli call_home -modify ‑schedulePeriodic standard ‑interval weekly -frequency 2 ‑startTime 2014‑08‑01