Subject: "GRANT SELECT ANY DICTIONARY" Privilege Required When Connecting from 9i OEM console to 10
Doc ID: 340951.1Type: PROBLEM Modified Date : 06-MAY-2007Status: MODERATEDIn this Document Symptoms Changes Cause Solution ReferencesThis document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.Applies to: Oracle Enterprise Manager - Version: 10.1.0.2This problem can occur on any platform.SymptomsTrying to connect a 10G database via 9i OEM standalone console.- Try connect with 'SYSTEM' user
开启基于java的oracle工具的tracing
10.2:Enabling Tracing for Java-Based Tools and Utilities in Oracle Real Application ClustersAll Java-based tools and utilities that are available in Oracle RAC are invoked by executing scripts of the same name as the tool or utility. This includes the Cluster Verification Utility (CVU), Database Configuration Assistant (DBCA), the Net Configuration Assistant (NETCA), the Virtual Internet Protocol Configuration Assistant (VIPCA), Server Control (SRVCTL), and the Global Services Daemon (GSD). For
Enabling Tracing for Java-Based Tools and Utilities in Oracle Real Application Clusters
in oracle database 10.2,by default, Oracle enables traces for DBCA and the Database Upgrade Assistant (DBUA). For the CVU, GSDCTL, SRVCTL, and VIPCA, you can set the SRVM_TRACE environment variable to TRUE to make Oracle generate traces.[@more@]
ORA-12519 错误解决
客户端连接间歇性失败,报错ORA-12519OERR: ORA-12519 TNS:no appropriate service handler found[@more@]Error: ORA-12519 / TNS-12519Text: TNS:no appropriate service handler found ---------------------------------------------------------------------------Cause: the listener could not find any available service handlers that are appropriate for the client connection. Action: run "lsnrctl services" to ensure that the instance(s) have registered with the listener, and are accepting connections.
ORACLE RAC 用于INTERCONNECT 的内网卡的物理连接方式的利弊
ORACLE RAC 用于INTERCONNECT 的内网卡的物理连接方式的选择:采用交换机连接或是网线直连。itpub讨论中谈到直连的弊端,一旦一个节点机的内网卡出现故障,oracle从OS得到两个节点的网卡状态都是不正常的,因而会导致两个实例都宕掉。下面是讨论过程:[@more@]biti说:从理论上来推测 这里面要注意区分 使用switch 和 直连 的情况:如果使用交换机,拔掉a的,b 会知道自己是活的,a 知道自己出问题了。那么b能提供服务,a将不能提供服务,应该选择down掉是合理的选择。如果是直连,可能出现 brain split,两个节点都不能正常提供服务。但k