oradebug
In Oracle database version 9i there is no way to determine the IP address through a database view. The only way to determine this IP address is with the oradebug command (Please keep in mind oradebug is not a supported product from Oracle, so if there are problems/crashes you are on your own). The oradebug ipc command creates a trace file. The example shows the process:
SQL> oradebug setmypid
SQL> oradebug ipc
SQL> oradebug tracefile_name
The last command will show the name of the created trace file. The next step is opening the trace file and looking for the string SKGXPCTX. The following is a typical example.
SKGXPCTX: 0xcd1e730 ctx
admno 0x7a0be402 admport:
SSKGXPT 0xcd1e884 flags SSKGXPT_READPENDING info for network 0
socket no 8 IP 140.87.79.67 UDP 9152
sflags SSKGXPT_WRITESSKGXPT_UP
info for network 1
The cluster interconnect IP address is shown in bold. In the example above
it is 140.87.79.67.
Friday, April 27, 2012
Modify the attribute AUTO_START to “always”
With Oracle 11.2 database auto start
policy in the clusterware is restore, which means that clusterware will
remember the last state of the database. If the database was stopped
normally then on the next restart of clusterware it won’t be started. Otherwise
if the server crashes or by some reason the OS is rebooted then clusterware
will start the database because last state was ONLINE (running).
Monday, April 23, 2012
hibernate.jdbc.fetch_size and hibernate.jdbc.batch_size
Two important settings for hibernate java application, affecting hibernate CRUD performance.
C = create, R = read, U = update, D = delete
Fetch Size determines when JDBC Statement read data, how many records are going to be read per fetch.
Recommend setting for Oralce JDBC application:
hibernate.jdbc.fetch_size 100
hibernate.jdbc.batch_size 25
Two important settings for hibernate java application, affecting hibernate CRUD performance.
C = create, R = read, U = update, D = delete
Fetch Size determines when JDBC Statement read data, how many records are going to be read per fetch.
Recommend setting for Oralce JDBC application:
hibernate.jdbc.fetch_size 100
hibernate.jdbc.batch_size 25
Friday, April 20, 2012
Disable Microsoft Office Upload Center
For starters, if you don't want it, don't run Microsoft SharePoint Workspace 2010 (what used to be called Groove). Workspace also loads the Upload Center, even if you simply start it, then cancel before doing anything. It also sets some values in the Windows registry that cause Upload Center to load again every time you restart Windows.
For starters, if you don't want it, don't run Microsoft SharePoint Workspace 2010 (what used to be called Groove). Workspace also loads the Upload Center, even if you simply start it, then cancel before doing anything. It also sets some values in the Windows registry that cause Upload Center to load again every time you restart Windows.
Thursday, April 19, 2012
Windows DBConsole internal stop. No OC4J admin passwd hence
hard stop
Enterprise manager cannot be started. The status shows
dbconsole is already started:
C:\>emctl status dbconsole
Oracle
Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright
(c) 1996, 2010 Oracle Corporation. All
rights reserved.
https://JDEORA01:5500/em/console/aboutApplication
Oracle
Enterprise Manager 11g is running.
------------------------------------------------------------------
Logs
are generated in directory
C:\APP\ORACLE\product\11.2.0\se1/jdeora01_e1prod/sysman/log
Install EM grid 11.1.0.1.0 on Linux
- Software
Downloads the following software:
opatch - Latest version (26M)
(There’s a known issue with installing Enterprise Grid Control on Weblogic 10.3.3)
Subscribe to:
Posts (Atom)