ORA-20603: Updating timezone region of a target is not supported

Enterprise manager does not start after updating the database. The emdb.nohup has an ORA-20603: Updating timezone region of a target is not supported error message in it.

The problem

The timezones have been updated within the database.


As Oracle run:

$ORACLE_HOME/bin/emctl resetTZ agent

and follow the instructions.  You’ll need the sysman or sys password to make the changes.

Viewing Oracle Application Server JMS Queues

When developing BPEL and ESB applications it is necessary to see if the message you sent actually made it on the queue. Using Hermes is an excellent way to view an application server queues and topics.


Need to view messages on a JMS Queue or Topic that you have published a message to.



Hermes is an opensouce solution to view JMS queues. But it doesn’t come out of the box to work with Oracle Application server and OC4J. Thankfully Mike Lehmann has created some information on how to do this http://mike-lehmann.blogspot.com/2006/09/i-was-working-with-oracleas-jms-over.html
Also helpful is the provider configuration information on the hermes websitehttp://www.hermesjms.com/confluence/display/HJMS/Oracleprovided by Demed L’Her. The viewlet is especially helpful for first time users.

Changing JMS Connection Password in Oracle SOA Suite

By default the the password for eis/Jms/TopicConnectionFactory JMS Connection is welcome1. This needs to be changed if the oc4jadmin password is not set to this.


After creating an ESB process you are unable to write to a JMS topic.  The following error message is displayed in the ESB Console:

The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12133
Unable to create JMS connection due to JMS exception.
Please examine the log file to determine the problem.
 [Caused by: JMSServer[soasuite01.markcallen.com:12601]: failed to authenticate "oc4jadmin/welcome1" via "[JAZNUserAdaptor: user=oc4jadmin]".]



The password for the TopicConnectionFactory needs to be changed.

Go to the SOA Suite Enterprise Manager:


  • Click on the Home JVM
  • Click on the Applications tab
  • Select Standalone Applications from the View drop down list
  • Click on the JMSAdapter link
  • Click on the Connection Factories tab
  • Click on eis/JMS/TopicConnectionFactory
  • Change the password to the SOA Suites oc4jadmin password.
  • Press the Apply button.

Try the ESB process again.

Installing Cygwin for Windows XP

Instructions on how to install Cygwin on Windows XP, setup ssh and create a shortcut for rxvt.


Download setup.exe from http://www.cygwin.com/


Run setup.exe

The basic tools required are:

  • openssh
  • rxvt

Other packages will also be installed in order to support these.

Click Here to view a movie on how to do this.


Run cygwin. Click Here to see how to make sure cygwin and rxvt are install and running correctly.

Create a public/private key

Create a public/private key for use with ssh. Click Here to see how to generate a public rsa key. Place the key in the authorized_keys file on the servers you access.

See Setting up sshd for Public Key Authentication for more information on how to setup sshd.

Create a short cut for rxvt

Create a desktop short cut for rxvt using the following parameters:

C:\cygwin\bin\rxvt.exe -geometry 120×40 -bg ivory -fg black -fn “courier-12” -sl 2000 -sr -title rxvt -e bash –login -i

Click Here to see how to create the shortcut.

Setting up VMware Server on Linux

Instructions on how to setup VMware server on linux and access it from a windows machine.


Download VMware server rpm for Linux from http://www.vmware.com and register for a free serial number.  The current version is 1.0.3.

Setup access to the server. See Installing Cygwin for Windows XP for instructions on how to setup access to the linux server.


Log into the linux server

ssh linux01
cd /media/usbdisk/source/vmware/server/linux/1.0.3

Install the RPM

rpm -ivh VMware-server-1.0.3-44356.i386.rpm

Configure VMware

As root run:


Accept the End User License.
Accept the default directory for mime type icon.
Accept the default desktop menu entry files
Accept the default for application's icons
Networking for Virtual Machines: yes
Ethernet network: eth0
NAT networking: yes
Probe for private subnet: yes
Host-only network: yes
Probe for private subnet: yes
Accept default for remote console connections
Accept default direction for virtual machine files
Enter the VMware serial number you received when you downloaded vmware server.

Verify that vmware will startup when the server reboots.  As root run:

/sbin/chkconfig --list vmware
vmware          0:off   1:off   2:on    3:on    4:off   5:on    6:off

Install VMware Console on Windows

Download VMware console for windows from http://www.vmware.com

On the windows workstation install the server:

Double click on VMware-console-1.0.3-44356.exe
Accept the End User Agreement.
Accept the default installation location.

Configure the Console

Double click on the VMware Server Console icon on the windows desktop.

In the Connect to Host dialog box enter the hostname, username and password.

ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

The database trying to be connected to is not running. Ensure the Oracle database is running and that the TNS entry you are using is correct.


Start the Oracle Database


Windows start the OracleServiceXE service.

Linux login as oracle and run dbstart.


Test TNS

To test TNS run tnsping on the command line and give it the TNS name you are trying to use:


tnsping <tns name>




Oracle XE Tuning

Oracle XE is an excellent starter database, but under normal loads the out of the box parameters need to be increased.

Database Sessions

Increase the number of sessions that the database can handle at one time.  This will allow for more users to access the database.

sqlplus /nolog
SQL> show parameters sessions
SQL> alter system set sessions=250 scope=spfile;

restart the database.


Database Processes

Increase the number of database processes that can be running at one time.  This will allow for more users to connect to the database.

sqlplus /nolog
SQL> show parameters processes
SQL> alter system set processes=200 scope=spfile;

restart the database.