分类
外汇操盘交易心得

客户选择 OCI 的原因

  • Open with Desktop
  • View raw
  • Copy 客户选择 OCI 的原因 raw contents Copy raw contents

Determine the Reason for Pod Failure

This page shows how to write and read a Container termination message.

Termination messages provide a way for containers to write information about fatal events to a location where it can be easily retrieved and surfaced by tools like dashboards and monitoring software. In most cases, information that you put in a termination message should also be written to the general Kubernetes logs.

Before you begin

You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

Writing and reading a termination message

In this exercise, you create a Pod that runs one container. The configuration file specifies a command that runs when the container starts.

Create a Pod based on the YAML configuration file:

In the YAML file, in the command and args fields, you can see that the container sleeps for 10 seconds and then writes "Sleep expired" to the /dev/termination-log file. After the container writes the "Sleep expired" message, it terminates.客户选择 OCI 的原因

Display information about the Pod:

Repeat the preceding command 客户选择 OCI 的原因 until the Pod is no longer running.

Display detailed information about the Pod:

The output includes the "Sleep expired" message:

Use a Go template to filter the output so that it includes only the termination message:

If you are running a multi-container pod, you can use a Go template to include the container's name. By doing so, you can discover which of the containers is failing:

Customizing the termination message

Kubernetes retrieves termination messages from the termination message file specified in the terminationMessagePath field of a Container, 客户选择 OCI 的原因 which has a default value of /dev/termination-log . By customizing this field, you can tell Kubernetes to use a different file. Kubernetes use the contents from the specified file to populate the Container's status message on both success and failure.

The termination message is intended to be brief final status, such as an assertion failure message. The kubelet truncates messages that are longer than 4096 bytes.

The total message length across all containers is limited to 12KiB, divided equally among each container. For example, if there are 12 containers ( initContainers or containers ), each has 1024 bytes of available termination message space.

The default termination message path is /dev/termination-log . You cannot set the termination message path after a Pod is launched

In the following example, the container writes termination messages to /tmp/my-log for Kubernetes to retrieve:

Moreover, users can set the terminationMessagePolicy field of a Container for further customization. This field defaults to " File " which means the termination messages are retrieved only from the termination message file. By setting the terminationMessagePolicy to " FallbackToLogsOnError ", you can tell Kubernetes to use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log 客户选择 OCI 的原因 output is limited to 2048 bytes or 80 lines, whichever is smaller.

What's next

  • See the terminationMessagePath field in Container.
  • Learn about retrieving logs.客户选择 OCI 的原因
  • Learn about Go templates.

Feedback

Was this page helpful?

Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

关于oci的介绍

luckninjya 于 2014-06-25 12:50:45 发布 853 收藏

当应用程序开发人员需要面向 Oracle 数据库服务器的最强大的接口时,他们将调用 Oracle 调用接口 (OCI)。OCI 提供了
对所有 Oracle 数据库功能的最全面的访问。OCI API 中包含了最新的性能、可伸缩性和安全性特性。


使用 OCI 客户群非常庞大,包括:

开发复杂数据库应用程序的财富 500 强中的大客户。
调整 Oracle 数据库以适应它们的需求的 ISV


如果编写 Oracle 数据库应用程序,则很可能要依靠 OCI。依赖 OCI 的某些类型的应用程序包括:

执行 SQL 的 PL/SQL 应用程序
使用 OCCI 的 C++ 应用程序
使用基于 OCI 的 JDBC 驱动程序的 Java 应用程序
使用 ODBC 驱动程序的 C 应用程序
使用 OLEDB 驱动程序的 VB 应用程序
Pro*C 应用程序
分布式 SQL

Oracle 10g 中的 OCI 新特性包括:

即时客户端
IEEE 754 浮点数支持 (binary_float/binary_double) 客户选择 OCI 的原因
无限大小的 LOB 支持

Instant Client 使 ISV 和客户能够快速安装和部署 Oracle 应用程序,而不会遇到任何麻烦。请访问 Instant Client 站点了解更多信息。

开发人员应当采用的 Oracle 9i 中的某些更重要的可伸缩性和性能特性包括:

连接池
会话池
语句高速缓存
可滚动游标

最新 Oracle 数据库服务器特性中的即时可用性
企业级的性能和可伸缩性
强健的安全模型
在所有运行 Oracle 的平台上的可移植性

要使一个客户端机器能连接oracle数据库,需要在客户端机器上安装oracle的客户端软件,唯一的例外
就是java连接数据库的时候,可以用jdbc thin模式,不用装oracle的客户端软件。假如你在机器上装了
oracle数据库,就不需要在单独在该机器上安装oracle客户端了,因为装oracle数据库的时候会自动安
装oracle客户端。

用过sql server数据库然后又用oracle的朋友可能会有这样的疑问:问什么我用sql server的时候不用装
sql server的客户端呢?原因很简单,sql server也是microsoft的,它在操作系统中集成了sql server客户端

客户选择 OCI 的原因

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

  • Open with Desktop
  • View raw
  • Copy raw contents Copy raw contents

Copy raw contents

Copy raw contents

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more 客户选择 OCI 的原因 about bidirectional Unicode characters

  • Copy lines
  • Copy permalink

Footer

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

ORA-12541: TNS: 无监听程序 的解决办法

小楼™ 又东风 于 2019-08-09 09:51:27 发布 31821 收藏 59

今天好好的,突然有用户报系统登录不了了,经过排查问题出在Oracle,报ORA-12541: TNS: 无监听程序,先是重新服务不行,然后重新配置监听还不行,最后上网查了一下,结果是是它的问题哈,就是下面我所说的解决方法1。下面根据我在网上的参考分别列出无监听程序问题平日最可能涉及到的三种情况及解决方法:

1、 首先查看监听文件是否超过4G,删除它,然后重启监听服务。

2、 找到 Oracle 监听配置文件(listener.ora)和TNS配置文件(tnsnames.ora),

我的安装路径为 " D:\oracle\product\11.2.0\dbhome_1\NETWORK\ADMIN " ,如下图:

将两个文件中的 HOST=192.168.78.138(当然这个是我的地址),全改为 " HOST=localhost " 。

以上两个配置文件修改完成后,Ctrl + R 在弹出框中输入 " SERVICES.MSC " ,找到Oracle的服务(OracleService)和 Oralce 监听服务 (OracleOraDb10g_homeTNLListener)

3、 重新配置监听,从开始菜单中打开“Oracle Net Configuration Assistance”,选择“监听程序配置”,如下图所示,点击下一步。