Search This Blog

Wednesday, June 22, 2011

Adding Source Code to a Blog

http://codeshode.blogspot.com/2010/06/format-my-source-code-for-blogging.html

Copy the following Code

  • Copy the following code and paste it into your Blogger Template just above the </head> tag

 

<link href='http://alexgorbatchev.com/pub/sh/current/styles/shCore.css' rel='stylesheet' type='text/css'/> 

<link href='http://alexgorbatchev.com/pub/sh/current/styles/shThemeDefault.css' rel='stylesheet' type='text/css'/> 

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shCore.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushCpp.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushCSharp.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushCss.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushJava.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushJScript.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushPhp.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushPython.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushRuby.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushSql.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushVb.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushXml.js' type='text/javascript'></script

<script src='http://alexgorbatchev.com/pub/sh/current/scripts/shBrushPerl.js' type='text/javascript'></script

<script language='javascript'

SyntaxHighlighter.config.bloggerMode = true;

SyntaxHighlighter.config.clipboardSwf = 'http://alexgorbatchev.com/pub/sh/current/scripts/clipboard.swf';

SyntaxHighlighter.all();

</script>

 

  • Save the template
  • Then you can start creating code blocks in your existing or new Blog entries.
  • There are 2 ways to add a code block using syntaxhighlighter

Add the following cdoe ,

<pre class="brush: java">
// Comment
public class Testing
{
public Testing() {
}
public void Method()
{
/* Another Comment
on multiple lines */
int x = 9;
}
}
</pre>

How to use AQ with WebLogic Server

Create the jmsuser user for accessing the AQ
sqlplus SYS/manager1@ORCL AS SYSDBA

grant connect,resource,aq_administrator_role to jmsuser identified by jmsuser;
grant select on sys.DBA_PENDING_TRANSACTIONS to jmsuser;
grant execute on sys.dbms_aqadm to jmsuser;
grant execute on sys.dbms_aq to jmsuser;
grant execute on sys.dbms_aqin to jmsuser;
grant execute on sys.dbms_aqjms to jmsuser;
exec dbms_aqadm.grant_system_privilege('ENQUEUE_ANY','jmsuser');
exec dbms_aqadm.grant_system_privilege('DEQUEUE_ANY','jmsuser');


package webserv1;

import java.util.Hashtable;

import javax.jms.Message;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueReceiver;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.Session;
import javax.jms.TextMessage;

import javax.naming.Context;
import javax.naming.InitialContext;

public class SendMsgQueue {
public SendMsgQueue() {
}

public static void main(String argv[]) throws Exception {

Hashtable env = new Hashtable();
// Standalone OC4J connection details
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "welcome1");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
// env.put(Context.PROVIDER_URL, "t3://ceiacb5.us.oracle.com:7001");
InitialContext context = new InitialContext(env);


// The producer and consumer need to get a connection factory and use it to set up
// a connection and a session

QueueConnectionFactory connFactory = (QueueConnectionFactory) context.lookup("AQJMS_XAConnectionFactory");
QueueConnection conn = connFactory.createQueueConnection();
// This session is not transacted, and it uses automatic message acknowledgement
QueueSession session = conn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue q = (Queue) context.lookup("jms/JMSDEMO_QUEUE1");
// Sender
QueueSender sender = session.createSender(q);
// Text message
TextMessage msg = session.createTextMessage();
msg.setText("Hello Test123");
System.out.println("Sending the message: "+msg.getText());
sender.send(msg);

session.close();
conn.close();
}
}


Program for Receving the Message


package webserv1;

import java.util.Hashtable;

import javax.jms.Message;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueReceiver;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.Session;
import javax.jms.TextMessage;

import javax.naming.Context;
import javax.naming.InitialContext;

public class RecvMsgQueue {
public RecvMsgQueue() {
super();
}

public static void main(String argv[]) throws Exception {

Hashtable env = new Hashtable();
// Standalone OC4J connection details
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "welcome1");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
// env.put(Context.PROVIDER_URL, "t3://ceiacb5.us.oracle.com:7001");
InitialContext context = new InitialContext(env);

// The producer and consumer need to get a connection factory and use it to set up
// a connection and a session

// QueueConnectionFactory connFactory = (QueueConnectionFactory) context.lookup("jms/oc4jQueueConnFactory");
QueueConnectionFactory connFactory =(QueueConnectionFactory) context.lookup("AQJMS_XAConnectionFactory");


QueueConnection conn = connFactory.createQueueConnection();
// This session is not transacted, and it uses automatic message acknowledgement
QueueSession session = conn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);

Queue q = (Queue) context.lookup("jms/JMSDEMO_QUEUE1");
// Queue q = (Queue) context.lookup("jms/oc4jQueue");
/* // Sender
QueueSender sender = session.createSender(q);
// Text message
TextMessage msg = session.createTextMessage();
msg.setText("Hello there!");
System.out.println("Sending the message: "+msg.getText());
sender.send(msg);

*/
// Receiver
QueueReceiver receiver = session.createReceiver(q);
conn.start();
Message m = receiver.receive();
if(m instanceof TextMessage) {
TextMessage txt = (TextMessage) m;
System.out.println("Message Received: "+txt.getText());
}
session.close();
conn.close();
}
}

Monday, June 20, 2011

How to Install multiple Linux Distributions in the same Machine

My requirement is to have the following OS's in my computer.

Windows 7
Redhat Linux 4
Oracle Enterprise Linux 5


First install Windows 7.

Using Windows 7 Disk Manager, create 3 partitions
say
hda5 => 50 GB (For RedHat Linux)
hda6 => 6 GB (For the Swap , we can use the same Swap for other linux install also)
hda7 => 50GB ((For Oracle Linux)

Now this install Redhat Linux 5 , select the root(/) partition as hda5
and swap as hda6. In the install screen please select the option to install the grub.

Now install Oracle Linux 5 , here select the root(/) partition as hda7
and swap as hda6.

In the install do not choose to install the grub option as you already have grub installed
by the first install.

Now Boot the machine in to Redhat Linux and mount the hda7 partition.

mount /dev/hda7 /test

Find out the files under the directory /test/boot directory ,

ls vm* init*

initrd-2.6.18-194.el5.img     vmlinuz-2.6.18-194.el5
initrd-2.6.18-194.el5PAE.img  vmlinuz-2.6.18-194.el5PAE

Now edit the /etc/grub.cong file and add the following entries

title Enterprise Linux (2.6.18-194.el5PAE)
        root (hd0,7)
        kernel /boot/vmlinuz-2.6.18-194.el5PAE ro root=LABEL=/ rhgb quiet
        initrd /boot/initrd-2.6.18-194.el5PAE.img
title Enterprise Linux-base (2.6.18-194.el5)
        root (hd0,7)
        kernel /boot/vmlinuz-2.6.18-194.el5 ro root=LABEL=/ rhgb quiet
        initrd /boot/initrd-2.6.18-194.el5.img

After this restart the machine and now you will see OEL , Windows 7 and Redhat in the grub boot screen.

Saturday, June 18, 2011

Changing the SOA Suite database Username etc in 10g

Changing the SOA Suite database Username etc in 10g

SOA 10g by default installs to orabpel and oraesb user. In a testing environment you may want to create more then one SOA 10g instance in one db. This procedure explains how to do that

1. First run the irca to create the necessary schemas.

./irca.sh all "xxxx.xxx.oracle.com 1521 xxx.xxx.oracle.com" welcome1 -overwrite ORABPEL welcome1  ORAESB welcome1 ORAWSM welcome1

Then run irca gaian with a different username's for example ORABPEL_OracleAS_3 , ORAESB_OracleAS_3 and ORAWSM_OracleAS_3.

./irca.sh all "xxx.xxx.oracle.com 1521 xxx.xxx.oracle.com" welcome1 -overwrite ORABPEL_OracleAS_3 welcome1  ORAESB_OracleAS_3 welcome1 ORAWSM_OracleAS_3 welcome1

2. Install the SOA Suite normally. SOA Suite 10g by default install in the orabpel and oraesb schema's only.

3. Now open the ${SOA_HOME}\j2ee\home\config\data-sources.xml file ,

and change the username and password etc for the data-sources. You can also use the EM Application Server control
for this purpose.


4.  From the ${SOA_HOME}\bpel\install\extensions directory, copy the following files to ${SOA_HOME}\bpel\domains\default\deploy:

    bpel_TaskActionHandler_1.0.jar
    bpel_TaskManager_1.0.jar

5. Connect to the oraesb schema  and run the following sql script ,

SQL> spool params.sql
SQL> SELECT 'INSERT INTO esb_parameter VALUES (''' || param_name || ''', ''' || param_value || ''');' FROM esb_parameter;
SQL> spool off
SQL> quit

Take the params.sql file and run it against the schema ORAESB_OracleAS_3.


6. Now apply the latest SOA 10g patch set ,
and run the schema upgrade scripts on the new schemans i.e ORABPEL_OracleAS_3 , ORAESB_OracleAS_3

If your SOA Suite is 10.1.3.3 or later, you will have to also run an additional script that updates the BPEL schema. This is documented in the install guides for each version, but in summary, the script is:

    ${SOA_HOME}\bpel\system\database\scripts\upgrade_10131_10135_oracle.sql


7. For OWSM open the file ,
${SOA_HOME}\owsm\bin\install_properties

Scroll down to the section that contains the install.db.* properties. After backing up the existing settings, modify them for your environment:

    install.db.type=oracle
    install.db.driver.type=thin
    install.db.host=localhost
    install.db.port=1521
    install.db.name=xe
    install.db.userid=oraowsm_OracleAS_1
    install.db.password=oraowsm

8. Run the command ,

${SOA_HOME}\owsm\bin\wsmadmin.bat install

9. Restart all the oc4j containers and check whether every thing is working fine or not.

Saturday, June 11, 2011

How to Add Shared Folders in VmWare Player

First Install the VMWare tools on the Guest OS.

With out the vmware tools the sharing feature may not work.

Launch VMWare Player. Confirm that the virtual machine that you want to modify the settings for it powered off, then right click it and click "Edit VM."

Click the "Options" tab on the top of the window, then click the "Shared Folders" category below.

Click the radio button labeled "Enabled." And add the directories you want to share.

Thursday, June 09, 2011

Search Oracle Forums

http://myforums.oracle.com/jive3/forum.jspa?forumID=3150 (integration_ww@oracle.com)
http://myforums.oracle.com/jive3/forum.jspa?forumID=3209 (helpwls_ww@oracle.com)
http://myforums.oracle.com/jive3/forum.jspa?forumID=3213 OC4J (helpj2ee_us@oracle.com)
http://myforums.oracle.com/jive3/forum.jspa?forumID=3208 Oracle Application Server (helpias_us@oracle.com)

SOA PS3 Purging Scripts With the Debug Option

spool soainfra_purge_n2_output3.txt
set serveroutput on
set pages 1000
ALTER PROCEDURE debug_purge  COMPILE PLSQL_CCFLAGS = 'debug_on:TRUE' REUSE SETTINGS;
ALTER PROCEDURE log_info COMPILE PLSQL_CCFLAGS = 'debug_on:TRUE' REUSE SETTINGS;

DECLARE

   MAX_CREATION_DATE timestamp;
   MIN_CREATION_DATE timestamp;
   batch_size integer;
   max_runtime integer;
   retention_period timestamp;

BEGIN

   MIN_CREATION_DATE := to_timestamp('2011-02-01 10:00:00','YYYY-MM-DD HH24:MI:SS');
  MAX_CREATION_DATE := to_timestamp('2011-07-08 09:00:00','YYYY-MM-DD HH24:MI:SS');
  max_runtime := 60;
   retention_period := to_timestamp('2011-07-08','YYYY-MM-DD');
    --batch_size := 10000;
    batch_size := 100000;
      soa.delete_instances(
      min_creation_date => MIN_CREATION_DATE,
      max_creation_date => MAX_CREATION_DATE,
      batch_size => batch_size,
      max_runtime => max_runtime,
      retention_period => retention_period,
      purge_partitioned_component => false);
   END;
   /

ALTER PROCEDURE debug_purge COMPILE PLSQL_CCFLAGS = 'debug_on:false' REUSE SETTINGS;
ALTER PROCEDURE log_info COMPILE PLSQL_CCFLAGS = 'debug_on:false' REUSE SETTINGS;
spool off

How to add swap space in linux

http://www.thegeekstuff.com/2010/08/how-to-add-swap-space/

 

dd if=/dev/zero of=/extraswap bs=1M count=512
mkswap /extraswap
cp /etc/fstab /etc/fstab.mybackup
Add this line at the end of the file
/extraswap   none   swap   sw   0   0
or
swapon /extraswap

Verify whether the newly created swap area is available for your use.
swapon -s

Tuesday, June 07, 2011

Create RAC Instance using Oracle VM

First Install the Oracle VM Server on a new machine.

On Some other linux machine (or an vmware instance) install the Oracle VM manager.

Extract the Oracle VM manager zip file and mount the iso file on a unix machine.
Install the Oracle VM manager by running the command ,
sh runInstaller.sh 

The Oracle VM manager asks a series of questions like db connect info etc
after this it will install Oracle XE and OC4J etc. If you have an existing DB you can use that
database instead of XE.

On the Oracle VM Server , create a HDD partion say about 100GB in /dev/sdb6
(ensure that you have atleast you have 80GB partition else the RAC install will fail)

and run the following commands to create the storage repository ,

mkfs.ext3 /dev/sdb6
/opt/ovs-agent-2.3/utils/repos.py -n /dev/sdb6
/opt/ovs-agent-2.3/utils/repos.py -i
/opt/ovs-agent-2.3/utils/repos.py -l
/opt/ovs-agent-2.3/utils/repos.py -r 90ab429e-a00f-488d-9680-91dd878e3f48

Output of the above commands ,

[root@oraclevm ~]# /opt/ovs-agent-2.3/utils/repos.py -n /dev/sdb6
[ NEW ] 90ab429e-a00f-488d-9680-91dd878e3f48 => /dev/sdb6
[root@oraclevm ~]# /opt/ovs-agent-2.3/utils/repos.py -i
*** Storage repositories initialized.
[root@oraclevm ~]# /opt/ovs-agent-2.3/utils/repos.py -l
[   ] 90ab429e-a00f-488d-9680-91dd878e3f48 => /dev/sdb6
[root@oraclevm ~]# /opt/ovs-agent-2.3/utils/repos.py -r 90ab429e-a00f-488d-9680-91dd878e3f48
[ R ] 90ab429e-a00f-488d-9680-91dd878e3f48 => /dev/sdb6

In the VM manager create a server pool and assign the Oracle VM Server to this pool.

Copy the RAC Vmware template file to /OVS/seed_pool and extract the file ,

After this run the following commands ,

# cd /OVS/seed_pool
# unzip -q /tmp/OVM_EL5U5_X86_11107RAC_PVM.zip
# tar xzf OVM_EL5U5_X86_11107RAC_PVM.tgz (or X86_64 for the 64-bit version)
(You may now delete the ZIP & TGZ files)
This will create the following, e.g.on 32bit:
/OVS/seed_pool/OVM_EL5U5_X86_11107RAC_PVM (or X86_64 for the 64-bit version)
|- System.img (OS image file)
|- Oracle11107RAC_x86-xvdb.img (database software image file)
|- vm.cfg (VM configuration file)
|- README
|- These PDF documents
|- lsinventory-sample.crs-32bit lsinventory-sample.rac-asm-32bit (or 64bit)

Now create 5 shared disks i.e say ASM1 to ASM5 each of 2GB.

Import the template using Oracle VM manager

Create 2 Virtual Machines using the imported template

Add the shared disks in the exact same order to both VMs.

Power ON both virtual machines

Complete the boot interview questions like private IP , public IP , VIP IP and hostnames etc.
For the private IP use 10.10.10.201 ,

If you have only one network card then use eth0:1 for the private interface.


Now Install Oracle RAC
First login as root user , (password is ovsroot) and run the command ,
cd /u01/clone/buildcluster.sh

This will install the RAC software.

For the command line tools , please download the following rpm’s

wget http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/oracle_addons/x86_64/ovmcli-2.2-9.el5.noarch.rpm

wget http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/addons/x86_64/python-ZSI-2.1-a1.el5.noarch.rpm

Run the command to configure the ovm client

ovm config

run the command ,

ovm -u admin -p welcome1 vm ls
Name    Size(MB) Mem  VCPUs Status  Server_Pool
fmwrac1 29086    1400 1     Running oraclevm1_test
fmwrac2 29086    1400 1     Running oraclevm1_test

Thursday, April 21, 2011

How to Redirect weblogic stdout to a log file

By configuring one option in the Admin console of weblogic
Server -> Admin server (or the Managed Server) -> Logging -> General -> Advanced Settings -> Redirect stdout logging enabled


or using JAVA_OPTIONS -Dweblogic.log.RedirectStdoutToServerLogEnabled=true

Thursday, March 31, 2011

How to apply WebLogic Private Patch

Patch Identifier: HJ5X
Passcode: I23H9PRN

1) First download the patch using the Smart Update tool (BSU):
    a) Launch Smart Update (BSU) as follows:
        -cd <MW_HOME>/utils/bsu where MW_HOME is location of 10.3.3 Install
        -Enter "bsu.sh" (for Unix/Linux) or "bsu.cmd" (for Windows)
    b) Login using your "My Oracle Support" account and password.
    c) If the 'Target Installation' (on left menu) is not correct then:
        - From menu bar, go to 'File -> Target Installation -> Find Other BEA Home'
        - Then choose the BEA Home for WebLogic 10.3.3
    d) Go to 'Get Patches' tab
    e) From menu bar, choose Patches -> Retrieve Private
    f) Enter the following:
          Patch Identifier: HJ5X
          Passcode: I23H9PRN
    g) Choose option to check for patch conflicts
    h) Patch will then be downloaded. The information is downloaded to these two files:
         i. <MW_HOME>/utils/bsu/cache_dir/HJ5X.jar
        ii. <MW_HOME>/utils/bsu/cache_dir/patch-catalog.xml

2) Next install the patch. There are two options for installing patch:
    Option 1: Install the patch using 'online mode' (this is the preferable option if you can run SmartUpdate Online, in the environment where you are applying patch)
    Option 2: Apply the patch in 'offline mode' (use this option in environments where you can't run SmartUpdate online due to firewall restrictions)

Below are instructions for 'Option 1' and 'Option 2'

Instructions for Option 1 (Smart Update Online)
-------------------------------------------------------------------------
a) If you aren't already logged into SmartUpdate, then log in using steps 1a through 1c (above)
b) Go to 'Manage Patches' tab
c) You will see the Patch 1Y9I in the 'Downloaded Patches' window (at bottom of page)
d) Click the'Apply' button next to the patch and it will be installed.

Instructions for Option 2 (Smart Update Offline)
------------------------------------------------------------------------------
a) Copy the files (that you downloaded in step 1) to the WebLogic environment where you are applying the patch.
    For example, if you downloaded the patch to MW_HOME1 but want to apply it to MW_HOME2, then do the following:
      i. copy <MW_HOME1>/utils/bsu/cache_dir/HJ5X.jar to <MW_HOME2>/utils/bsu/cache_dir/HJ5X.jar
     ii. copy <MW_HOME1>/utils/bsu/cache_dir/patch-catalog.xml to <MW_HOME2>/utils/bsu/cache_dir/patch-catalog.xml
b) Go to your <MW_HOME2>\utils\bsu and launch bsu.cmd (or bsu.sh)
c) When prompted for your Support ID, click the 'Work Offline' button
d) You will see the Patch HJ5X in the 'Downloaded Patches' window (at bottom of page)
e) Click the'Apply' button next to the patch and it will be installed.

To check whether the patch has been applied or not , start the weblogic server you will see the entry as

<Version: WebLogic Server Temporary Patch for 9833357 Fri Aug 13 13:14:52 EDT 2010
WebLogic Server 10.3.3.0  Fri Apr 9 00:05:28 PDT 2010 1321401 >

Wednesday, March 16, 2011

Sunday, March 13, 2011

How to enable JDBC SQL Statement Tracing in OC4J

Take a backup of ojdbc14.jar and  ojdbc14dms.jar files.

cd ORACLE_HOME\jdbc\lib

copy ojdbc14.jar ojdbc14.jar.org
copy  ojdbc14dms.jar ojdbc14dms.jar.org

Replace the  JDBC jar files with the JDBC log files
copy ojdbc14dms_g.jar ojdbc14dms.jar
copy ojdbc14_g.jar ojdbc14.jar

In the opmn.xml add the following values to the opmn.xml file
-Doracle.jdbc.Trace=true -Djava.util.logging.config.file=c:/temp/OracleLog.properties
 
 
For example ,

<process-type id="oc4j_soa" module-id="OC4J" status="enabled">
               <module-data>
                  <category id="start-parameters">
<data id="java-options" value=" -Doracle.jdbc.Trace=true -Djava.util.logging.config.file=c:/temp/OracleLog.properties   -Xrs -server -XX:MaxPermSize=128M -ms512M -mx1024M -XX:AppendRatio=3 -Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Doraesb.home=d:\soa1013\integration\esb -Dhttp.proxySet=false -Doc4j.userThreads=true -Doracle.mdb.fastUndeploy=60 -Doc4j.formauth.redirect=true -Djava.net.preferIPv4Stack=true -Dorabpel.home=d:\soa1013\bpel -Xbootclasspath^/p:d:\soa1013\bpel/lib/orabpel-boot.jar -Dhttp.proxySet=false"/>                  </category>
                  <category id="stop-parameters">
         

Sample OracleLog.properties  file
==================================

#### Console Handler ######

#java.util.logging.ConsoleHandler.level = ALL
#java.util.logging.ConsoleHandler.formatter =
#java.util.logging.SimpleFormatter
#handlers = java.util.logging.ConsoleHandler

#### File  Handler ######

oracle.jdbc.handlers=java.util.logging.FileHandler
java.util.logging.FileHandler.level=ALL
java.util.logging.FileHandler.pattern=c:/temp/jdbc.log
java.util.logging.FileHandler.count=1
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter

# Uncomment and/or change the levels for more detail
#oracle.jdbc.level = FINEST
#oracle.jdbc.connector.level = FINE
#oracle.jdbc.driver.level = FINEST
#oracle.jdbc.internal.level = FINEST
#oracle.jdbc.oci.level = FINE
#oracle.jdbc.oracore.level = FINE
#oracle.jdbc.pool.level = FINE
#oracle.jdbc.rowset.level = FINEST
#oracle.jdbc.util.level = FINEST
#oracle.jdbc.xa.level = FINE
#oracle.jdbc.xa.client.level = FINE
#oracle.jpub.level = FINE
#oracle.net.level = FINE
#oracle.sql.level = FINEST
#.level=CONFIG
#oracle.level=CONFIG
#oracle.jdbc.pool.level=CONFIG
#oracle.jdbc.util.level=CONFIG
#oracle.sql.level=CONFIG

#oracle.jdbc.driver.level=FINE


# This is the setting needed for sql debug
oracle.jdbc.driver.level=FINE
oracle.level=OFF

oracle.level=OFF
#oracle.jdbc.driver.level=CONFIG
#oracle.sql.level = FINEST


#set JAVA_OPTIONS=-Doracle.jdbc.Trace=true  -Djava.util.logging.config.file=c:/temp/OracleLog.properties

Saturday, March 12, 2011

How to use the JDBC Driver Tracing in Weblogic/SOA 11g to capture the sql statements issued by the JDBC Drivers

Before starting the weblogic server set the following environment variables ,

On Windows

set EXT_PRE_CLASSPATH=C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\oracle\11g\ojdbc6_g.jar
set JAVA_OPTIONS=-Doracle.jdbc.Trace=true -Djava.util.logging.config.file=c:/temp/OracleLog.properties 

On Unix

set EXT_PRE_CLASSPATH=/home/oracle/Middleware/wlserver_10.3/server/ext/jdbc/oracle/11g/ojdbc6_g.jar
set JAVA_OPTIONS=-Doracle.jdbc.Trace=true -Djava.util.logging.config.file=/tmp/OracleLog.properties 


In the OracleLog.properties have the following entries ,

#### Console Handler ######

#java.util.logging.ConsoleHandler.level = ALL
#java.util.logging.ConsoleHandler.formatter =
#java.util.logging.SimpleFormatter
#handlers = java.util.logging.ConsoleHandler

#### File  Handler ######

oracle.jdbc.handlers=java.util.logging.FileHandler
java.util.logging.FileHandler.level=ALL
java.util.logging.FileHandler.pattern=c:/temp/jdbc.log
java.util.logging.FileHandler.count=1
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter

# Uncomment and/or change the levels for more detail
#oracle.jdbc.level = FINEST
#oracle.jdbc.connector.level = FINE
#oracle.jdbc.driver.level = FINEST
#oracle.jdbc.internal.level = FINEST
#oracle.jdbc.oci.level = FINE
#oracle.jdbc.oracore.level = FINE
#oracle.jdbc.pool.level = FINE
#oracle.jdbc.rowset.level = FINEST
#oracle.jdbc.util.level = FINEST
#oracle.jdbc.xa.level = FINE
#oracle.jdbc.xa.client.level = FINE
#oracle.jpub.level = FINE
#oracle.net.level = FINE
#oracle.sql.level = FINEST
#.level=CONFIG
#oracle.level=CONFIG
#oracle.jdbc.pool.level=CONFIG
#oracle.jdbc.util.level=CONFIG
#oracle.sql.level=CONFIG

#oracle.jdbc.driver.level=FINE


# This is the setting needed for sql debug
oracle.jdbc.driver.level=FINE
oracle.level=OFF

 

TRACE_1: Public Enter: "DELETE FROM MDS_LABELS WHERE LABEL_NAME = ? AND LABEL_PARTITION_ID =?"
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.PhysicalConnection prepareStatement
TRACE_1: return: oracle.jdbc.driver.OraclePreparedStatementWrapper@1d56ac0
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.PhysicalConnection prepareStatement
TRACE_1: Exit
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OracleStatement setPoolable
TRACE_1: Public Enter: true
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OracleStatement setPoolable
TRACE_1: Exit
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setString
TRACE_1: Public Enter: 1, "preDeployLabel_soa-infra"
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setString
TRACE_1: Exit
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setLong
TRACE_1: Public Enter: 2, 1
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setLong
TRACE_1: Exit
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement executeUpdate
lTRACE_1: Public Enter:
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OracleStatement doExecuteWithTimeout
CONFIG: SQL: DELETE FROM MDS_LABELS WHERE LABEL_NAME = ? AND LABEL_PARTITION_ID =?

The sql statement is "DELETE FROM MDS_LABELS WHERE LABEL_NAME = ? AND LABEL_PARTITION_ID =?"
The bind variales are "preDeployLabel_soa-infra" and 1.
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setString
TRACE_1: Public Enter: 1, "preDeployLabel_soa-infra"
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setLong
TRACE_1: Public Enter: 2, 1

The sql statement is "DELETE FROM MDS_LABELS WHERE LABEL_NAME = 'preDeployLabel_soa-infra' AND LABEL_PARTITION_ID =1"

Another example ,

TRACE_1: Public Enter: "SELECT PARTITION_ID FROM MDS_PARTITIONS WHERE PARTITION_NAME=?"

Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setString
TRACE_1: Public Enter: 1, "soa-infra"
Mar 12, 2011 10:18:10 PM oracle.jdbc.driver.OraclePreparedStatement setString

The sql statement is "SELECT PARTITION_ID FROM MDS_PARTITIONS WHERE PARTITION_NAME='soa-infra'


If you want only the sql statements with out bind variables use
oracle.jdbc.driver.level=CONFIG

This displays the sql statemnets as

CONFIG: 13EEB53C SQL: update  MEDIATOR_CASE_INSTANCE  set  STATUS ='locked',  LOCK_TIME =?,  CONTAINER_ID =? where  STATUS  = 'ready' and rownum < ?
CONFIG: 466208C SQL: SELECT CASE_ID, CONTAINER_ID, MSG_ID, OPERATION, COMPONENT_DN, PRIORITY, LOCK_TIME, QNAME_LOCAL_PART, IS_EVENT, QNAME_NAMESPACE, CASE_INFO, SOURCE_URI, COMPONENT_STATUS, INSTANCE_CREATED, CREATION_DATE, STATUS, DUMMY1 FROM MEDIATOR_DEFERRED_MESSAGE WHERE (((STATUS = ?) AND (LOCK_TIME = ?)) AND (CONTAINER_ID = ?))

Saturday, March 05, 2011

OPatch on Windows 7 fails with the error OPATCH_JAVA_ERROR: Wrong number of arguments

"Opatch apply" went smooth till verify patch and then exit with following error description:

"OPATCH_JAVA_ERROR: Wrong number of arguments. VerifyPatch needs ORACLE_HOME, OUI location, patch location, patch I
Exception in thread "main" java.lang.Exception: Wrong number of arguments. VerifyPatch needs ORACLE_HOME, OUI location, patch location, patch ID and path to 'ar' command, no_inventory, OS_ID.

at opatch.VerifyPatch.main

Verification of the patch failed.
ERROR: OPatch failed as verification of the patch failed.

Even rolling back a patch is failing.

The OS_ID is retruning as "0" , that was the main reason why it is failing on Windows 7.


Please set the environment variable

set OPATCH_PLATFORM_ID=233 and run the opatch apply command.

Friday, March 04, 2011

How to use different JDBC drivers with SOA 10g

Please refer to the following note for the certification information on the jdbc drivers with OAS 10.1.3.

JDBC Driver Support for Oracle Application Server (Fusion Middleware) (Doc ID 365120.1)

Couple of points ,

Please note that we can use only thin drivers. Please also note that replacing the shipped JDBC drivers with the new ones are not supported. We have to use the application library support
feature available in 10.1.3.x versions.

How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container (Doc ID 420303.1)


The procedure given below should help you in configuring the 11g JDBC thin drivers with OAS 10.1.3. Please also refer to the BUG 8726607 - 10.1.3.5 CERT WITH 11G JDBC DRIVERS : EXTRA STEPS TO NOTE 420303.1

1. Within each container, create the following directory to host the
shared library:

  $OH/j2ee/<container>/shared-lib/oracle.jdbc/11.1.0.7
2. From the Oracle Database 11g installation, copy the following files
into the newly created directory above:

   $OH/rdbms/jlib/aqapi.jar
   $OH/jdbc/lib/ojdbc5.jar *
   $OH/oc4j/j2ee/home/lib/ojms-provider.jar

ojdbc5.jar is for application server installs using JDK 5 (the
default in 10.1.3).  For installs configured to use JDK 6, copy
ojdbc6.jar instead.

3. Create the following oracle.jdbc shared-library entry in the
container $OH/j2ee/<container>/config/server.xml file with the version
attribute set to 11.1.0.7, and at the same time specify the new version
for the BPEL and ESB imported oracle.jdbc shared libraries.

- Make sure the oracle.jdbc library is defined before the oracle.bpel.common
and oracle.esb libraries.
- Replace "[$OH]" in the below example with the path to your Oracle Home
directory.

 

<application-server ?

   <shared-library name="oracle.jdbc" version="11.1.0.7">
     <code-source path="ojdbc5.jar"/>
     <code-source path="aqapi.jar"/>
     <code-source path="ojms-provider.jar"/>
      <code-source path="[$OH]/opmn/lib/ons.jar"/>
      <code-source path="[$OH]/jdbc/lib/ocrs12.jar"/>
    </shared-library>
    <shared-library name="oracle.bpel.common" ?>
     
      <import-shared-library name="oracle.jdbc"   min-version="11.1.0.7"/>
     
    </shared-library>
    <shared-library name="oracle.esb" ?>
     
      <import-shared-library name="oracle.jdbc" min-version="11.1.0.7"/>
     
    </shared-library>
 
</application-server>
 
4. Open the AppsAdapter, AqAdapter and DbAdapter config in these files:
 
$OH/j2ee/oc4j_soa/application-deployments/default/AppsAdapter/oc4j-ra.xml
$OH/j2ee/oc4j_soa/application-deployments/default/AqAdapter/oc4j-ra.xml
$OH/j2ee/oc4j_soa/application-deployments/default/DbAdapter/oc4j-ra.xml
 
Edit the config as below to specify the same minimum version of the
oracle.jdbc shared-library.
 
    <import-shared-library name="oracle.jdbc" min-version="11.1.0.7"/>
 
5. Restart the container

Monday, January 31, 2011

SOA Oracle Lite DB Tracing

SOA Uses 10.2 POLite.

Please refer to the link for more debuginfo.

Set OLITE_SQL_TRACE=TRUE in c:\windows\polite.ini file ,

The sql trace info is written to c:\windows\system32\oldb_trc.txt

OLITE_SQL_TRACE

Generates the SQL statement text, compilation time, execution plan, and the bind value.

For example:

OLITE_SQL_TRACE = TRUE


SQL trace output is dumped to a trace file named oldb_trc.txt in the current working directory of the database process. For a database service on Windows, Windows NT or the Oracle Database Lite daemon for a Linux platform, the current working directory is specified by the wdir parameter during the database startup service or daemon. Applications that use an embedded connection to connect to the database contain a working directory. This working directory is the application working directory. To implement the tracing feature, the database process must contain permissions to create the trace file in the current working directory. The trace output is always included in the trace file. If the trace file does not exist, it is created automatically.

Sunday, January 30, 2011

How to Install additional packages/upgrade OEL 5

  1. Download and Install Oracle Linux
  2. Download and copy the appropriate yum configuration file in place, by running the following commands as root:

    Oracle Linux 4, Update 6 or Newer
    # cd /etc/yum.repos.d
    # mv Oracle-Base.repo Oracle-Base.repo.disabled
    # wget http://public-yum.oracle.com/public-yum-el4.repo


    Oracle Linux 5


    # cd /etc/yum.repos.d
    # wget http://public-yum.oracle.com/public-yum-el5.repo


    Oracle VM 2


    # cd /etc/yum.repos.d
    # wget http://public-yum.oracle.com/public-yum-ovm2.repo




  3. Enable the appropriate repository by editing the yum configuration file




    • Open the yum configuration file in a text editor


    • Locate the section in the file for the repository you plan to update from, e.g. [el4_u6_base]


    • Change enabled=0 to enabled=1





  4. Begin using yum, for example:



    yum list ,  yum update  , yum install firefox





  5. You can also use  “system-config-packages” for this purpose.



Wednesday, January 26, 2011

How to setup iscsi target on OEL 5.5

http://fedoraproject.org/wiki/Scsi-target-utils_Quickstart_Guide

RedHat have included an iSCSI daemon which is also installable using yum:

yum install iscsi-initiator-utils

To connect to the target, edit /etc/iscsi/initiatorname.iscsi and change InitiatorName to something you prefer (Remember! it must be in the IQN format, iqn.yyyy-mm.{reversed domain name}:an_easy_to_remember_lablel. I usually use iqn.2009-02.com.hamzahkhan:hostname_of_box). Next start up iSCSId:

/etc/init.d/iscsid start

and use iSCSI target descovery to find the targets on the server:

iscsiadm -m discovery -t st -p $SERVERS_IP

If all is well, it should output the names of all the targets that the initiator is allowed to connect to!

Next, we need to create the disk nodes. To do this, RedHat have provided a nice start up script. This script will login to all the targets that the iSCSI daemon knows about. We have already used the iscsiadm command to tell the iSCSI daemon which targets exist on the server, so using the script is all that is left:

/etc/init.d/iscsi start

On Windows 7 use this note ,

http://www.windowsnetworking.com/articles_tutorials/Connecting-Windows-7-iSCSI-SAN.html