OID reference

serverTransactionLogFileWritePolicy

1.3.6.1.4.1.140.625.730.1.330

Description

The policy that determines how transaction log file entries are written to disk. This policy can affect transaction performance. (Note: To be transactionally safe, the Direct-Write policy may require additional OS or environment changes on some Windows systems.) WebLogic Server supports the following policies: Cache-F…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.140.625.730.1 (serverEntry)
Node code
330
Node name
serverTransactionLogFileWritePolicy
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.140.625.730.1.330
URN notation
urn:oid:1.3.6.1.4.1.140.625.730.1.330
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 140 625 730 1 330}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bea(140) wls(625) serverTable(730) serverEntry(1) serverTransactionLogFileWritePolicy(330)}
OID-IRI notation
  • /1/3/6/1/4/1/140/625/730/1/330
  • /ISO/Identified-Organization/6/1/4/1/140/625/730/1/330
  • /ISO/3/6/1/4/1/140/625/730/1/330
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/identified-organization/dod/internet/private/enterprises/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/identified-organization/dod/internet/private/vendor-objects/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/org/dod/internet/private/enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/org/dod/internet/private/enterprises/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/org/dod/internet/private/ldap-enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/org/dod/internet/private/vendor-objects/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-identified-organization/dod/internet/private/enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-identified-organization/dod/internet/private/enterprises/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-organization/dod/internet/private/enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-organization/dod/internet/private/enterprises/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy
  • /iso/iso-organization/dod/internet/private/vendor-objects/bea/wls/serverTable/serverEntry/serverTransactionLogFileWritePolicy

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-only
Status in MIB
current

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: serverIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.140.625.730.1.330

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

The policy that determines how transaction log file entries are written to disk. This policy can affect transaction performance. (Note: To be transactionally safe, the Direct-Write policy may require additional OS or environment changes on some Windows systems.) WebLogic Server supports the following policies: Cache-Flush. Flushes operating system and on-disk caches after each write. Direct-Write. Tells the operating system to write directly to disk with each write. Direct-Write performs better than Cache-Flush and is available on Windows, HP-UX, and Solaris. If Direct-Write is not supported on the host platform, the policy becomes Cache-Flush and a log message is printed. Note: On Windows, unlike Solaris and HP, the 'Direct-Write' policy may leave transaction data in the on-disk cache without writing it to disk immediately. This is not transactionally safe because a power failure can cause loss of on-disk cache data. For transactionally safe writes using 'Direct-Write' on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache. The on-disk cache for a hard-drive on Windows can be disabled through system administration: Control-Panel -> System -> Hardware-tab -> Device-Manager-button -> Disk-Drives -> name-of-drive -> Policies-tab -> 'Enable write caching on the disk' check-box. Some file systems do not allow this value to be changed. For example, a RAID system that has a reliable cache.
Sources for this description

Circitor

Parsed from BEA-WEBLOGIC-MIB.mib · BEA-WEBLOGIC-MIB

Source file: Download BEA-WEBLOGIC-MIB.asn1 · Publisher's file

Related source files and packages:

Source file: Download BEA-WEBLOGIC-MIB.mib

Browse all files from Circitor

Description 2

The policy that determines how transaction log file entries are written to disk. This policy can affect transaction performance. (Note: To be transactionally safe, the Direct-Write policy may require additional OS or environment changes on some Windows systems.) WebLogic Server supports the following policies: Cache-Flush. Flushes operating system and on-disk caches after each write. Direct-Write. Tells the operating system to write directly to disk with each write. Direct-Write performs better than Cache-Flush and is available on Windows, HP-UX, and Solaris. If Direct-Write is not supported on the host platform, the policy becomes Cache-Flush and a log message is printed. Note: On Windows, unlike Solaris and HP, the 'Direct-Write' policy may leave transaction data in the on-disk cache without writing it to disk immediately. This is not transactionally safe because a power failure can cause loss of on-disk cache data. For transactionally safe writes using 'Direct-Write' on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache. The on-disk cache for a hard-drive on Windows can be disabled through system administration: Control-Panel -> System -> Hardware-tab -> Device-Manager-button -> Disk-Drives -> name-of-drive -> Policies-tab -> 'Enable write caching on the disk' check-box. Some file systems do not allow this value to be changed. For example, a RAID system that has a reliable cache.
Sources for this description

MIBdepot

Source file: Download BEA-WEBLOGIC-MIB.mib.txt

Related source files and packages:

Source data warning: The published IMPORTS clause omits the import of enterprises. A SHA-reviewed lookup uses an independent archived module with an explicit RFC1155-SMI import, original RFC 1155 namespace definitions and the official IANA PEN 140 registration. Published names, imports and definitions are preserved; all supporting originals are available below.

Browse all files from MIBdepot

Historical records

Additional source information

Information from OID Repository
Vendor: Independence Technologies, Inc.(ITI)
Module: BEA-WEBLOGIC-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot 
serverTransactionLogFileWritePolicy OBJECT-TYPE
      SYNTAX      OCTET STRING
      MAX-ACCESS  read-only
      STATUS      current
      DESCRIPTION "The policy that determines how transaction log file entries are written to disk. This policy can affect transaction performance. (Note: To be transactionally safe, the Direct-Write policy may require additional OS or environment changes on some Windows systems.)  WebLogic Server supports the following policies:    Cache-Flush. Flushes operating system and on-disk caches after each write.    Direct-Write. Tells the operating system to write directly to disk with each write. Direct-Write performs better than Cache-Flush and is available on Windows, HP-UX, and Solaris.    If Direct-Write is not supported on the host platform, the policy becomes Cache-Flush and a log message is printed.  Note: On Windows, unlike Solaris and HP, the 'Direct-Write' policy may leave transaction data in the on-disk cache without writing it to disk immediately. This is not transactionally safe because a power failure can cause loss of on-disk cache data. For transactionally safe writes using 'Direct-Write' on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache.  The on-disk cache for a hard-drive on Windows can be disabled through system administration: Control-Panel -> System -> Hardware-tab -> Device-Manager-button -> Disk-Drives -> name-of-drive -> Policies-tab -> 'Enable write caching on the disk' check-box. Some file systems do not allow this value to be changed. For example, a RAID system that has a reliable cache."
      ::= { serverEntry 330  }
Information from Circitor 
serverTransactionLogFileWritePolicy OBJECT-TYPE
      SYNTAX      OCTET STRING
      MAX-ACCESS  read-only
      STATUS      current
      DESCRIPTION "The policy that determines how transaction log file entries are written to disk. This policy can affect transaction performance. (Note: To be transactionally safe, the Direct-Write policy may require additional OS or environment changes on some Windows systems.)  WebLogic Server supports the following policies:    Cache-Flush. Flushes operating system and on-disk caches after each write.    Direct-Write. Tells the operating system to write directly to disk with each write. Direct-Write performs better than Cache-Flush and is available on Windows, HP-UX, and Solaris.    If Direct-Write is not supported on the host platform, the policy becomes Cache-Flush and a log message is printed.  Note: On Windows, unlike Solaris and HP, the 'Direct-Write' policy may leave transaction data in the on-disk cache without writing it to disk immediately. This is not transactionally safe because a power failure can cause loss of on-disk cache data. For transactionally safe writes using 'Direct-Write' on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache.  The on-disk cache for a hard-drive on Windows can be disabled through system administration: Control-Panel -> System -> Hardware-tab -> Device-Manager-button -> Disk-Drives -> name-of-drive -> Policies-tab -> 'Enable write caching on the disk' check-box. Some file systems do not allow this value to be changed. For example, a RAID system that has a reliable cache."
      ::= { serverEntry 330  }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.140)

Berthet Gerard

Siblings (135)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.140.625.730.1.329 serverLowMemoryTimeInterval00 The amount of time (in seconds) that defines the interval over which this server determines average free memory values. By def…
1.3.6.1.4.1.140.625.730.1.331 serverHttpTraceSupportEnabled00 Returns the HttpTraceSupportEnabled value
1.3.6.1.4.1.140.625.730.1.332 serverKeyStores00 Which configuration rules should be used for finding the server's identity and trust keystores?
1.3.6.1.4.1.140.625.730.1.333 serverAutoMigrationEnabled00 Specifies whether Node Manager can automatically restart this server and its services on another machine if the server fails.
1.3.6.1.4.1.140.625.730.1.334 serverPeriodLength00 The time interval in milliseconds of the heartbeat period. A value of 0 indicates that heartbeats are turned off.
1.3.6.1.4.1.140.625.730.1.335 serverStuckThreadTimerInterval00 The number of seconds after which WebLogic Server periodically scans threads to see if they have been continually working for t…
1.3.6.1.4.1.140.625.730.1.336 serverDGCIdlePeriodsUntilTimeout00 The number of idle periods allowed before object is collected.
1.3.6.1.4.1.140.625.730.1.337 serverMuxerClass00 The muxer class name.
1.3.6.1.4.1.140.625.730.1.338 serverHealthCheckIntervalSeconds00 The number of seconds that defines the frequency of this server's self-health monitoring. The server monitors the health of it'…
1.3.6.1.4.1.140.625.730.1.339 serverRestartIntervalSeconds00 The number of seconds during which this server can be restarted, up to the number of times specified in RestartMax.
1.3.6.1.4.1.140.625.730.1.340 serverIdlePeriodsUntilTimeout00 The number of idle periods until peer is considered unreachable
1.3.6.1.4.1.140.625.730.1.341 serverCustomTrustKeyStoreFileName00 The path and file name of the custom trust keystore. The path name must either be absolute or relative to where the server was…
1.3.6.1.4.1.140.625.730.1.342 serverHostsMigratableServices00 Gets the hostsMigratableServices attribute of the ServerMBean object
1.3.6.1.4.1.140.625.730.1.343 serverExternalDNSName00 The external IP address or DNS name for this server. This address will be sent with HTTP session cookies and with dynamic serv…
1.3.6.1.4.1.140.625.730.1.344 serverOutboundPrivateKeyEnabled00 Specifies whether the SSL identity specified by {@link SSLMBean#ServerPrivateKeyAlias SSLMBean#ServerPrivateKeyAlias} for this …
1.3.6.1.4.1.140.625.730.1.345 serverAdministrationProtocol00 Returns the protocol to be used for administrative connections when none is specified.
1.3.6.1.4.1.140.625.730.1.346 serverCustomIdentityKeyStoreType00 The type of the keystore. Generally, this is JKS. If empty or null, then the JDK's default keystore type (specified in java.se…
1.3.6.1.4.1.140.625.730.1.347 serverStartupMode00 The state in which this server should be started. If you specify STANDBY, you must also enable the domain-wide administration p…
1.3.6.1.4.1.140.625.730.1.348 serverNMSocketCreateTimeoutInMillis00 Returns the timeout value to be used by NodeManagerRuntime when creating a a socket connection to the agent.
1.3.6.1.4.1.140.625.730.1.349 serverListenDelaySecs00
1.3.6.1.4.1.140.625.730.1.350 serverIdleIIOPConnectionTimeout00
1.3.6.1.4.1.140.625.730.1.351 serverMaxCOMMessageSize00
1.3.6.1.4.1.140.625.730.1.352 serverMessagingBridgeThreadPoolSize00
1.3.6.1.4.1.140.625.730.1.353 serverServerVersion00
1.3.6.1.4.1.140.625.730.1.354 serverIIOPTxMechanism00
1.3.6.1.4.1.140.625.730.1.355 serverMSIFileReplicationEnabled00
1.3.6.1.4.1.140.625.730.1.356 serverJNDITransportableObjectFactoryList00
1.3.6.1.4.1.140.625.730.1.357 serverHealthCheckTimeoutSeconds00
1.3.6.1.4.1.140.625.730.1.358 serverStuckThreadMaxTime00
1.3.6.1.4.1.140.625.730.1.359 serverCompleteCOMMessageTimeout00
1.3.6.1.4.1.140.625.730.1.360 serverConnectTimeout00
1.3.6.1.4.1.140.625.730.1.361 serverGatheredWritesEnabled00
1.3.6.1.4.1.140.625.730.1.362 serverScatteredReadsEnabled00
1.3.6.1.4.1.140.625.730.1.363 serverVirtualMachineName00
1.3.6.1.4.1.140.625.730.1.364 serverUseFusionForLLR00