My Tech Lab

I was recently creating a database VM (Oracle Linux 6 Update 3 on Oracle VM) on my laptop and encountered this issue. I have created a Virtual Disk for the database of 12 GB size and when I tried to install my schema using RCU I ran out of space. Solution was to create another Virtual Disk and move the database data files (.dbf) to this new drive. After few google search and looking at the blogs these are the steps I followed: Login to the database sqlplus / as sysdba Get the data file location  select file_name from dba_data_files; Shutdown the database shutdown immediate Shutdown the listener lsnrctl stop Shutdown the VM Guest OS. Created a new Virtual Disk of 20 GB. Start the Guest OS. Mount the drive. My mount point is u02. Move the dbf files under oradata/SID folder to the new disk. You will find the oradata folder under your Oracle home. E.g. move DEV_soainfra.dbf from /u01/app/oradata/soa to /u02/app/oradata. Start the database using command startup mount...

The idea is to get all the pieces together for installling a SOA Suite 11.1.1.5 on a Oracle Linux Server 6. Although the 11.1.1.5 is not yet certified on Oracle Linux 6 still it works like wonder. I will share the details over a period of time as I install the server. Step 1: Get Hardware 1. Since the RAM requirement for 11g is quite high, I will install a linux server on my Toshiba 4GB Laptop which has a dual core. 2. JDev will be on a difrrent laptop which should have alteast 2 GB RAM. Step 2: Get Software 1. Oracle Linux Server 6 - Oracle is releasing new versions at quite a pace so will take what ever is the latest version. 2. Oracle SOA Suite - 11.1.1.5 PS4 3. Database - Oracle XE 11g beta How to mount a FAT16/FAT32 Pen Drive 1. Login as root 2. Type fdisk -l to get a list of all the drives Locate your pen drive --- Disk /dev/sdb: 4012 MB, 4012900352 bytes 120 heads, 55 sectors/track, 1187 cylinders Units = cylinders of 6600 * 512 = 3379200 bytes Sector size (logical/physical): 51...

Some of the most common issues faced while installing AIA Foundation Pack 2.5 on Oracle Application Server 10.1.3.4 1. Configuration Assistance Failed Solution: In case configuration assistance failed to complete, check the install log under AIA_HOME/logs/Install/FP and correct the issues. Then restart the configuration assistance from SOA_HOME/cfgtools/configToolFailedCommands file. It typically looks like E:\\product\10.1.3.1\OracleAS_1\jdk\bin\java.exe -jar E:\product\10.1.3.1\OracleAS_1/Infrastructure/install/lib/AIAUtils.jar -i E:\product\10.1.3.1\OracleAS_1 -nopips 2. Uninstall option is not available with FP2.5 installer Solution: To uninstall FP you need to use OUI under \Disk1\install. Browse through the Oracle Application Server > Application Integration Architecture 2.5.0.0.0.0 3. AIAReadJMSNotificationProcess compilation fails with following message: ORABPEL-01501 undefined part element. In WSDL at "http:// :8888/orabpel/default/AIAErrorTaskAdministrationProcess/AIA...

SQL> connect sys as sysdba Enter password: Connected to an idle instance. SQL> startup ORA-44412: XE edition memory parameter invalid or not specified SQL> startup pfile=C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 bytes Redo Buffers 2904064 bytes Database mounted. Database opened. SQL> create spfile from pfile='C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora'; File created. SQL> shutdown Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 byt...

bpel_synch Shared via AddThis

Enqueue Message DECLARE enqueue_options DBMS_AQ.enqueue_options_t; message_properties DBMS_AQ.message_properties_t; msg_handle RAW (16); ipmsg ip_message_type; xml_clob CLOB; msg_id NUMBER (10); subscribers DBMS_AQ.aq$_recipient_list_t; BEGIN xml_clob := ''; subscribers (1) := SYS.aq$_agent (' ' , NULL , NULL); message_properties.recipient_list := subscribers; DBMS_AQ.enqueue (queue_name => ' ' , enqueue_options => enqueue_options , message_properties => message_properties , payload => xml_clob , msgid => msg_handle); COMMIT; END; Dequeue Message DECLARE dequeue_options DBMS_AQ.dequeue_options_t; message_properties DBMS_AQ.message_properties_t; message_handle RAW (16); xml_clob CLOB; BEGIN dequeue_options.consumer_name := ' '; dequeue_options.dequeue_mode := DBMS_AQ.remove; -- Only if you want to remove message dequeue_options.navigation := DBMS_AQ.next_message; dequeue_options.WAIT := DBMS_AQ.forever; DBMS_AQ.dequeue (queue_name => ...

It's explained in the Developer Guide. The ERRBUF is the message that you return and RETCODE is the return code. These two parameters are very much required exactly in the fashion. If the RETCODE is 0 stands for Success, 1 for success with warnings and 2 for Errors. For example you have a stored procedure created as below CREATE PROCEDURE TEST_CONC(ERRBUF OUT VARCHAR2,RETCODE OUT VARCHAR2) AS BEGIN --- PROCESSS ERRBUF := 'Successful Operation'; RETCODE := '0'; EXCEPTION --- EXCEPTION HANDLING ERRBUF := 'Found Exception '; RETCODE := '2'; END;